Problem Definition
CloudPeak is a B2B SaaS company generating $85 million in annual recurring revenue (ARR) from 1,200 customers. The company provides supply chain visibility software that helps manufacturers and logistics firms track shipments, manage inventory, and optimize procurement across their supply networks.
The company currently prices on a per-seat basis at $150 per user per month. However, the competitive landscape is shifting: newer entrants are gaining market share with usage-based pricing models that charge per transaction processed through the platform. CloudPeak's CEO argues that transitioning to usage-based pricing at $0.10 per transaction would lower the barrier to entry for new customers and allow revenue to expand naturally as customers increase platform usage. The CFO counters that early pilot data shows significant revenue redistribution risk across customer segments.
Pilot results indicate that 30% of customers would pay more under usage-based pricing, 45% would pay less, and 25% would see roughly equivalent costs. Net revenue retention currently stands at 108% under the per-seat model. The board has hired your team to recommend the optimal pricing strategy: full transition to usage-based, a hybrid model, or maintaining per-seat pricing. What is your recommendation and why?
Additional InformationAsk for more dataHide data
- CloudPeak was founded in 2016 and has been growing at ~22% YoY
- The product processes supply chain events (shipment updates, inventory changes, PO confirmations) as "transactions"
- Average contract length is 24 months for enterprise, 12 months for mid-market and SMB
- Switching costs are high for enterprise (6-9 month implementation) but low for SMB (2-4 weeks)
- The company completed a Series D round 18 months ago and is targeting IPO readiness within 2 years
- Customer acquisition cost (CAC) payback is 18 months for enterprise, 14 months for mid-market, and 22 months for SMB
- Sales team compensation is currently based on annual contract value (ACV)
- Product usage data is available at the customer level going back 3 years
Question 1Structuring
"How would you structure your approach to evaluating CloudPeak's pricing transition decision?"
Hint · Structuring
Build 3–4 branches that are specific to this client and question, not a generic framework. Check they don't overlap and together cover the problem.
Additional InformationAsk for more dataHide data
Provide if the candidate asks:
- No regulatory constraints on pricing model changes
- Current billing infrastructure can support both per-seat and usage-based pricing
- CloudPeak has not tested usage-based pricing with enterprise accounts yet; pilot was mid-market and SMB only
- Competitors have not changed pricing in the last 12 months
Try it first, then checkShow model answerHide model answer
A strong framework would include:
1. Revenue Impact by Segment
- Map the 30/45/25 pricing impact against revenue concentration by segment
- Calculate effective price per transaction under current vs. proposed model
- Model revenue scenarios with and without churn adjustments
2. Customer Retention and Expansion Risk
- Assess switching costs and contract lock-in by segment
- Determine which segments drive the 108% NRR and protect them
- Evaluate how price changes affect renewal rates and expansion revenue
3. Competitive Dynamics
- Benchmark against competitor pricing models, growth rates, and NRR
- Identify where CloudPeak is losing deals due to pricing structure vs. product gaps
- Assess pricing headroom given competitor price points
4. Implementation and Strategic Fit
- Evaluate operational readiness (billing, sales compensation, contract terms)
- Assess impact on IPO narrative (ARR predictability vs. growth rate)
- Design migration path that minimizes disruption to high-value accounts
What the interviewer is looking forShow guidanceHide guidance
Good (3): Candidate identifies revenue impact analysis, customer segmentation, and competitive positioning as key areas. Uses a generic pricing framework (e.g., value-based pricing, willingness-to-pay) without adapting to the SaaS-specific context. Mentions customer retention but does not connect it to revenue concentration.
- Level 1: "We should look at how revenue changes under each model."
- Level 2: "The revenue shift matters because some segments contribute disproportionately."
Strong (4): Candidate structures around three pillars: (1) Revenue impact by customer segment, (2) Customer behavior and retention risk, (3) Competitive and market dynamics. Recognizes that the 30/45/25 split needs to be mapped against revenue contribution, not just customer count. Identifies sales incentive alignment and contract migration as operational considerations.
- Level 2: "The 45% who pay less might include our highest-value accounts."
- Level 3: "We need to identify exactly which segments fall into each bucket and weight the revenue impact accordingly before modeling scenarios."
Excellent (5): Candidate adds a fourth dimension: (4) Strategic positioning for IPO. Explicitly calls out that customer COUNT percentages are meaningless without REVENUE-WEIGHTED analysis. Identifies the tension between a growth narrative (usage-based = land-and-expand) and a profitability narrative (per-seat = predictable ARR) in the context of IPO readiness. Notes that protecting the 108% NRR is a constraint, not just a metric.
- Level 3: "The IPO story needs both predictable ARR from the base and a growth lever for expansion. A single pricing model forces us to choose one narrative; a segmented model lets us tell both."
Question 2Numeracy
"Using the data in Exhibit 1, calculate the revenue impact of transitioning all customers to usage-based pricing at $0.10 per transaction. Then estimate the adjusted impact assuming a 15% churn risk among enterprise customers due to the pricing change."
Hint · Numeracy
Write the formula before you plug in numbers, keep units and zeros explicit, and sanity-check the order of magnitude at the end.
Exhibit 1Customer Segment Analysis
| Metric | Enterprise | Mid-Market | SMB |
|---|---|---|---|
| Number of customers | 150 | 270 | 780 |
| % of total customers | 12.5% | 22.5% | 65.0% |
| Annual revenue | $45.0M | $24.3M | $15.6M |
| % of total revenue | 53% | 29% | 18% |
| Avg seats per customer | 167 | 50 | 11 |
| Avg monthly transactions | 200,000 | 75,000 | 25,000 |
| Transactions per seat per month | 1,198 | 1,500 | 2,273 |
| Annual logo churn | 3% | 8% | 18% |
| Net revenue retention (NRR) | 120% | 102% | 85% |
| Avg contract length | 24 months | 12 months | 12 months |
Source: CloudPeak case file
Exhibit 2Competitive Pricing Landscape
| Company | Pricing Model | Price Point | Primary Segment | YoY Revenue Growth | NRR |
|---|---|---|---|---|---|
| TrackFlow | Usage-based | $0.08/txn | SMB, Mid-Market | 45% | 115% |
| SupplyVue | Per-seat | $175/user/month | Enterprise | 18% | 130% |
| ChainSync | Hybrid | $1K/mo + $0.06/txn | Mid-Market | 32% | 108% |
| LogiTrack | Freemium + usage | $0.12/txn (paid tier) | SMB | 65% | 95% |
| CloudPeak | Per-seat | $150/user/month | All segments | 22% | 108% |
Source: CloudPeak case file
Try it first, then checkShow model answerHide model answer
Calculation Tables
Step 1: Calculate current effective cost per transaction by segment
| Segment | Current ARR per Customer | Annual Transactions (Monthly x 12) | Effective $/Transaction |
|---|---|---|---|
| Enterprise | $300,000 | 200,000 x 12 = 2,400,000 | $0.125 |
| Mid-Market | $90,000 | 75,000 x 12 = 900,000 | $0.100 |
| SMB | $20,000 | 25,000 x 12 = 300,000 | $0.067 |
Insight: Enterprise customers currently pay the MOST per transaction ($0.125), meaning they overpay relative to usage. SMBs pay the LEAST ($0.067), meaning they underpay relative to usage. Usage-based pricing at $0.10 reprices both segments toward their actual consumption.
Step 2: Calculate new ARR under usage-based pricing ($0.10/transaction)
| Segment | Customers | Annual Txn per Customer | New ARR per Customer | Segment Revenue | Current Revenue | Delta |
|---|---|---|---|---|---|---|
| Enterprise | 150 | 2,400,000 | $240,000 | $36.0M | $45.0M | -$9.0M |
| Mid-Market | 270 | 900,000 | $90,000 | $24.3M | $24.3M | $0.0M |
| SMB | 780 | 300,000 | $30,000 | $23.4M | $15.6M | +$7.8M |
| Total | 1,200 | $83.7M | $84.9M | -$1.2M |
Net revenue impact: -$1.2M (-1.4%). The aggregate appears nearly neutral.
Step 3: Adjust for enterprise churn risk (15%)
| Metric | Calculation | Result |
|---|---|---|
| Churned enterprise customers | 150 x 15% | 23 |
| Remaining enterprise customers | 150 - 23 | 127 |
| Adjusted enterprise revenue | 127 x $240,000 | $30.5M |
| Adjusted total revenue | $30.5M + $24.3M + $23.4M | $78.2M |
| Revenue loss vs. current | $84.9M - $78.2M | -$6.7M (-7.9%) |
The "nearly neutral" -1.4% aggregate masks a -7.9% risk-adjusted loss when accounting for enterprise churn. Reality check: a $6.7M revenue loss would erase roughly 8% of ARR and significantly damage the IPO trajectory.
What the interviewer is looking forShow guidanceHide guidance
Good (3): Correctly calculates new ARR per segment under usage-based pricing and arrives at the aggregate -$1.2M impact. Notes that enterprise loses revenue while SMB gains.
Strong (4): Calculates effective cost per transaction first to explain WHY segments are affected differently. Completes the churn adjustment to identify the -$6.7M risk-adjusted loss. Notes that aggregate neutrality is misleading because the loss and gain come from different segments with different strategic value.
Excellent (5): Additionally observes that each churned enterprise customer ($240K new ARR) requires 8 new SMB customers ($30K each) to replace, making the replacement math extremely unfavorable. Points out that 15% enterprise churn may be conservative given that TrackFlow (Exhibit 2) offers $0.08/txn, undercutting CloudPeak's proposed $0.10 rate. Flags that lost enterprise customers also take their 120% NRR with them, meaning the Year 2 revenue impact compounds far beyond the Year 1 loss.
Question 3Judgement & Insights
"Looking at Exhibits 2 and 3, what insights can you draw about the competitive landscape and CloudPeak's usage growth trends? How should these inform the pricing decision?"
Hint · Judgement & Insights
Read the exhibit title, axes and units first. Lead with the ‘so what’, then back it with one or two numbers.
Exhibit 3CloudPeak Quarterly Usage and Customer Trends
| Quarter | Enterprise Txn Growth | Mid-Market Txn Growth | SMB Txn Growth | New Logos | Churned Logos | Net New |
|---|---|---|---|---|---|---|
| Q1 2025 | +2% | +4% | +8% | 45 | 38 | +7 |
| Q2 2025 | +3% | +5% | +12% | 52 | 42 | +10 |
| Q3 2025 | +2% | +6% | +10% | 48 | 45 | +3 |
| Q4 2025 | +3% | +4% | +15% | 55 | 40 | +15 |
Transaction growth figures represent quarter-over-quarter change in average monthly transactions per customer.
Source: CloudPeak case file
Try it first, then checkShow model answerHide model answer
From Exhibit 2 (Competitive Landscape):
- Usage-based models correlate with higher growth but NOT necessarily higher NRR
- TrackFlow's $0.08/txn creates a pricing floor that constrains CloudPeak's usage-based options
- SupplyVue proves that per-seat pricing can deliver exceptional retention (130% NRR) in enterprise
- ChainSync's hybrid model produces moderate growth (32%) with CloudPeak-equivalent NRR (108%)
From Exhibit 3 (Usage Trends):
- SMB transaction growth is accelerating (8% to 15% QoQ) but the SMB segment has highest churn
- Enterprise transaction growth is stable but modest (2-3% QoQ), indicating mature usage patterns
- Net new logos are volatile: Q3 saw only +3 net new customers despite 48 new logos acquired
- High-churn quarters nearly offset acquisition, suggesting a retention problem rather than a pricing problem
Strategic implication: The data does NOT support a full usage-based transition. It supports protecting enterprise economics (stable, high-NRR, low-churn) while selectively using usage-based pricing as an acquisition tool for new SMB customers.
What the interviewer is looking forShow guidanceHide guidance
Good (3): Candidate notes that usage-based competitors grow faster (TrackFlow 45%, LogiTrack 65% vs. CloudPeak 22%) and that SMB transaction growth is accelerating. Concludes that CloudPeak should adopt usage-based pricing to match competitive growth rates.
- Level 1: "Usage-based competitors are growing faster, so CloudPeak should follow suit."
Strong (4): Candidate distinguishes between growth rate and growth quality. Notes that LogiTrack has the highest growth (65%) but the lowest NRR (95%), indicating a leaky-bucket model. SupplyVue has the highest NRR (130%) despite being per-seat and the slowest growth (18%). Observes that CloudPeak's net new logos are volatile (Q3 nearly flat at net +3) and that the 18% annual SMB churn rate means the segment benefiting most from usage-based pricing is also the most prone to leaving.
- Level 2: "High growth with low NRR is a treadmill, not a strategy. LogiTrack acquires fast but retains poorly."
- Level 3: "We should benchmark against SupplyVue's retention model for enterprise and TrackFlow's acquisition model for SMB, not try to copy one competitor's entire approach."
Excellent (5): Adds that TrackFlow at $0.08/txn creates a pricing ceiling: CloudPeak cannot price usage above $0.10 without being uncompetitive, but at $0.10 enterprise customers would already save 20%. Enterprise customers might still leave for TrackFlow to save even more, making the 15% churn estimate conservative. Notes that SMB transaction growth (8-15% quarterly in Exhibit 3) combined with 18% annual SMB churn (Exhibit 1) suggests that many SMBs grow usage rapidly before churning, meaning usage-based pricing would briefly capture higher revenue from power users before they leave rather than building durable relationships. Also flags that SMB CAC payback (22 months) exceeds average SMB contract length (12 months), meaning CloudPeak already loses money on many SMBs before the pricing change.
- Level 3: "The data says: protect enterprise economics, fix SMB unit economics before scaling SMB acquisition, and use usage-based pricing as a landing mechanism for new customers rather than a repricing of the existing base."
Question 4Synthesis
"Based on your analysis, what is your final recommendation to CloudPeak's board?"
Hint · Synthesis
Answer first: the recommendation, two or three reasons with numbers, then risks and next steps.
Try it first, then checkShow model answerHide model answer
Recommendation: Segmented pricing strategy with phased implementation
Tier 1 -- Enterprise (protect the base):
- Maintain per-seat pricing at $150/user/month
- Protects $45M revenue (53% of ARR) and 120% NRR
- Enterprise switching costs (6-9 months) provide a natural retention buffer
- If enterprise customers request usage-based pricing, offer it with contractual minimum commits at or above current spend
Tier 2 -- Mid-Market (offer flexibility):
- Allow customers to choose per-seat or usage-based at renewal
- Most mid-market customers are roughly revenue-neutral either way (~$90K ARR)
- Optionality becomes a competitive differentiator against rigid competitors
Tier 3 -- SMB (drive growth):
- All new SMB customers on usage-based pricing at $0.10/transaction
- Existing SMB customers grandfathered for one contract cycle (12 months)
- Lower barrier to entry should improve the 22-month CAC payback, currently the worst segment
IPO narrative: "Predictable enterprise ARR base with a high-growth, usage-based expansion engine" -- a stronger story than either pure model alone.
Key risks to monitor:
- Enterprise competitive losses (TrackFlow at $0.08/txn threatens at-scale accounts)
- SMB churn rate under usage-based pricing (does it improve retention or accelerate churn?)
- Mid-market self-selection (are profitable mid-market customers choosing the cheaper model?)
- Sales compensation alignment (usage-based SMB deals require different incentive structures than enterprise ACV quotas)
Contributed by CaseDrill practice community
What the interviewer is looking forShow guidanceHide guidance
Good (3): Recommends a segmented approach (enterprise stays per-seat, SMB goes usage-based) with basic rationale around revenue protection. Mentions implementation considerations like contract migration timing.
Strong (4): Recommends a segmented strategy with three tiers and quantifies the impact: (1) Enterprise maintains per-seat to protect $45M and 120% NRR, (2) Mid-market offered a choice between models at renewal since they are roughly revenue-neutral, (3) New SMB customers priced usage-based to lower acquisition barriers while existing SMBs are grandfathered for one contract cycle. Addresses the IPO angle: per-seat enterprise preserves ARR predictability while usage-based SMBs demonstrate a growth lever for the equity story.
Excellent (5): Quantifies the upside case: if usage-based pricing increases new SMB logo acquisition by 30% (from ~40 SMBs/quarter to ~52/quarter), net of 18% annual churn, the company adds ~50 net new SMBs per year at $30K ARR = $1.5M incremental ARR in Year 1, growing as usage expands. Combines this with the protected enterprise base of $45M (growing at 120% NRR to $54M in Year 2) to model a path to $95M+ ARR. Identifies execution risks: sales compensation must be redesigned for usage-based SMB deals, mid-market self-selection must be monitored to prevent profitable customers from choosing the cheaper model, and enterprise competitive losses to TrackFlow require quarterly tracking. Proposes contractual usage floors if enterprise customers eventually request usage-based pricing, ensuring no downside below their current spend.