Should we keep building or start selling?

A founder has an early version of the product. There are still obvious things missing, and the roadmap is full of features the team could build next.

So when do you stop building and start selling?

For an early-stage startup, the answer depends on what you still need to learn. If you do not yet know whether customers care enough to commit, start selling. If customers want the product but repeatedly hit the same barrier to getting value, build that next.

Before product-market fit, selling is not only about revenue. It is one of the fastest ways to learn whether you are building something people care enough about.

Do not wait for the product to feel finished

There is a big difference between someone saying, “That sounds useful,” and asking, “When can I use it?”

There is an even bigger difference when they ask what it costs, agree to a pilot, introduce another decision-maker or invest time in getting started. Those actions tell you more than another internal discussion about the roadmap.

You may discover that the feature the team considers essential barely matters to customers. Something you thought could wait may be the reason someone is willing to buy. Or the people showing the strongest interest may not be the customer segment you originally expected.

That is why I would not wait for the product to feel complete before putting it in front of potential customers. You need enough of the product, prototype or explanation for someone to make a real decision about it.

A commitment tells you more than a compliment

Talking to customers is useful, but asking whether they “like the idea” can produce a lot of positive feedback without much evidence.

Selling changes the conversation. Would they pay? Would they run a pilot? Would they introduce the product into their business? Would they spend time onboarding or involve someone else from their team?

The commitment does not always need to be money this early. But saying yes should require something.

A polite compliment is easy. A commitment is information.

And that information should influence what gets built next.

Let customer evidence drive more of the roadmap

Before product-market fit, I would not think about product development and selling as two separate phases.

If nobody is committing, the answer is not automatically another feature. The problem could be the customer, the problem you are solving, the positioning, the price, the timing or the product itself.

You need to understand which one before spending another month building.

The opposite is also true. If several relevant customers understand the value and want the product, but repeatedly stop at the same missing capability or broken part of the experience, that is useful evidence too.

Now the roadmap is responding to something real.

So, should you keep building or start selling?

Ask what you are still uncertain about.

If the uncertainty is whether the right customers care enough, start trying to sell.

If the evidence already says customers want it, but the product is stopping them from reaching value, build.

Do not scale either one yet. The goal at this stage is to keep shortening the distance between what you build, what customers do and what you learn.

The goal before product-market fit is not to finish the product. It is to reduce the uncertainty around what product is worth finishing.