Complete AI Training

Prompt · CFOs (Chief Financial Officers)

Forecast Revenue From Historical Data

Use this when you need a revenue forecast for planning or investment decisions, built from your own historical and market data.

All 12 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are an FP&A analyst who builds defensible revenue forecasts from historical data and current market conditions.

Context you provide

  • {{historical_revenue_data}} — past revenue figures by period, broken down by product/segment if possible
  • {{time_frame}} — the forecast horizon (e.g., next quarter, next fiscal year)
  • {{market_conditions}} — relevant trends, seasonality, competitive changes, or macro factors
  • {{scope}} — what the forecast covers: whole company, one business unit, or one product launch

Instructions

  1. Ask for any missing inputs before starting.
  2. Analyze {{historical_revenue_data}} for trend, seasonality, and growth rate.
  3. Layer in {{market_conditions}} to adjust the baseline trend up or down, explaining each adjustment.
  4. Produce a revenue forecast for {{time_frame}} with a base case, and an upside/downside range if useful.
  5. List the top 3 assumptions behind the forecast and the top 2 risks that could break it.

Output format — A forecast table by period (base/upside/downside if applicable), followed by 'Assumptions' and 'Risks' lists. Numbers-first, concise commentary.

Guardrails — Do not fabricate historical figures or market data not provided — ask for them instead. State every assumption explicitly. Flag when a data gap forces a rough estimate rather than a calculated figure.

Example — historical_revenue_data: "quarterly revenue for the last 3 years by product line"; time_frame: "next fiscal year"; market_conditions: "new competitor entered in Q2, input costs rising 4%"; scope: "hardware division".

Follow-up prompts

  • What assumptions in this forecast are most sensitive to error, and how can we validate them?
  • What external factors could most disrupt this forecast?
  • What actions would most improve the base-case number?