RecordBook guide
Joint Revenue Forecasting for Co-Sell Deals
Two companies forecasting the same deals from two CRMs rarely agree. How to get to one joint revenue forecast — a single number, agreed stages, a shared pipeline.
Joint revenue forecasting is predicting what co-sell deals will close, when, and for how much — as one number both companies agree on. It sounds like ordinary forecasting, and the math is. What’s hard is that two companies are forecasting the same deals from two CRMs, and their numbers almost never match.
When your forecast says $400k of joint pipeline will land this quarter and your partner’s says $650k, somebody is about to miss a commit or misreport a program tier. Here’s how to get to one forecast you can both stand behind.
Why co-sell forecasts don’t match
Three things pull the two numbers apart, and they compound.
Two systems of record. Your deals live in your CRM, your partner’s in theirs. Nobody is looking at the same list, so the forecast starts from two different pipelines before anyone even disagrees about a deal.
Two definitions of “committed.” Your “commit” might mean verbal yes and signed order form. Theirs might mean the rep feels good about it. Same word, different bar — so the same deal sits in commit on one side and best-case on the other.
Double-counting. Both companies book the full deal value toward their own number, which is correct for each company’s books but wrong for the joint forecast, where that one deal should be counted once.
Agree on one number, and whose it is
Before you forecast anything, settle two questions with your partner:
What amount are we forecasting? For a joint forecast, pick the total deal value and count it once — not your slice plus their slice, which either double-counts or requires a split nobody has agreed on. Each company can still report its own share internally; the shared forecast tracks the one deal.
What does each stage mean? Map both sides’ stages to a small set of joint ones and define the bar for each. “Commit” should mean the same evidence on both sides — a signed order, a set close date, procurement underway — or the category is meaningless. (This is the same stage-mapping that makes partner pipeline management work; the forecast just reads from it.)
Forecast from a shared pipeline, not two exports
A forecast is only as current as the pipeline under it. When that pipeline is a spreadsheet merged from two CRM exports, the forecast is stale the moment it’s built, and every update means rebuilding it.
Forecasting from a shared pipeline that syncs from both CRMs fixes the root cause: both sides’ deals roll up into one view, in real time, so the joint forecast is a live read of the same data instead of a reconciliation you redo every Friday. In-period revenue forecasting then shows what’s actually landing this quarter, not just what’s open.
Separate the forecast from the pipeline
Total open pipeline is not a forecast. A forecast is your honest call on what will close in the period, and it’s usually a fraction of the pipeline.
Keep the two numbers distinct in every joint review: here’s the joint pipeline, and here’s what we’re committing will land this quarter. Co-sell deals make this easy to blur, because a big joint pipeline feels like a big forecast. It isn’t — a deal stuck in a partner’s procurement for two quarters is pipeline, not commit.
Run a joint forecast cadence
Forecast on a rhythm, together, and keep it short:
- Weekly: each side updates its own deals in the shared pipeline — stage, date, amount, next step. No meeting required; just keep the record current.
- Every two weeks: a 20-minute joint review of commit and best-case deals. Does the evidence still match the category? What changed?
- End of period: compare called vs. closed on both sides, and note where the two numbers drifted, so next quarter’s forecast starts more honest.
The cadence matters more than the model. A simple forecast reviewed every two weeks beats a sophisticated one built once and never revisited.
Red flags in a joint forecast
A few patterns reliably mean the number is softer than it looks:
- A commit deal with no next step. If nothing is scheduled, it isn’t committing to anything.
- A close date that keeps sliding. Three pushes is not a timing problem; it’s a qualification problem.
- Your number and your partner’s are far apart. That gap is deals sitting in different stages on each side — find them before the customer does.
- A deal nobody has touched in weeks. A stalled deal in the commit column is the most expensive kind of wrong.
Common questions
Whose number counts in a joint forecast — ours or our partner’s?
Neither, and that’s the point. A joint forecast is a shared number both sides agree on, built from one shared pipeline, with one agreed definition of each stage. Each company still reports its own share to its own leadership, but the co-sell forecast itself is a single fact, not a competition between two CRMs.
How do we avoid double-counting co-sell revenue?
Decide up front what the joint forecast measures — total deal value, counted once — and split for internal reporting separately. Forecasting from one shared record instead of two means the deal exists in a single place to begin with, so there’s nothing to deduplicate later.
How often should we forecast co-sell deals?
Keep the records current weekly and review commit and best-case together every two weeks. Monthly is too slow for deals that move across two organizations — a stall or a slipped date can hide for weeks, which is exactly the window that breaks a forecast.
Get one forecast you can both trust
RecordBook rolls your CRM and your partner’s CRM into one shared pipeline and forecasts in-period revenue from it — so your joint forecast is a live, agreed number instead of two spreadsheets that disagree. Try it free, no credit card required.
More co-selling guides
- PRM vs CRM: what partner teams need to co-sell
- Partner-sourced vs. partner-influenced revenue
- The co-sell operating model: roles, cadences and metrics
- What is co-selling? How partner teams sell together
- Partner pipeline management: running a shared sales pipeline
- Sales forecasting with in-period revenue