- Growth
- Lifetime value
- Pricing
- Pricing strategy
Wiki
Pricing strategy
On this page
SaaS platform introduces consumption-based expansion
An analytics platform charged a flat rate of £5,000/month regardless of data volume processed. As customers grew, they consumed 10-100x more data but paid the same price, reducing profitability. The platform introduced tiered pricing: Base tier (up to 1M events) at £3,000/month, Professional tier (up to 100M events) at £10,000/month, Enterprise tier (custom). This consumption-based expansion enabled NRR to increase from 105% to 145% because growing customers naturally expanded to higher tiers. The pricing change increased profitability 50% while actual customer retention stayed nearly identical.
SaaS platform increases price, grows profitability 35%
A project management SaaS platform was acquiring customers at £15k CAC with £4k ACV. This unsustainable unit economics prevented scaling. Through customer research, they discovered customers perceived far more value than price suggested. The team increased pricing from £20/user/month to £30/user/month (a 50% increase). Conversion rate declined only 12%, but because CAC remained constant, their payback period improved from 4.2 months to 2.8 months. This single pricing change made their unit economics profitable at scale and enabled them to exceed profitability targets within 18 months.
How to apply
Analyse the value your product creates for customers in quantifiable terms. If your product saves a customer 100 hours annually at £100/hour, it creates £10,000 annual value. You should price significantly below this value threshold (£3,000-£7,000 annually depending on competitive context) to create compelling ROI for customers. Never price so high that customers struggle to justify ROI; equally, don't price so low that you capture almost no value.
Structure pricing to align with customer growth. A per-seat model naturally expands as companies grow - adding team members increases cost, which aligns with expanding benefit. A flat-rate model doesn't expand, leaving you with no expansion revenue. Per-usage models expand as customers consume more. Choose pricing structures that grow with customer value perception, creating natural expansion revenue without requiring upsell conversations.
Test pricing changes through controlled experiments. Rather than implementing a 20% price increase across all customers simultaneously, increase prices for new customers and measure the impact on conversion rates and customer acquisition. If conversion declines less than 10% when you increase price 20%, you've discovered significant pricing power. Use these controlled tests to identify optimal pricing before full implementation. Document the relationship between price and conversion rate so you can make informed pricing decisions based on data rather than intuition.
Consulting firm shifts from hourly to outcome-based pricing
A management consulting firm traditionally charged £250/hour for implementation consulting. A project that consumed 400 hours resulted in £100k revenue, but the client's business improved by £5m annually. The consultant shifted pricing to outcome-based: £150k fixed project fee plus 5% of year-one improvements. The client paid £150k + £250k (5% of £5m improvement) = £400k - 4x the hourly pricing. This alignment with customer value made pricing a conversation about value creation rather than hours consumed. Outcome-based pricing also motivated the consultant to focus on quick, high-impact implementations rather than lengthy engagements.
Pricing strategy is the set of decisions about how much you charge, how you charge it (per user, per usage, per outcome, flat fee), and how the price grows as a customer gets more value out of you. It sounds like a one-time decision, but it's one of the highest-leverage levers in the business: a 10% price rise usually drops almost straight to profit, because your cost of acquiring the customer doesn't change. Most B2B companies price too low and leave money on the table.
The common models: per-seat (charge per user, expands as the team grows), per-usage (charge per transaction, API call, or unit consumed), per-outcome (charge a slice of the result you deliver), and tiered editions (Basic / Pro / Enterprise). Most good companies blend them, a base seat price plus usage on top.
The deeper rule is value-based pricing: anchor the price to the quantified value you create, not your costs or a competitor's number. If you save a customer 100 hours a year at £100/hour, you've created £10,000 of value, so a £3,000-£7,000 price is an easy yes. Price too low and you signal low value and attract price-shoppers who churn; price right and you attract customers who care about ROI.
Why it matters
Pricing decides whether growth makes you money. A £50k cost-to-acquire against a £25k contract value is a treadmill; the same £50k against £150k is a machine. Two companies can grow customers at the same rate and one doubles profit while the other shrinks it, the difference is pricing. It also shapes who you sell to and how: a £2,000/year product can't carry a two-month sales cycle, the maths never closes.
How to apply it
Start by measuring the value you create in real numbers, then price well below it so the ROI is obvious. Then structure the price so it grows on its own as the customer grows, so expansion revenue arrives without a renegotiation. Finally, treat price as a thing you test, not guess.
Three ways tooling makes this concrete:
- Say you're running a usage-based SaaS and want to move customers onto consumption tiers. You need to see the value first, so wire your product events into Amplitude and look at which accounts consume 10-100x more than the median, those are the ones a flat rate is quietly subsidising. The data tells you where the tier breaks should sit.
- Say you raise prices for new customers only and want to know if conversion held. Run it as an experiment on your pricing page with VWO, old price versus new to a split of traffic. If a 20% rise costs you under 10% of conversions, you've just found real pricing power, on evidence rather than a hunch.
- Say you're moving from a single price to Good/Better/Best tiers and a sales-assisted motion. Model the new deal sizes in your CRM, in Pipedrive you can set the tiers as products on each deal and watch how average contract value and win-rate shift per tier, so you can see which package customers actually land on.
- And once a customer says yes, the per-seat or per-usage price has to bill correctly every month, so push the agreed terms into your invoicing in Moneybird and reconcile what you charged against what they consumed, mispriced overage is revenue you earned and never collected.
Why it matters
For B2B growth teams, pricing strategy directly impacts business scalability and profitability. A SaaS company can grow customer count 50% but decline in profitability if pricing falls while acquisition cost rises. Conversely, the same growth can double profitability with optimised pricing. This means pricing strategy deserves as much attention as customer acquisition because the financial outcome depends on both. A £50k CAC with £25k ACV is unsustainable; a £50k CAC with £150k ACV is highly scalable.
Pricing also influences customer fit and satisfaction. If you price too low, you attract price-sensitive customers who are difficult to support and likely to churn when better alternatives appear. If you price clearly relative to customer value, you attract customers who appreciate your value and are unlikely to shop on price. Higher-priced customers also tend to be more successful because they're motivated to get ROI from their investment.
Pricing strategy also impacts sales team capability. Salespeople selling low-priced products spend their time on volume; salespeople selling high-priced products are selective. Low-priced products require efficient, scalable sales processes; high-priced products can support consultative selling. Your target go-to-market model should align with your pricing strategy. Trying to sell a £2,000/year product with a two-month sales cycle is impossible; the unit economics don't work.