How we work

Four phases.
No surprises.

Every engagement runs through the same methodology. Each phase has defined inputs, defined outputs, weekly cadence, and a clean exit. You always know what we are working on, why, and what it will produce.

  1. Discover

    Week 0 — 20 minutes to 2 weeks

    We listen. We map your current operating state — your tools, your data flows, your team rhythm, your bottlenecks. We identify the two or three levers that, if moved, would change the most. By the end of Discover you know exactly what we recommend and what it costs. No follow-up sequences, no upsell.

    Inputs

    • 20-minute discovery call
    • Access to current data, tools, and team where helpful
    • Honest description of what is and is not working

    Outputs

    • A one-page diagnostic with the highest-leverage levers
    • Recommended engagement shape (or recommendation to engage someone else)
    • Fixed-price quote for the next phase

    What you see

    A 20-minute call. If we proceed to a paid Discovery Sprint, a 2-week diagnostic engagement (£6k) with interviews, document review, and a written recommendation memo.

    What we avoid

    We do not produce free strategy documents or deck-ware in this phase. Real diagnostic work requires access; access requires a paid scope.

  2. Architect

    Week 1 — 1 to 3 weeks

    Before any code, content, or commitment, we design the system. You see the architecture diagram, the data model, the integration points, the assumptions. You veto, suggest, or approve. We close this phase when the spec is buildable by anyone — including you, if you decide to take it elsewhere.

    Inputs

    • Signed engagement letter for the work ahead
    • Working sessions with your team
    • Existing technical documentation, if any

    Outputs

    • Architecture diagram of what we will build
    • Data model and integration map
    • Sprint plan with weekly milestones
    • Definition of done — measurable

    What you see

    Weekly working sessions. Architecture diagram in a shared workspace. A specification document you could hand to any senior engineer or marketer and they could build it.

    What we avoid

    We do not skip this phase to look fast. Architecture-led work is what survives contact with reality; vibe-led work is not.

  3. Build

    Weeks 2-12 depending on engagement

    Focused sprints. Weekly demos on a staging URL — you see the system growing in real time, not via PDF reports. Every Friday you can pause, redirect, or stop. The discipline of public progress every week is what keeps the work honest.

    Inputs

    • Approved architecture from Phase 02
    • Access to your tools (CRM, repos, cloud accounts)
    • One weekly checkpoint per discipline

    Outputs

    • Working system on a staging URL within 2 weeks
    • Weekly demos showing the system growing
    • Production deployment with monitoring
    • Full documentation and handover materials

    What you see

    A live staging URL by end of week 2. Weekly demo with the working software, content, or workflow. A Slack or Linear board where every task is visible.

    What we avoid

    We do not work in private and surprise you at month-end. Public progress means no surprises, and no surprises means the trust compounds.

  4. Scale

    Month 3 onward — ongoing retainer or clean handoff

    The system runs. We monitor it, optimise it, and iterate it against real production data. If you want us to keep operating it on a monthly retainer, we do. If you want to take it in-house at month four, we hand over cleanly with documentation and a 30-day transition. Both are valid endings.

    Inputs

    • Live system from Phase 03
    • Real production usage data
    • Your decision: extend retainer, take in-house, or end engagement cleanly

    Outputs

    • Optimisation reports tied to your business metrics
    • Feature roadmap reviewed quarterly
    • Either ongoing operating retainer OR clean handover documentation

    What you see

    Monthly business review. Real numbers tied to real outcomes. A roadmap of what to optimise next.

    What we avoid

    We do not pad retainer hours to keep them billable. If the system is running and there is nothing high-leverage to do that month, we say so and recommend reducing the retainer.

Cadence

What a typical week looks like.

Monday: async standup in your Slack or Linear. We post what we shipped last week, what is next, and what is blocked.

Wednesday: 45-minute working session with the team lead — review progress on a staging URL, decide trade-offs, surface risks.

Friday: demo. Always demoable, always deployable. You see what changed and what is coming.

Month-end: a one-page business review with the numbers, the calls we are recommending, and a forecast for the next month.

Ready to start at Discover?

Begin with a 20-minute call.

Book a Discovery Call