Skip to content
Start to finish

From your first emailto the day it ships.

The whole thing, in the order it actually happens. Three steps before any money moves, then a build in your hands every week until it is in the store, and the payment schedule written out rather than left to be asked about. Nothing here is a stage I invented to fill a page; it is what the last four projects did.

  1. 01

    A reply, within a day

    Usually the same day. If I’m mid-project I’ll say so and give you a realistic start date rather than stringing it out. You’ll always know where you stand.

  2. 02

    Questions in writing, or a call

    Usually a short list of questions by email, answered whenever suits you. If it is easier to talk it through, thirty minutes on a call instead. For a small site with a clear brief, the written answers are usually enough on their own.

  3. 03

    A written scope and a fixed quote

    What’s included, what isn’t, what it costs and when it lands. You decide from that document, not from a conversation you half remember.

That is everything that happens before you have spent anything. If the scope and the price are right, you say so, and the first week starts on the date the quote named.

How I work

You see it every week.Not a demo at the end.

  1. 01

    We agree the scope first.

    A written scope and a fixed quote before any money moves. If I don't think I'm the right person, I'll say so.

  2. 02

    You see it weekly.

    A build in your hands every week, not a demo at the end. You change direction while it is still cheap. If you would rather only have the written update, say so and that is what you get.

  3. 03

    I build it to last.

    TypeScript strict, tests on the logic that matters, error tracking wired in. Open it in a year and it still makes sense.

  4. 04

    I hand it over completely.

    The code, every account, where it is hosted and the notes on how it works, on the day it ships rather than months later.

WHAT THE WEEKS LOOK LIKEA TYPICAL MOBILE BUILD
  1. WEEK 1

    Scope, repo, environments

    A written scope, the repository in your account, CI green.

  2. WEEK 2

    Data model and auth

    First build in your hands. Installable, not a staging link. It is there to prove the thing works; the design lands across the two weeks after it.

  3. WEEK 3–4

    Core features, one build a week

    You change direction while changing direction is still cheap.

  4. WEEK 5

    Hardening

    Error tracking, tests on the logic that matters, anything an extra added.

  5. WEEK 6

    Submission and handover

    Both store reviews, then repository, accounts, deployment and docs.

Every build lands on your device. There is never a link to chase.

Not all of it is building. A stretch of it is store review, which runs at Apple’s pace rather than mine, and the rest moves at the speed you come back on each build. The projects that finish in four weeks are the ones where somebody looks at Friday’s build on Monday.

Payment

Three payments,each against something delivered.

A fixed quote in writing before anything starts, then split across the stages below and agreed with the quote itself. Nothing is charged against time, and no stage is asked for before the thing it is attached to exists.

  1. At signing

    Before any work starts, against a written scope and a fixed price. It is the only payment that buys something you cannot look at yet, which is why it is the smallest share the schedule can carry and still be worth starting.

    UNDER €1,00050%
    FROM €1,0001/3
  2. When you sign off the design

    The design is yours to approve or send back. Five working days to say which, and past that it counts as approved and the build carries on, because a project cannot stand still and spend calendar at the same time.

    UNDER €1,000–
    FROM €1,0001/3
  3. Before it goes live

    Ahead of the domain being pointed or the app being sent for review. The handover document comes with it: repository, accounts, deployment and documentation.

    UNDER €1,00050%
    FROM €1,0001/3
  • Five working days to confirm the design. No answer inside that window and it counts as approved, so an unanswered email cannot quietly become a delay you are charged for later.

  • The repository, the deployment and every account are in your name from week one. None of this schedule is leverage over work you have already paid for.

  • Store fees are yours and paid direct: €99 a year to Apple, $25 once to Google. They are not in the price and they never pass through me.

Taking on new projects

Tell me what you’re building.A written scope and a fixed quote before any money moves.

I reply to everything within one working day. If I’m not the right person for it, I’ll tell you straight away rather than three weeks in.