Pricing at Series B: Packaging, Tiering, and the 20% Rule
Pricing power is one of The Opagio 12 intangible assets — and at Series B it is the asset partners can verify in the data room within an hour. The architecture matters more than the headline price: how tiers are constructed, how price increases land, and whether the top-decile customers are paying meaningfully more than the median.
The short answer
A Series B-grade pricing architecture has three properties: annual price increases of 5-15% land without measurable churn impact (the test of pricing power), customer pricing is dispersed across the base such that the top-decile customer is paying approximately 20% more than the median customer (the test of value capture), and the tier structure is producing measurable upgrade flow between tiers (the test of architectural intentionality). The three tests can be run from the data room in an afternoon. Partners do.
Key Takeaway: Pricing power is observable in the customer pricing distribution, not in the headline list price. A Series B-grade pricing architecture produces a customer-price dispersion the partner can read directly from the contract data.
Directional benchmarks drawn from B2B SaaS pricing convention 2024-26.
Why most founders get this wrong
The first error is treating pricing as a one-off exercise rather than as architecture. Founders set the price at Series A based on early customer feedback, leave it there for two years, and discover at Series B that the architecture cannot support the expansion motion the round thesis requires. Pricing is an operating practice; partners want evidence that the architecture is reviewed, that price increases have been tested in the base, and that the founder treats pricing as a strategic input rather than a constraint.
The second error is leaving the entire customer base on a flat price point. A flat-price base signals the founder has not yet figured out value capture — every customer extracting roughly the same value is paying roughly the same price, which is a red flag at Series B because it tells the partner there is no premium tier producing the meaningful expansion contribution. The 20% rule for top-decile pricing is the test of whether the founder has built the architecture for value capture or has been negotiating each large deal individually.
The third error is over-engineering the tier structure. Five or six tiers, a la carte modular pricing, complex usage-based meters that customers cannot self-forecast — each adds friction at the buying decision and creates expansion-motion confusion. The Series B convention is three tiers (Good / Better / Best), with optional usage layers on top, and clear documented reasons why customers move tier. Simplicity in the tier structure correlates with operational discipline in the expansion motion.
Warning: A flat customer-price distribution at Series B reads to partners as either "the founder hasn't figured out pricing yet" or "the customer base doesn't have premium-paying segments". Neither reading prices the round at the level the founder is targeting. The 20% premium for top-decile customers is the artefact partners look for first.
The three pricing models — when each fits
Good / Better / Best (feature tiering). The default for B2B SaaS targeting heterogeneous customer segments. Tier gaps based on functional capability, integration depth, or service level. The pricing architecture that maps most cleanly onto a Series B-grade expansion motion because the upgrade flow is observable.
Per-seat or per-user. The default for collaboration and workflow tools where the value scales naturally with team size. Combines well with feature-tiering as a layer (Good / Better / Best per seat). The architecture is simple to communicate and forecastable for the customer.
Usage-based or consumption-based. The default for infrastructure, AI inference, and analytics products where customer value scales with consumed capacity. Requires careful forecast tooling so customers can self-budget. Combines best with a feature-tier base layer to avoid pure-usage commercial volatility.
What "good" looks like
The Series B-grade pricing architecture has six observable artefacts in the data room. Partners check each.
| Artefact | What partners check | Series B-grade |
|---|---|---|
| Tier structure | Number of tiers, gaps between them | 3 tiers, meaningful gaps in capability |
| Annual price-increase clause | Standard contract has it | 5-15% annual, indexed or fixed |
| Customer pricing distribution | Top-decile vs median pricing | Top-decile ~20% above median |
| Tier-upgrade flow | Measured movement between tiers | Documented quarterly upgrade rates by segment |
| Discounting discipline | Discount approval governance | Tiered approval thresholds, exception log |
| Pricing review cadence | How often pricing is reviewed | Quarterly review, documented decisions |
The 20% rule and why it matters
The 20% rule says that the top-decile customer (by ARR) should be paying approximately 20% more than the median customer for an equivalent product configuration. The premium is the observable test of whether the founder has built the architecture for value capture — premium tiers, value-add modules, enterprise pricing layers — or has been holding pricing flat to avoid customer-success conversations. Customers in the top decile typically extract 3-5× the value of median customers; the 20% pricing premium captures a fraction of that value differential and signals that the architecture has the room to capture more.
Partners read the customer pricing distribution directly from the contract data. Founders who have not built the dispersion before the data-room exposure cannot fix it in time for the diligence cycle. The work is a 6-12 month effort done before the round, not during it.
Annual price increases — the discipline
Annual increases of 5-15% should be a standard contract clause and a standard operating practice. The discipline has three properties: the increase is communicated 60-90 days in advance with a clear value-justification message, the customer-success organisation handles the conversations and expects them, and the churn impact is measured cohort-by-cohort over the two quarters following the increase. Founders who have run the cycle for two consecutive years, with measurable churn impact under 1%, have demonstrated pricing power partners can underwrite. Founders who have never raised prices on the existing base have an asset they have not tested, which the partner discounts.
How to apply it to your round
The pricing architecture is one of the asset components that compounds for 12-18 months before showing up cleanly in the metrics. The work has to start well before the Series B raise.
Audit the current architecture. Map the customer pricing distribution. Calculate the top-decile vs median premium. List the tiers and the gaps. Look at the tier-upgrade flow over the last four quarters. The audit usually surfaces 2-3 specific gaps that explain the metric profile.
Build the 20% premium. If the top-decile customer is currently paying within 5% of the median, build the premium tier(s) the architecture is missing. The most common gap is an enterprise tier with security, governance, or support features the largest customers actually need but cannot currently buy at premium.
Run the annual increase cycle. If the cycle has never run, the first increase is the hardest. Choose a 5-7% target rather than a 10-15% one for the first year; build the customer-success conversation discipline; measure the cohort impact carefully. By year two, the convention is established and the 10-15% increase becomes operationally straightforward.
Connect to the underlying drivers. Pricing power is its own intangible asset in The Opagio 12. The drivers behind it include brand and reputation (premium pricing requires brand support), customer capital (depth of the customer relationship that survives the increase), switching costs (the architectural lock-in that makes the alternative more expensive), and Organisational Knowledge (the customer-success discipline that runs the cycle).
Pricing architecture that fails diligence
- One or two tiers with minimal gaps
- Customer pricing distribution is flat
- No standard annual-increase clause
- Heavy discounting without discipline
- Pricing reviewed infrequently or never
Pricing architecture that earns the round
- 3 tiers with meaningful capability gaps
- Top-decile customer ~20% above median
- 5-15% annual increase tested in the base
- Discount governance with approval thresholds
- Quarterly pricing review cadence with exec sign-off
The Bottom Line
Pricing is an architecture, an operating practice, and an intangible asset all at once. The Series B-grade architecture has three tiers, a 20% top-decile-vs-median premium, an annual-increase cycle that runs without measurable churn impact, and discounting governance that survives diligence. Partners verify each from the data room in an afternoon. Founders who treat pricing as a one-time decision rather than a continuous operating practice present a static asset; founders who treat it as architecture present a compound one.
Related reading
Pricing architecture sits at the intersection of the expansion motion and the metric headlines. For the operating motion that uses the architecture: building the expansion motion before Series B. For the retention metric the architecture supports: from 108% to 128% NRR. For the broader Series B bar: the Series B efficiency bar in 2025. For the underlying pricing-power driver among The Opagio 12: The Opagio 12 value drivers. For how pricing architecture shows up in the valuation conversation: why 70% of your valuation is intangible. For the bridge-round implications when pricing power is the binding constraint: the runway math that determines your bridge size.
Build the pricing architecture before the round opens
Eight minutes. Twelve drivers. The starting view of how your pricing power sits as a Series B-grade intangible asset — and which adjacent drivers compound the value-capture.