How I work
Listen. Map. Build. Hand over.
The same four steps whether the fix is a folder structure, a website or a camera. The thinking is the work. The build is the easy part.
Listen
A free 45-minute call. You walk me through how the work actually happens, not how it's supposed to. I ask to see the last one you did, what breaks, and who feels it when it does.
You get
A clear read on whether this is a job I should do. If it isn't, I'll say so on the call and point you somewhere better.
Takes
One call.
Map
I write down what you told me: the steps in order, where the information lives, where the time leaks, and the decisions that should stay yours. You read it and correct it.
You get
A written map of your process you can keep whether or not we go further, and a fixed quote for the build.
Takes
A few days to a week.
Build
The scope is fixed before I start. I build in the open, with a preview you can look at as it comes together, and I stop to ask when something needs your judgement.
You get
The working thing, tested on a real example from your business, not a demo.
Takes
Two to six weeks depending on scope. You'll know before we start.
Hand over
I hand you the files, the accounts and a plain-English guide written for whoever will look after it. Then I step back.
You get
Ownership. The repo, the folders, the logins, the guide. If you want me to keep it running, that's a separate, simple arrangement.
Takes
Half a day.
What you own at the end
Everything.
- The files and folders, in plain formats you can open without me.
- The code, in a repository under your account.
- The domain, hosting and email accounts, in your name.
- A guide written for the person who comes after.
Start with the call.
No pitch. You talk, I listen, and you leave with a clearer picture of what to fix first.