Process

From idea to paying customers.

Five phases, each with a clear purpose and a clear output. You always know what we are doing, what you will have at the end of it and what we need from you to keep moving.

  1. Phase 01

    Validate

    We test the problem and the price with real prospects before building, so the decision to spend on development rests on evidence.

    What happens

    • Write down the problem, the customer and the price you believe in
    • Interview people who have the problem about how they handle it today
    • Review the tools and workarounds they already pay for
    • Run a landing page test with a real price

    You receive

    • Interview summary and competitor teardown
    • A written go, change or stop recommendation
    • A first MVP scope if the answer is go

    We need from you

    • Your view of the problem and who has it
    • Any contacts or communities where prospects can be reached
  2. Phase 02

    Design

    We design the flows and screens for the one job the product does, and agree them with you before any building starts.

    What happens

    • Map the path a customer takes from sign-up to the first useful result
    • Sketch and then design the key screens
    • Agree what is in the first version and what waits
    • Fix the scope, milestones and quote

    You receive

    • Agreed screen designs for the core flows
    • A written scope with milestones
    • A quote with the timeline and price

    We need from you

    • Feedback on the designs, ideally from someone who will use the product
    • Your brand assets, if you have them
  3. Phase 03

    Build

    We build in short milestones and release each one to a staging version you can click through, so there is no big reveal at the end.

    What happens

    • Build the core job end to end, then the supporting parts
    • Set up accounts, billing and the admin view
    • Release each milestone to staging with a short note on what changed
    • Test the paths customers will take, including payment

    You receive

    • A working product on staging after every milestone
    • Regular written progress notes
    • A tested product ready to go live

    We need from you

    • Time to use each milestone and tell us what you think
    • Quick decisions when a question comes up
  4. Phase 04

    Launch

    Billing, hosting, analytics and the launch page go live together, on accounts in your name.

    What happens

    • Set up production hosting, backups, error tracking and uptime checks
    • Switch billing from test mode to live payments
    • Publish the launch page and turn on onboarding emails and analytics
    • Check every key path with real users once live

    You receive

    • A live product that can take payment
    • All code, accounts and access in your name
    • Documentation and a runbook

    We need from you

    • Payment, hosting and domain accounts opened in your name
    • Your business and tax details for invoices
    • Your launch list or channels, if you have them
  5. Phase 05

    Grow

    We measure usage and revenue and decide the next features with you, based on what customers do rather than what anyone guesses.

    What happens

    • Review the numbers from visit to sign-up, first use and payment
    • Talk to early customers about what is missing and what confuses them
    • Run small experiments on onboarding, pricing and messaging
    • Plan and build the next features in order of evidence

    You receive

    • A regular read-out of usage and revenue
    • A prioritised list of next features
    • Ongoing releases, fixes and updates under Build & run

    We need from you

    • Access to customer feedback and support conversations
    • A regular review meeting to agree priorities

Principles

How we work at every stage

Evidence before code

We test demand and price with real people before building, and keep testing after launch. Opinions, including ours, come second.

One job, done properly

A focused product that solves one problem well beats a broad one that solves several badly. We protect the scope.

Visible progress

You can use the product as it is built. Every milestone is something you can click through, not a status report.

Yours from the start

Code, hosting, payment accounts and customer data are in your name throughout, not handed over as a favour at the end.

Agreed in writing

Scope, timeline and price are set out in the quote before work begins, and changes are agreed in writing as they come up.

Have an idea worth testing?

Tell us the problem and who has it. We will reply with how we would validate it and what an MVP could look like.