Skip to content

What happens between the first call and production.

Eight steps. The same every time, so you know what comes next before it happens.

The eight steps as stations on a loop: call, quote, kickoff, weekly demos, mid-sprint checkpoint, production deploy, fix window, and the retainer, which leads back to the start. Work turns green once it is deployed.

The eight steps.

  1. A 30-minute call, or a brief.

    You tell us what you want built. We ask what we need to quote it. No NDA needed for the call; we sign one within 24 hours if you want it.

  2. A written quote in three business days.

    One price, one end date, the scope in plain language, what is out, the payment schedule and the fix window. For a Platform Sprint, a five-day Scoping Review comes first.

    The Scoping Review is $1,500 and is credited against the sprint if you sign within 30 days.

  3. Kickoff. Accounts in your name.

    Repository, cloud account, model accounts and domain are created under your organisation. We work inside them with the access you grant.

  4. Weekly demos. Week-one exit.

    You see working software every week. After the first demo you can stop, pay only the deposit, and keep everything built.

  5. Mid-sprint checkpoint.

    Half way, we show the whole system end to end against the scope. New ideas go on a visible "next" list, in writing.

  6. Production deploy.

    On your cloud account, monitored, documented, with a runbook, and used by real people with real data. A demo is a milestone. This is the finish line.

  7. Fix window, then the launch review.

    30, 60 or 90 days of fixes depending on the tier. In the last sprint week we present the "next" list as a roadmap.

  8. Continuous Build, if you want it.

    The same people on a monthly retainer with a fixed number of build days, a weekly release and a roadmap call. It starts while the fix window is still open. 30 days of notice to stop.

What we need from you.

  • One person who can make decisions.
  • About two hours a week: the demo and a few questions.
  • Access to the systems we integrate with, early.
  • Sample data, real where possible, in the first week.

How agents and the founder split the work.

  • The founder designs the architecture, writes the hard parts, and is on every call.
  • AI coding agents write most of the code, under the founder's review.
  • Every change ships with tests and passes a review gate before it reaches your repository.
  • Specialists join for the parts that need them: design, QA, security review, a second engineer.

Questions we get on the first call.

What happens after the fix window ends?

Most clients continue on a Continuous Build retainer, which starts while the fix window is still open, so there is no gap. If you stop, you keep everything and can hire anyone else to continue. There is no lock-in to break.

What does the week-one exit mean in practice?

After the first weekly demo you can stop. You pay only the signing deposit, which covers that week, and you keep everything built so far, including the repository and the accounts in your name.

What does "in production" mean to you?

Deployed on your cloud account, monitored, documented, with a runbook, and used by real people with real data. A demo is a milestone. Production is the finish line.

What do you need from us each week?

One person who can make decisions, about two hours a week for the demo and questions, access to the systems we integrate with, and sample data early. The faster the answers, the faster the build.

Book a call, or send the brief. A written price in three working days.

No NDA needed for the call. We sign one within 24 hours if you want it.