The four steps

4 steps
STEP 01

Scope

One call to define what ships, what it costs and when. Written down before anything is built.

STEP 02

Build

Weekly builds you can click. No month-long silence, no surprise at handover.

STEP 03

Ship

We deploy it, hand over the repository and the access, and document what matters.

STEP 04

Iterate

Stay on retainer or take it in-house. Either way the code is yours.

Why it works this way

2 causes

Most projects go wrong in the same two places. The scope was never written down, so nobody agrees what "finished" means. And the client sees nothing until the end, so the first chance to correct course is the last one.

A written scope fixes the first. Weekly builds fix the second. Neither costs you anything, and together they remove most of the risk of hiring an outside team.

  • The price is agreed before we start and does not move unless you ask for a change.
  • A change is quoted before it is built, never billed after.
  • You see working software every week, on a link you can send to anyone.
  • Handover includes the repository, the hosting and every account, in your name.

Common questions

4 questions
What do you need from us to start?

A rough idea of what you want, who it is for and when you need it. That is enough for the first call. Text, images and access we can gather as we go.

What if we want to change something mid-project?

Tell us and we quote the change before building it. You decide whether it is worth it. Nothing gets added to the invoice that you have not agreed to first.

How much of our time does it take?

One call to scope it, then roughly a short review each week. We do not need you in a standing meeting, and we do not disappear either.

What happens after launch?

Whatever you prefer. Stay on retainer, call us when you need something, or take it in-house. You hold the code and the accounts, so it is genuinely your choice.

Next step

Start with the scope call.

Send a brief. You get a scope and a price, not a discovery process.