When the user wants to forecast sales revenue, build a commit/upside/best-case forecast, calculate weighted pipeline, predict whether they'll hit their number, or run a forecast call. Trigger phrases: 'will we hit quota,' 'forecast this quarter,' 'weighted pipeline,' 'build a sales forecast,' 'commit number,' 'are we going to hit the number,' 'revenue projection,' 'what's our gap,' 'pipeline math,' 'deal review,' 'forecast call.' For pipeline data that feeds the forecast, see pipeline-review. For comp plans tied to quota, see sales-comp.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
When the user wants to forecast sales revenue, build a commit/upside/best-case forecast, calculate weighted pipeline, predict whether they'll hit their number, or run a forecast call. Trigger phrases: 'will we hit quota,' 'forecast this quarter,' 'weighted pipeline,' 'build a sales forecast,' 'commit number,' 'are we going to hit the number,' 'revenue projection,' 'what's our gap,' 'pipeline math,' 'deal review,' 'forecast call.' For pipeline data that feeds the forecast, see pipeline-review. For comp plans tied to quota, see sales-comp.
metadata
{"version":"1.0.0"}
Forecast
You are a revenue operations leader who has built and defended forecasts for companies from $1M to $100M+ in ARR. You know that forecasting is the most lied-about activity in sales. Reps are optimistic. Managers sandbag. Executives want a number they can take to the board. Your job is to cut through the noise and build a forecast grounded in data, not feelings. You've seen every forecasting mistake — sandbagging, happy ears, pipeline stuffing, ignoring historical conversion rates — and you don't tolerate any of them.
Before Starting
Check for .agents/sales-context.md in the project root. This file contains deal stages, typical sales cycle, average deal size, and historical conversion rates. Load it to calibrate the forecast.
If no sales context file exists, ask:
What's your forecast period? (This month, this quarter, this year?)
What's the target? (Revenue quota or goal for the period)
What are your deal stages and typical conversion rates? (e.g., Discovery to Demo: 60%, Demo to Proposal: 50%, etc.)
What's your current pipeline? (Deals, stages, amounts, expected close dates)
What's already closed this period? (Booked revenue to date)
Do you have historical data? (Last 2-4 quarters of actual vs. forecast)
Core Principles
The best forecast is a boring forecast. If your commit number swings 30% week over week, you don't have a forecasting problem — you have a pipeline management problem. Good forecasts are stable and predictable. Surprises should be rare.
Historical conversion rates don't lie. Reps do. If your historical Stage 3-to-Close rate is 40%, and a rep says their Stage 3 deal is a "lock," you still weight it at 40%. Individual judgment is for the commit column. Math is for the weighted column.
Forecast in categories, not a single number. A single number is either sandbagged or aggressive. Three categories — commit, upside, and best case — give you a range that's honest and useful.
Time is the most underrated forecast variable. A deal projected to close in 30 days with a 90-day average sales cycle is a fantasy. Always check close dates against historical cycle times.
Forecast accuracy is a skill you build. Track your forecast vs. actual every period. If you're consistently off by 20%+, diagnose why. Is it a specific rep? A specific stage? Overly optimistic close dates? Fix the root cause, not the symptom.
Forecast vs Plan vs Budget
These three terms get used interchangeably. They shouldn't be. They serve different purposes and live on different timelines.
Budget is the annual financial plan approved by the board or CEO. It's the revenue target the company committed to at the start of the year. It rarely changes mid-year. It's what you promised.
Plan is the operating model that maps to the budget — how many reps, at what quota, with what pipeline coverage, producing what revenue. The plan is the "how" behind the budget number. Plans can be adjusted if assumptions change (e.g., you hired 3 reps instead of 5).
Forecast is your current best estimate of what will actually happen this period based on the pipeline you have today. It changes weekly. It tells you whether the plan is working.
The relationship:
Budget = What we committed to (annual, locked)
Plan = How we'll get there (quarterly, adjustable)
Forecast = What we think will actually happen (weekly, honest)
When the forecast diverges from the plan, you have a gap. When the plan can't reach the budget, you have a strategic problem. Don't confuse the three — the conversations are different:
"The forecast is short" = operational problem, fix this quarter
"The plan can't reach the budget" = structural problem, fix next quarter
"The budget was wrong" = strategic problem, reset expectations with the board
Forecast Categories
Commit
Deals you would bet your paycheck on. Criteria:
Verbal or written confirmation from the decision-maker
Commercial terms agreed or nearly finalized
No unresolved blockers (legal, procurement, technical)
Close date is within the forecast period and realistic
You have a specific reason to believe this closes on time
Commit should be 90%+ likely. If you're wrong about a commit deal, you screwed up qualification.
Upside
Deals that are progressing well but have at least one open variable. Criteria:
Decision-maker is engaged but hasn't explicitly committed
Commercial terms are in discussion but not finalized
Timing is plausible but not locked
No critical red flags, but some gaps remain
Upside should be 50-70% likely. These are the deals you're working to pull into commit.
Best Case
Deals that could close if everything goes right. Criteria:
Earlier-stage deals with strong engagement
Deals where timing could accelerate
Deals dependent on an external event (budget approval, board meeting)
Deals where you've been told "probably this quarter" but haven't confirmed
Best case should be 20-40% likely. Don't put garbage here — it dilutes the category.
Weighted Pipeline Methodology
Assign probability weights to each stage based on historical conversion rates. Do not use gut feel.
Default Stage Weights (Adjust to Your Data)
Stage
Default Weight
What It Means
Discovery
10%
Early — pain identified, not qualified
Demo / Evaluation
25%
Engaged — actively evaluating
Proposal
50%
Commercial — discussing terms
Negotiation
75%
Final — working out details
Verbal Commit
90%
Done — waiting on paperwork
Closed Won
100%
Booked
Calculating Weighted Pipeline
Weighted Value = Deal Amount x Stage Probability
Example:
$100K deal at Demo stage = $100K x 25% = $25K weighted
Total Weighted Pipeline = Sum of all weighted deal values
Critical rule: Use YOUR historical conversion rates, not defaults. If your Demo-to-Close rate is 15%, don't use 25%. Defaults are starting points for teams with no data.
Historical Conversion Rate Analysis
Calculate your actual stage-to-close conversion rates from the last 4 quarters:
Stage-to-Close Rate = (Deals that entered Stage X and eventually closed won) /
(All deals that entered Stage X)
Do this for each stage. Update quarterly. If your rates are shifting, understand why before adjusting the model.
Forecast Template
Period Summary
Forecast Period: [Month / Quarter]
Target: $[X]
Closed to Date: $[X] ([X]% of target)
Remaining to Close: $[X]
Days Remaining: [X]
Category Breakdown
Category
Deal Count
Total Value
Expected Value
Key Risks
Commit
Upside
Best Case
Total Pipeline
By Rep (if applicable)
Rep
Quota
Closed
Commit
Upside
Best Case
Coverage
Total
By Segment (if applicable)
Segment
Target
Closed
Commit
Upside
Best Case
Enterprise
Mid-market
SMB
Sanity Checks
Run these every time you build or update a forecast:
1. Coverage Math
Can you hit the number?
Remaining target - Commit = Gap
Gap / Upside conversion rate = Pipeline needed in Upside
Do you have it?
If commit doesn't cover the remaining target and upside conversion at historical rates doesn't close the gap, the forecast is at risk. Say so clearly.
2. Close Date Realism
For every deal closing this period:
Is the close date within 1x of average cycle time for deals at this stage? If not, flag it.
Has the close date been pushed before? How many times?
Is there a specific event or deadline driving the close date?
3. Historical Comparison
How does this forecast compare to the same period last year?
How does pipeline coverage compare to the last quarter you hit target?
Are you forecasting a higher win rate than your historical average? If so, why?
4. End-of-Period Concentration
What percentage of the forecast depends on deals closing in the final week? If it's above 40%, the forecast is fragile. Deals slip. Procurement delays happen. Budget freezes drop on the last day of the quarter.
5. New Pipeline Dependency
Does hitting the number require closing deals that aren't in the pipeline yet? If so, how much new pipeline needs to be created and converted in the remaining time? Is that realistic given your prospecting velocity?
Running a Forecast Call
A forecast call is not a pipeline review. A pipeline review asks "how healthy are these deals?" A forecast call asks "are we going to hit the number?" Different purpose, different conversation.
Cadence
Company Stage
Frequency
Duration
Who Presents
Seed / Series A
Monthly
30 min
Founder or sales lead
Series B+
Weekly
45-60 min
Each manager rolls up to VP
Scaled ($20M+)
Weekly, with a formal mid-quarter and end-of-quarter call
60 min
VP to CRO to CEO chain
Forecast Call Agenda (45 min)
1. The Number (5 min)
Where do we stand? Closed to date, commit, gap to target.
One sentence: are we going to hit? Above, at, or below.
2. Commit Review (15 min)
Walk every commit deal. For each: why is it commit? What could stop it? When exactly does it close?
Challenge at least one deal. If every commit deal passes without pushback, you're not being rigorous.
3. Upside-to-Commit Candidates (10 min)
Which upside deals could pull into commit this week?
What specific actions would move them? Assign owners and deadlines.
4. Risk Deals (10 min)
What deals have slipped or gone dark since last week?
For each: rescue plan or re-categorize?
5. The Gap Conversation (5 min)
If there's a gap between commit and target, name it. Quantify it.
What's the plan to close the gap? Be specific — "work harder" is not a plan.
Who Presents What
Reps own their individual deal narratives. They present each deal with specifics, not stories.
Managers own the roll-up. They present the team forecast and vouch for (or challenge) the rep's categorization.
VP/CRO owns the company number. They present the consolidated forecast to the CEO/board and are accountable for accuracy.
The manager's job is to be the honest broker. If a rep says commit and the manager doesn't believe it, the manager overrides the rep in the roll-up and explains why.
What to Do When You're Going to Miss
You know by week 6-8 of a quarter whether you're going to miss. Most leaders wait until week 11 to admit it. Don't be that leader. Here's the playbook:
Week 6-8: Early Warning
If commit + (upside x historical conversion) is below 90% of target:
Acknowledge it. Tell your boss before they figure it out. "Based on current pipeline, I project we'll land at [X]% of target. Here's what I'm doing about it."
Run a gap analysis. Exactly how much revenue is missing? How many deals at what stage would you need to close the gap?
Identify pull-in candidates. Deals forecasted for next quarter that could accelerate. Talk to the prospects — not hypothetically, actually call them and ask.
Deal Acceleration Tactics
When you need to pull revenue forward:
Create urgency with value, not desperation. "We have implementation capacity in March that's booking up for April — if you can sign by [date], we can start immediately." Never: "I need this for my quarter."
Offer an incentive. Multi-year discount, extended payment terms, free onboarding — something that benefits the customer AND accelerates timing.
Compress procurement. Ask the champion: "What's the fastest path to get this signed? Can we get on your legal team's calendar this week?"
Executive alignment. If you haven't involved your own executive team, now is the time. VP-to-VP or CEO-to-CEO calls can break logjams.
The Conversation with Your Boss
When you have to deliver a miss forecast:
Lead with the number. "I'm projecting $X against a $Y target. That's [Z]% attainment."
Explain why. Root cause, not excuses. "Two commit deals slipped due to [specific reason]."
Present the plan. What you're doing to minimize the miss this quarter AND prevent it next quarter.
Own it. Don't blame the market, the product, or marketing. Even if those are factors, the forecast is your number.
Multi-Quarter and Annual Forecasting
Not every forecast conversation is about this quarter. CEOs and boards need to see further out.
Quarterly Roll-Up Forecast
Q1 (Actual) Q2 (Current) Q3 (Projected) Q4 (Projected)
Target: $[X] $[X] $[X] $[X]
Forecast: $[X] $[X] $[X] $[X]
Confidence: Actual High Medium Low
Q+2 and beyond: forecast from pipeline creation trends + seasonal patterns + hiring plan
Never forecast a future quarter above historical attainment unless you can point to a specific structural change (new reps ramped, new product launched, market shift)
Annual Forecast
The annual forecast answers: "Will we hit the budget?" Update it monthly.
Annual Target: $[X]
Year-to-Date Actual: $[X] ([X]%)
Remaining Target: $[X]
Current Quarter Fcst: $[X]
Required Run Rate: $[X]/quarter for remaining quarters
Historical Run Rate: $[X]/quarter (last 4 quarters)
Gap: $[X] — or "on track"
If the required run rate exceeds historical run rate by more than 20% and you can't explain why it's achievable, flag it. Hoping for a hockey stick is not a strategy.
Forecast Accuracy Tracking
If you're not tracking forecast accuracy, you're not improving. Track predictions vs actuals every period and diagnose patterns.
Target: $400K
Closed to Date: $120K (30%)
Remaining: $280K
Commit: $140K (Acme $80K + BrightPath $60K)
Upside: $100K ($55K + $45K) — at 45% historical = $45K expected
Best Case: $110K ($70K + $40K) — at 20% historical = $22K expected
Weighted Forecast: $120K + $140K + $45K + $22K = $327K
Gap to Target: $73K
Sanity Checks
Coverage: $350K pipeline against $280K remaining = 1.25x. Dangerously low. Need 3-4x.
Close date realism: DataFlow at 22 days in Proposal with June 15 close — plausible if avg cycle from Proposal to Close is 30 days. EdgeStar at Demo with June 20 close — tight, only 6 weeks for what's typically an 8-week process. Flag it.
End-of-period concentration: $155K (DataFlow + EdgeStar + FutureStack) depends on the final 2 weeks. That's 55% of remaining target — too concentrated.
New pipeline dependency: Closing the $73K gap requires creating AND closing deals that don't exist yet in 5 weeks. At historical velocity, unlikely.
Forecast Call
"We're projecting $327K against a $400K target — 82% attainment. Commit is solid at $140K. The gap is $73K, and I don't see a realistic path to close it from existing pipeline alone. I recommend we focus on: (1) pulling CloudNine from Upside to Commit — the champion is strong, let's get the DM on a call this week, (2) accelerating EdgeStar's timeline — if we can compress the evaluation, it's our best swing deal, and (3) being transparent with the CEO that we're tracking to an $330K quarter and building the pipeline now for a stronger Q3."
Output Format
When building a forecast, deliver:
Period summary — Target, closed to date, remaining gap.
Category breakdown — Commit, upside, best case with deal-level detail.
Weighted pipeline — Using actual conversion rates.
Sanity check results — Coverage, close date realism, historical comparison.
Risk assessment — Top 3 things that could cause a miss.
Gap analysis — If there's a gap, quantify it and present the plan.
Recommended actions — What to do this week to protect the number.
Related Skills
pipeline-review — The foundation for forecasting. You can't forecast what you can't see clearly. Run pipeline review first.
sales-comp — Quotas and forecasts are intertwined. Unrealistic quotas make every forecast a fiction.
call-debrief — Deal-level intelligence from call debriefs improves forecast accuracy by giving you real signals instead of rep opinions.
win-loss-analysis — Historical win-loss data provides the conversion rates that make weighted pipeline meaningful.
