Made to Ship

Process

Six weeks from kickoff to production.

Not every project fits in six weeks, and we say so at the scope stage rather than at week five. What does not change is the shape: a written scope, two-week sprints with a demo you can click, and a launch that leaves your team owning the result.

  1. Week 0

    Scope

    One working day with the people who decide. Out comes a written scope: the outcome, the screens, the data, what is explicitly out of scope, the fixed price and the dates. You sign it before anyone writes code.

  2. Weeks 1–2

    The thin slice

    One path through the whole system, end to end: database, API, screen, deploy. It is in staging by day three and demoed on the second Friday. Everything after this is depth, not discovery.

  3. Weeks 3–4

    The real workflow

    The ugly cases: the refund, the duplicate webhook, the customer who has two accounts, the export the accountant actually needs. This is the sprint where a product starts to feel finished.

  4. Week 5

    Hardening

    Authentication and payment paths tested, backups restored once on purpose, alerts wired to a human, a runbook written by the person who will be on call. Performance measured, not assumed.

  5. Week 6

    Launch

    Production, with a rollback rehearsed. Repository, infrastructure and documentation handed over in your accounts. Two weeks of support are included, then you decide whether you need us again.

Inside a sprint

What a fortnight looks like.

Mon

Plan

Forty-five minutes. What ships by Friday, what we are deliberately not doing, what we need from you and by when.

Tue–Thu

Build

Code, tests, review. A short written note each afternoon so nothing waits a week to surface.

Fri

Demo

You click it yourself, on a staging URL. Written notes follow, and the next sprint is adjusted against what you saw.

Working together

The rules we hold ourselves to.

You talk to the engineers. There is no layer of account management translating what you said into a ticket, and no weekly status call that repeats what is already written down.

Decisions are written where you can find them: scope, architecture, releases, risks. If a decision turns out wrong, it is amended in the same place, with the date — not quietly forgotten.

  • AccessA shared channel and a shared board; you see the work as we do
  • OverlapAt least four hours a day with your timezone
  • ReportingWritten, weekly, three lines: shipped, blocked, next
  • ChangeA change to scope is priced in writing before it is built
  • ExitAny sprint boundary, two weeks notice, everything handed over

Next

See the engagements.

What a discovery sprint, a build sprint and a retainer cost, and what each one is for.

Engagements & pricing