Monthly Sales Forecasting: How to Build a Number Your Leadership Will Actually Believe

The forecast your leadership believes isn't the one closest to reality — it's the one you can break open in front of them, deal by deal, and explain why every riyal in it is there. What usually sinks a forecast isn't a bad estimate. It's the absence of a fixed derivation method, which turns every review into a fresh argument about gut feel.

The short version: what makes a monthly number credible

Three conditions. Meet them, and the number becomes a professional discussion instead of a source of suspicion.

1. One entry rule: every deal enters the forecast on the same criteria — not on the enthusiasm of the rep who owns it.
2. A declared confidence gradient: the number isn't one lump sum, but three tiers, each with a different operational meaning.
3. A variance log: you compare last month's forecast against what actually closed, and show where you were wrong and why.

A manager who walks into the leadership meeting with those three discusses numbers. A manager who walks in with a single bare figure defends himself.

The four questions every deal must answer before it enters the forecast

No deal enters the monthly forecast until four questions have written answers in the system — not verbal answers in the hallway.

1. Who signs? Not "who are we talking to," but who holds the authority to approve the amount. If the answer is "I think it's the CFO," the deal isn't forecast-ready. In the Saudi market specifically, plenty of deals stall when someone discovers late that approval requires a board or a procurement committee with a fixed meeting calendar.

2. What's the budget, and where does it come from? Is the amount already in the current year's budget, or will it require an exceptional approval request? The gap between those two is at least two months.

3. What's the next step, and when? A concrete step with an owner and a date: "technical demo Sunday with the operations manager." "We'll follow up with them" is not a step.

4. What could delay it? Having the rep name the obstacle explicitly — infosec sign-off, waiting on the current contract to expire, the decision-maker's vacation — improves forecast quality more than any probability formula.

A deal with four clear answers goes in. A deal missing two answers stays out, no matter how large the amount. That rule alone removes the deals that would have broken your forecast.

The three tiers: committed, likely, possible — and what belongs to none of them

Split the forecast into three tiers, each with a written entry condition that isn't renegotiated every month.

Tier	Entry condition	How leadership uses it
Committed	Quote approved verbally or in writing by the authorized signer, close date within the month, no open blockers	The number you commit to in front of leadership
Likely	Decision-maker identified, budget confirmed, but final approval not yet issued	The upper end of the forecast range
Possible	Confirmed need and an engaged contact, but no confirmed budget or authority	An indicator for next month, not this one

And what enters no tier at all: deals with no two-way contact in the past two weeks, deals whose close date has slipped three times in a row, and tenders before pre-qualification results are announced. These stay in the pipeline for follow-up, but out of the monthly calculation.

The practical benefit: when you tell leadership "committed is X, likely is Y," you've handed them a range they can plan financially around, instead of a single number that either lands or doesn't.

## Deriving the number: a fully hypothetical, step-by-step example

Note: all figures below are entirely hypothetical and used for illustration only. They do not represent any real company's data.

Suppose — hypothetically — a security systems supplier ends the month with 34 open deals worth SAR 42.0 million in total. The gross figure has no planning value, so we start filtering.

Step (hypothetical figures)	Deals	Value
Open pipeline	34	42.0M
After removing close dates outside the month	19	18.5M
After removing stalled or thrice-slipped deals	14	13.0M
After applying the four questions	11	10.2M

The remaining eleven are then distributed across the tiers: four committed deals worth SAR 3.1M, four likely worth SAR 4.4M, and three possible worth SAR 2.7M.

So what do you tell leadership? "We commit to 3.1 million. The likely range reaches 7.5 million if every likely deal closes — which has never happened historically — so our working estimate is between 4.5 and 5.5 million." That statement can be audited line by line. Which of the four committed deals does leadership want opened? You open it with them.

Notice that what matters here isn't the figures — they're invented for illustration — but the sequence: filter first, tier second, range third.

The monthly forecast review: a thirty-minute agenda

A long meeting is a symptom of a missing method. If the rules are written down, half an hour is enough:

• 5 minutes — Variance: last month's forecast versus actuals, plus a one-sentence reason for each deal that fell through.
• 10 minutes — The committed tier: one deal at a time, one question: what's stopping the signature this week?
• 10 minutes — Promotions and demotions: which deals deserve to move from likely to committed, and which must be downgraded. Demotion isn't a punishment. A rep who downgrades a deal early gets thanked, not blamed — otherwise your team learns to hide bad news until the last day.
• 5 minutes — Commitments: who does what before next Monday.

One important rule: never discuss the "possible" tier in this meeting. It belongs in the weekly pipeline session. Mixing the two is exactly what turns a review into two hours with no decisions.

Where the system helps — and where it can't replace human judgment

A CRM helps in three specific places: standardizing stages and fields so each rep doesn't interpret "negotiation stage" their own way; showing the pipeline visually so you spot congestion in one stage at a glance; and generating the three-tier report from the same underlying data instead of rebuilding it by hand in a spreadsheet every month. In Effistar, the visual pipeline and reports serve exactly this purpose: one source of truth for deals, with a classification everyone can see.

There's a fourth thing leadership needs: every deal should be openable, with its history of follow-ups and updates visible — so the only record of the deal doesn't live inside one rep's head. And if you want finer tracking of close-date changes specifically, check what tracking capabilities your plan includes before you build a management policy on top of them.

What no system does: decide for you whether the customer's words were an approval or a courtesy. Reading the decision-maker's tone, knowing that a particular government entity doesn't disburse before Q4, interpreting two weeks of silence — that's human judgment. The system stores the judgment and makes it visible and reviewable. It doesn't produce it.

Measuring your accuracy: the monthly variance log and how to read it

Keep a table with four columns only: month, committed forecast, actual closed, variance percentage. After six months you'll have something more valuable than any single forecast: knowledge of the direction of your error.

• Consistently under forecast? Your committed-tier entry conditions are too loose. Tighten them.
• Consistently over forecast? You're withholding qualified deals out of fear of blame, and leadership loses its ability to plan.
• Variance swinging with no pattern? The problem isn't the rules — it's data entry discipline.

The most important read of all: review the reasons deals fell through, not just their size. If "finance approval delayed" shows up in three deals, you have a problem with when you involve finance, not with your estimating. A good forecast always ends in an improvement to how you sell — not merely a more accurate number.

Start next month with the simplest version: the four questions, the three tiers, and the variance log. Three months is enough to turn the forecast review from a defense into a discussion.