The revenue cycle is the end-to-end sequence a company runs to turn demand into revenue it keeps and grows. It spans demand generation, pipeline creation, deal qualification, deal progression, closing, onboarding, renewal, and expansion. Every stage produces data. Revenue operations instruments that data and uses it to forecast what the business will actually earn, which makes the revenue cycle the system RevOps measures and predicts rather than a diagram on a slide.
The stages of the revenue cycle
The cycle moves in order, and each stage feeds the next. Demand generation creates awareness and interest. Pipeline creation converts that interest into qualified opportunities. Deal progression moves opportunities through stages toward a decision. Closing turns opportunities into bookings. After the signature, onboarding activates the account, and renewal and expansion decide how much of that revenue survives and compounds. In B2B SaaS the cycle does not end at the close. Most lifetime revenue is decided after it, which is why retention belongs inside the cycle and not in a separate report.
How RevOps instruments the revenue cycle
RevOps places a measurement at each stage so the company can see cause, not only outcome. Instrumentation turns the cycle into a system you can manage while the quarter is still open.
| Stage | What RevOps measures | Signal to watch |
|---|---|---|
| Demand generation | Sourced pipeline by channel | Pipeline creation rate |
| Progression | Coverage, stage conversion, velocity | Close-date changes |
| Closing | Win rate, realized vs. booked deal size | Deals closing below CRM value |
| Retention | Gross and net revenue retention | Support-case volume |
Why the forecast models the cycle, not coverage
A common mistake is treating pipeline coverage as the forecast. Coverage tells you whether enough opportunities exist. It says nothing about how the quarter will happen. A company can carry 4x coverage and still miss when the pipeline is stale, concentrated in one stage, dependent on a few large deals, or inflated with deals that never close at their forecast value.
A forecast built on the cycle decomposes revenue into where it comes from: carry-over deals already in pipeline on day one, in-quarter deals that do not exist yet but will be created and closed inside the period, and pull-forward deals brought early from future quarters. The visible pipeline is a weak proxy for this. ORM finds that of the pipeline dated to close in the quarter on the first day, roughly 20% actually closes that quarter, which leaves 80% of the day-one value unrealized. Modeling the full cycle is how you know the shape of the quarter on day one, early enough to change it.
Frequently Asked Questions
What are the stages of the revenue cycle?
The revenue cycle runs from demand generation to pipeline creation, deal qualification, deal progression, closing, onboarding, renewal, and expansion. In B2B SaaS the post-sale stages carry most of the lifetime value, so retention and expansion are part of the cycle, not a separate function.
How is the revenue cycle different from the sales cycle?
The sales cycle covers the selling portion, from a qualified opportunity to a closed deal. The revenue cycle is wider. It includes demand generation before the opportunity exists and onboarding, renewal, and expansion after the deal closes. The sales cycle is one segment of the revenue cycle.
Is pipeline coverage the same as the revenue cycle forecast?
No. Pipeline coverage measures whether enough opportunities exist against the target. It does not explain how the quarter will happen. A forecast built on the revenue cycle decomposes revenue into carry-over deals, in-quarter deals created and closed inside the period, and pull-forward deals. ORM finds that of the pipeline dated to close in the quarter on day one, only about 20% actually closes that quarter, so coverage alone overstates what will land.
How does RevOps forecast the revenue cycle?
RevOps instruments every stage, then models how revenue will be created and closed rather than reading the current pipeline as the answer. ORM's models train on a company's historical sales performance in four to six weeks and target 95% forecast accuracy that holds from day one to day 90 of the quarter, updating as conditions change.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like revenue cycle into prescriptive action for your team.
Schedule a Demo