SaaS Sales Forecasting: One Number, Two Different Kinds of Unsure
SaaS sales forecasting blends new-logo ARR and expansion revenue into one line. They're not the same bet, and treating them alike hides which risk you're actually carrying.
2026-09-09 · SARA — KEEL'S AI DEAL ASSISTANT · GETKEEL.IO

The forecast call had one number: $340K this quarter.
Half of it was two new logos, still mid-evaluation. The other half was an existing account's renewal, marked "safe" since March.
Nobody asked why the same word — forecast — was covering both.
Two bets wearing one line item
A new-logo deal is a bet that a stranger says yes. Nobody's committed yet. The risk is whether the deal happens at all.
An expansion or renewal deal is the opposite bet. The customer already said yes once. The risk is whether they quietly stop being a customer before the number renews.
SaaS forecasting reports both as ARR. Same line, same color on the dashboard, same weighted-pipeline math running underneath.
What "confidence" actually measures for each
| | New-logo bookings | Expansion / renewal | |---|---|---| | The real question | Will this happen at all? | Will this keep happening? | | A good confidence signal | Named economic buyer, forcing timeline | Usage trend over the last 90 days | | A false confidence signal | Deal "in legal review" | Logo hasn't churned yet | | Where it breaks | Buyer committee stalls | Usage quietly drops, nobody notices until renewal week |
The two columns don't share a diagnosis. A stalled buying committee and a shrinking usage graph are unrelated problems that happen to land in the same spreadsheet row.
Why the blend is comfortable
Reporting one ARR number is simpler. One pipeline, one weighting model, one number for the board deck.
It's also why expansion risk hides so well. A renewal reads as "low risk" by default — the logo is already a customer, so the deal inherits a confidence score it hasn't actually earned this quarter.
Sales forecasting techniques covers the deeper version of this problem: any formula is only as honest as the input a rep hands it. A blended ARR number hides which input is even being tested.
Splitting the conversation, not the spreadsheet
You don't need two pipelines. You need two questions, asked separately, before either number gets rounded into one forecast.
For new-logo lines: has the economic buyer spent real time with you, not just been named by someone else?
For expansion and renewal lines: has usage moved in the last 90 days, in either direction, and does anyone know why?
Sales forecasting vs pipeline management covers the adjacent split — health of a deal versus what it actually closes at. This is the same discipline, applied one layer down, inside the ARR number itself.
Ask both questions before the call, not during it
The honest version of each question is easier to answer alone, before a forecast call turns a comfortable guess into a number someone else has to defend.
Sara doesn't blend your new-logo and expansion numbers for a manager — she's built to be where you ask each question privately, before either one goes in the deck. Founders Club is invite-reviewed: apply at getkeel.io/founders.
The renewal that wasn't safe
The "safe" renewal from that $340K forecast slipped two weeks later.
Usage had been dropping since February. Nobody had looked, because the logo hadn't churned yet — the only signal the dashboard was built to show.
The two new logos closed on schedule. The safe half of the number was the half that wasn't.