Four phases. No surprises in the fourth.

What happens

We take the brief apart against the feature catalogue. Every requirement gets sorted into configuration, extension, or genuine build. Where something is ambiguous, we ask rather than assume — and where we assume, we write the assumption down.

You get

A written scope with the boundary drawn explicitly: what's in, what's out, what's deferred, and what we assumed. Plus an estimate you can take to whoever approves it.

We need

Access to whoever knows how the business actually works — not just how it's meant to.

What happens

Content model, features, roles, branding, and settings. This phase is mostly configuration rather than code, which is why it's fast.

You get

A working admin panel with your data model in it. Your team can log in and click around before a line of front-end code exists.

We need

Feedback in days, not weeks. This is the cheapest moment to change your mind.

Depends on scope — this is the phase your project is different in.

What happens

The part that's genuinely yours — the specific workflow, the unusual rules, the integrations, the front end. Built against an API that's already been running for a fortnight.

You get

Working software, reviewable continuously rather than at the end. Every endpoint carries its tests and its latency budget as it lands.

We need

Content and imagery. This is the single most common cause of delay, and it is never an engineering problem.

What happens

Real data, load testing, the security pass, the launch checklist. Then documentation and a handover session with whoever will operate it.

You get

A live product, operational documentation, and a team who knows how to run it. Plus a clear statement of what's ours to maintain and what's yours.

We need

The people who'll actually operate it in the handover session — not their manager taking notes.