Turn Raw Quarterly Numbers into a Board-Ready Report in 5 Minutes
Why this prompt matters
Board members spend an average of 2.5 minutes per board pack page. Reports that bury the lead, present raw numbers without narrative, or force directors to reverse-engineer the story lose the room before the meeting starts. Management credibility is won or lost in how numbers are framed — not just what the numbers say. A poorly structured board report has derailed funding rounds and eroded board confidence in otherwise strong-performing teams.
What we use it for
A founder has a board meeting on Monday. It is Friday afternoon. They have a spreadsheet of Q2 numbers and a dozen Slack messages from department heads. They need a coherent narrative that tells the story behind the numbers — not just lists them — and they have 45 minutes to pull it together.
Prompt
Act as a senior financial analyst and board communications specialist with 15+ years of experience preparing executive reports for venture-backed and public company boards. Context: I am [YOUR ROLE — e.g., CFO, Founder, VP Finance] at [COMPANY NAME], a [BRIEF DESCRIPTION — e.g., B2B SaaS company, 50 employees, Series A]. Here is our raw performance data for [QUARTER, e.g., Q2 2026]: [PASTE YOUR DATA HERE — include any combination of: revenue, ARR/MRR, growth rates, churn, burn rate, runway, headcount, customer counts, NPS, product KPIs, or department updates] Task: Transform this raw data into a polished, board-ready quarterly report with these exact sections: 1. **Board TL;DR** — One bold sentence: the single most important thing the board needs to know this quarter 2. **Executive Summary** — 3–4 sentences: the narrative arc of the quarter (what we set out to do, what happened, what it means) 3. **Financial Performance** — Revenue, margin, burn rate, runway with clear period-over-period comparisons 4. **Key Wins** — Top 2–3 achievements with supporting metrics 5. **Challenges & Risks** — Honest, data-backed assessment; flag any trend that needs board attention 6. **Strategic Outlook** — What we are prioritizing next quarter and the specific rationale 7. **Ask** — What we need from this board: decisions, introductions, approvals, or guidance Constraints: - Write in confident, direct language — no hedging, no filler phrases - Back every claim with the data provided; mark gaps as [DATA NEEDED: specify] rather than inventing numbers - Use bullet points for KPI tables; narrative paragraphs for analysis and context - Target 400–550 words total — board packs get skimmed, not read cover to cover - Do not use the phrases "in today's landscape", "it's important to note", or "moving forward" Output Format: Return the complete report in markdown with H2 headers for each section. Start immediately with the Board TL;DR.
Result
<p><strong>Board TL;DR: We hit 118% of revenue target in Q2, but CAC increased 34% YoY — we need a board decision on enterprise pricing before we re-enter those conversations.</strong></p><h2>Executive Summary</h2><p>Q2 2026 was a quarter of top-line strength with emerging bottom-line pressure. Acme Corp closed $2.1M in net new ARR — 18% above plan — driven by our mid-market expansion motion. We grew to 214 paying customers (up from 168 in Q1) and pushed NRR to 112%. However, two enterprise deals slipped to Q3 due to procurement delays, and increased paid acquisition costs compressed runway from 18 months to 14 months. We enter Q3 with strong momentum but tighter capital efficiency than planned.</p><h2>Financial Performance</h2><ul><li><strong>ARR:</strong> $8.4M (up from $6.3M in Q1, +33% QoQ)</li><li><strong>Net New ARR:</strong> $2.1M (plan: $1.78M, 118% attainment)</li><li><strong>Gross Margin:</strong> 71% (Q1: 74% — compressed by enterprise onboarding costs)</li><li><strong>Monthly Burn:</strong> $410K (Q1: $340K)</li><li><strong>Runway:</strong> 14 months at current burn</li><li><strong>CAC:</strong> $18,400 (Q2 2025: $13,700, +34% YoY)</li><li><strong>NRR:</strong> 112%</li></ul><h2>Key Wins</h2><ul><li><strong>Mid-market motion validated:</strong> 7 new logos in the $60K–$120K ACV range; average deal cycle 42 days, down from 67 in Q1</li><li><strong>NRR crossed 110% for the first time:</strong> Expansion revenue from existing accounts outpaced churn; 3 customers upgraded from Professional to Enterprise tier</li><li><strong>API v2 launched June 3 with zero P0 incidents:</strong> Shipped on revised schedule after Q1 slip; early adoption rate at 23% of active accounts within 30 days</li></ul><h2>Challenges & Risks</h2><ul><li><strong>Rising CAC:</strong> Google and LinkedIn CPMs up 28% since January; testing a partner referral channel as a lower-CAC alternative — early results inconclusive</li><li><strong>Two slipped enterprise deals ($340K combined ACV):</strong> Both in active pipeline for Q3; delays are procurement-driven, not product or pricing objections</li><li><strong>Burn trajectory:</strong> If both enterprise deals close in Q3, burn normalizes to ~$360K/month; if they slip again, runway falls below 12 months by October — at that point a bridge conversation becomes necessary</li></ul><h2>Strategic Outlook</h2><p>Q3 priorities: close the two carried enterprise deals, launch partner program (target: 5 active referral partners by end of August), and begin Series B relationship-building with a target raise window of Q1 2027. We are reducing paid acquisition spend by 15% in Q3 to improve CAC while the partner channel matures.</p><h2>Ask</h2><ul><li><strong>Decision needed:</strong> Approve the proposed enterprise pricing floor ($180K ACV minimum) before we re-engage the two slipped deals — current pricing created ambiguity in procurement conversations</li><li><strong>Introductions:</strong> Warm intros to Sequoia (Sarah Chen) and Lightspeed (Marcus Webb) for early Series B relationship-building</li></ul>
<p>Most founders and finance leads know their numbers cold. What trips them up is the framing — turning a spreadsheet into a story that builds confidence, surfaces the right risks, and gets the board to the decisions that matter.</p><p>This prompt does that translation work in under five minutes. It takes your raw quarterly data — revenue, burn, KPIs, team updates, whatever you have — and structures it into the seven sections a board actually needs: a one-line TL;DR, an executive summary, financial performance with period comparisons, wins, challenges, strategic outlook, and a clear ask.</p><h2>Why the Prompt Works</h2><p>The <strong>Role</strong> instruction positions the model as a board communications specialist, not a generic writing assistant. That framing matters: it biases the output toward executive brevity and direct language rather than academic hedging.</p><p>The <strong>Context block</strong> with <code>[PASTE YOUR DATA HERE]</code> is intentionally open-ended. You can drop in a CSV export, bullet points, a Slack summary, or a mix of all three — the model normalizes whatever format you provide.</p><p>The <strong>Constraints</strong> section prevents the two most common board report failure modes: invented numbers (solved by requiring <code>[DATA NEEDED]</code> markers) and vague prose (solved by capping length at 550 words and banning filler phrases explicitly).</p><p>The <strong>Board TL;DR</strong> section — a single bold sentence at the top — forces the model to identify the single most important thing the board needs to know. This is the hardest part to write by hand and the part boards remember longest.</p><h2>When to Use It</h2><p>This prompt is designed for quarterly board meetings, but it adapts naturally to monthly investor updates, Series A/B data room narratives, and all-hands communication to leadership teams. Swap <code>[QUARTER]</code> for a month or milestone and the structure holds.</p><h2>Tips for Better Output</h2><ul><li>Include YoY and QoQ comparisons in your raw data — the model uses whatever period references you provide</li><li>Add context about slipped deals or anomalies in your data paste; the model will flag risks more accurately if it understands the why</li><li>Run it twice with slightly different data formats and pick the version with the stronger TL;DR</li><li>Use the <code>[DATA NEEDED]</code> markers the model inserts as a checklist for your pre-meeting data gathering</li></ul>