How It Works

From call to launch

Software projects go badly for one reason: nobody agreed what was being built. So that gets settled first, in writing, before anything is made.

1. 01

   The call

   30 minutes, free

   You describe what you are trying to do. I ask the questions that usually surface the real requirement, which is often not the one people arrive with. You leave knowing whether this is a small job or a real project.

2. 02

   Scope and number

   Two to three days

   You get a written scope: what gets built, what it does, what it does not do, and one fixed price. If the honest answer is that you do not need what you asked for, that is in there too.

3. 03

   Build

   Two to eight weeks, typically

   You see it as it comes together, not at the end. Real progress on a link you can open, so surprises surface while they are still cheap to fix.

4. 04

   Handover

   Launch week

   Accounts in your name, code in your hands, and a walkthrough recorded so you are not relying on memory. Anything you should be able to change yourself, you get shown how to change.

5. 05

   After

   Your call

   Take it and run. It is yours, and it is built to be handed over. When the next thing needs building, you know where I am.