How Complete Does a Product Need to Be Before It Goes to Market?

Author：Sandy Tsai     Time：2026.08

Over the past few years I have mentored a large number of startup teams, and one line comes up again and again when they pitch: the product is not ready yet, so we have not launched.

There is usually a reasonable consideration behind this. The founder wants the product complete first, with the user experience, the functionality and the quality all meeting expectations, before taking it formally to market. An immature product can leave a negative first impression, and first impressions are seldom available twice.

For an early-stage team with limited resources, however, this way of thinking carries a risk of its own: committing excessive resources to a complete product before the market has been validated. It gives too little weight to the other expensive risk, which is that the direction is wrong.

Suppose a team spends 18 months and the bulk of its capital and finally launches, only to find that consumers are unwilling to use the product, that market demand differs from what was expected, and that even investors and market research point to a product direction in need of adjustment. Redesigning and rebuilding at that stage means that most of the time, the manpower and the capital already committed cannot be recovered.

For an early-stage company this is not merely a question of efficiency. It can become a risk to the company's survival.

Have you been through this, or taken part in it: a company pours everything into building a product, then spends just as much effort looking for a market and looking for customers?

Broken down, there is a question here worth thinking about:

If the product really does solve a clear and important pain point in the market, why should it still cost so much to find customers willing to buy?

This is not to say that a finished product needs no selling. It is a reminder to founders that, before committing significant resources, they should first establish who has the problem, how important it is to them, and whether they are willing to pay for a solution.

There is nothing wrong with pursuing a complete product. What has to be avoided is treating a complete product as the starting point of a venture while the key assumptions are still unvalidated.

How can a founder confirm the market direction?

1. Start from the market problem, not from the product

Before development begins, settle a few basic questions.

2. Who is the target customer? What's the ideal customer profile?

Which specific group does the product serve, as opposed to everyone who might possibly need it?

3. What is their real pain point?

How much does the problem cost the customer in time, cost, revenue or efficiency? Is the pain great enough to prompt them to look for a solution?

4. Does a solution already exist in the market?
If none does, that may point to an opening in the market, or it may point to demand that is simply not strong enough. The two need to be told apart.

5. If competing products already exist, why does the customer need another option?
Can the new product deliver enough value on price, efficiency, experience, technology, distribution or another key dimension to make the customer switch?

The purpose of these questions is not to forecast the market, but to reduce the informational uncertainty that exists before a product is built.

Validate the market at the lowest reasonable cost

A good product should not hold up only in an imagined market.

Rather than committing substantial resources to a complete product and then waiting for the market to answer, bring the real market into the validation early, through a minimum viable product (MVP) or other low-cost means.

For example :

• A pop-up experience or a small-scale trial
• A prototype built with AI or other low-cost tools and given to testers
• A one-page website to test market interest
• Opening reservations or registrations, to see whether potential customers will leave their contact details or make a low-cost payment
• Delivering the service by hand in place of automation that is not yet necessary, so that the demand is validated first

Kenbun Capital Tips : when validating, work out which elements are indispensable to testing the core value and which can be optimized later. And what price did the participant pay in order to signal that willingness?

The purpose of these methods is not to make the product crude, but to obtain, at the lowest reasonable cost, market information sufficient to support the next decision.

If the market response falls short of expectations, the team can change direction at a lower cost. If the demand is validated, resources can then go into deepening the product and scaling it.

Early in a venture, validate the direction before committing more resources

The truly expensive risk in a venture is usually not that the product is imperfect, but that limited resources have been committed too heavily to the wrong direction.

For an early-stage company, product development is not a one-time endpoint but a continuing process of validation and correction.

Understand the market first, then validate at the lowest reasonable cost. Correct the assumptions against real customer feedback, and commit more resources once the direction is confirmed. A process of this kind does more than improve the efficiency with which resources are used. It lets the product, the market and the business model be built step by step on real demand, and it strengthens the confidence that the market and investors have in you.

Author：Sandy Tsai      Time：2026.08