By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information.
Revenue Operations

Consumption Forecasting: What RevOps Needs to Know

swirled squiggle accent

For years, revenue teams have lived and died by bookings forecasts. But in a world dominated by consumption and usage-based pricing, those spreadsheets no longer tell the full story. If even 20–30% of your top line is variable, it’s not enough to “close the deal.” You also have to predict when and how customers consume what they’ve bought.

That’s the new reality explored in this deep-dive discussion with Greg Lewis, Co-founder and President at revVana, Amy Cook, Co-founder and CMO at Fullcast, and Matthew Volm, CEO of RevOps Co-op and Eventful. Together, they unpack what it really takes to operationalize consumption forecasting—bridging the gap between bookings and revenue, between Sales and Finance, and between strategy and execution.

For an in-depth guide on consumption forecasting, check out this e-book Consumption Forecasting: How to Do it.

Why Consumption Forecasting Matters Right Now

The subscription economy is evolving into the consumption economy. Modern SaaS companies—from AWS to Snowflake to OpenAI—don’t charge for seats, they charge for usage. That shift is fundamentally changing how revenue is planned, recognized, and forecasted.

Greg Lewis explains that traditional RevOps forecasting focuses on bookings—when deals are sold. But usage-based revenue unfolds long after the signature, and if you’re not measuring and forecasting it properly, your entire revenue plan starts to drift.

“If your revenue is variable, you have to forecast it, plan it, and target it—just like pipeline.” — Greg Lewis, Co-founder & President, revVana

The challenge: unlike subscription revenue, usage-based consumption isn’t tied neatly to contract start dates. It ebbs and flows based on customer adoption, data processing volume, or even macro events like seasonality. And because Finance still needs predictability, RevOps becomes the critical connective tissue between what Sales commits, what CS delivers, and what Finance books.

Where Forecasting Breaks Down

1. The “Excel Hero” Problem

Most organizations still rely on spreadsheets as their forecasting engine. Sales leaders export data from Salesforce, apply formulas in Excel, and then email files back to Finance.

The problem?

  • Forecasts are static and lagging.
  • By the time data is aggregated, it’s already outdated.
  • Each function (Sales, CS, Finance) works from a different version of the truth.

“Spreadsheets are great for analysis, but terrible for scale. You can’t steer the ship when your visibility lags by three weeks.” — Amy Cook, Fullcast

For more on this topic, check out this whitepaper on Forecasting Complex Revenue Models.

2. Misaligned Ownership

Who owns consumption forecasting—Sales, CS, or Finance? The answer is none of them individually. Sales owns bookings, CS owns usage, and Finance owns recognition. Without RevOps orchestrating these moving parts, data silos grow—and forecast accuracy plummets.

3. Forecasting the Wrong Thing

Many companies still treat usage as “pipeline.” They add forecasted consumption into their opportunity amounts. But this inflates bookings, obscures true ARR, and muddies visibility into what’s actually realized.

RevOps needs to separate contracted value (what’s sold) from realized value (what’s consumed), so the organization can manage both acquisition and adoption as discrete metrics.

You should also check out this blog post on Metrics Every RevOps Leader Should Track (Beyond Pipeline).

Five Building Blocks of a Scalable Consumption Forecast

1. Codify Your Revenue Logic

Forecasting requires clarity: What does a “$1M deal” mean? Is that the committed volume, the expected ramp, or a blend of both? RevOps should create a “consumption dictionary” defining:

  • Contracted vs. realized usage
  • Start dates, end dates, and ramp assumptions
  • Measurement units (e.g., API calls, GB processed, messages sent)
  • Thresholds for recognition

By documenting assumptions up front, RevOps prevents Sales from forecasting on “vibes” and gives Finance the structure to model revenue accurately.

2. Create Ramp Curves Based on Reality

A usage-based forecast without time alignment is meaningless. Tie expected ramps to project milestones—deployment dates, go-lives, and customer adoption timelines. If historical usage data is limited, use proxy data like industry benchmarks, customer size, or similar account patterns to model expected ramps.

“Base your forecast on what customers actually do, not what Sales hopes they’ll do.” — Amy Cook

3. Segment and Layer Your Forecast

Segmenting consumption forecasts into layers gives clarity and accountability.

  • Committed Base Revenue: Consumption from existing contracts.
  • New Logo Consumption: Revenue from new deals yet to go live.
  • Expansion Consumption: Upsells or additional workloads.
  • Unrealized Revenue Risk: Consumption shortfalls vs. plan.

Layered forecasting makes it easier to explain variance, identify risk, and focus the team on driving realized revenue, not just pipeline.

For more on identifying Upsell opportunities, check out this blog post on Finding Upsell Opportunities That Drive SaaS Growth.

4. Close the Loop Between Systems

Don’t let usage data live in a silo. Integrate product telemetry, billing systems, and CRM data so usage actuals automatically flow back into your forecast model. Tools like revVana can automate this, ensuring that actuals update daily instead of quarterly.

That feedback loop enables RevOps to track forecast accuracy in real time—and quickly course-correct when customers under-consume.

5. Standardize the Cadence

Forecasting consumption should be as routine as pipeline reviews.

  • Weekly: CS + Sales syncs on usage deltas and customer health.
  • Monthly: RevOps-led review aligning usage actuals with forecast.
  • Quarterly: Executive-level review of realized vs. planned consumption.

Usage forecasting is iterative. You’ll never be 100% accurate, but tighter cadence means faster error detection and continuous improvement.

The Consumption Complication: Incentives and Territories

Forecasting consumption is hard enough. Incentivizing it adds another layer of complexity.

  • Sales Incentives: Should AEs get comped on usage? If so, when—at commitment, activation, or realization?
  • CS Incentives: Should CSMs earn credit for driving adoption?
  • Territories: Who owns accounts where usage grows cross-region or product line?

Greg recommends a tiered compensation model that balances accountability and control. AEs get credit for committed usage; CS earns accelerators for realized usage beyond baseline. Both functions share a joint “usage expansion” target to align incentives.

“If your comp plan rewards bookings, you’ll get bookings. If it rewards realization, you’ll get revenue.” — Greg Lewis

For more on this topic, check out When Sales Growth Drops, Improve Your Revenue Visibility.

The Finance Connection: From Sales Forecast to Revenue Plan

For Finance, usage forecasting isn’t just about predictability—it’s about credibility.

When RevOps can forecast revenue realization with precision, it transforms quarterly guidance from guesswork into confidence. One enterprise client, Greg shared, discovered that only 50% of sold consumption ever realized, exposing a $150M gap between bookings and actual revenue.

By modeling consumption ramps and automating actuals, they cut that variance by 70%—a board-level win.

“RevOps should be the tollgate between Sales and Finance—where truth and accountability meet.” — Greg Lewis

For more on consumption based forecasting in Salesforce, check out How to Forecast Consumption-Based Revenue in Salesforce: Best Practices and Common Pitfalls.

Pitfalls to Avoid

  • Overengineering early: Don’t build complex models before data maturity. Start with rough curves, refine monthly.
  • Ignoring seasonality: Usage drops on holidays and surges mid-quarter; model cyclicality.
  • Treating adoption as a black box: Make CS accountable for tracking feature-level usage, not just renewals.
  • Siloing product telemetry: If your product data isn’t flowing into CRM, your forecast will always trail reality.

30-Day Implementation Roadmap

Week 1: Define and Align

  • Map your variable revenue sources.
  • Document key consumption metrics.
  • Identify data owners across CS, Sales, and Finance.

Week 2: Audit and Integrate

  • Inventory all systems capturing usage data.
  • Integrate telemetry, billing, and CRM fields into a central data model.

Week 3: Model and Forecast

  • Build initial ramp curves by product and customer cohort.
  • Layer historical averages with sales input for forward view.

Week 4: Automate and Iterate

  • Deploy automation to update actuals daily.
  • Publish variance reports comparing forecast vs. realized usage.
  • Establish weekly CS/Sales syncs and monthly RevOps review.

The New RevOps Mandate

Consumption forecasting is no longer optional. As pricing models evolve, it’s becoming a core competency for high-performing RevOps teams. It blends financial acumen, data analytics, and cross-functional orchestration—everything RevOps was built for.

“If bookings are the promise, consumption is the proof. RevOps is the bridge that keeps the two aligned.” — Amy Cook

Final Takeaways

  • Treat consumption forecasting like pipeline forecasting—structured, layered, and continuous.
  • Build clear ownership between Sales, CS, and Finance.
  • Automate the loop between product usage, billing, and CRM.
  • Use consumption data to align comp, incentives, and revenue recognition.
  • Start simple, iterate fast, and measure variance religiously.

Looking for more great content?

Check out our RevOps Co-op Blog for more frameworks and expert insights.

Ready to operationalize your consumption model? Join the RevOps Co-op Community to connect with 18,000+ operators building the next generation of revenue infrastructure.

Related posts

Join the Co-op!

Or