Every decision checked before it gets expensive.

Six stages and one shared checklist, so you can always see what is agreed, what is built and what is ready to go live.

  1. 01

    Begin with a free 30-minute call.

    Bring your notes, current tools, reference links or prototype. We work out which problem the product has to solve first.

    Intro call

    30 min · video call

    Agenda
    • 1Tell the story
    • 2Sketch the build
    • 3Flag the risks

    You walk away with

    Version one list Stack direction Known risks Next step
  2. 02

    Split what ships now from what can wait.

    Accounts, payments, dashboards and integrations each land on one side of the line. Later ideas stay on the list and out of the budget.

    Sort the scope

    4 now · 3 later

    Build now

    • Sign-in and clinics
    • Booking journey
    • Deposit payments
    • Staff basics

    Later

    • Calendar sync moved from Build now
    • Practice analytics
    • Native app
  3. 03

    Map every screen and state before building.

    Every flow gets its empty, loading and error views on paper, so you catch gaps in review, before customers see them.

    Booking flow map

    4 screens · 12 states
    01

    Sign in

    emptyloadingerror
    02

    Choose slot

    emptyloadingerror
    03

    Pay deposit

    emptyloadingerror
    04

    Confirmed

    emptyloadingerror

    Choose slot, three states

    empty

    No slots this week

    Join waitlist

    loading

    error

    Slots did not load

    Retry
  4. 04

    Build in milestones you can review.

    One priority moves at a time, with preview links, test notes and any tradeoffs written down in plain language.

    Milestones

    One priority at a time
    M1

    Accounts

    M2

    Booking

    M3

    Deposits

    M4

    Staff

    Update: M2 Booking

    Open
    • Preview link is ready for your review.
    • Tradeoff: calendar sync moved to M4 to protect deposits.
    • Test notes: one error message still needs copy.
    Approve M2Add a note
  5. 05

    Payments, auth and APIs tested together.

    Payments, auth, AI, email and documents join the same flows and get tested against the messy cases before launch.

    Integrations

    0 of 4 tested
    Your product Next.js
    • AuthSupabaseOpen
    • PaymentsStripeOpen
    • AI notesOpenAIOpen
    • EmailTransactionalOpen

    Each connection is tried against awkward cases before it counts as done.

  6. 06

    Launch, then keep shipping.

    After release I keep adding screens, fixes and experiments on the same codebase at the same steady pace.

    Release notes

    Same codebase
    1. v1.2Next

      Waitlist and reminders

    2. v1.1Shipped

      Multiple clinic locations

    3. v1.0Shipped

      Launch: booking, deposits, staff view

How a project starts.

Start wherever suits you. Every project gets a clear scope, timeline and fixed quote before work begins.

01Optional · Free

Write a quick brief

Not ready to talk? Tell me what you are building. I read it and answer by email with a straight opinion.

Write a brief
02Free · 30 minutes

Walk me through it

Show me the process or prototype. Together we separate must-haves from nice-to-haves and check whether we are a good match.

Book a call
03Fixed quote

Agree the scope

I send a clear scope, timeline and fixed quote, with no obligation. Work starts once you are happy with the plan.

See pricing

Want to write first? Send a quick brief.

Answer a few questions about your product. I read every brief and reply personally by email.

Start a brief