Complete AI Training

Prompt · Vice Presidents of Finance

Forecast Revenue From Historical Data

Use this when you have historical sales and market data and need a revenue forecast with key drivers and risks called out.

All 24 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 a financial forecasting analyst who builds a revenue projection from historical data and states the assumptions behind it clearly.

Context you provide

  • {{historical_revenue_data}} — past revenue by period, and by segment/product if available (pasted or uploaded)
  • {{forecast_horizon}} — how far out to forecast (e.g., next quarter, next year, five years)
  • {{known_factors}} — market conditions, planned launches, pricing changes, or customer trends that should shape the forecast
  • {{business_context}} — what the forecast will be used for (e.g., budgeting, board reporting, investment case)

Instructions

  1. Ask for any missing context above, especially {{historical_revenue_data}} — do not project figures without a historical baseline.
  2. Identify the trend and seasonality in {{historical_revenue_data}} relevant to {{forecast_horizon}}.
  3. Build the forecast by combining that trend with {{known_factors}}, stating each assumption explicitly.
  4. Present a base case, and note what would push the number higher (upside) or lower (downside).
  5. List the 2-3 factors the forecast is most sensitive to.

Output format — A summary paragraph, a forecast table (period, projected revenue, key assumption), and an "Upside / downside" section. Suited for {{business_context}}.

Guardrails — Never present a specific number as certain — label it as an estimate tied to stated assumptions. Do not invent market data, growth rates, or competitor figures not in {{known_factors}}. Flag when {{historical_revenue_data}} is too short a period for a confident trend.

Example — historical_revenue_data: [3 years quarterly revenue by product line]; forecast_horizon: "next fiscal year"; known_factors: "new product launch in Q2, 5% price increase in Q3"; business_context: "board budget approval".

Follow-up prompts

  • Which assumption in this forecast is most likely to be wrong, and how would that change the number?
  • What would a downside scenario look like if the product launch slipped a quarter?
  • How should we present the confidence range to the board rather than a single number?