Pricing is strategy.

Founders spend a disproportionate amount of time on the pricing number. What should we charge? Are we above market? Below? What does the competitor charge? If we lower the price, does volume make up for it?

These are real questions. They are also the wrong starting point.

Before the number, there is the model: subscription or transaction, seat based or usage based, retainer or project, outcome linked or time linked. Each of those choices is a bet on how value is created and how it is captured. Getting the model right is the work. Getting the number wrong is recoverable. Getting the model wrong means you are structurally misaligned with the customer regardless of where you set the price.

Every pricing model encodes an assumption about the nature of the relationship between the business and its customer.

A subscription model assumes that value is delivered continuously and that the customer's willingness to pay is persistent over time. The bet is on retention: that you can hold the customer long enough that the acquisition cost becomes irrelevant. This works when the product is embedded in a workflow and the cost of switching is high. It fails when the product is used occasionally and the customer resents the recurring charge during the gaps.

A transactional model assumes that value is discrete and episodic. The bet is on frequency and margin per transaction. This works when the need is clear and recurring and the product is the obvious solution in the moment of need. It fails when the value is hard to attribute to a single event and the customer starts questioning why they are paying each time.

A retainer model assumes that the value of ongoing access is higher than the value of any individual deliverable. The bet is on relationship and predictability. This works when the client genuinely cannot internalise the capability and the cost of uncertainty is high. It fails when the client starts measuring output per retainer dollar and finds the ratio wanting.

The question is not what the market will bear. The question is what relationship between cost and value the model implies, and whether that relationship is honest.

The deeper issue with most pricing models is alignment. When the pricing model is misaligned with how the customer experiences value, the commercial relationship is structurally adversarial, and it will eventually behave that way.

A professional services firm billing by the hour has a pricing model that is in fundamental tension with the client's interest. The client wants the problem solved as efficiently as possible. The billing model rewards inefficiency. Both parties usually understand this. The relationship is shaped by that understanding in ways that neither party fully acknowledges.

A SaaS product billing per seat has a pricing model that penalises adoption. Every additional user who should be using the product is a line item the buyer will resist. The company's interest is in broad deployment. The pricing model creates an incentive against it.

These misalignments are not always fatal. They are managed, worked around, and sometimes hidden under the relationship. But they do not disappear. They resurface at renewal, at expansion, at the moment when the customer has to actively choose to continue. And at that moment, the pricing model's logic becomes visible in a way it was not when the contract was signed.

The pricing model also signals market positioning in ways founders often do not intend.

A low price signals accessibility but also, in many markets and categories, signals low quality. This is especially true in professional services and in any category where the customer cannot directly observe quality before purchase. In these markets, a price that is too low creates distrust rather than demand. The customer is not asking whether they can afford it. They are asking why it is so cheap, and whether the answer should concern them.

A high price with no structural justification signals either confidence or delusion, and the market will form a view on which one quickly. A high price with clear structural justification, built on demonstrable capability, a track record, or a genuine scarcity of supply, is a positioning statement. It defines the customer you are building the business around and the ones you are not.

The choice of model also defines the competitive surface. A per seat SaaS product is in direct comparison with every other per seat SaaS product in the category. An outcome based product is harder to compare directly. That is partly what makes it harder to sell. It is also what makes it harder to commoditise.

The business that wins on price is always one price reduction away from losing. The business that wins on model is playing a different game.

Most businesses get the pricing model wrong the first time. This is not a criticism. It is a function of the fact that the right model is only legible in retrospect, after you have run the wrong one long enough to understand what it costs you.

The mistake founders make is not choosing the wrong model initially. It is treating the model as fixed once it is set. Changing a pricing model is uncomfortable. Existing customers feel aggrieved. The sales motion has to be rebuilt. The numbers look worse before they look better.

But a wrong pricing model compounds its damage over time. It attracts the wrong customers, the ones for whom your model makes sense even though your product does not. It trains the market to value you in a way that does not reflect the actual value you create. And it makes every pricing conversation harder than it needs to be, because you are defending a structure that neither you nor the customer fully believes in.

The right time to fix the model is always earlier than it feels comfortable. Before the customer base is large enough that a change is politically difficult. Before the team has built sales motions, marketing materials, and internal processes around a model that needs to change.

The honest question to ask about your pricing model is not: what is the market willing to pay? It is: does this model accurately reflect the relationship between the value we create and the cost we charge for it?

If the answer is yes, the pricing conversation is relatively simple. You set a number, you test it, you adjust. The model is doing its job.

If the answer is no, the pricing number is a secondary problem. The primary problem is that you are selling a relationship you have not fully designed. And no amount of optimisation on the number will fix a model that was wrong from the start.

Price is a number. Pricing is a decision about what kind of business you are building.