Expert responses
The PM — Product Manager
Hybrid pricing is your only viable path to fix churn and unlock expansion without chaos.
Here's my read: stay with per-seat as your primary model, but layer in a usage-based expansion component immediately. The hybrid approach is your play, and it's not a compromise—it's the only model that actually solves your immediate problem while protecting your revenue base. Let me be direct about what the pushback really means. When customers push back on seat counts at renewal, they're not saying "we want usage-based pricing." They're saying "we're not getting value proportional to the number of people we're paying for." That's a different problem than the pricing model itself. A pure usage-based switch won't fix that—it'll just shift the pain to a different metric and create new friction. --- Per-Seat (Status Quo) Key advantage: Predictability. You know your MRR, you can forecast, your sales team can close deals in a day. At $5M ARR, this is real oxygen. Key risk: You're already seeing it. Customers will either churn at renewal, negotiate aggressively, or find a workaround (shared logins, feature hoarding). The market data is stark—per-seat-only models now face 2.3× higher churn. That's not noise; that's a structural problem. Who it's best for: Teams with low feature adoption variance and highly predictable seat growth. If your customers' seat counts correlate tightly with their business outcomes, this works. If they don't, you're fighting gravity. Score: 4/10 — You're already experiencing the failure mode. Staying here means accepting higher churn and slower expansion revenue. --- Pure Usage-Based Key advantage: Alignment. Customers pay for what they use. No seat-count arguments. Expansion is theoretically unlimited. Key risk: This is where I'd pump the brakes hard. Usage-based pricing requires three things you likely don't have yet: (1) a product where usage correlates cleanly to customer value, (2) customers comfortable with variable bills (enterprise buyers hate this), and (3) operational maturity to track, bill, and support metered consumption. At $5M ARR, you're not there yet. You'll also face a 6-12 month transition period where your revenue becomes unpredictable, your sales team loses the ability to close deals, and customers will either over-consume to "get their money's worth" or under-consume and feel resentful. The data shows usage-based excels in expansion for AI/infrastructure but offers lower predictability than per-seat. For a company at your stage, that's a real problem. Who it's best for: Mature SaaS companies ($20M+ ARR) with infrastructure/API products where usage is the actual value metric, or companies with strong product-market fit and predictable consumption patterns. Score: 3/10 — Too much operational risk and revenue volatility for where you are. You'd be solving a customer problem by creating a business problem. --- Hybrid (Per-Seat + Usage-Based Expansion) Key advantage: You keep the revenue predictability of per-seat (customers budget for X seats), but you capture expansion when they actually use more value. Customers feel the pricing is fair because they only pay extra when they genuinely get more value. This is where 61% of B2B SaaS is moving, and the market data backs it: hybrid models drive higher expansion revenue without the churn penalty of pure usage-based. How it works in practice: Tier your base price on seats (e.g., $5K/month for 10 seats), then layer on a usage metric that only charges when they exceed expected consumption. Example: "Your plan includes 10,000 API calls/month. Additional calls are $0.10 each." Or: "Your plan includes 5 power users. Each additional power user is $500/month." Key risk: Pricing complexity. You now have two levers to tune, and you need to get the ratio right. If your usage component is too aggressive, customers feel nickel-and-dimed. If it's too generous, you leave money on the table. You also need to instrument your product to track the usage metric reliably—if your billing system can't track it accurately, you'll have disputes. Who it's best for: B2B SaaS companies at $2M–$50M ARR with products where some customers use significantly more than others. This is you. Score: 8/10 — Solves your immediate churn problem, maintains revenue predictability, and opens an expansion channel. The operational lift is real but manageable. --- My Recommendation Implement a hybrid model over the next 12 months, structured in two phases: Phase 1 (Months 1–3): Add a usage-based expansion layer to your existing per-seat model. Pick ONE usage metric that correlates to customer value and is easy to measure (API calls, documents processed, users activated, whatever your product does). Grandfather existing customers into their current per-seat pricing, but offer them the option to add the usage tier if they want. This removes the negotiation friction at renewal without forcing a migration. Phase 2 (Months 4–12): Migrate new customers to the hybrid model from day one. Your sales team quotes per-seat + usage tier together. Existing customers can migrate at renewal if they want, but don't force it. This gives you a 12-month runway to see how the model performs before you make any hard decisions. Why this works: You keep your revenue predictability (seats are still your anchor). You capture expansion revenue from high-usage customers (the ones who'd otherwise push back). You reduce churn because customers feel the pricing is fair (they only pay extra when they use more). You buy time to understand your usage patterns before committing to a pure usage-based model. Your sales team can still close deals quickly (seats are the primary number). The single strongest reason: You're at the inflection point where per-seat alone is starting to leak revenue, but you're not mature enough for pure usage-based. Hybrid is the bridge. It solves your customer satisfaction problem and your revenue growth problem without creating operational chaos. The companies that are winning right now aren't choosing between these models—they're layering them. Do that.
The Sales Leader — Chief Revenue Officer
Adopt a hybrid pricing model now to unlock expansion revenue and end seat-based renewal fights.
The pushback you're getting on seat counts isn't just a renewal problem; it's a flashing red light that your pricing is no longer aligned with the value you deliver. At $5M ARR, you've exhausted the easy per-seat growth. Continuing with it is like trying to drive a sports car with the parking brake on. It's safe, predictable, and throttling your real potential. Here's my breakdown of your options for the next 12 months. Option 1: Maintain Per-Seat Pricing Key Advantage: It’s simple and predictable. Your finance team loves it because they can build a forecast that's accurate. Your reps know how to sell it. There's zero operational lift. Key Risk: You are actively incentivizing your customers to use your product less. They'll share logins, be selective about who gets a seat, and fight you on every renewal to keep costs down. You are leaving a massive amount of expansion revenue on the table and creating unnecessary friction with your best customers. Who It's Best For: Companies where value is unequivocally tied to individual human interaction, like a project management tool. If adding a user has a direct, linear, and obvious impact on the value for everyone else, it works. For most modern SaaS, this is an outdated model. Score: 4/10. It got you to $5M, but it won't get you to $20M. It's the path of least resistance and lowest growth. Option 2: Switch to Pure Usage-Based Pricing Key Advantage: This is the most purely aligned model with customer value. Customers only pay for what they consume, which removes the barrier to entry and encourages wall-to-wall adoption. It's the engine behind every great product-led growth story. When a customer's business grows using your tool, your revenue grows with them, automatically. Key Risk: Revenue forecasting becomes a nightmare. Your revenue can swing wildly month-to-month based on customer consumption, which will make your CFO and your board extremely uncomfortable. It also requires a significant investment in metering and billing infrastructure. If you pick the wrong value metric to charge on (e.g., API calls vs. records processed), you'll kill adoption and misalign your price all over again. Who It's Best For: Infrastructure products or APIs where a single, scalable metric is the core of the product (think Twilio, Stripe, Snowflake). It's a high-risk, high-reward play that requires operational excellence. Score: 6/10. It's the right long-term direction philosophically, but jumping straight into it is a massive, risky operational shock for a company your size. Option 3: Adopt a Hybrid Model (Recommended) Key Advantage: It's the pragmatic solution that solves your core problem without taking on existential risk. You keep a predictable base revenue stream (via a platform fee or a base package of seats/usage) and add a usage-based component on top. This gives you the best of both worlds: forecastability for finance and expansion upside for sales. It immediately reframes renewal conversations from "how many seats can we cut?" to "look at the value you're getting." Key Risk: It introduces complexity. You have to be crystal clear in how you communicate it, or you'll confuse customers and your sales team. You still need to build the metering capability, but you can roll it out more gradually. You risk creating a "Frankenstein" model if you make it too complicated. Who It's Best For: The vast majority of B2B SaaS companies, especially those transitioning from a seat-based model. It's the perfect way to capture value from your highest-consuming customers while keeping a stable revenue base from the rest of the cohort. Score: 9/10. This is the move I've seen work a hundred times at your stage. My Recommendation Adopt a hybrid model within the next two quarters. Start by defining a clear value metric that isn't a user seat. Is it projects created? Reports run? Data processed? Once you have that, structure a simple hybrid model: Keep your existing tiers, but redefine them. Instead of just seats, each tier now includes a generous allowance of your new value metric (e.g., the Pro plan includes 10 seats and 1,000 reports per month). Add a usage-based overage fee. If a customer exceeds their allowance, they pay a small, clear price for additional consumption. Grandfather existing customers for a limited time to ease the transition, but move all new business to this model immediately. This approach de-risks the change. It maintains your predictable base, immediately solves the seat-based renewal fights, and creates a natural, frictionless expansion path. Your best customers will start paying you more without a single conversation, because they're simply using the product more. Here's the one thing to remember: Your pricing model is a feature of your product. Right now, that feature is creating friction. A hybrid model turns it into an engine for growth.
The Skeptic — Risk Assessor
Switching pricing models without understanding why customers resist is a gamble that risks revenue and trust.
Here's the thing that should keep you up at night: you don't actually know why customers are pushing back on seat counts. That's the fatal gap in this entire question. "Customers push back on seat counts at renewal" could mean five completely different things — they have shelfware and can't justify the spend, they're consolidating headcount, they think the per-seat price is too high for light users, they're using it as a negotiation tactic, or they genuinely don't see value proportional to what they're paying. Each of those root causes points to a different pricing fix. Switching models without diagnosing the disease is like changing antibiotics because the patient has a fever — you might accidentally be right, but the odds aren't great. That said, let me stress-test all three options against the failure modes I'd expect at $5M ARR. --- Option 1: Maintain Per-Seat Pricing (Status Quo) Key advantage: Operational simplicity and revenue predictability. You know what a renewal looks like. Your finance team can forecast. Your sales comp is straightforward. Key risk: Death by a thousand cuts. If seat-count pushback is a proxy for "we don't see enough value," you're watching a slow churn spiral. At $5M ARR, losing even 5-8% of your base to downgrades compounds fast — that's $250-400K in contraction you have to replace just to stay flat. Who it's best for: Companies where the pushback is tactical (customers negotiating for discounts) rather than structural (customers genuinely have too many unused seats). Score: 4/10. You're already telling me there's friction. Doing nothing is a bet that the friction doesn't get worse. That's a bet I wouldn't take. --- Option 2: Switch to Pure Usage-Based Pricing Key advantage: Directly addresses the "I'm paying for seats I don't use" complaint. Aligns cost to value. OpenView data shows 18-23% higher net revenue retention and 34% faster land-and-expand for usage-based companies. Key risk — and this is the big one: Revenue volatility will wreck your planning at $5M ARR. You don't have the scale to absorb the variance. Pure UBP companies report that 73% struggle with revenue forecasting. At your size, a bad quarter of usage dips could mean missing payroll targets or cutting growth investment. Worse, the operational lift is enormous — you need metering infrastructure, real-time billing, usage dashboards for customers, and a completely retrained sales team that sells on value metrics instead of headcount. That's a 6-9 month build at minimum, and you'll be executing a pricing migration and a systems migration simultaneously. Here's the failure sequence I see: You announce the switch. Implementation takes longer than expected. Customers get confused bills during the transition. Your best customers — the heavy users — suddenly see higher bills than before and scream. Your light users pay less, which is great for them but terrible for your revenue. Net effect: you traded seat-count complaints for usage-spike complaints, and your ARR dips 10-15% during the transition year. Who it's best for: Companies at $20M+ ARR with engineering resources to build metering, or companies whose product has a natural, easily understood consumption metric (API calls, data processed, messages sent). Score: 3/10. The execution risk at your scale is too high, and the 12-month timeline is too short to absorb the transition costs. --- Option 3: Hybrid Model (Platform Fee + Usage or Tiered Seats + Usage Overages) Key advantage: This is where the market is moving — 61% of SaaS companies now use some hybrid structure, up from 49% in 2024. Hybrid companies show the highest median growth at 21%. You keep a predictable base (protecting your floor) while adding a usage component that lets heavy users expand naturally and light users feel less gouged. Key risk: Complexity. You're now explaining two pricing dimensions to buyers. Your sales team needs to model scenarios. Your billing system needs to handle both. And here's the specific failure mode: if you set the platform fee too high, customers see it as a price increase disguised as a model change. If you set it too low, you cannibalize your existing ARR. The calibration is brutally hard to get right on the first try, and at $5M ARR, you probably get one shot before customer trust erodes. Additional risk: You still haven't told me what the usage metric would be. "Usage" is not a pricing model — it's a category. The metric has to be something customers can predict, understand, and control. If it's opaque or spiky, you'll generate the same renewal friction you have now, just in a different flavor. Who it's best for: Companies with a clear, measurable value metric that customers already understand, and enough engineering capacity to instrument billing within 3-4 months. Score: 6/10. Best of the three, but only if you can identify the right usage metric and calibrate the base fee correctly. Those are big "ifs." --- My Recommendation Hybrid — but not yet, and not the way you're probably thinking about it. Here's what I'd actually do in the next 12 months: Months 1-3: Don't touch the pricing model. Instead, instrument your product to understand actual usage patterns. Find out which customers are pushing back and why. Segment them: shelfware customers, light users, negotiation tacticians, genuinely dissatisfied. You need this data before you make any structural change. Months 3-6: Introduce a tiered per-seat model as a bridge — something like "light user" and "full user" seat types at different price points. This directly addresses the most common complaint (paying full price for occasional users) without requiring new billing infrastructure. It's operationally simple and buys you time. Months 6-12: If the data supports it, layer in a usage component on top of the tiered seats for your highest-value features. This is your hybrid, but you're building it on evidence, not assumptions.
The Customer — User Voice
Hybrid pricing kills unused-seat resentment and keeps budgets predictable—stop nickel-and-diming me.
I've been the person sitting across the Zoom screen during those painful renewals. Last year, I canceled a $15,000 subscription because we were paying for 50 seats, but only my core team of eight logged in every week. The account rep kept trying to show me "feature adoption reports," but all I felt was resentment. I was paying for empty chairs, and every invoice felt like a penalty. When your customers are pushing back on seats, what they are actually saying is: "I do not feel like I am getting the value I am paying for." Here is how I experience your three options from the other side of the invoice: 1. Maintain Per-Seat Pricing Key Advantage: Predictability. I know exactly what I'm paying, which my finance team loves. Key Risk: Churn from resentment. When my usage drops but my bill doesn't, I feel cheated. Every unused seat is a daily reminder to cancel. Best For: Core utilities that absolutely every single employee must open every day (like email). Score: 3/10. You are already feeling the pushback. Ignoring it is how you lose me. 2. Switch to Pure Usage-Based Key Advantage: Total fairness. I only pay for what my team actually consumes. Key Risk: Billing terror. I tried a pure usage-based data tool once, and our bill spiked 400% in one month because a junior rep accidentally ran a massive export. I immediately locked down team permissions, which killed our adoption of the product entirely. Best For: Developer infrastructure or purely transactional products (like sending SMS). Score: 5/10. It fixes the empty-chair problem but makes my finance department nervous. 3. Adopt a Hybrid Model (Base + Usage) Key Advantage: It aligns with reality. Charge me a reasonable base rate for access so my casual users can look around, and tie the variable cost to the heavy lifting my power users do. Key Risk: Confusion. If I have to bust out a calculator to understand your pricing page, I will close the tab. Best For: Products where a few power users drive 90% of the value. Score: 9/10. My Recommendation: Adopt a Hybrid Model. Give me a flat platform fee that includes unlimited (or highly bundled) basic viewing access, and charge me based on the actual value or heavy actions my power users consume. The strongest reason? It instantly kills the "unused seat" resentment while keeping a predictable floor for my budget. When I don't feel like you are nickel-and-diming me for every new intern who needs a login, we stop arguing about licenses and go back to talking about the actual work. — The Customer · Analyzed by SynthBoard.ai
The CFO — Financial Controller
Hybrid pricing blends revenue stability with value capture and reduces churn risk better than pure seat or usage models.
Per-Seat (status quo) Key advantage: Predictable billing; easy for finance and sales to quote. Key risk: Renewal friction—30-40 % of customers negotiate seat cuts, typically eroding 8-12 % ACV. Who it’s best for: High-engagement users where value correlates with individual log-ins (e.g., CRM seats). Pros • Revenue stability: 90 %+ of ARR locked in under annual contracts (confidence 0.8). • Low ops burden: no metering build-out; GTM motion already trained. Cons • Customer satisfaction: NPS drags when CFOs see “shelf seats” (prob. 0.6 that churn ticks up 2-3 pts). • Growth ceiling: seat growth tied to head-count; many clients in hiring freezes—expected seat CAGR just 5 % (vs. 12 % company target). Score: 6/10 Usage-Based (UBP) Key advantage: Aligns price with realized value; reduces renewal battles. Key risk: Volatility—logo retention may stay flat while revenue per logo swings ±25 %. Who it’s best for: Workflow or API products where transactions/events are the core value unit. Pros • Upside: Top quartile UBP SaaS firms grew 30-40 % faster than seat-based peers in 2023 (source: OpenView). Even a modest 15 % lift would add ~$750k ARR (p=0.4). • Customer perception: “Pay for what you use” scores 8–10 % higher in CSAT surveys (p=0.7). Cons • Implementation: Metering, billing, rev-rec rules—expect 4–6 mo engineering + $200-300k cost. • Cash-flow risk: 20 % probability that heavy users optimize consumption, cutting ARR by >10 %. Score: 7/10 Hybrid (base seats + usage tier or minimum commit + variable overage) Key advantage: Blends predictability with value alignment. Key risk: Complexity can confuse buyers if not messaged crisply. Who it’s best for: Mid-market/enterprise accounts with diverse user intensity. Pros • Revenue resilience: Minimum commit preserves ~85 % of current ARR; variable tail captures upsell. Expected ARR lift 10 %, downside capped at 5 % (EV ≈ +$250k). • Negotiation tool: Lets CSMs trade variable discounts instead of chopping seats—early pilots often cut churn by 1–2 pts (p=0.6). • Ops feasibility: Can layer usage meter on top of existing seat SKUs; 2-3 mo dev window. Cons • Sales enablement: Requires tight packaging and clear collateral; risk of sales rep confusion (p=0.5). • Finance: More complicated forecasting, though still easier than pure UBP. Score: 8/10 Recommendation Shift to a hybrid model for the next 12 months. It preserves 85–90 % of today’s cash-generating base while giving you a controlled experiment in value-based pricing—and you can ship it before Q3 renewals hit. If it underperforms, you still have a defensible per-seat floor; if it overperforms, you’ve paved the road to full usage-based later. Single takeaway: Keep the predictable base, but let customers buy incremental value rather than argue over empty seats—hybrid delivers that balance.
