To test an offer or price change, write down the few things that must be true for it to work, check them against evidence you already hold, then test willingness to pay with real buyers and real proposals before you build anything. Agree in writing what result means go, change course, wait or stop before the results arrive.
Established B2B companies rarely launch something from scratch. They add a tier, repackage a service, raise a price, move from day rates to fixed fees, or take an existing offer into a new sector. This guide sets out the sequence I'd use to test any of those before the quarter's budget is committed.
Why Offer Changes Fail Quietly
Most offer and price changes fail slowly. Pipeline looks fine for a few weeks, then conversion drifts, and nobody can say exactly why.
The McKinsey analysis of the average S&P 1500 company shows the stakes.
Consider the average income statement of an S&P 1500 company: a price rise of 1 percent, if volumes remained stable, would generate an 8 percent increase in operating profits.
The same sentence says that impact is nearly 50 percent greater than a 1 percent fall in variable costs and more than three times greater than a 1 percent increase in volume. It's US data published in 2003 and your cost base will differ. The arithmetic runs the other way too, so a price that's slightly too high, or a package buyers quietly don't want, can take more out of a year than the slide that proposed it suggests.
Most of these failures trace back to one of three untested assumptions:
- that buyers want the change,
- that they'll pay the new price,
- and that the team can deliver it at that price.
Sometimes the failure is loud. In 2023, the restaurant software company Toast added a $0.99 fee to orders of $10 or more, then removed it. Its CEO, Chris Comparato, said the company had made the wrong decision. Jason Lemkin's write-up on SaaStr drew the lesson that SaaS has more price elasticity than we thought, but it isn't unlimited.
If you're new to the wider topic, what is market validation? covers the basics and the evidence that counts.
Test the riskiest assumption first, with the cheapest test that could prove it wrong. Everything else can wait.
Write Down What Has to Be True
Before testing anything, write the change as a short set of statements that must all be true for it to work. Here's an example for moving a consultancy service from day rates to a fixed-fee package:
- Our best-fit clients prefer a fixed fee to an open-ended day rate for this work.
- They'll accept a price at or above what the work costs us plus our target margin.
- We can scope the work tightly enough that fixed fees don't erode margin.
- Sales can explain the package in one sentence without a call.
Then rank them by two questions. How damaging would it be if this were false? And how little evidence do we have today? The statement that scores worst on both is the one to test first.
Teams often skip this step because it feels obvious, and it's where the arguments surface. If your sales lead and your delivery lead write different lists, you've found your first risk before spending anything. If the switch to fixed fees is the change you're weighing, our guide to fixed-price go-to-market services covers how buyers compare fixed fees with day rates and retainers.
Gather the Evidence You Already Hold
Before running any new test, look at what's already in your CRM, your proposals and your delivery data. It's cheaper than a new test and often just as informative.
- Lost deals. The stated reasons, the competitor or alternative named, and the stage where each deal stalled.
- Discount history. Where discounts cluster tells you where the current price meets resistance, and for which buyers.
- Sales calls and enquiries. The questions prospects ask before buying, in their own words. Repeated questions mean the offer is unclear.
- Delivery data. Actual hours, scope creep and margin by client type. A fixed-fee package built on optimistic hours fails on delivery, long after it's been sold.
- Competitor pricing pages. What the alternatives charge, how they package it, and what they show publicly. Capture them with a date.
That last one matters because your buyers have usually looked at the same pages before they talk to you. In the 6sense 2025 buyer study, 94% of buyers said they had ordered their shortlist according to preference before engaging sellers, and 77% (of 3,744 buyers in the main survey) said their first vendor conversation was with the vendor that went on to win. Buyers evaluated an average of 5.1 vendors. It's a vendor-run survey, so treat the figures as directional.
| Ordered their shortlist by preference before engaging sellers | 94% |
|---|---|
| First vendor conversation was with the eventual winner | 77% |
Source: 6sense, 2025 B2B Buyer Experience Report, 2025. Vendor-run survey of just under 4,000 buyers. The 77% figure is from a question answered by 3,744 of them. Directional only. Chart by ThriveFinity.
If that's even roughly right, your price is judged against the alternatives before you've had a chance to explain it. If you don't know what those alternatives charge, you're pricing blind. Our guide to competitive intelligence sets out a simple way to track them.
Test Willingness to Pay Before Building
Asking buyers would you pay this? invites polite answers. Better tests ask for a commitment, or at least a trade-off. Here are four, roughly in order of how much they tell you.
Price-range questions (Van Westendorp)
The Van Westendorp Price Sensitivity Meter was developed in the 1970s by the Dutch economist Peter van Westendorp. Sawtooth Software's guide gives the four questions as:
- At what price would you consider the product to be so inexpensive that you would feel the quality couldn't be very good?
- At what price would you consider the product to be priced so low that you would feel it's a bargain?
- At what price would you say the product is starting to get expensive, but you still might consider it?
- At what price would you consider the product to be so expensive that you would not consider buying it?
With a modest number of qualified buyers, the answers show a range rather than a single guess. It's quick and cheap. It also has real limits. Sawtooth notes the method asks about price without a competitive context, doesn't predict sales volume on its own, and that the line-crossing approach has largely been criticized and discredited as lacking good theory. Sawtooth's Bryan Orme walks through the weaknesses here:
I'd use it to find a sensible range for a proposal. I wouldn't use it to set the final number.
Choice between options
Show two or three packages side by side and ask which they'd choose. The choice reveals more than a rating, because it forces a trade-off between price and what's included.
A real offer to a few real buyers
Put the new package in front of a small number of prospects in live sales conversations, with a proposal and a price. A signed order, or a clear reason for no, is the strongest evidence you can get.
A page before a programme
A single landing page describing the new offer, shown to a defined audience, with a request for a call or a proposal. Measure the requests, not the visits.
| Test | What it tells you | What it can't tell you | Best for |
|---|---|---|---|
| Price-range questions | An acceptable price range for a defined offer | Whether anyone will actually buy, or how many | Setting the range for a first proposal |
| Choice between options | Which package and price point buyers prefer when forced to choose | Absolute demand, because every respondent picks something | Tiering and repackaging |
| Real proposals to real buyers | Whether qualified buyers sign at the price | Much about the wider market, because the sample is small | Price increases and new packages for existing segments |
| A landing page | Whether a defined audience asks for a call or proposal | Price acceptance, unless the price is on the page | New offers and new segments |
How many buyers is enough?
There's no magic number for a B2B test, and anyone who gives you one without knowing your market is guessing. The useful question is how much weight the result has to carry. A test that decides whether to change the headline price for every new client needs more conversations, with more types of buyer, than a test of one new add-on.
My rule of thumb: keep going until one enthusiastic or hostile buyer can't change the answer on their own. And never stop at your friendliest clients.
Whichever test you choose, record how many people were asked, who they were, and when. A result from six friendly existing clients is useful, but it's a different result from thirty prospects who've never bought from you.
If you want a practical walkthrough of how to arrive at a number and then justify it to buyers, Tom Blomfield's Startup School session for Y Combinator covers the value equation, cost and competition in about 18 minutes. It's aimed at start-ups, so adapt it to an established price list:
Existing Clients and New Prospects Need Different Tests
Test existing clients and new prospects separately. Existing clients tell you about fit and delivery. New prospects tell you whether the offer wins business on its own. Mixing the two hides the difference.
Existing clients also read a price change differently, because they're comparing it with what they paid last year. Jason Lemkin's advice for anyone raising prices is to put more value in alongside the increase:
If you do raise prices, how about also adding more value than price increase?
That's a view from SaaS, and it's easy to forget when the spreadsheet says the increase pays for itself. My advice: test the new price with new prospects first. If it holds there, you've got evidence to take to existing clients, along with a reason the price has moved. Check your contracts for notice periods before you announce anything.
If you publish prices, the rules apply too. The CAP Code is direct about it.
Price statements must not mislead by omission, undue emphasis or distortion.
It also says quoted prices must include non-optional taxes, duties, fees and charges that apply to all or most buyers, with an exception for VAT-exclusive prices when everyone the claim is addressed to pays no VAT or can recover it. A fee bolted on after the headline price is exactly what that rule is about.
Check You Can Deliver It at That Price
A price change is also a delivery change. Before launch, model the offer at the volume you hope to sell: who does the work, how many hours it really takes, where scope will creep, and what margin is left if it does.
If the offer only works when a founder or director delivers it personally, it won't scale past their diary.
A simple way to check is to take the last ten pieces of work that look most like the new offer and recost them at the new price. Use the hours they actually took rather than the hours in the proposal. Then ask three questions.
- How many of the ten would have made your target margin?
- What caused the overruns on the ones that didn't?
- Would the new scope have prevented those overruns, or just moved the argument to a change request?
If fewer than half would have made margin, the price isn't the problem yet. The scope is. Fix that first, because a higher price on a loose scope just makes the overruns more expensive for everyone.
Watch your input costs too, because they're often the reason for the change in the first place. If your price rise only just covers this year's cost increases, you haven't priced the offer. You've postponed the next conversation.
The free ROI calculator can help you put a number on what a wrong call would cost before you decide how much testing it deserves.
Decide With Clear Criteria
Before the results are in, agree what would make you go ahead, change course, wait or stop. For example: Go if at least three of the ten prospects accept a proposal at or above the target price and delivery hours stay within budget. Change course if they want the offer but not at this price. Stop if fewer than two show real interest.
Writing the criteria down first stops the team from moving the goalposts once they've fallen for the idea. Daniel Kahneman, Dan Lovallo and Olivier Sibony described the risk in Harvard Business Review in 2011. HBR's summary of the article says a team that has fallen in love with its recommendation may subconsciously dismiss evidence. Criteria agreed in advance are the cheapest defence I know.
They also give the board a decision it can check, which matters if the change is big enough to show up in next quarter's forecast. Before you commit the wider go-to-market plan around the new offer, it's worth running the checks in is your go-to-market strategy ready?
One page: the change, the assumptions ranked by risk, the evidence for each with its source and date, the test you ran, the result, and the decision with the criteria you set in advance. Keep it short enough that someone joining the team next year can read it in five minutes and understand why the price is what it is.
Where ThriveFinity Fits
A team testing its own offer is marking its own homework. That's fine for small changes. For a launch or repricing that will drive next quarter's pipeline, an independent check is worth having.
- Offer Self-Check (free, five questions): the offer self-check is a quick way to see where your own answers are thin.
- Offer Signal (free, under an hour): a directional read on the offer with all 12 lenses scored and three costed next moves. Describe your offer in two to five sentences.
- Decision Brief (£749): the full Decision Brief verdict, sourced evidence graded A to E, signed by a named verifier on a 48-hour target.
- Decision Brief (£749): one decision, such as how to price or package an offer, taken to a signed recommendation and 90-day plan on a 48-hour target.
Our methodology sets out how evidence is graded and what we refuse to certify.
We're not the right choice if the decision has already been made and can't be reversed, or if your offer is already generating strong, consistent revenue and you only want to fine-tune it. A pricing specialist running large-scale conjoint studies will serve you better there. And if what you really want is confirmation, save your money. The verdict can come back as Stop.
❓ Common Questions
How do I test a price increase without losing customers?
Do we have to tell existing clients before a price increase?
Sources
- Michael V. Marn, Eric V. Roegner and Craig C. Zawada. The power of pricing. McKinsey Quarterly, 1 February 2003.
- Jason Lemkin. Toast: We Crossed The Line on Price Increases (and Fixed It). SaaStr, 24 July 2023.
- 6sense. 2025 B2B Buyer Experience Report. 2025, checked 20 October 2026.
- Sawtooth Software. Van Westendorp Price Sensitivity Meter. Last updated 5 March 2024.
- Committee of Advertising Practice. The CAP Code, section 3: Misleading advertising (rules 3.17 and 3.18 on prices). Checked 20 October 2026.
- Daniel Kahneman, Dan Lovallo and Olivier Sibony. Before You Make That Big Decision. Harvard Business Review, June 2011.
- ThriveFinity published prices and scope: /pricing (October 2026).