What actually happens
The homepage version of this is the short one. Here is every step between the first email and a finished job, including what you are actually holding at the end of each one, so that paying somebody technical stops being an act of faith.
A conversation
A short call or an email exchange. You tell me what the business does and what is getting in the way. No jargon, no pitch deck.
What you get: An honest answer about whether this is worth building, and whether I am the right person to build it.
You get a fixed price
I write down exactly what I will build, what it costs, and when it will be done. If the scope changes later, you hear about the cost before I start, not after.
What you get: A written scope and a fixed price, with a date on it.
I build it
You see progress as it happens rather than disappearing for six weeks. Changes along the way are normal and expected.
What you get: A working site or tool at a real address, updated as it comes together.
It goes live, and I stay reachable
I hand it over with a walkthrough. If something breaks at 9am on a Tuesday, you message me directly.
What you get: The thing live, the accounts in your name, and a walkthrough of the parts you will want to change yourself.
Afterwards, if you want it
Some businesses take the keys and run with it. Others would rather somebody kept an eye on hosting, backups and the occasional change. Either is fine, and neither is assumed.
What you get: A support plan if it earns its place, and no hard feelings if it does not.
Got something in mind?
Tell me what you are trying to do and I will tell you honestly whether I can help, what it would cost, and how long it would take. I reply within one working day.