Positioning and Pricing as Product Decisions
Positioning extracted from customer language rather than invented, and pricing as a judgment about what you will trade — not a prediction exercise.
Chapter 6 · 3 ideas · 10 checks · 17 min
Start here
Your homepage says: the intelligent platform that empowers modern teams to work smarter.
Nobody wrote that sentence badly on purpose. It went through four drafts and two rounds of feedback, and each round made it broader, because every narrowing prompted someone to say "but that excludes the customers who—".
Now read three things your actual customers said last month, taken from their renewal calls:
"We use it to catch the invoices that don't match the PO before they hit accounts payable."
"Honestly it replaced a spreadsheet Devon built that nobody else could maintain."
"It's the only thing that tells us which of our suppliers is quietly slipping."
Those are narrower, stranger, and more specific than anything on the homepage. They are also more interesting. Somebody reading them who has that problem would stop.
Here is the awkward part. The homepage sentence is true. It is true of your product and it is true of forty others, and a buyer skimming it learns nothing they can use — including whether to keep reading.
The team knows the homepage is weak. What they cannot agree on is what to replace it with, because every specific version excludes somebody they hope to win.
So: where does a positioning statement actually come from, and why does the right one always feel like a loss?
Core concepts
Each idea is a short read, one picture and one quick check.
Idea 1 of 3
Positioning is context, and you choose it
A buyer landing on your product slots it into a category in about four seconds (oh, it's one of those), with or without your help. That slot decides what they compare you against, what they expect it to cost, and what counts as good.
Positioning is the context you deliberately place a product in so that its value is obvious to the people who should buy it. Not a slogan, not a feature list: a claim about what kind of thing this is. Change the frame and the same product looks excellent or overpriced, without a line of code changing.
It is extracted, not invented, from a few inputs taken in order, each constraining the next. Here they are run over the three quotes from Start here:
Picture it
The real alternative
Devon's spreadsheet
What the spreadsheet can't do
Match invoices to POs, flag supplier drift
Who cares most
Finance teams with many suppliers, thin AP staff
The frame
Catch bad invoices before they're paid, for finance teams with many suppliers
The test takes ten seconds: could a competitor put their name on this sentence? If yes, it is not positioning. It is a description of a market.
Check yourself
Three homepage lines from three different companies. Which one could a competitor not put their name on?
Go deeper
How to use it. Work from evidence rather than aspiration. The full method has five inputs (the picture folds the third into the last), in this order:
- What would customers use if you didn't exist? The real alternative, which is usually a spreadsheet, a contractor, or nothing — not the named competitor your team argues about in meetings.
- Which of your capabilities do those alternatives lack? Concretely. Not "better UX."
- What value do those capabilities enable? Stated as an outcome for the customer, not as a feature of yours.
- Who cares about that value disproportionately? There is always a segment that cares much more than the average. Find it.
- What market frame makes the value obvious to them? This is the sentence.
How to spot it going wrong. The characteristic error is doing this backwards: inventing the frame first, then hunting for evidence. It produces language that is fluent, category-shaped, and true of everyone.
Why the right answer feels like a loss. Honest positioning is almost always narrower than the team hoped, and it excludes buyers. That is not a side effect to be minimised — it is the mechanism. A statement that excludes nobody informs nobody. The discomfort you feel choosing it is the same discomfort a buyer would have felt failing to understand the broad version, moved from them to you.
Back to the homepage. Run the five inputs over those three quotes and the sentence is narrower than "modern teams". It excludes buyers. Someone in the room will say so, and they will be right. They will also be describing the point.
One thing that has changed. Positioning statements are the single easiest artifact to generate and among the hardest to generate well, because the inputs are customer language nobody wrote down. Ask a model for positioning and you get something fluent and category-shaped, assembled from how the category already talks about itself — which is precisely the thing you are trying to differentiate from. The failure signature is a sentence that would fit forty products, and the competitor test catches it in one read.
Idea 2 of 3
Pricing is a choice, not a forecast
"What should we charge?" gets treated as a question about the world, as though there is a correct number and the job is to estimate it. So the team runs willingness-to-pay surveys, builds competitor tables, fills in a value calculator. The number arrives, and the argument carries on anyway.
A price is not a prediction. It is a decision about which customers you want, what behaviour you want from them, and what you are willing to give up to get it. So state what the price is for before choosing it: land more accounts at the cost of margin, raise revenue from existing customers at the cost of some churn, deter a segment you serve badly, signal seriousness to enterprise buyers. Then name what each candidate sacrifices.
Picture it
Pricing recommendation · new tier
- Recommended price £79 per seat per month.
- Value-based rationale and an eight-product competitor table.
- Projected revenue impact, year one.
- What the price is for: — (circled)missing
- What it gives up: — (circled)missing
A number arrived. Nobody chose it.
Check yourself
The new tier's goal is written down: pull existing £29 customers upward. At £79 fewer of them will upgrade than at £59. Which line states the trade £79 makes?
Go deeper
How to use it. State what the price is for. Then name what each candidate price sacrifices: volume, margin, positioning, the ability to raise later, the complexity of the sales conversation. Then ask what would have to be true for this number to be wrong, and how you would find out.
How to spot it going wrong. A pricing recommendation that arrives as a single number with a rationale and no stated sacrifice. Chapter four's costless tradeoff, in the one place where the tradeoff is the entire content of the decision.
On willingness-to-pay research. Treat it as a hypothesis generator only. "Would you pay £X" is a forward-looking question asked of someone who has not had the problem cost them anything — chapter two's rule, and it does not stop applying because the subject is money. What is evidence: what they pay today for the alternative, what they paid for the workaround, what they have cancelled.
One thing that has changed. A model will produce a confident price with a plausible rationale and a competitor table, none of which is evidence, and the fluency of the output substitutes for the judgment that was never made. The useful division of labour is the one in the next idea: let the model enumerate options and mechanisms, keep the part about what you are willing to trade.
Idea 3 of 3
Prediction is cheap; judgment is the scarce half
This is the clearest place in the domain to see a distinction that runs under the whole course.
Think of AI economically as a large drop in the cost of prediction: filling in missing information. When something gets cheap, demand rises for what complements it. Prediction's complement is judgment: knowing what outcomes are worth, what to do when the prediction is wrong, and what the decision is actually for.
Pricing shows it cleanly. A model can forecast which accounts will churn at a given price, and the forecast can be genuinely good. It cannot decide what churn is worth preventing, at what price, in which segment, because that is a question about what you want. No fact about the world answers it.
Check yourself
Each line is part of one pricing decision. Prediction or judgment?
How many small accounts will cancel if the £29 seat price rises to £39.
Whether losing those small accounts is worth the extra margin.
What revenue each of three candidate prices would bring in year one.
Whether the new tier is meant to land accounts or grow the base.
What we do if the first ten big accounts push back on the new price.
Which competitors' customers look most like ours.
Go deeper
How to use it. Split any decision into its two halves. The prediction half: what will happen? The judgment half: what do we want, what would we trade for it, what does an error cost? Automate toward the first. Keep and invest in the second.
How to spot the confusion. Any argument of the form "AI can now do X, so we should Y" where the leap from X to Y crossed the prediction/judgment line without stopping. The tell in a document: a recommendation whose support is entirely a forecast, with no statement of what the forecast is being traded against.
One thing that has changed. This whole idea is the AI-era note: the forecast half used to need an analyst and a week, so teams rarely had a good one and argued about the number instead. Now the forecast arrives in minutes, which makes it easy to mistake a good forecast for a finished decision.
Why the bar rose rather than fell. When everyone's prediction is equally cheap, the differentiated part of the work is the part that was never prediction. That is the thesis of this whole product, and pricing is where it is easiest to see: two companies with identical churn models still make different pricing decisions, and the difference is entirely judgment.
Worked examples
Make the call yourself first. The reasoning opens after you choose.
Example 1 of 3
The rewrite that lost buyers on purpose
A team sells a scheduling tool. Homepage: smart scheduling for growing teams. An afternoon of support tickets and two renewal calls shows that almost every enthusiastic customer runs shift work across several locations, and what they mention is not scheduling: it is handling last-minute swap requests without a manager arbitrating. The five inputs (below the choice) give a new sentence: shift swaps that don't need a manager, for multi-site hourly teams. Professional-services firms, 20% of customers, no longer see themselves on the homepage.
Check yourself
Should the team ship the narrow sentence?
Example 2 of 3
Taking apart the AI analyst's pricing recommendation
A founder asks a model to recommend pricing for a new tier. What comes back is good work: a competitor table with eight products, a value-based rationale ("customers save an estimated 6 hours per week, worth £180"), a recommendation of £79 per seat per month, and a projected revenue impact. It is well organised, internally consistent and confidently worded. The founder has twenty minutes before the call where the number gets agreed.
Check yourself
Which one thing should the founder check in the twenty minutes?
Example 3 of 3
The narrower frame that raised the price
A company sells a document-review tool at £40 per seat, positioned as faster document review for busy teams. Growth is flat and every deal is a price negotiation. Three-quarters of revenue comes from legal teams doing contract review, and those accounts churn least and negotiate least. The team wants to reframe as contract review for in-house legal and charge three times as much. Going back later would mean giving up the specialist claim.
Check yourself
What should the team settle before they commit to the reframe?
Case studies
Real situations with more than one defensible reading.
Case 1 of 1
The pricing recommendation, taken apart and rebuilt
An invented composite. The artifact is the kind of document a competent model produces today; the company is not real.
A three-year-old company selling supplier-risk monitoring to mid-market manufacturers. £3.2m annual revenue, one product, flat pricing at £29 per seat per month with a 20-seat minimum. Growth has slowed from 6% to 2% monthly over three quarters, and the board has asked for a pricing review.
The founder, short on time, briefs a model with the customer list, the competitor set and last year's win/loss notes, and gets back an eleven-page pricing strategy: three tiers at £29 / £79 / "contact us", a comparison across eight competitors, a value-based justification building to £79, a migration plan, a projected £740k of incremental annual revenue, and a risks section listing migration complexity, sales retraining and billing changes. A year ago it would have taken an analyst three weeks.
Check yourself
The board meets in a week. Where does the founder start?
Go deeper
Where a good decision could still go wrong. The five-account pilot selects the five friendliest accounts, so the pushback condition is tested against people who will not push back. The per-supplier component makes revenue harder to forecast, which the board will notice next quarter. And the "6 hours saved" figure, having been written down once, reappears in a sales deck six months later with the original document as its source.
What great operators do
The rules this chapter's scenarios test for, and how to tell when someone follows them.
Rules to keep
Before you open each card, say what you'd look for.
Common failure patterns
How smart people get this wrong. Find each one in the wild.
Trap 1 of 2
Hypothetical validation
What it looks like. Willingness-to-pay surveys, "would you pay £X", and feature-request rankings collected from people who have never had the problem cost them anything, presented as evidence for a price.
Check yourself
Tap the lines that treat a forecast as evidence for the price.
Pricing research — Pro tier
Found 0 of 2.
Why smart people do it. It scales, it produces charts, and it arrives fast. Real behavioural evidence about price is slow, small-n, and awkward to collect because it means asking people about money they have actually spent.
The correction. Convert every forward-looking question into a backward-looking one. What do they pay today, for what, and what did they cancel? Treat surveys as hypothesis generators, never as validation — and note that the presence of a number makes this failure harder to see, not easier.
Trap 2 of 2
Naked metric
What it looks like. A price comparison table with no units, no inclusions, and no definitions. "Competitors charge £65–£95." A value claim with no traceable source: "customers save 6 hours per week."
Check yourself
Tap the numbers that can't support the conclusion as stated.
Board deck, slide 4 — Are we underpriced?
Found 0 of 2.
Why smart people do it. The numbers are real, or real-adjacent, and supplying the definitions is extra work that can only make the comparison messier. A clean table is more persuasive than an honest one.
The correction. Compared to what, at what stage, in what category, measured how. In pricing the fourth question does most of the work: two products priced per different units are not comparable, and that is the most common way a competitor table misleads.
Cheat sheet
The whole chapter on one card. Save it or share it.
Positioning and Pricing as Product Decisions
- 1If a competitor could sign it, it isn't positioning.Positioning says what kind of thing this is, and who it's for.
- 2Lift positioning from customers' own words.Their real alternative, their job, their phrasing. Don't invent it.
- 3Positioning that excludes no one informs no one.The narrow version feels like a loss. That's how you know it says something.
- 4Say what a price is for before you pick the number.Land accounts, raise revenue per account, deter a segment. Each needs a different price.
- 5Ask what they pay today, not what they would pay."Would you pay £X?" is a forecast. Spend on a workaround is evidence.
- 6Check the unit before comparing prices.Per seat or per workspace? Including what? Most competitor tables fail here.
- 7Let the model predict. Keep the decision.A forecast says what happens at a price. Only you can say if it's worth it.
Memes
The failure patterns, one picture each. For the group chat.
Your turn
Make the call
The checkpoints follow the chapter. In the positioning one you take the homepage from Start here and the customer calls behind it, say what the calls support, and tell the marketing lead what to ship. In the pricing memo you choose which claim in a machine-written analysis to check first, and decide what goes to the board; it is a different company from the case study, so don't carry its findings across. The short forecast case asks whether an accurate churn forecast is enough to sign off a price rise.
The trap. For positioning, the tempting answer is a tighter version of the same generic sentence: it reads better and a competitor could still sign it. For pricing, it is throwing the whole memo out. It is good work in the half it can do; the job is naming which claims are load-bearing and unsourced, and noticing that the judgment half of the decision is missing.
The positioning that says nothing: Is draft 4 fine?
Say what the ten calls support, then tell Nell what the homepage should claim
The AI analyst's pricing recommendation: Decision-ready for Thursday?
Check one claim in the memo, then tell Tobi what goes to the board

