PRICING AS A GROWTH ENGINE
What If Your Price Was 0.01% of Your Customer’s Revenue?
How One Bold Pricing Proposal Reveals Everything B2B SaaS Gets Wrong About Monetization
A playbook for fractional CROs, revenue architects, and B2B executives ready to stop leaving money on the table
The Proposal That Changes the Conversation
Here’s a pricing proposal that would make most B2B SaaS companies uncomfortable:
Charge 0.01% of your customer’s revenue. That’s it. No tiers. No seat counts. No feature gates. Just a hundredth of a percent of the topline your product helps them protect and grow.
This is the pricing strategy I recently proposed to HALO, an executive intelligence platform that gives leaders a single point of truth to make revenue-impacting decisions 97% faster. And the reason it matters goes far beyond one company’s pricing page.
This proposal is a litmus test. How you react to it reveals everything about whether your company treats pricing as a strategic growth lever — or as a billing afterthought you revisit once a year in a conference room.
Because here’s the uncomfortable truth: most B2B SaaS companies are leaving 15–25% of their total profits on the table by refusing to align their pricing with the value they actually deliver. McKinsey’s research is unambiguous on this. And yet only about one in four SaaS companies regularly experiments with pricing.
15–25%
of total profits driven by pricing advantage (McKinsey)
24%
of SaaS companies run pricing experiments
Let me walk you through why a proposal like 0.01% of revenue isn’t just defensible — it’s the logical conclusion of every trend reshaping B2B SaaS monetization right now. And along the way, I’ll show you how fractional CROs are turning this kind of thinking into operational reality through RevOps.
Why 0.01% of Revenue Is the Purest Form of Value Pricing
It Says What Every SaaS Company Wants to Say — But Won’t
Every B2B SaaS company claims to deliver ROI. But almost none of them put their pricing where their pitch deck is. Seat-based pricing says “we charge for access.” Tier-based pricing says “we charge for features.” Revenue-percentage pricing says something radically different:
We’re so confident we impact your revenue that we’ll price ourselves as an invisible fraction of it. If we’re not worth a hundredth of a percent of your topline, we’re not worth anything.
That’s not just a pricing model. That’s a brand statement. It’s the kind of positioning that moves you out of the feature-comparison game entirely — and into a category of one.
It Eliminates the Two Things That Kill Enterprise Deals
Procurement friction and adoption anxiety. These are the silent killers of B2B SaaS growth, and they’re both rooted in the same problem: buyers can’t predict what they’ll pay, or they can’t justify what they’re being asked to pay.
At 0.01% of revenue, a $10M company pays $1,000 a year. A $100M company pays $10,000. A $500M company pays $50,000. The number is always proportional, always predictable, and always an insignificant fraction of the value being delivered. No enterprise buyer fights over a line item that small relative to their topline.
This is exactly what the most forward-thinking SaaS companies have discovered. Writer, the enterprise AI platform, charges a fixed platform fee plus a generous monthly token allowance. The result? Increased willingness to trial, more confidence in expanding usage. Intercom offers annual credit buckets and outcome-based pricing to remove the leap of faith. The pattern is clear: when customers know what they’re on the hook for, they sign the deal and they actually use your product.
It Creates a Self-Expanding Revenue Engine
This is the part that should excite any growth-stage CEO or investor. With revenue-percentage pricing, your revenue grows automatically as your customer’s revenue grows. No upsell required. No renewal negotiation. No expansion motion. It compounds silently.
Snowflake proved this model at massive scale — growing 106% year-over-year before reaching $1B ARR, with enterprise customers expanding usage by 65–80% annually. Their secret wasn’t aggressive sales. It was a consumption model where price scaled with value. The HALO proposal takes this same principle and makes it even simpler: instead of metering compute credits, you meter the one thing every executive cares about — revenue.
Why Most Companies Won’t Do This — and Why That’s Your Advantage
If revenue-percentage pricing is so powerful, why isn’t everyone doing it? Because it requires something most B2B SaaS companies don’t have: the operational infrastructure to execute it.
The Plumbing Problem
Here’s what’s really holding companies back. It’s not strategy — it’s plumbing. At most SaaS companies, the monetization model is stitched together with process debt: sales quotes one price, billing charges another, finance can’t reconcile revenue until quarter-end, and engineers get pulled off product work to make a packaging tweak.
Every pricing change becomes a cross-functional fire drill. When one person sticks their neck out to propose something bold — like, say, 0.01% of customer revenue — they don’t get full exec support because no one can figure out how the billing system would actually handle it.
This is the gap that fractional CROs are built to close. They don’t just propose the strategy — they build the RevOps infrastructure to execute it.
The Confidence Problem
Revenue-percentage pricing also requires something deeper: genuine confidence in your product’s impact. You can’t tie your price to customer revenue if you’re not sure you actually move the needle. That’s why this model works so well for HALO specifically — a platform that demonstrably accelerates revenue-impacting decisions by 97%. The value claim and the pricing model are the same sentence.
For companies where the value proposition is vaguer — “we help teams collaborate better” or “we provide insights” — this pricing model would expose the gap. And that exposure is exactly why it’s valuable as a strategic exercise, even if you don’t ultimately adopt it. If you can’t defend tying your price to customer revenue, your value story needs work.
The Companies That Proved Bold Pricing Wins
The HALO proposal doesn’t exist in a vacuum. The most successful SaaS companies of the last decade all made pricing moves that felt uncomfortable at the time — and created compounding advantages that competitors still can’t replicate.
Snowflake: Consumption as a Growth Weapon
Snowflake generated over 90% of revenue from consumption-based pricing. They built an internal data platform called Snowhouse that refreshes revenue forecasts daily. They restructured sales comp so a large portion was tied to actual customer consumption, not bookings. As former CEO Frank Slootman put it: “When customers only pay for what they use, you have to earn your revenue every day.”
CASE STUDY: Snowflake
Growth: 106% YoY revenue growth before hitting $1B ARR
Expansion: Enterprise customers expand 65–80% annually after initial deployment
Valuation premium: Companies with usage-based pricing achieve ~50% higher enterprise value vs. pure subscription peers (Bessemer)
Source: Stripe customer interviews; Snowflake SEC filings; Bessemer Venture Partners
New Relic: The Painful Bet That Paid Off
In 2020, New Relic scrapped their legacy host-based subscription model and shifted to pure consumption pricing. ARR growth dipped for multiple quarters. Sales reps who thrived on upfront commitments left. But they rebuilt the team with reps who understood land-and-expand, and restructured comp so reps got paid on consumption — not bookings.
The result: accelerated account growth, deeper platform adoption, lower churn, and committed ARR spend up approximately 15%. Their CFO later reflected they wished they’d been even more aggressive.
CASE STUDY: New Relic
The bet: From per-host subscription to consumption-based pricing (2020)
Short-term cost: Revenue softness for multiple quarters; significant sales team turnover
Long-term payoff: Accelerated account growth, lower churn, ~15% lift in committed ARR. One of the first public SaaS companies to fully adopt consumption pricing.
Source: OpenView Partners; New Relic earnings calls; SEC filings
HubSpot: Iterative Pricing as a Compounding Machine
HubSpot’s NRR was 70% at the time of their Series A — a dangerously low number. Over a decade, they methodically restructured: contact-based tiers, multi-hub packaging, and most recently a seat-based model (March 2024) that removed minimum seat requirements and created a natural expansion path. By 2021, NRR peaked at 115%. Full year 2024 revenue grew 21% to $2.6B+, with 43% of Pro+ customers subscribing to three or more hubs.
Now they’re introducing AI credits for their Breeze agent features — signaling the next evolution toward usage-based monetization. Their Agent.AI ecosystem grew from 50,000 to over 500,000 users in just six months.
CASE STUDY: HubSpot
NRR evolution: From ~70% at Series A to 115% peak — one of the most remarkable NRR turnarounds in SaaS history
Revenue: $2.6B+ in 2024; 21% YoY growth; deals over $5K MRR grew 35% YoY
The lesson: You don’t need to make one giant pricing bet. Iterative, data-driven evolution compounds into billions.
Source: HubSpot Q4 2024 earnings; SaaStr NRR analysis; HubSpot IR filings
The pattern across all three: they aligned price to value, accepted short-term discomfort, built the operational infrastructure to sustain the new model, and created expansion engines that compounded over years. The 0.01% revenue model for HALO is the same playbook — taken to its purest expression.
Why This Requires a Fractional CRO — Not Just a Good Idea
Here’s where theory meets execution. Proposing 0.01% of revenue is the easy part. Operationalizing it requires someone who can rewire the entire revenue engine — and that’s the fractional CRO’s job.
Get Tom Opper’s stories in your inbox
Join Medium for free to get updates from this writer.
Move 1: Build the Revenue Verification Infrastructure
A revenue-percentage model only works if you can reliably verify the customer’s revenue. The fCRO architects the data pipeline: integrations with financial systems, third-party data sources for private companies, contractual mechanisms tied to publicly reported revenue for larger customers. This is the RevOps foundation everything else sits on.
Move 2: Design Floor Pricing That Maintains Perceived Value
At 0.01%, a $5M company pays $500/year. That’s less than a single HubSpot seat. The fCRO solves this by implementing a minimum floor — say $5K–10K annually — that maintains perceived value at the low end while keeping the percentage model as the scaling mechanism for larger accounts. This is the hybrid approach: predictable minimums plus value-aligned upside.
Move 3: Restructure Sales Comp for the New Model
Revenue-percentage pricing creates a comp challenge: the initial close may be small, but the long-term account value compounds. Snowflake learned this when reps on 100% consumption comp struggled with the mental shift. Their solution was a blended structure — 60% consumption, 40% bookings for volume reps, heavier consumption weight for enterprise reps.
The fCRO designs a similar structure for HALO: comp that rewards reps for landing accounts and driving adoption, not just closing contracts. The cultural shift is the same one Snowflake made: sales stops being about the close and starts being about the adoption curve.
Move 4: Turn Pricing Into a Continuous Experiment
Top SaaS companies in the PricingSaaS 500 Index made over 1,800 pricing and packaging changes in 2025 alone. Lovable made roughly one meaningful pricing update per month on its way to $200M ARR. Even Salesforce launched AI credits, new license types, and an agentic enterprise agreement — all in one year.
The fCRO builds this experimentation muscle into HALO’s RevOps: simulating pricing scenarios against historical customer data, running segmented pilots, tracking results in real time, and rolling back what doesn’t work. The 0.01% model becomes the starting hypothesis, not the final answer.
~40%
cost savings: fCRO vs. full-time CRO hire
90 Days
typical timeline to measurable revenue impact
The Hard Truth: Where This Goes Wrong
Bold pricing moves fail all the time. Here are the specific traps that could derail the HALO proposal — or any pricing transformation — pulled directly from real-world failures.
Pitfall 1: Moving Without Full Executive Alignment
This is the number-one killer. As SaaS pricing expert Kyle Poyar put it: “Pricing changes are really hard because they’re cross-functional. One person sticks their neck out, they don’t get full exec support, and the pricing change becomes a disaster.”
A revenue-percentage model touches every team: Finance (revenue recognition), Legal (contract structure), Sales (comp and objection handling), Product (customer revenue integrations), and CS (value realization). The fCRO’s job is to get all of them aligned before anything ships.
⚠ THE ALIGNMENT TEST
Before proposing 0.01% externally, HALO needs internal alignment on four questions: How do we verify customer revenue? What’s our minimum floor? How do we comp reps? And what does Finance need for revenue recognition? If any of those answers involve “we’ll figure it out later,” you’re not ready.
Pitfall 2: Pricing Too Low to Be Taken Seriously
There’s a real risk that enterprise buyers don’t take a $500–$1,000 annual product seriously. Procurement may not process a PO that small. Executives may equate low price with low value. This is the inverse of the adoption anxiety problem — instead of being afraid of overpaying, buyers are suspicious of underpaying.
⚠ THE PERCEPTION TRAP
The fix is a floor, but the floor must be set carefully. Too high and you lose the elegance of the percentage model. Too low and you lose credibility. The fCRO models this by analyzing HALO’s current customer segments, competitive pricing, and the minimum price point at which enterprise buyers engage seriously.
Pitfall 3: Inheriting Your Customer’s Macro Risk
With revenue-share pricing, a downturn hits your customers and your revenue simultaneously — across your entire book of business. New Relic experienced multiple quarters of revenue softness during their transition. HALO needs to model for a scenario where customer revenues contract 10–20% and plan accordingly.
⚠ THE EXPOSURE CALCULATION
The fix: Build minimum annual commitments into contracts so that revenue-percentage pricing applies only above the floor. This creates a hybrid model: guaranteed base revenue for HALO, with value-aligned upside. The customer keeps the pricing alignment they want; HALO keeps the predictability it needs.
Pitfall 4: The Wrong Value Metric for the Wrong Segment
Revenue works as a pricing metric for executive-level tools where the link between better decisions and topline growth is intuitive. But if HALO expands into operational or departmental use cases where the revenue connection is less direct, the metric may need to evolve.
Mixpanel learned this lesson when they initially priced on raw data events — customers felt penalized for deeper engagement. They shifted to tracked users, which better reflected the value delivered. HALO should monitor whether “percentage of revenue” continues to resonate as the customer base diversifies.
Pitfall 5: Doing Nothing Because It’s Hard
Every pitfall above is solvable. The one that isn’t? Inertia. As Poyar warned: “The bigger risk is that companies just don’t make the changes that are ultimately necessary. Inertia leads to avoidance, which hurts the business more than moving early and making a mistake.”
The companies that win the next decade won’t be the ones with the best features. They’ll be the ones that iterate on pricing as fast as they iterate on product.
The AI Multiplier: Why This Matters More Now Than Ever
HALO is an AI-powered executive intelligence platform — which means the pricing stakes are even higher.
Traditional SaaS enjoys 80–90% gross margins. AI products often run at 50–60%. Every query, every inference, every intelligence summary burns real compute dollars. Pricing that doesn’t account for this reality can turn profitable customers into margin-crushing liabilities.
50–60%
Typical AI product gross margins vs. 80–90% for traditional SaaS (Bessemer)
The 0.01% model solves this elegantly. Because the price scales with customer size, larger customers — who generate more queries, need more intelligence, and consume more compute — pay proportionally more. The pricing model naturally mirrors the cost structure without requiring complex metering or credit systems.
This is exactly the dynamic the market is moving toward. Credit-based pricing surged 126% year-over-year in the PricingSaaS 500 Index, with HubSpot, Salesforce, and Figma all adopting credits in 2025. But credits add complexity. Revenue-percentage pricing achieves the same margin protection with radical simplicity.
As one data infrastructure CFO told Metronome’s field research team: “We’re not monetizing AI to juice revenue. We’re monetizing to avoid eating $10K of costs on a $500 plan.” The 0.01% model makes that impossible by design.
The Value Proposition: What This Is Actually Worth
Let’s put real numbers behind both sides of this equation — what HALO’s customers get, and what HALO’s investors should expect.
For HALO’s customers: A $50M company pays $5,000/year for a platform that makes revenue-impacting decisions 97% faster. If that speed advantage influences even one deal, one retention save, or one strategic pivot, the ROI is measured in thousands of percent. The pricing model makes the purchase decision nearly irrational to decline.
For HALO’s growth: Revenue compounds automatically as customers grow. No upsell required. Net revenue retention becomes structurally embedded in the pricing model itself — not something you have to engineer through cross-sell motions. If your average customer grows 10% annually, your revenue from that customer grows 10% annually. Full stop.
For the category: While competitors in executive intelligence fight over seat counts and feature tiers, HALO occupies a positioning no one else can claim. You’re not selling software. You’re selling a fraction of the revenue outcomes your platform enables. That’s a conversation competitor sales teams can’t match.
THE COMPOUNDING MATH
Year 1: 100 customers at average $25M revenue = $250K ARR for HALO at 0.01%
Year 3: If customers grow 10% annually and HALO adds 50 new customers/year: ~$600K+ ARR with zero upsell effort
Year 5: Network effects and word-of-mouth from a pricing model that sells itself: $1.5M+ ARR trajectory
Contrast: Traditional $50/seat/month pricing with the same 100 customers at ~5 seats each = $300K ARR, with every dollar requiring active sales effort to expand
The difference: Revenue-percentage pricing turns customer success into automatic revenue growth. Seat-based pricing turns it into a sales problem.
The fCRO investment to build this: $60K–$150K over a 6-month engagement. The expected return: a monetization engine that compounds for years, a category-defining pricing position, and the RevOps infrastructure to iterate on it continuously. That’s 5–10x ROI in year one — before the compounding even kicks in.
The Bottom Line
The 0.01% proposal for HALO isn’t just a pricing recommendation. It’s a test of a bigger thesis: that the next generation of B2B SaaS winners won’t compete on features, seats, or tiers. They’ll compete on the confidence to align their price with the value they deliver.
New Relic proved that even a painful pricing transformation pays off when you commit. Snowflake proved that consumption pricing creates unprecedented growth. HubSpot proved that iterative pricing evolution compounds into billions.
HALO has the chance to prove something even bolder: that an executive intelligence platform confident enough to price at a fraction of customer revenue can build a category — not just a company.
The only question is the one that applies to every pricing transformation, at every stage, in every market:
HOW MANY QUARTERS OF COMPOUNDING GROWTH
ARE YOU WILLING TO LEAVE ON THE TABLE?
Start with one experiment. Audit your value metric. Build the infrastructure to iterate. Ship.
SOURCES & FURTHER READING
Metronome — Monetization Operating Model Whitepaper & Pricing Experimentation Playbook • Bessemer Venture Partners — The AI Pricing & Monetization Playbook • McKinsey — Pricing Research & SaaS Monetization • OpenView Partners — Usage-Based Pricing Research & New Relic Case Study • Gartner — RevOps Forecast Accuracy Studies • Snowflake SEC Filings & Stripe Customer Interview (Michael Scarpelli, CFO) • HubSpot IR — Q4 2024 Earnings & 2025 Guidance • SaaStr — HubSpot NRR Analysis • PricingSaaS — 2025 State of SaaS Pricing Changes (Growth Unhinged) • Kyle Poyar — SaaS Pricing Predictions, Metronome Webinar • Chargebee — Usage-Based Pricing Transition Guide • HALO (haloforall.com) — Executive Intelligence Platform
