Pricing gets treated as something to figure out later, by finance, once the product exists. That is backwards. Price is a product decision, and deferring it quietly shapes the product into something that struggles to charge for itself.
Most early teams postpone pricing until there is “something to price.” The logic feels sound: build the product, prove it works, then decide what to charge. By the time they get there, the product has already been shaped by the unexamined assumption that pricing would sort itself out. Often it does not.
Price is not a number you attach at the end. It is a claim about who the product is for, what they value, and how much of that value you intend to capture. Make that claim late and the product is built to answer a different question than the one the market will ask.
Price is a constraint, not an afterthought
A target price is one of the most useful constraints an early product can have. It forces decisions that are otherwise easy to avoid: which customer you are actually building for, which problems are worth solving for them, and which features earn their place.
A product being built toward twenty dollars a month is a different product from one being built toward two thousand. Not a cheaper version of the same thing, a different thing: different buyer, different depth, different proof, different everything. Deferring the price defers that fork, and the product drifts toward whatever the team found interesting to build.
A product built toward twenty dollars a month is a different product from one built toward two thousand. Not cheaper, different.
What a target price forces you to decide
Set a target price and three product questions become unavoidable.
Who is the buyer. Price segments the market before a single feature does. It decides whether you are selling to an individual, a team, or a procurement department, and each of those wants a different product.
What the value metric is. What does the customer pay per: seats, usage, outcomes, a flat platform fee. The value metric is a product decision that shapes how the product is instrumented and what it optimises for.
What has to be true to justify it. A price is a promise. The higher it is, the more the product has to demonstrably do, and the earlier you learn what that is.
The cost of deferring
When pricing is left to the end, the product tends to arrive shaped for a buyer who does not exist at the price the business needs. Then the team faces a bad choice: charge less than the model requires, or retrofit value the product was never built to deliver. Both are expensive, and both were avoidable.
Set a target price in the first 30 days
The fix is not to finalise pricing early. It is to set a structural target price early, in the first thirty days, and let it constrain the product decisions that follow. Not a final price, a working one, held loosely enough to revise and firmly enough to shape the build.
If the target price does not support the shape of the product being built, that is a finding, and an early one. One of them has to move, and it is far cheaper to discover the tension now than after a year of building toward a buyer who will not pay.
What we recommend
Treat price as a first-class product input, alongside the thesis and the roadmap. Set a target early, use it to decide who you are building for and what you are building, and revise it as you learn rather than discovering it at the end. The teams that price as they build ship products that can charge for themselves. The teams that defer it ship products that have to be talked into a business model afterwards.