Overview
A revenue forecast report helps a revenue operations lead turn pipeline, conversion history, sales velocity, and assumptions into one reusable view of expected revenue.
This playbook replaces the forecast spreadsheet that tends to sprawl across tabs, copied formulas, stale exports, and side-channel caveats. Juno installs a forecast page and model table so the number, the math, and the judgment stay together.
The default workflow uses pipeline and history the team has already supplied in the workspace, pasted into the task, uploaded as files, or maintained in existing Juno tables. It does not require a CRM connector to be useful, and it does not pretend to be a finance planning suite.
Why you should make forecast assumptions visible
Forecasting gets tense when the headline number travels faster than the assumptions behind it. A pipeline total can look healthy while the expected revenue is weaker because stage conversion, deal velocity, expected inflow, or stale source data tells a different story.
Salesforce describes revenue forecasting as estimating future revenue from historical sales data, current pipeline activity, and expected conversion rates to guide business decisions (Salesforce). That is exactly where spreadsheets often get fragile: the inputs may be reasonable, but the logic is too easy to hide.
Velocity matters too. HubSpot frames sales velocity around opportunity volume, deal value, win rate, and sales cycle length (HubSpot). Keeping those pieces visible helps a RevOps team explain whether the forecast is believable, not just whether it is large.
Juno gives the recurring review a cleaner home. The page shows the forecast and major assumptions, while the table keeps the model and judgment calls auditable before they become meeting folklore.
Step-by-step
- 1Confirm the business, forecast window, currency, amount basis, review cadence, and any starting assumptions the revenue team already uses.
- 2Set up the installed forecast workspace with a revenue forecast page and forecast model table.
- 3Load current pipeline by stage and segment from supplied files, pasted updates, existing workspace tables, or manual inputs, then label the source and freshness.
- 4Add historical conversion and velocity context where available, defaulting to a recent completed lookback period when the team has not specified one.
- 5Calculate expected revenue by keeping pipeline value, expected inflow, conversion, velocity, forecast probability, and confidence status visible as separate parts of the model.
- 6Refresh the forecast page so leaders can see expected revenue, total pipeline, rows needing review, major caveats, and the inputs required before the next forecast call.
Frequently asked questions
Does this connect to our CRM automatically?
No. The default playbook works from user-supplied pipeline and history so teams can replace the spreadsheet first. A connected CRM export can be added later as a source choice, but it is not required for the minimum workflow.
What data do I need for the first useful forecast?
Start with current pipeline by stage, pipeline value, deal count, historical won and entered counts, average velocity, expected inflow, currency, and the forecast window. Missing inputs can be marked directly in the model.
How does Juno handle weak or missing data?
It keeps the row visible and labels the issue, such as missing history, missing velocity, missing pipeline, or an outlier that needs review. The report should show confidence gaps instead of smoothing them away.
When should this run?
Use it weekly for active forecast calls or monthly for operating and leadership reviews. Leave cadence as run-once while the team is still agreeing on model rules.