Process

Seven days to a prototype. Thirty to a system.

Fixed scope. Fixed price. Fixed timeline. The plan below is what actually happens — not a sales pitch.

Phase 01

Prototype · 7 days

We cut the idea down to its smallest useful version, then ship it.

  1. Day 01

    Scope

    60-minute working session. We agree on the smallest version of your idea that proves the value, then create a one-page spec.

    • Goal, users, and the one scenario the prototype must handle
    • Stack chosen on the call (no fashion projects)
    • What is in scope, what is explicitly out
  2. Day 02—03

    Build

    Repo set up, infra wired, the core loop running end-to-end with placeholder data.

    • Project repo, env templates, deploy pipeline
    • Core user journey, page flow, or automation working end-to-end
    • Daily Loom showing what is alive
  3. Day 04—06

    Iterate

    You try it. We sharpen. Edge cases caught and named, with a tiny eval suite for the critical path.

    • Real data plugged in
    • Edge cases caught and named
    • Tiny eval suite for the critical path
  4. Day 07

    Ship

    Hosted, documented, demoable. Either we stop here or roll into Day 30.

    • Hosted demo link
    • Source, prompts, and configs handed over
    • 30-min review call: keep, scale, or kill

Phase 02

System · 30 days

We harden the prototype into a production system you can run for years.

  1. Week 01

    Foundation

    Auth, roles, data model, and the first integration. Everything typed end-to-end.

    • Auth and roles wired
    • Data model finalised
    • First integration live (CRM / payments / telephony)
  2. Week 02

    Depth

    Real flows for the people who will use this every day. Two more integrations as needed.

    • Workflow UIs
    • Background jobs and queues
    • Up to two more integrations
  3. Week 03

    Hardening

    Quality gates, tracing, monitoring, and the boring-but-important things that keep production systems honest — including evals when AI is in the loop.

    • Tests or evals for critical paths
    • Tracing and structured logs
    • Performance, cost, and latency monitoring where relevant
  4. Week 04

    Launch

    Deployment, documentation, handover, and two weeks of bug-fix support.

    • Production deployment and runbook
    • Documentation and handover session
    • Two weeks of post-launch bug fixes

Guarantees

No drama, by design.

Working or refunded

If the Prototype is not running by Day 7, you get a full refund. We have not had to do this yet.

You own everything

Code, prompts, evals, weights — all handed over on Day 7. No lock-in, no per-seat fees.

No surprise scope

Scope is locked on Day 1. Any addition is a separate, written change order. No silent creep.

Bring the problem. We will bring the playbook.

Tell us what you want to build on the intake form. We will reply within one business day with a scoping slot.

Start a project