Build a sensitivity table for EBITDA margin
Run a two-variable sensitivity (price × volume) on EBITDA margin and identify the breakpoints worth flagging to the board.
Copy and customize
You are a senior CFO producing the following deliverable: build a sensitivity table for ebitda margin.
Context
- Workflow: Forecasting
- Inputs available: {paste the data here}
- Period: {month / quarter}
- Audience: {who reads this}
What to produce
1. The headline takeaway in one sentence.
2. The three things that materially moved the result, with quantified contribution.
3. The one risk or anomaly worth flagging.
4. A short forward-looking note: what to watch next period.
Guardrails
- Use only the numbers provided; do not invent values.
- Cite a row reference for every claim.
- Flag anything you cannot reconcile rather than smoothing it over.
Run it in four steps
- Pull the plan P&L with revenue, COGS, and OpEx by line, and split each cost into fixed and variable.
- Paste it into
{paste the data here}, set{month / quarter}, and state the price and volume ranges to flex (typically ±5–15%). - Run it to build the two-variable sensitivity on EBITDA margin and find the breakpoints.
- Check the fixed/variable split first; it drives every cell, and a wrong classification makes the whole table confidently wrong.
When to reach for this prompt
Use for board prep when leadership wants to see margin under stress, or before pricing/discounting changes that may compress margin. Pair with the gross margin bridge if margin is currently moving.
What you can expect back
EBITDA margin sensitivity (Q4 plan)
| Volume -10% | Volume 0 | Volume +10% | |
|---|---|---|---|
| Price -5% | 11.8% | 13.4% | 14.9% |
| Price 0 | 14.2% | 15.8% | 17.3% ← plan |
| Price +5% | 16.5% | 18.1% | 19.6% |
Breakpoint: at Price -5% / Volume -10%, margin drops below the 12% covenant threshold.
This prompt has real limitations you should understand.
Two-variable sensitivities hide interaction effects with COGS mix and OpEx fixed/variable behavior. Treat the table as directional, not as a forecast — and never report a single cell from the table without context.
Interaction effects are missing
Price and volume do not move independently. A 5% price cut typically lifts volume; a 10% volume drop usually pressures discounting. The two-variable table treats them as independent and overstates the corners.
Step-functions hide in fixed costs
OpEx that looks fixed at the budgeted volume becomes variable past a threshold — new hires, new offices, new server clusters. The prompt assumes fixed stays fixed across the entire sensitivity range, and the upside corners look better than they are.
Single cells get quoted out of context
Whoever reads the table will gravitate to one number. The "Price -5% / Volume -10% → 11.8% margin" cell ends up in a board document with no surrounding scenario — and becomes the new base case in someone's head.
What your data needs to look like
- Plan P&L with revenue, COGS, and OpEx by line
- A clean split of fixed vs. variable in OpEx and COGS
- Realistic price / volume ranges (typically ±5-15%)
- Any covenant or compliance thresholds for context
See how FinanceOS handles this prompt on real financial data.
Book a 20-minute walkthrough. We’ll run this exact prompt against a sample dataset reconciled through FinanceOS, and show you what changes when the data underneath is right.
Book a walkthrough