Build a ProductPeople Will Pay For

Discovery is a set of focused sessions that test your idea before development starts. We work through the Four Phases (Business Understanding, Market Understanding, User Understanding and the Execution Plan), so you find out what's actually worth building before you spend a dollar on code.

The hard, expensive risk today is building the wrong thing. We wrote the long version in What is Product Discovery and Why Does It Matter?, and how our process works in Foundational Product Discovery.

In a set of focused sessions, one phase at a time. Between sessions we do the research and write up what each one settled, so every session ends with something you can act on. We spend the most time where you're weakest, and if you've taken the Lens, your report already shows where that is. Your part is the sessions themselves; the research happens on our side.

The full phase by phase breakdown is in Foundational Product Discovery.

A Blueprint built around your Product: what the Four Phases settled, written down so any capable team can build from it. What goes in it depends on what your Product needs, and we agree that with you at the start.

It's yours to keep, whoever ends up building it.

Then you're halfway there. Product Discovery settles the rest: what to build, and what to build first. Users often ask for the symptom, so we dig to the real need and then prioritize ruthlessly.

See Identifying User Requirements on requests-versus-needs, and Product Prioritization Frameworks on deciding what comes first.

A wrong build can cost months of runway, and Discovery costs a fraction of one wrong hire. If you need a working prototype too, we scope and price that with you before we start.

The most common money pit we see is Founders building commodities they should have bought, like custom auth or billing. More on that call in Build vs. Buy.

Maybe, eventually. Validate first, though, because a Product that's been through Discovery and has a team behind it can often go further than a cofounder hire would. A cofounder takes 20 to 40% equity, and it's a bet you can't undo.

We laid out the math, and when you genuinely do need one, in Stop Looking for a Technical Cofounder.

No. It works just as well for a live Product: when you're adding a new Product or a big feature, or planning a rebuild. We run it the same way, and spend the most time where you're weakest.

The difference is in Initial vs. Continuous Product Discovery.

We talk through your idea, where it stands today, and which of the Four Phases are still open. By the end you'll know whether Discovery is the right next step, and if it isn't, we'll tell you.