LFH Lab Start a project
Process

Frame it, build thin, ship early, run it.

Four phases. Each one ends with something you can hold, and each one is priced on its own so you can stop after any of them. This is the same shape every product on the shelf went through.

01
1–2 weeks

Frame it

I write down the problem, the person with it, and what has to be true for this to work. You get a scope you can price and the riskiest assumption named out loud.

What you have at the end
  • A written problem statement
  • Scope and price per phase
  • The assumption I test first
02
2–4 weeks

Build thin

One real path end to end before I widen anything — real data, real auth, real deploy. Ugly and working beats broad and hypothetical.

What you have at the end
  • A running app on its own domain
  • One complete user path
  • Weekly builds you can click
03
Week 4 onward

Ship early

In front of users while it's still cheap to change. Every product on the shelf shipped before it felt ready, and every one was better for it.

What you have at the end
  • Public launch
  • Analytics and error tracking
  • A list of what to fix, ranked
04
Ongoing or handover

Run it

I run every product on this shelf myself, so I know what year three costs. I can keep yours running, or hand it over with the docs to run it yourself.

What you have at the end
  • Monitoring and on-call
  • Release cadence
  • Handover docs if you want them
What skipping a phase costs