Every founder we talk to has a feature list. Almost none of them have a first version. Here’s the cut we make on every discovery call — and the four questions that make it painless.
Every founder we talk to arrives with a feature list. Almost none of them arrive with a first version. That gap is the single most expensive thing in early-stage product work, and it has almost nothing to do with design.
Why the list always grows
A feature list grows for good reasons. You talked to twelve potential customers and each one wanted something slightly different. Your co-founder has a strong view about onboarding. An investor asked what your moat is, so you added the thing that sounds like a moat. None of these are mistakes — they are all evidence of doing the work.
The problem is that a list assembled from twelve conversations is a description of a market, not a description of a product. It has no centre. And a product without a centre cannot be designed, because there is nothing to design around.
A list assembled from twelve conversations describes a market, not a product.
In practice, this shows up as scope that is roughly 40% larger than what your first version needs. We’ve now seen the number hold across healthcare, fintech, real estate, and marketplace products. Not because founders are undisciplined, but because the discipline required is genuinely unnatural — you are being asked to say no to things you believe in.
The cut we make on every call
On a discovery call we’re not trying to shrink your ambition. We’re trying to find the one loop your product has to close before anything else matters. Every product has one. For a queue management system it’s: patient arrives, staff sees them, patient knows their position. For a file sharing app: sender uploads, receiver gets it, both trust that it happened.
Everything that isn’t in that loop is version two. It might be excellent. It might be the thing that eventually differentiates you. It is still version two, because until the loop closes, nothing you build on top of it can be evaluated.
Four questions that do the cutting
- What has to happen for a user to get value once? Not repeatedly, not at scale. Once. Write down every step. That’s your loop.
- Which of these features exist only because a competitor has them? Those go to a separate list. They are positioning decisions, not product decisions, and they should be made after you have users.
- Which features can be a human doing it manually for the first 50 customers? Onboarding, matching, moderation, support, even parts of a marketplace. If a person can do it, a person should do it until the volume proves the automation is worth designing.
- What would you cut if the deadline moved up three weeks? Whatever you name here, you have already decided it isn’t essential. You just haven’t admitted it yet.
That fourth question is the one that does most of the work. Founders answer it instantly and accurately, which tells you the knowledge was always there — it just needed permission.
What usually survives
A first version that survives this process tends to look like 15 to 25 screens, one primary user role, one complete journey from arrival to value, and honest empty states for everything that isn’t built yet. That’s a real product. It can be shown to an investor, tested with a user, and built by two developers in a reasonable number of weeks.
It is also — and this matters more than it sounds — a product that can be designed well, because the designer can hold the whole thing in their head at once. Scope discipline isn’t just a budget decision. It’s a quality decision.
The objection we always hear
“But if we launch with just that, we’ll look thin.”
You’ll look focused. There is a real difference, and users can tell. A product that does one thing completely reads as intentional. A product that does eight things partially reads as unfinished — because it is.
The version of your product that impresses people is not the one with the most features. It’s the one where every screen you show feels resolved. That’s a far more achievable target, and it’s reachable in weeks rather than quarters.
How fast can you actually start?
Usually within three to five business days of the proposal being signed. If your timeline is tighter than that, say so on the discovery call — we hold capacity for urgent raises and launch dates.
What if I don’t know which package I need?
That’s the most common situation and it’s exactly what the free call is for. Bring what you have — a document, a sketch, a competitor you like — and we’ll tell you which stage you’re actually at.