How Smriti Irani's New SaaS Comparison Nearly Broke A Team
— 6 min read
Answer: Smriti Irani’s fresh SaaS comparison exposed a hidden pricing flaw that threatened to break the team’s growth plans, forcing a rapid redesign of their billing model.
In the scramble that followed, the company realized that old per-seat contracts were capping revenue, and the new approach reshaped how they think about pricing.
In 2022, a routine client expansion request revealed a critical flaw in the billing system, prompting an urgent audit of the company’s per-seat pricing structure.
The Day Their Old SaaS Pricing Models Failed
When the quarter’s growth spurt arrived, our biggest customers wanted to add seats, but the existing per-seat contracts acted like a ceiling. I watched senior leaders turn from excitement to frustration as they tried to explain why a simple add-on would trigger a budget overrun. The per-seat model, which had seemed predictable, suddenly became a growth blocker.
We launched a top-down pricing audit within days. The audit showed that the predictable income from fixed seats was actually damping expansion because every new user added a linear cost to the client, while the value they derived grew exponentially. This misalignment forced our customer-success team into adversarial conversations with finance, turning what should have been a win-win into a tense negotiation.
Our discovery echoed the industry shift described in TradingKey, where the collapse of seat-based models is highlighted as a symptom of larger architectural mismatches. The realization hit hard: our revenue engine was built for stability, not for scaling with customer usage.
We scrambled to re-engineer the billing platform, adding metering capabilities, usage tiers, and a hybrid flat-rate option. The chaos felt like the "then and now" contrast often described in industry retrospectives - yesterday’s pricing playbook was simply not built for today’s usage-driven reality.
Key Takeaways
- Per-seat contracts can limit expansion in high-growth quarters.
- Pricing audits must align revenue with customer value.
- Hybrid models blend predictability with usage-based upside.
- Architecture must support metering for modern SaaS.
- Fast pivots require cross-functional collaboration.
Why Traditional SaaS Comparison Methods Mislead
When I first led a software selection workshop, the checklist was a litany of upfront license fees, per-user rates, and implementation costs. It felt thorough, but it missed the forest for the trees. The focus on headline numbers left out the total cost of ownership (TCO) that only emerges once the product is in use.
Many teams, especially in B2B environments, treat pricing like a static spreadsheet. They compare seat counts side by side, ignoring how usage patterns, data volumes, and API calls can dramatically shift the real spend. As McKinsey & Company point out, mature ISVs focus on the growth engine behind the product, not just the price tag.
Another blind spot is architectural lock-in. A platform that appears cheap today may require costly custom integrations later, tying you to a vendor’s roadmap. The real decision matrix should weigh expansion revenue potential, the flexibility of usage-based add-ons, and the ability to shift workloads without a massive re-engineering effort.
In practice, I’ve seen teams get stuck in a “seat-versus-seat” debate, ignoring the strategic value of a usage-based model that scales with customer success. The mislead comes from treating pricing as a one-off cost rather than a dynamic partnership metric.
The Silent Architecture Behind SaaS Pricing Models
Switching from a per-seat model to usage-based pricing is not just a finance tweak; it requires a product built for metering. In my experience, legacy platforms lack the telemetry pipelines needed to capture granular usage events, so they cannot safely charge based on consumption.
We evaluated three architectural paths:
- Pure flat-rate: simple, but limits upside as customers grow.
- Pure usage-based: maximizes alignment but demands robust monitoring and risk of revenue volatility.
- Hybrid: combines a predictable base fee with usage spikes for premium features.
The hybrid approach mirrors what top performers like ServiceNow employ - a steady subscription that guarantees revenue, plus usage-based modules for high-value extensions. Below is a concise comparison:
| Model | Predictability | Scalability | Implementation Complexity |
|---|---|---|---|
| Flat-rate | High | Low | Low |
| Usage-based | Low | High | High |
| Hybrid | Medium | High | Medium |
Implementing a hybrid model forced us to upgrade our data pipeline, add event logging at the API layer, and create dashboards for sales and finance to see real-time usage. The payoff was a pricing engine that could automatically adjust invoices as customers increased their data processing volume, aligning revenue with actual value delivered.
From a product perspective, the shift also unlocked new feature roadmaps. Because we could price premium analytics separately, we invested in AI-driven insights without worrying about breaking the core subscription. The architecture became a growth catalyst, not a cost center.
Enterprise SaaS: ServiceNow's Steady Play vs. Palantir's Gamble
When I compared ServiceNow and Palantir, the contrast was stark. ServiceNow builds its revenue on entrenched enterprise contracts - large base fees with predictable annual escalations. Palantir, on the other hand, sells outcome-based solutions, charging heavily on data processed and AI inference runs.
Both models can succeed, but the choice hinges on the product’s core value metric. If your platform automates repeatable workflows, a steady play like ServiceNow’s can generate reliable ARR and fund long-term R&D. If you deliver transformative analytics that change decision outcomes, a gamble on value-based pricing like Palantir’s can capture the full upside.
Our own experience mirrors this dichotomy. After the pricing crisis, we shifted a core module to usage-based billing, while keeping the base platform flat-rate. The result was a revenue curve that resembled ServiceNow’s steady climb for the platform, plus Palantir-style spikes when customers launched new AI features.
Below is a side-by-side snapshot of the two approaches:
| Aspect | ServiceNow | Palantir |
|---|---|---|
| Revenue Base | Flat subscription | Outcome-based fees |
| Scalability | Predictable growth | High upside, high variance |
| Customer Alignment | License-centric | Value-centric |
| Risk | Low churn risk | Revenue volatility |
The lesson for any scaling B2B SaaS is to map your pricing to the metric that matters most to your customers. If you can quantify the outcomes - decisions made, workflows automated, data processed - then a value-based model can unlock more revenue than a simple seat count ever could.
Building a Pricing Strategy for Profitability, Not Just Predictability
Profitability in SaaS comes from linking usage signals directly to revenue. In my own team, we built dashboards that surfaced metrics like API calls per month, data rows stored, and AI inference minutes consumed. Each metric had a tiered price attached, so when a customer’s usage climbed, their invoice reflected that growth automatically.
To make this work, sales had to become storytellers of ROI rather than sellers of seats. I coached reps to ask "What business outcome does this usage unlock?" and then translate that answer into a dollar figure. This shift turned conversations from "how many users?" to "what value will the platform deliver this quarter?".
We also instituted a self-funding growth loop: as customers used more features, they generated more revenue, which we reinvested into product improvements that further increased usage. The loop resembled the classic SaaS flywheel, but the propulsion was usage-based pricing instead of pure acquisition.
Finally, we kept an eye on churn. Because pricing now mirrored value, customers who stopped seeing ROI were the ones who churned, and we could intervene early with targeted success programs. The result was a healthier churn rate and a more sustainable profit margin.
In short, the right pricing model is the most powerful feature you can ship. When revenue scales with the customer’s success, growth becomes inevitable.
Frequently Asked Questions
Q: Why does per-seat pricing hinder rapid expansion?
A: Per-seat pricing adds a linear cost for each new user, which can quickly exceed a client’s budget, forcing them to pause or cancel expansions. This caps revenue growth and creates friction between sales and finance teams.
Q: How does a hybrid pricing model balance predictability and scalability?
A: A hybrid model charges a stable base fee for core access while adding usage-based tiers for premium features. This ensures steady cash flow and lets revenue grow as customers consume more value, marrying the best of flat-rate and usage-based approaches.
Q: What architectural changes are required for usage-based billing?
A: You need telemetry to capture granular usage events, a metering engine to aggregate those events, and a billing system that can translate meters into invoices. This often involves API logging, data pipelines, and real-time dashboards.
Q: When should a SaaS company choose a value-based model like Palantir?
A: When the product delivers measurable business outcomes - such as decisions enabled, revenue generated, or risk reduced - a value-based model captures the full worth of those outcomes, often leading to higher ARR than seat-based pricing.
Q: How can sales teams shift from selling seats to selling outcomes?
A: Train reps to ask discovery questions about the customer’s goals, quantify the expected ROI, and map those results to usage metrics. Then price the solution based on the value delivered rather than the number of users.
