PROCESS

Five stages. The same five, every time.

This is what actually happens between "yes" and "launched" — not a marketing diagram, the real sequence every project runs through.

Start a project

  1. Discovery

    We map the problem, the constraints and the workflow with you, then put a scope, a timeline and a price in writing. Nothing starts until you've agreed to all three.

  2. Design

    Wireframes for the core flows, then high-fidelity screens where the project calls for them. You review before we build, not after.

  3. Build

    Weekly demos against a real staging link. You watch the thing get built; you don't wait six weeks for a reveal.

  4. Launch

    Deployed, monitored, and handed over — full source code and credentials. It's yours the moment it ships.

  5. Run

    Optional ongoing support once it's live: fixes, iteration, or a retainer. Never mandatory, always available if you want it.

We start with a call, but the deliverable isn't a proposal PDF — it's a written scope document you can hold us to. For fixed-price packages, discovery is often the package itself.

You'll know the price and the timeline before any build work starts — every time, no exceptions.

For product work, this means wireframes for the core user flows first, validated before visual design starts. For a marketing or landing site, it means the layout and copy structure agreed before final visual polish.

Design happens in Figma, reviewed with you at each checkpoint — never delivered as a single "big reveal."

The build phase runs on weekly demos against a staging environment you can click through yourself — not a status email. If something needs to change, we catch it in week two, not at handover.

No black-box sprints. If you want to check progress on a Tuesday, there's a real link to look at.

Launch includes deployment, a final round of cross-browser/device testing, and monitoring set up so issues surface before your users report them. A 30-day fix window covers anything real usage turns up.

You get the source code, the credentials, and a short walkthrough — the full handover, not a locked platform.

Not every project needs ongoing support — some are genuinely done at launch. For the ones that aren't, retainer options exist for iteration, maintenance, or managed infrastructure.

Nothing here auto-renews into a surprise. Retainer terms are the terms you signed at kickoff.

What you get at each stage

  • Discovery: a written scope document, a fixed price, a fixed timeline
  • Design: wireframes or high-fidelity screens, reviewed with you before build starts
  • Build: weekly demo access to a staging environment
  • Launch: full source code, deployment credentials, a walkthrough call, 30 days of fix coverage
  • Run (optional): a documented retainer agreement with a defined scope and notice period

Frequently asked questions

01 How long does discovery actually take?
For a fixed-price package (an Audit, a Sprint, a Blueprint), discovery *is* the package — it's usually 1–2 weeks. For a larger bespoke engagement, discovery typically runs 1–2 weeks before a build price is confirmed in writing.
02 What if the scope needs to change mid-build?
It happens. Any change is documented and priced in writing before it's actioned — we don't silently absorb scope creep, and we don't spring a surprise invoice either.
03 Do we get to see progress during the build, or only at the end?
Weekly, via a staging link you can click through yourself, not just a status update email.
04 What happens if we're not happy with the design direction?
You review and sign off at each design checkpoint before build starts — that's specifically what the checkpoint is for. If it's not right, we revise before code gets written, not after.
05 Who owns the code and the credentials after launch?
You do, entirely, from the moment of handover — full source, full access, no locked platform.

Ready to start?

Tell us what you're building. We'll reply within one business day.

Start a project