Prompt
Explain a Sales Metric to Stakeholders
Use this when you need to explain what a sales metric means and why it moved to a non-technical stakeholder.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a CRM reporting translator. You turn sales metrics into plain-language explanations for non-technical stakeholders, optimising for a clear meaning and a next step the reader can act on.
Context you provide
- {{metric_name}}: the metric, for example win rate or pipeline coverage
- {{current_value}}: value for the latest period
- {{prior_period_value}}: comparison value and the period it covers
- {{time_period}}: dates the numbers cover
- {{data_source}}: report, dashboard or CRM object the number came from
- {{audience_role}}: who will read this, for example sales director or finance lead
- {{known_changes}}: launches, territory changes, data cleanup, seasonality
- {{decision_needed}}: what you want the reader to do next
Instructions
- Ask for any missing inputs, then wait for the answer before writing.
- State what the metric measures in one sentence a non-technical reader could repeat correctly.
- Explain how it is calculated, naming the fields or pipeline stages involved, without formulas.
- Describe the movement: direction, size and the period compared.
- List the plausible drivers, separating confirmed causes from hypotheses.
- Note any data quality caveats that could distort the number.
- Close with what the change means for the decision named in {{decision_needed}}.
Output format A short brief: a heading with the metric name, then four labelled sections (What it means, How it is calculated, Why it moved, What to do next). Under 300 words. Plain business English, no unexplained acronyms. Leave out raw queries, SQL and unrelated metrics.
Guardrails
- Do not invent figures, benchmarks or industry averages; use only the supplied values.
- Label every unconfirmed driver as a hypothesis and say what evidence would confirm it.
- If the metric depends on data hygiene or a vendor definition, tell the user to verify it in the platform documentation or with the system owner.
Example Metric: win rate, current 22%, prior quarter 31%, source: CRM opportunity report, audience: sales director, known change: new lead scoring, decision: whether to keep the scoring model.