AI AI Tools Guidebook
AI Use Cases

AI Business Driver Breakdown: The Two Numbers That Move Revenue

Hand AI your revenue and cost trees and let it write the executive narrative for what is really driving the quarter.

Published: Author: AI Productivity Guide Team 🌐 查看中文版本

The task

Revenue is up 14%. Margin is down 2 pts. You need to write, in one paragraph, which two underlying drivers actually explain both — for a board pre-read where nobody will open the appendix.

When this is the right job for AI

  • You already have a decomposition tree (volume × price × mix, or units × ARPU, etc.).
  • You can hand AI the deltas at each node — not the raw GL.
  • You want narrative, not modeling. AI is good at “explain this tree”; bad at “build this tree.”

What to feed the AI

  • Top-line metric, base and current period (e.g. “Revenue: $38M → $43.4M”)
  • The first 2 levels of the driver tree as a flat list:
    • Volume: 1.2M → 1.32M (+10%)
    • Price: $31.6 → $32.9 (+4%)
    • Mix: B-tier share 18% → 24%
  • Margin tree similarly
  • Audience and length constraint

Copy-ready prompt

You are writing the "drivers" paragraph for a board pre-read.

Revenue: $38M → $43.4M (+14%)
Drivers (level 1):
- Volume +10% (units 1.20M → 1.32M)
- Price +4% (ARPU $31.6 → $32.9)
- Mix: B-tier share 18% → 24% (higher-priced)
- One-time: enterprise renewal pulled forward = +$0.8M

Margin: 56% → 54% (-2 pts)
Drivers (level 1):
- COGS/unit +6% (input costs)
- Mix shift toward enterprise = -1 pt gross margin
- FX (CNY/USD) -0.5 pt

Write:
1. The two drivers (one for revenue, one for margin) that actually carry the story.
2. One sentence on which is structural vs. one-time.
3. One implication for next quarter.

Audience: board members, non-finance. 120 words. No bullets — one paragraph.

Sample output structure

Revenue growth is real but two-thirds volume-driven, not price — sustaining 14% next quarter requires we keep the volume engine running, since pricing only carries 4 pts. Margin compression is the more structural story: COGS/unit is up 6% on input costs and is unlikely to reverse this quarter. The one-time pull-forward ($0.8M) flattered Q3 revenue by ~2 pts; back it out and underlying growth was closer to 12%. Implication: Q4 plan should assume 12% growth and a 54% margin floor unless we successfully renegotiate two top supplier contracts.

How to refine

  • AI gives you a list of 5 drivers — push back: “pick the one driver that explains 80% of the move.”
  • Output too quantitative — add “the audience does not have the deck open; do not cite percentages they cannot see.”
  • AI conflates one-time and structural — add a hard rule: “label each driver structural or one-time in your head and tell me which is which.”

Common mistakes

  • Feeding AI the raw GL trial balance and asking it to build the tree. It will hallucinate aggregations.
  • Asking for 8 drivers. The audience will remember zero. Two drivers, one paragraph.
  • Skipping the “structural vs. one-time” split — this is the single most useful framing for execs.
  • Letting AI invent benchmarks (“industry average is 6%”). Strip those unless you have a real source.

Practical depth notes

For AI Business Driver Breakdown: The Two Numbers That Move Revenue, the difference between a usable AI result and a generic one is the input packet. Give the model the audience, the current draft or raw material, the desired format, the decision you need to make, and two examples of what good and bad output look like. Ask it to preserve facts first, then improve structure or wording second.

After the first response, do a separate review pass. Look for missing constraints, invented details, weak calls to action, and language that sounds plausible but does not match the real situation. The best final output should be easy to use immediately: clear owner, clear next step, and no hidden assumption that someone else has to untangle. A stronger version of this workflow also defines the handoff. Decide who will use the output, what they should do next, and what information would make them reject it. If the deliverable is copy, test whether it has a single clear action. If it is analysis, test whether it separates observation from recommendation. If it is planning, test whether dates, owners, and tradeoffs are explicit enough for someone else to execute. One final check: compare the finished result against the original goal in a single sentence. If that sentence is hard to write, the output is probably polished but unfocused. Tighten the goal, remove decorative language, and rerun only the weak section instead of regenerating the entire piece.

FAQ

  • What if my driver tree is incomplete? Tell AI exactly that: “These are the only levers I have measured. Do not infer hidden drivers.” It will stay disciplined.
  • Can I have AI suggest drivers I haven’t measured? Yes — separate prompt, separate output. Do not mix exploratory and reportable.
  • How does this differ from variance analysis? Drivers explain “why the metric moved at all”; variance explains “why we missed plan.” Different audiences.

Tags: #AI writing #Finance #Business analysis #KPI #Executive update

Related Articles