What a good v1 leaves out

The best first versions of a product are defined by what they refuse to build. Here is how founders should think about scope, focus, and shipping a strong v1.

What a good v1 leaves out, from Camel Design

A founder came to us with a plan for his first product version. It had a long list of features, every one of them reasonable. The problem was not any single feature; it was all of them together. Trying to build everything meant launching slowly, spending heavily, and confusing users about what the product was actually for. The hardest and most valuable work we did with him was not deciding what to build. It was deciding what to leave out.

A strong first version is an act of subtraction. Here is how to think about it.

Why more features make a weaker v1

Every feature you add to a first version costs time, money, and clarity. It delays launch, which delays learning. It adds complexity, which makes the product harder to understand. And it splits your focus, so nothing is done as well as it could be. A v1 crammed with features is not more valuable; it is more diluted.

Find the one thing it must do brilliantly

Every product has a core promise, the one thing it must do well for anyone to care. A good v1 does that one thing brilliantly and leaves almost everything else for later. Ask yourself: if the product could only do one thing, what would it be? Build that, make it excellent, and cut or postpone the rest.

Leaving out is not the same as never

Saying no to a feature in v1 does not mean killing it forever. It means sequencing. You ship the core, you learn from real users, and then you add what the evidence tells you matters, not what you guessed upfront. Most of the time, what users actually want is different from the long list you started with, which is exactly why launching lean and learning fast beats building everything blind.

A focused v1 teaches you more

The whole point of a first version is to learn. A simple, focused product gives you clear signal: people either use the core thing or they do not. A bloated product gives you noise, because you cannot tell which of the twenty features is working or failing. Less to launch means clearer answers.

The honest bottom line

That founder’s best decision was not what he built, but what he had the discipline to leave out. A good v1 is defined by its restraint. Ship the core brilliantly, learn from real people, and add the rest with evidence instead of guesses. Saying no now is how you earn the right to say yes to the right things later.

That is how we help founders shape a v1 at Camel: not by cramming in everything, but by finding the core worth shipping and making it excellent.

Written by Jamil, Founder of Camel, a global design studio from Madurai working with founders worldwide.

(Start a project)

Shaping your product’s first version?

Tell us what you’re building. We reply within 24 hours.