Last updated on Friday, August 8, 2025
Most teams forecast based on what sales reps put into their CRM. Opportunity stages, probabilities, close dates.
It’s a good start. But it’s not enough.
If you’re only forecasting pipeline, you’re only seeing a slice of the picture. And that’s usually where things break down, in board meetings, planning cycles, or when Finance asks for real numbers.
To get a full view of revenue, you need to go further.
What they are
These forecasts are built on sales opportunities. You take the deal size, apply a probability, and maybe weight it by stage.
Why teams use it
It’s the default in a CRM. Easy to set up. Reps update fields. Managers run reports.
Where it breaks
It stops at “deal signed.” It doesn’t show how or when revenue will actually show up. And it doesn’t work well for multi-phase deals, delayed contracts, or usage-based models.
What they are
These forecasts show when booked revenue will actually be recognized, based on your contracts, schedules, and GAAP rules.
Why teams need it
Finance, accounting, and the board care about this. It tells them what revenue to expect in each quarter, not just what deals might close.
Common issues
What helps
Tie opportunity data to product SKUs, billing terms, and schedules, all inside your CRM. That way, your revenue forecast updates in real time when sales changes a deal.
What they are
These show expected revenue based on usage, for companies with consumption, variable pricing, or usage-based models.
Why they’re hard
You don’t know exactly how much a customer will use. Forecasting becomes a mix of trends, seasonality, and customer behavior.
Why they’re important
If you bill based on usage, this is where most of your revenue is. And it’s often the part you can’t see clearly in your CRM.
What helps
Use historical usage data and build models that connect with your CRM. Forecast in units first, then apply pricing. RevOps teams need tools that can do this natively in their CRM.
Most companies stop at pipeline. A few build spreadsheet models for revenue recognition. Very few do all three.
If you’re not modeling revenue after the deal closes, your forecast isn’t complete. It’s just potential.
Ask these questions:
If the answer is “no” or “not really,” it’s time to rethink your process.
Resource forecasting is the practice of predicting how people, time, and capacity will be required in the future to deliver work and revenue. It sounds straightforward. In reality, it is one of the most misunderstood and underdeveloped capabilities in modern organizations.
Usage-based pricing didn’t appear as a trend. It showed up as a response to how these businesses actually operate.As AI-driven products moved from experimentation to production, the subscription models that once worked for SaaS began to fracture. Revenue became tied to tokens, minutes, inference calls, credits drawn down, and compute consumed. Growth accelerated, but predictability suffered.
Salesforce is very good at answering one question: What did we sell? Royalty forecasting asks a different one: What will we owe, and when? For RevOps teams supporting licensing, media, data, or IP-driven businesses, that gap creates real risk. Pipelines look clean. Forecasts roll up neatly. And yet royalty exposure consistently surprises finance months later.