FP&A professionals spend up to 60% of their week on routine data collection and formatting, leaving only 35% for high-value analysis. By using a structured Context-Reasoning-Output prompt framework, you can automate variance commentary, scenario planning, and board reporting, saving at least 5 hours per week of manual work.
The 10 prompts
Prompt 1: The variance narrative generator saves ~45 min/month
This is the bread and butter. Instead of writing "Revenue was $2.3M vs. $2.1M budget, favorable by $200K due to stronger enterprise bookings" fourteen times, you feed it your table and let it draft.
You are a senior FP&A analyst writing commentary for a monthly business review.Here is a variance table in CSV format:[PASTE YOUR VARIANCE TABLE HERE]Write concise, professional variance commentary for each line item. Use this format:- Lead with the dollar variance and direction (favorable/unfavorable)- State the primary driver in plain business language (not accounting jargon)- Flag any items requiring management attention with [WATCH]- Keep each line to 1–2 sentences maximumTone: direct, confident, board-ready. Avoid passive voice.
Real result: first draft in 2 minutes vs. 35 minutes manual. Required light editing in ~60% of cases.
Prompt 2: The bridge-to-budget translator saves ~1.5 hrs/month
The hardest FP&A writing task is explaining a complex budget bridge to a non-finance audience. This prompt turns a waterfall into a story.
I need to explain our Q3 budget bridge to a non-finance executive audience.Budget: $4.2M EBITDAActual: $3.7M EBITDAVariance: -$500K unfavorableKey drivers (in order of impact):1. Higher COGS due to freight surcharges: -$280K2. Headcount savings from delayed backfills: +$120K3. Marketing spend pulled forward from Q4: -$180K4. One-time legal settlement: -$160KWrite a 3-paragraph executive summary that:- Opens with the headline number and overall context- Explains each driver in business terms (no accounting jargon)- Closes with what we expect going forward and what management is doing about itAudience: CEO and board members with no finance background. Tone: transparent, confident, solution-oriented.
Prompt 3: The scenario summary table saves ~30 min/week
You've built three scenarios in Excel. Now you need to explain them in the board deck in a way that doesn't require a PhD. This prompt generates the narrative table in seconds.
I have three forecast scenarios for FY2025. Summarize them in a clear comparison table with a brief narrative for each.Base case: Revenue $42M, EBITDA $6.1M (14.5% margin) — assumes stable macro, no new enterprise winsUpside case: Revenue $47M, EBITDA $7.8M (16.6% margin) — assumes 2 enterprise deals close in Q3Downside case: Revenue $37M, EBITDA $4.2M (11.4% margin) — assumes one existing customer churns, freight costs stay elevatedFormat: a markdown table with columns for Scenario, Revenue, EBITDA, Margin, and Key Assumption.Then write 2-sentence narrative for each scenario explaining the "so what" for leadership.
Prompt 4: The management commentary rewriter saves ~20 min/report
You have decent commentary but it's too long, too passive, or too jargon-heavy for the CFO. This prompt cleans it up without losing the substance.
Rewrite the following FP&A commentary to be more concise and executive-ready.Rules:- Maximum 2 sentences per line item- Lead with the business impact, not the accounting movement- Remove passive voice ("was driven by," "was impacted by")- Replace jargon: "unfavorable variance" → "missed by", "YTD actuals" → "year-to-date results"- Keep all numbers exactly as written — do not round or estimateOriginal commentary:[PASTE EXISTING COMMENTARY HERE]
Prompt 5: The department cost walk explainer saves ~40 min/month
Department heads always want to know why their budget looks the way it does. This prompt generates department-specific cost walk summaries you can send directly.
Write a cost walk summary for the Engineering department's Q2 actuals vs. budget.Department: EngineeringBudget: $1.85MActual: $2.1MVariance: $250K unfavorableDrivers:- Headcount: 2 hires came in above band (+$95K)- Contractor spend: exceeded plan due to product launch support (+$130K)- Software licenses: under plan due to delayed renewal (-$40K)- T&E: slightly over due to team offsite (+$65K)Write this as a plain-language email summary I can send to the VP of Engineering. Tone: collaborative, not accusatory. Include a brief ask for their input on Q3 guidance.
Prompt 6: The board deck bullet sharpener saves ~25 min/deck
Board deck bullets are their own artform - short, punchy, no fluff, and they need to land in 10 seconds of glancing. This prompt is ruthless at producing them.
Convert the following financial narrative into 3–5 board-ready bullet points for a slide titled "Q2 Financial Highlights."Rules:- Each bullet must be one line, maximum 12 words- Start each bullet with a number or percentage where possible- Lead with the positive, footnote the risks- No sentences starting with "We" or "Our"- Use parallel structure across all bulletsSource narrative:[PASTE YOUR NARRATIVE HERE]
Prompt 7: The reforecast rationale writer saves ~1 hr/quarter
Every reforecast needs a written rationale explaining why the numbers changed. Nobody wants to write this. Now nobody has to.
Write a reforecast rationale memo for our Q3 FY2025 reforecast submission.Original full-year guidance: Revenue $44M, EBITDA $6.5MUpdated forecast: Revenue $41M, EBITDA $5.6MDelta: Revenue -$3M, EBITDA -$900KPrimary reasons for revision:1. Enterprise deal slip from Q3 to Q4 (2 deals, ~$2.1M revenue impact)2. Gross margin compression from higher cloud hosting costs (-$600K)3. Partial offset from lower G&A due to hiring freeze (+$800K impact)Audience: CFO and FP&A leadershipFormat: 3 paragraphs — (1) headline summary, (2) driver detail, (3) path forward and any actions being takenTone: factual, accountable, forward-looking. Do not be defensive.
Prompt 8: The KPI deviation alert drafter saves ~30 min/week
When a KPI breaks threshold mid-month, you need to notify stakeholders fast. This prompt generates a clean alert message that doesn't cause unnecessary panic.
Draft a KPI deviation alert for our weekly finance flash report.KPI: Gross Margin %Expected range: 62–65%Current week actual: 58.3%Deviation: -3.7 percentage points below floorKnown cause: One-time freight surcharge from supplier on 3 SKUs (identified, non-recurring)Expected resolution: Returns to range by week 3Write a 2-paragraph alert for the weekly flash. Paragraph 1: state the deviation and magnitude clearly. Paragraph 2: explain the cause and expected resolution.Tone: factual, calm, informative. This goes to the CFO and three VPs — do not bury the number or soften the magnitude.
Prompt 8: The KPI deviation alert drafter saves ~30 min/week
When a KPI breaks threshold mid-month, you need to notify stakeholders fast. This prompt generates a clean alert message that doesn't cause unnecessary panic.
Draft a KPI deviation alert for our weekly finance flash report.KPI: Gross Margin %Expected range: 62–65%Current week actual: 58.3%Deviation: -3.7 percentage points below floorKnown cause: One-time freight surcharge from supplier on 3 SKUs (identified, non-recurring)Expected resolution: Returns to range by week 3Write a 2-paragraph alert for the weekly flash. Paragraph 1: state the deviation and magnitude clearly. Paragraph 2: explain the cause and expected resolution.Tone: factual, calm, informative. This goes to the CFO and three VPs — do not bury the number or soften the magnitude.
Prompt 9: The rolling forecast assumption documenter saves ~20 min/report
The assumption log is the most neglected artifact in FP&A. This prompt builds a clean, audit-ready assumption table from your bullet notes.
Convert the following rough forecast assumptions into a structured assumption table.My rough notes:- Revenue: assuming 5% QoQ growth based on pipeline coverage of 1.8x; doesn't include any deals under legal review- COGS: holding gross margin flat at 63%; doesn't model any freight changes- Headcount: includes 4 approved backfills in Q4, no new req approvals- CapEx: Q4 server refresh delayed to Q1 next year per ITFormat as a table with columns: Category | Assumption | Basis | Key Risk | OwnerUse plain, precise language. Flag any assumption where the basis is weak or the risk is high with a [HIGH RISK] tag.
Prompt 10: The QBR narrative builder saves ~45 min/quarter
The quarterly business review narrative is the single most time-consuming FP&A writing task. This prompt builds the skeleton in one pass then you refine it.
Write the financial narrative section of our Q2 Quarterly Business Review.Company: [B2B SaaS, ~$40M ARR]Audience: full leadership team and board observersQ2 Summary:- Revenue: $10.3M vs. $9.8M plan (+5.1%, +$500K favorable)- Gross Margin: 61.2% vs. 63.5% plan (-230bps, primarily freight)- EBITDA: $1.1M vs. $1.4M plan (-21% unfavorable)- Cash: $8.2M, 7.4 months runwayWrite 4 sections:1. Q2 headline (2–3 sentences, lead with what went well)2. Revenue performance (explain beat, name top contributors)3. Margin and profitability (explain the gross margin miss and EBITDA gap honestly)4. Looking ahead to Q3 (top 3 financial priorities, one risk to flag)Tone: honest, confident, forward-looking. The CEO will read this out loud in the meeting.
The quarterly business review narrative is the single most time-consuming FP&A writing task. This prompt builds the skeleton in one pass — then you refine it.
Write the financial narrative section of our Q2 Quarterly Business Review.Company: [B2B SaaS, ~$40M ARR]Audience: full leadership team and board observersQ2 Summary:- Revenue: $10.3M vs. $9.8M plan (+5.1%, +$500K favorable)- Gross Margin: 61.2% vs. 63.5% plan (-230bps, primarily freight)- EBITDA: $1.1M vs. $1.4M plan (-21% unfavorable)- Cash: $8.2M, 7.4 months runwayWrite 4 sections:1. Q2 headline (2–3 sentences, lead with what went well)2. Revenue performance (explain beat, name top contributors)3. Margin and profitability (explain the gross margin miss and EBITDA gap honestly)4. Looking ahead to Q3 (top 3 financial priorities, one risk to flag)Tone: honest, confident, forward-looking. The CEO will read this out loud in the meeting.
Pro tips
