Executive Decision-Making Prompts

How to Use These Templates

Each template includes:

When to use it: The situation or forecasting need
Required inputs: Information you must provide
AI prompt: Copy, customise, and paste into your preferred AI tool
Template structure: The output format you can expect

Global AI Safety Line

Paste the following instruction at the start of every forecasting prompt:

“If unsure about any assumption, growth rate, or projection, write ‘VERIFY:’ next to it. Do not invent financial data or benchmarks. Flag all assumptions explicitly. This forecast is for internal planning and is not financial advice. Past performance does not guarantee future results.”

Before You Start

Gather accurate historical data before running any forecast
Verify all AI-generated calculations independently
Document every assumption for future reference
Treat forecasts as informed estimates, not certainties

Forecasting Methods Overview

Choose the right method based on your data availability and business stage.

Note: Typical fit depends on horizon, volatility, and data quality. VERIFY for your specific context.

Method	Best For	Data Required	Typical Fit
Bottom-Up	Sales-driven businesses	Leads, conversion rates, deal sizes	Short-term planning with reliable pipeline data
Top-Down	Market expansion planning	Market size, share estimates	Strategic planning, less precise for operations
Time Series	Stable revenue with seasonality	At least 12 monthly points for baseline trend. Ideally at least two full seasonal cycles for seasonality.	Best for baseline planning in stable businesses
Weighted Pipeline	Active sales pipelines	CRM opportunity data with recent stage win rates	Pipeline-heavy models with consistent stage definitions
Cohort-Based	Subscription businesses	Customer acquisition and retention data	SaaS with sufficient cohort history
Scenario-Based	Uncertain environments	Multiple assumption sets	Provides range, not point estimate

Bottom-Up Forecasting Templates

Lead-to-Revenue Forecast

When to use: Estimating future revenue by connecting lead volume to sales outcomes. Ideal for demand-gen-driven organisations.

Required inputs: [leads by channel], [conversion rates by stage], [average deal size], [sales cycle length]

AI PROMPT

[Global AI Safety Line]

Create a lead-to-revenue forecast for the next [X] months.

Lead data by channel:
• Channel A: [expected leads per month] • Channel B: [expected leads per month] • Channel C: [expected leads per month]

Conversion rates:
• Lead to opportunity: [percentage] • Opportunity to proposal: [percentage] • Proposal to close: [percentage] • Or overall lead-to-close rate: [percentage]

Deal metrics:
• Average deal size: [amount] • Sales cycle length: [days/weeks]

Provide:

Monthly forecast table:
• Leads by channel
• Opportunities created
• Expected closes
• Projected revenue

Quarterly summary:
• Total leads, opportunities, closes, revenue

Assumptions table:
• List every assumption with source or rationale
• Mark assumptions without historical support as ‘VERIFY:’

Sensitivity analysis:
• Impact if lead volume varies by +/- 20%
• Impact if conversion rate varies by +/- 10%

Format as a spreadsheet-ready table I can paste into Excel or Sheets.

Sales Capacity Forecast

When to use: Projecting revenue based on sales team capacity and productivity.

Required inputs: [number of reps], [ramp time], [quota per rep], [attainment rate]

AI PROMPT

[Global AI Safety Line]

Create a sales capacity forecast for the next [X] months.

Team data:
• Current ramped reps: [number] • New hires planned: [number and start dates] • Average ramp time to full productivity: [months] • Planned attrition: [number or percentage]

Productivity metrics:
• Quota per ramped rep: [amount per month/quarter] • Historical quota attainment: [percentage] • Ramping rep productivity: [percentage of full quota by month]

Provide:

Monthly capacity table:
• Ramped rep count
• Ramping rep count (weighted)
• Total effective capacity
• Expected revenue at historical attainment

Hiring impact analysis:
• Revenue contribution from new hires by month
• Break-even point for each hire

Risk factors:
• Impact of delayed hiring
• Impact of higher attrition
• Impact of lower attainment

Mark all productivity assumptions as ‘VERIFY:’ unless based on recent data.

Weighted Pipeline Forecasting

Stage-Based Pipeline Forecast

When to use: Active sales pipelines where deals progress through defined stages. Improves accuracy compared to gut-based forecasts.

Required inputs: [pipeline by stage], [stage probabilities], [expected close dates]

AI PROMPT

[Global AI Safety Line]

Create a weighted pipeline forecast for [time period].

Important: Stage probabilities should be based on recent win rates that reflect current process, pricing, and ICP. VERIFY the lookback window that best reflects present conditions.

Close date distribution:
• Deals expected to close this month: [list or count by stage] • Deals expected to close next month: [list or count by stage] • Deals expected to close in 60+ days: [list or count by stage]

Provide:

Weighted forecast:
• Unweighted pipeline total
• Weighted pipeline total (value × probability)
• Expected revenue by close date period

Pipeline health metrics:
• Pipeline coverage ratio (weighted pipeline / target)
• Average deal size by stage
• Deals at risk (aging beyond normal cycle)

Forecast categories:
Example categorisation (customise to your sales process):
• Commit: Deals with >80% probability
• Best case: Deals with 50-80% probability
• Upside: Deals with <50% probability
VERIFY your internal definitions match these thresholds.

Accuracy note:
Weighted pipeline forecasting depends heavily on accurate CRM data and realistic stage probabilities. VERIFY that historical win rates reflect recent performance.

Deal-Level Forecast

When to use: Enterprise sales with fewer, larger deals where individual deal tracking matters.

Required inputs: [list of active deals], [deal details], [close date estimates]

AI PROMPT

[Global AI Safety Line]

Create a deal-level forecast for [time period].

Provide:

Forecast summary:
• Total pipeline value
• Commit forecast (high confidence deals)
• Best case forecast (high + medium confidence)
• Upside forecast (all deals)

Timeline view:
• Expected closes by week/month
• Revenue concentration risk (large deals as % of forecast)

Deal risk assessment:
• Deals with slipped close dates
• Deals with no recent activity
• Deals with single-threaded relationships

Next actions:
• Critical activities needed for commit deals
• Deals requiring executive engagement

Flag any deals with close dates that seem inconsistent with their current stage.

Subscription and Recurring Revenue Forecasts

MRR/ARR Forecast

When to use: Subscription businesses tracking recurring revenue. Projects future MRR based on current base and expected movements.

Required inputs: [current MRR], [MRR components], [growth assumptions]

AI PROMPT

[Global AI Safety Line]

Create an MRR forecast for the next [X] months.

Current state:
• Starting MRR: [amount] • Active customers: [number] • ARPU: [amount]

Historical monthly averages:
• New MRR: [amount] • Expansion MRR: [amount] • Contraction MRR: [amount] • Churned MRR: [amount]

Growth assumptions:
• Expected change in new customer acquisition: [percentage or amount] • Expected change in expansion rate: [percentage] • Expected change in churn rate: [percentage]

Provide:

Monthly MRR waterfall:
| Month | Starting MRR | New | Expansion | Contraction | Churn | Ending MRR |
|——-|————–|—–|———–|————-|——-|————|
| [Month 1] | | | | | | |
| [Continue for forecast period] | | | | | | |

Key metrics by month:
• Net new MRR
• MRR growth rate
• Net revenue retention
• Customer count

ARR projection:
• Ending ARR for forecast period
• ARR growth rate

Assumptions table:
• List all assumptions
• Mark any without historical basis as ‘VERIFY:’

Note: MRR forecasts are highly sensitive to churn assumptions. Small changes in churn rate compound significantly over time.

Cohort-Based Revenue Forecast

When to use: SaaS companies wanting to project revenue based on how customer cohorts behave over time.

Required inputs: [cohort data], [retention curves], [expansion patterns]

AI PROMPT

[Global AI Safety Line]

Create a cohort-based revenue forecast for [time period].

Expansion data:
• Average expansion per customer per year: [percentage or amount] • Typical expansion timing: [months after acquisition]

Future acquisition assumptions:
• Expected new customers per month: [number] • Expected starting ARPU: [amount]

Provide:

Cohort revenue projection:
• Revenue contribution from each existing cohort by month
• Revenue contribution from future cohorts by month
• Total projected revenue by month

Retention analysis:
• Are newer cohorts retaining better or worse than older cohorts?
• Projected lifetime value by cohort

Sensitivity analysis:
• Impact if retention improves/declines by 5%
• Impact if acquisition slows by 20%

Mark cohort projections as estimates. Actual cohort behaviour may differ from historical patterns.

Scenario-Based Forecasting

Three-Scenario Forecast

When to use: Planning for uncertainty when multiple outcomes are plausible.

Required inputs: [baseline assumptions], [variable ranges], [historical data]

AI PROMPT

[Global AI Safety Line]

Create a three-scenario revenue forecast for [time period].

Baseline metrics:
• Current revenue run rate: [amount] • Historical growth rate: [percentage] • Key revenue drivers: [list]

Variables to model with ranges:
• [Variable 1]: Low [X], Base [Y], High [Z] • [Variable 2]: Low [X], Base [Y], High [Z] • [Variable 3]: Low [X], Base [Y], High [Z]

External factors:
• Market conditions: [description] • Competitive landscape: [description] • Economic indicators: [description]

Provide three scenarios:

Conservative (Downside) Scenario:
• Assumptions and rationale
• Monthly/quarterly revenue projections
• Annual total
• Probability assessment (subjective)
• Key risks this scenario reflects

Base Case (Most Likely) Scenario:
• Assumptions and rationale
• Monthly/quarterly revenue projections
• Annual total
• Probability assessment (subjective)
• What this scenario assumes about execution

Optimistic (Upside) Scenario:
• Assumptions and rationale
• Monthly/quarterly revenue projections
• Annual total
• Probability assessment (subjective)
• What would need to happen to achieve this

Decision triggers:
• Leading indicators that suggest which scenario is unfolding
• Recommended actions for each scenario

Label all scenarios as planning estimates. Actual results may fall outside these ranges.

Quarterly Business Review Forecast

When to use: Updating annual forecasts quarterly with actual results and revised assumptions.

Required inputs: [original forecast], [YTD actuals], [updated assumptions]

AI PROMPT

[Global AI Safety Line]

Update the annual forecast based on Q[X] results.

Original annual forecast:
• Annual target: [amount] • Q1 forecast: [amount] | Q1 actual: [amount] • Q2 forecast: [amount] | Q2 actual: [amount if available] • Q3 forecast: [amount] • Q4 forecast: [amount]

YTD performance:
• YTD actual revenue: [amount] • YTD variance to forecast: [amount and percentage] • Key variance drivers: [list]

Updated assumptions for remaining quarters:
• [Assumption 1]: Original [X], Updated [Y], Reason [Z] • [Assumption 2]: Original [X], Updated [Y], Reason [Z]

Provide:

Revised forecast:
• Updated Q3 forecast: [if applicable] • Updated Q4 forecast:
• Revised annual total:
• Change from original forecast:

Variance analysis:
• One-time vs. recurring factors
• Factors expected to continue vs. normalise

Forecast confidence:
• Confidence level in revised forecast
• Key risks to achieving revised forecast
• Upside opportunities not included in base forecast

Tracking metrics:
• Leading indicators to monitor
• Trigger points for next revision

Clearly distinguish between known factors and assumptions about remaining quarters.

Time Series Forecasting

Historical Trend Forecast

When to use: Stable businesses with sufficient historical data. Good for identifying seasonality and baseline growth.

Required inputs: [monthly revenue for 12-24+ months], [known seasonality], [planned changes]

AI PROMPT

[Global AI Safety Line]

Create a time series forecast based on historical data.

Data note: At least 12 monthly points helps estimate a baseline trend. Ideally at least two full seasonal cycles for seasonality. For monthly seasonality, this often means 24+ months. Data requirements are method-specific. VERIFY that your data history matches the assumptions of the forecasting approach you select.

Known patterns:
• Seasonal peaks: [months and typical magnitude] • Seasonal lows: [months and typical magnitude] • One-time events in historical data: [describe]

Planned changes:
• Price changes: [timing and magnitude] • Product launches: [timing and expected impact] • Marketing campaigns: [timing and expected impact]

Provide:

Trend analysis:
• Overall growth trend (percentage per month/year)
• Seasonality index by month
• Adjusted baseline (removing one-time events)

Forecast model:
• Monthly projections for next 12 months
• Seasonal adjustments applied
• Growth rate assumption used

Model limitations:
• Time series forecasting assumes historical patterns continue
• Major market changes may invalidate the model
• Mark any projected changes as ‘VERIFY:’

Note: This method works best for stable, mature businesses. High-growth or volatile businesses should use other methods.

Financial Planning Templates

Annual Budget Forecast

When to use: Building next year’s revenue budget from multiple inputs.

Required inputs: [current year actuals/forecast], [growth assumptions by segment], [planned initiatives]

AI PROMPT

[Global AI Safety Line]

Create an annual revenue budget for 2026.

Current year baseline:
• Expected current year revenue: [amount] • Revenue by segment: [breakdown] • Revenue by product: [breakdown] • Revenue by region: [breakdown]

Growth assumptions by segment:
• Segment A: [growth percentage and rationale] • Segment B: [growth percentage and rationale] • Segment C: [growth percentage and rationale]

Planned initiatives:
• New product launches: [timing and expected revenue] • Market expansion: [timing and expected revenue] • Pricing changes: [timing and expected impact] • Marketing investments: [expected revenue impact]

Headwinds:
• Known customer losses: [amount] • Market challenges: [expected impact] • Competitive pressure: [expected impact]

Provide:

Annual budget summary:
• Total revenue target
• Growth over current year (amount and percentage)
• Revenue by segment
• Revenue by quarter

Bridge from current year:
• Current year ending revenue
• Plus: Growth from existing business
• Plus: New initiatives
• Minus: Known headwinds
• Equals: Next year budget

Assumptions register:
• List every assumption with owner and validation status
• Mark unvalidated assumptions as ‘VERIFY:’

Risk and opportunity:
• Risks to achieving budget
• Upside not included in base budget

Cash Flow Forecast

When to use: Projecting cash position based on revenue forecast, expenses, and timing.

Required inputs: [revenue forecast], [expense forecast], [payment timing], [current cash]

AI PROMPT

[Global AI Safety Line]

Create a cash flow forecast for [time period].

Starting position:
• Current cash balance: [amount] • Current AR balance: [amount] • Current AP balance: [amount]

Revenue and collections:
• Monthly revenue forecast: [by month] • Average days to collect: [days] • Collection pattern: [percentage collected in 30/60/90 days]

Important: Revenue recognition timing may differ from cash collection timing. This forecast focuses on cash movement, not GAAP revenue.

Expenses and payments:
• Fixed monthly expenses: [amount] • Variable expenses as % of revenue: [percentage] • Payroll timing: [dates] • Major planned expenses: [list with timing]

Provide:

Collections detail:
• Revenue recognised vs. cash collected
• AR aging projection

Disbursements detail:
• Operating expenses
• Payroll
• One-time expenses

Cash position analysis:
• Minimum cash balance during period
• Month of minimum cash
• Average cash balance

Alerts:
• Months where cash drops below [minimum threshold] • Recommended actions to address shortfalls

Cash flow forecasts are sensitive to timing assumptions. VERIFY collection patterns and payment terms.

Quick Reference: Forecasting Formulae

Basic Calculations

Calculation	Formula	Use
Growth Rate	(New – Old) / Old × 100	Trend analysis
Weighted Pipeline	Sum of (Deal Value × Stage Probability)	Pipeline forecasting
Pipeline Coverage	Pipeline Value / Revenue Target	Forecast sufficiency
Break-Even Units	Fixed Costs / (Price – Variable Cost)	Minimum volume

SaaS Calculations

Calculation	Formula	Use
Net New MRR	New + Expansion – Contraction – Churn	MRR forecasting
Net Revenue Retention	(Starting MRR + Expansion – Contraction – Churn) / Starting MRR	Retention forecasting
Implied ARR	MRR × 12	Annual run rate
Months to Payback	CAC / (ARPU × Gross Margin)	Unit economics

Pipeline Calculations

Calculation	Formula	Use
Weighted Revenue	Deal Value × Win Probability	Expected value
Required Pipeline	Target / Average Win Rate	Pipeline planning
Velocity	(Opportunities × Win Rate × Deal Size) / Cycle Length	Capacity planning (heuristic metric, VERIFY stage consistency and cycle definition)

Forecasting Accuracy Tracking

Track these metrics to improve your forecasting over time:

Mean Absolute Percentage Error (MAPE)

Formula: Average of | (Actual – Forecast) / Actual | × 100
Lower is better
Note: MAPE is undefined when Actual = 0 and can distort results with small Actual values
Some teams target low double-digit MAPE for stable, mature revenue lines. VERIFY targets by forecast horizon, volatility, and business model.
If Actual values can be zero or near zero, consider complementary metrics such as Mean Absolute Error or scaled errors.

Forecast Bias (Mean Percentage Error)

Formula: Average of (Forecast – Actual) / Actual × 100. Positive values indicate over-forecasting.
Positive value = consistently optimistic (forecasting too high)
Negative value = consistently pessimistic (forecasting too low)
Target: Close to zero
Note: Like MAPE, this metric can distort when Actual values are near zero. Consider using Mean Error (Forecast – Actual) for absolute dollar bias instead.

Forecast Variance by Category

Track accuracy of Commit, Best Case, and Upside separately
Identify which categories are most/least reliable

Accuracy Improvement Checklist

Review forecast vs. actual monthly
Identify patterns in forecast errors
Update conversion rates and stage probabilities quarterly
Remove or re-stage deals that have aged beyond normal cycle
Validate assumptions against recent performance
Document reasons for significant misses

Best Practices for Forecasting

Data Quality

Start with clean, trustworthy data
Standardise CRM fields and make critical inputs mandatory
Run automated data quality checks weekly
Data quality improvements usually reduce forecast error. VERIFY impact for your environment.

Assumption Management

Document every assumption explicitly
Assign an owner to each assumption
Set review dates for key assumptions
Update assumptions as new data arrives

Forecast Hygiene

Update forecasts regularly, often weekly for pipeline and monthly for financial. Cadence may vary by deal velocity and business size.
Remove stale opportunities from pipeline
Distinguish between “commit” and “hope” deals
Track forecast changes over time to identify sandbagging or optimism

Communication

Present ranges, not false precision
Clearly label assumptions and confidence levels
Explain methodology to stakeholders
Update stakeholders when forecasts change materially

Common Forecasting Mistakes

Mistake	Problem	Solution
Happy ears	Believing optimistic customer signals	Verify with multiple contacts and proof points
Sandbagging	Underforecasting to guarantee beats	Track forecast accuracy and hold reps accountable to best estimates
Ignoring churn	Forecasting only new business	Always model gross and net revenue
Static assumptions	Using outdated conversion rates	Update assumptions regularly with recent data
Single-point forecasts	Presenting one number as certain	Use ranges and scenarios
Ignoring seasonality	Missing predictable patterns	Analyse at least two full seasonal cycles of data when seasonality materially affects revenue

Forecasting Templates

How to Use These Templates

Global AI Safety Line

Before You Start

Forecasting Methods Overview

Bottom-Up Forecasting Templates

Lead-to-Revenue Forecast

Sales Capacity Forecast

Weighted Pipeline Forecasting

Stage-Based Pipeline Forecast

Deal-Level Forecast

Subscription and Recurring Revenue Forecasts

MRR/ARR Forecast

Cohort-Based Revenue Forecast

Scenario-Based Forecasting

Three-Scenario Forecast

Quarterly Business Review Forecast

Time Series Forecasting

Historical Trend Forecast

Financial Planning Templates

Annual Budget Forecast

Cash Flow Forecast

Quick Reference: Forecasting Formulae

Basic Calculations

SaaS Calculations

Pipeline Calculations

Forecasting Accuracy Tracking

Best Practices for Forecasting

Common Forecasting Mistakes

Further Reading

About

Support

Legal