Pricing while the market is still speaking

In a startup's early stages, price is not a decision made once and for all: it is one of the fastest tools for understanding the market. The practical answer is this: choose a pricing unit tied to the value the customer receives, put a concrete price on the table early, observe reactions methodically, and revise the price list at set intervals, with clear rules on what changes for existing customers. Waiting for "enough data" before setting a price usually means giving the product away for longer than necessary.

In short

• Price communicates what the product is worth: charging little or nothing produces weak signals.
• Choose the pricing unit first (per user, per site, per volume, per outcome), then the level.
• Say a number in sales conversations and record what happens.
• Tell objections about price apart from objections about value or timing.
• Decide in advance when and how you will revise the price list, and what you guarantee early customers.

Why price is a signal, not just revenue

When a product is free or nearly free, people say yes easily and the yes is worth little. When there is a real price, the conversation changes: you find out who controls the budget, which alternatives the customer is weighing, and which problem is urgent enough to justify spending. That is valuable information for both product and sales.

That is why it pays to introduce a price early, even in pilots. A paid pilot, even one priced well below your future list price, filters for customers who are genuinely interested and makes the later conversion easier.

Choose the pricing unit before the level

The question "how much do we charge?" comes after another one: "what do we charge for?". The pricing unit should grow with the value the customer receives. The most common options:

• per user: simple to understand, suited to products whose value grows with the number of people using them;
• per site, plant or operating unit: common in industrial B2B, where value is tied to a physical footprint;
• per volume: documents processed, transactions, calls, machine hours;
• packages or tiers: different features for different needs;
• outcome-based: part of the price depends on a measurable result, harder to manage but sometimes very persuasive.

A good test: if the customer uses the product twice as much and gets twice the value, does your revenue grow? If not, the unit is probably wrong. Also check that the unit is easy to measure and easy to explain to a procurement department.

Setting the first level

Without historical data, the first price is built from three reference points:

1. value to the customer: time saved, errors avoided, revenue added. Have customers tell you in their own numbers rather than estimating it yourselves;
2. the alternatives: what the customer does today to solve the problem, including doing it by hand or doing nothing, and what that costs them;
3. your costs: the price must leave a margin that sustains service, support and winning new customers.

The final price usually falls between the cost of the alternatives and a fraction of the value. Start higher than feels comfortable: it is easier to grant a justified discount than to raise a price you have already communicated.

Listen to the market methodically

The price has to be said out loud, in demos and proposals. Then, for each conversation, record:

• the price and unit proposed;
• the immediate reaction, in the customer's words;
• the type of objection, if any;
• the outcome and how long it took to get there.

Objections need careful sorting, because "it's too expensive" can mean different things:

• price: the value is clear, but the number exceeds the budget or the alternatives;
• value: the customer does not yet see enough benefit, and lowering the price will not fix it;
• timing: this year's budget is closed, or the project is not a priority now;
• process: approval is needed at a higher level, or a purchasing procedure applies.

If almost nobody objects to the price, it is probably too low. If everyone objects on value, the problem lies elsewhere.

After ten or so recorded conversations, read the table together as a team. Look for recurring patterns: one type of customer who accepts without discussion, another who always asks for the same discount, an objection that only comes up when you speak to a certain role. These patterns are worth more than any single negotiation, and they often suggest changing the pricing unit or creating a different tier for a specific segment, rather than lowering the price for everyone.

Changing the price without losing trust

In the first years the price list will change several times. To do it without damaging relationships:

• set a review cadence in advance, for example every six months, rather than changing it in every negotiation;
• write into early customers' contracts what happens to their prices at review time, for example a price locked for a defined period;
• announce changes ahead of time and explain what has changed in the product;
• keep track of every discount granted and why, so you avoid unmanaged parallel price lists.

What to do in the next two weeks

1. Write down the pricing unit you use today and check whether it grows with customer value.
2. Ask current customers for the value they get, in their own numbers.
3. List the customer's alternatives and what they cost.
4. Set a list price and use it in every upcoming proposal.
5. Prepare a table to record reactions and objections, sorted by type.
6. Set the date of the next price review and the guarantees for early customers.
7. If you want to talk your pricing through with someone outside the team, get in touch.

In Resources you will find a template for logging sales conversations, and in the community other founders working through the same choices.

Subscribe to Dispatch, the PATAVIUM newsletter, for practical tools to build your startup every week.