Convert a 30-Slide Board Deck Into a One-Page CFO Summary With Claude (2026)

Your CFO will not read 30 slides before a board meeting. What they will read is the one-pager sitting in their inbox the night before, and that document is what shapes the questions they ask and the positions they take. The problem is that producing a tight, accurate one-pager from a full board deck takes two to four hours of careful editing, and most ops teams compress that time badly, sometimes changing numbers in the process. Claude can reduce a 30-slide deck to a structured one-page summary in under 15 minutes, but only if you give it a fixed rubric and then cross-check every figure it produces against the source slides. A summary that quietly changes a number is worse than no summary at all.

TL;DR

• CFOs read the ask, the numbers, variance to plan, and risks. Not narrative slides.

• Use a fixed five-section rubric so every summary has the same shape.

• Chunk slides into groups of five to eight before pasting into Claude.

• Have Claude list every figure with its source slide, then verify totals yourself.

• Escalate missed forecasts. Flatten boilerplate.

What do CFOs actually read on a board deck?

CFOs focus on four things: the specific decision or approval being requested, the core metrics with period-over-period comparison, actual versus plan variance with an explanation for the delta, and the risks with their financial exposure. Narrative slides, vision pages, team spotlights, and product roadmaps are skimmed or skipped entirely. McKinsey's CFO advisory practice notes that finance executives consistently report spending less than 20 percent of their board-prep time on strategic narrative and over 60 percent on financial details and risk review. If your summary does not isolate those four items on page one, the CFO is already doing their own extraction, and they may get it wrong.

The implication for your Claude workflow is simple: do not ask Claude to summarize the whole deck. Ask it to extract the four categories the CFO cares about and ignore the rest. The rubric below is how you make that instruction concrete and repeatable.

The one-page rubric: what belongs in each section

A one-page CFO summary works when every version follows the same five-section structure. CFOs build pattern recognition across decks, and a consistent shape lets them skip the orientation phase and go straight to the numbers. The table below is the rubric. Paste it into every Claude prompt you use for this workflow.

This rubric is also how you scope what Claude should ignore. Tell it explicitly: "Do not summarize vision, team, product roadmap, or appendix slides." That instruction reduces the output length and the hallucination surface area at the same time.

The chunking method: why you never paste a raw 30-slide dump

You should split the deck into slide groups before sending anything to Claude. Each group should cover five to eight slides on a single topic: one group for the exec summary, one for the metrics package, one for the variance analysis, one for risks, one for the ask. Send each group separately and tell Claude which rubric section it maps to. This keeps Claude's context focused on one job at a time, which produces cleaner extractions and makes it easy to trace every line of the final summary back to a specific slide range.

If you paste all 30 slides at once, Claude has to decide what matters and what does not, and it will sometimes average across slides or pull a number from the wrong chart. Chunking removes that decision. You are doing the editorial judgment work (which slides belong to which section) and letting Claude do the text compression work (turning five slides of budget commentary into four bullets). Each role gets the job it is actually good at.

A practical grouping for a standard Series A board update: slides 1-3 are exec summary, slides 4-9 are metrics, slides 10-15 are budget and variance, slides 16-19 are risks and mitigations, slides 20-22 are the ask, slides 23-30 are appendix (skip entirely). This grouping takes about two minutes to produce and saves the downstream cross-check from needing to scan the whole deck.

The numbers-consistency cross-check

This step is not optional. After Claude produces the draft summary, your next prompt should be: "List every number in this summary with the slide it came from." Claude will return a table of figures and source references. You then check two things: each figure against the actual slide, and whether totals are internally consistent (revenue minus cost of goods sold should equal gross profit, for example). Finance leads report that even well-prompted summaries occasionally transpose a figure or confuse a quarterly number with an annual one. The cross-check catches those errors before the summary goes to the CFO.

The exact cross-check prompt you paste in is:

"Review the summary you just wrote. List every numeric figure it contains in a table with three columns: the number as written, the section of the summary it appears in, and the slide number it came from. If you are not certain of the source slide for a figure, flag it with [VERIFY]. Do not infer or calculate any numbers that were not explicitly stated in the slides I gave you."

Any row with [VERIFY] means you open the deck and confirm it yourself before the summary goes out. This one prompt turns a plausible-looking summary into a traceable one. It also means the CFO can ask "where did this $4.2M number come from" and you can answer in ten seconds.

What to escalate versus flatten

Not every piece of information in a board deck deserves equal weight in the CFO summary. The decision you make on each item is escalate (include with prominence, possibly more detail than the slide had) or flatten (compress to a single phrase or drop entirely). The rule: anything with a dollar variance, a covenant implication, or a decision attached gets escalated. Everything else gets flattened.

Specific escalation triggers: a revenue miss of more than 5 percent against plan, a burn rate that has increased quarter-over-quarter without a corresponding growth offset, a customer concentration risk above 20 percent of ARR in one account, or an open legal or regulatory item with financial exposure. These do not just get included. They get a separate bullet with the dollar figure and a one-sentence cause statement, even if the board deck buries them in an appendix table.

Flatten without hesitation: the company mission statement, product philosophy paragraphs, team bios, generic market size slides (unless the TAM is the specific thing being discussed), and any slide that is purely a visual without a number attached to it. These are relevant for board members who are reading the full deck. They are not relevant for a CFO reviewing the financial picture before the meeting. Your instructions to Claude should name both categories explicitly so it applies the same judgment you would.

The finance and legal AI tool directory covers the broader set of tools that handle document extraction, contract review, and financial analysis, if you are building a more comprehensive workflow around board prep.

Worked examples: the same rubric applied to three deck types

The rubric table above works across deck types, but the source slides and emphasis shift. Here is how the five sections map for three common board updates.

Series A board update (monthly or quarterly): Decision asked is usually "note the monthly update" or occasionally "approve the new hire plan." Key metrics are MRR, net revenue retention, burn multiple, and months of runway. Variance section focuses on MRR versus plan and how churn landed. Risks include concentration in top three customers and sales pipeline coverage. The ask is usually approval of a specific budget reallocation or a heads-up on a covenant-relevant metric. This type of deck is the most common and the cleanest fit for the rubric.

Ops review (internal, quarterly): Decision asked is headcount or tooling spend approval. Key metrics shift to unit economics: CAC, LTV, gross margin by segment, headcount productivity. Variance section is where department heads justify or explain their budget lines. Risks are operational: a key departure, a system outage with a revenue impact, a vendor contract renewal. The ask is the budget approval or the headcount table sign-off. Claude handles this type well because the source material is usually more tabular and less narrative.

M&A update (strategic): This type requires more care. Decision asked is often "approve LOI" or "authorize diligence spend." Key metrics are the target's ARR and growth rate, the proposed valuation multiple, and the estimated integration cost. Variance section does not apply in the traditional sense but can cover how the target's metrics compare to initial projections. Risks are deal-specific: regulatory, retention of key employees at the target, integration timeline. The ask is precise: the dollar amount of the diligence budget, the proposed LOI terms, the board vote required. For M&A decks, do not let Claude summarize the legal or valuation modeling sections. Extract those verbatim and attach them as a separate block marked "CFO review required."

In all three cases, the before/after looks like this: a 30-slide deck that takes an experienced finance person 90 minutes to distill goes through the chunked Claude workflow and produces a draft summary in 12 to 15 minutes, with the cross-check adding another five minutes. The draft requires one pass of human editing to confirm escalation decisions and verify the flagged numbers, bringing the total to roughly 25 to 30 minutes. Operators who have run this workflow report saving two to three hours per board cycle across the prep team. See the 2026 AI automation rate card for how teams price this kind of workflow when it is deployed as a managed service.

For teams that also use Claude for document processing across other office tools, the Claude Microsoft Office integration guide covers how to set up the workflow if your board decks originate in PowerPoint or your summaries go out via Outlook.

Want this workflow built for your board prep process?

Vantaige builds done-for-you AI document workflows: board deck extraction, CFO summary templates, number cross-check automations, and integration with your existing finance stack. If your team spends hours on board prep that should take minutes, book a free automation audit and we will show you exactly where the time is going.

FAQ

Can Claude read a PPTX or PDF directly?

Yes. Claude can accept PDF files directly via the file upload feature in Claude.ai. For PPTX, the most reliable approach is to export to PDF first, then upload, because raw PPTX can lose chart data during extraction. Anthropic's documentation confirms PDF support up to 100MB in the 2026 model versions. Always verify that charts and tables converted correctly before running the summary prompt, since image-only charts in a PDF will not extract as numbers.

Will Claude invent numbers that are not in the deck?

It can, and this is the specific risk the cross-check prompt addresses. Claude may interpolate, average, or confuse similar-looking figures from different slides, particularly when charts share color schemes or when the same metric appears in multiple time periods. The cross-check instruction ("flag any figure you cannot source to a specific slide") is what catches this before it reaches the CFO. Do not skip it.

Is my financial data used to train Anthropic's models?

Anthropic's usage policy states that inputs submitted via the API are not used to train models by default. For Claude.ai Pro and Team plans, Anthropic also states that conversations are not used for training. If you are working with material-nonpublic financial information, check your organization's data handling policy and consider whether the Claude Team plan's data controls meet your requirements before uploading sensitive board materials. Anthropic's privacy page at claude.ai is the authoritative source for current data handling terms.

How long should the finished one-pager be?

One page means one page: roughly 400 to 600 words in the final document, or the equivalent in a formatted template with five sections. If the draft is longer, tell Claude to cut the key metrics section to the top four figures only and to remove any sentence that does not contain a number, a named risk, or a specific decision. The CFO does not need context they already have from the deck. They need the extraction.

Can Claude match our existing CFO summary template?

Yes. Paste your template structure into the prompt as a formatting instruction before you send the slide content. Include exact section headers, preferred number formatting (for example, "$4.2M" versus "4,200,000"), and any house style for variance notation ("+12% vs. plan" or "12pp above forecast"). Claude follows explicit formatting instructions reliably when they are included at the start of the prompt, before the content.

Is this workflow available on the free Claude plan?

The free plan has file upload limits and rate limits that make a multi-chunk 30-slide workflow impractical for regular use. Claude Pro (individual) or Claude Team (organization) are the right tiers for board prep workflows. Team adds SSO, higher usage limits, and the data-usage controls that regulated finance teams need. Pricing is on the Anthropic website.

What should you never delegate to Claude in this workflow?

Never delegate the escalation decision itself. Claude can identify that a metric missed plan, but it cannot assess whether that miss represents a covenant breach, a red flag for investors, or something the CFO already knows about from a side conversation. That judgment is yours. Also never send Claude the final summary to "improve" without re-running the cross-check, because editing passes can introduce paraphrase errors that change a number's meaning. Human review on the figures is the non-negotiable last step every time.

Related from Vantaige

• Claude: full tool profile and use case guide

• Claude with Microsoft Office: Excel, Word, and Outlook setup (2026)

• Finance and legal AI tools: the full directory

• 2026 AI automation rate card: what operators charge

References

1. Anthropic, Claude model capabilities and file upload documentation. docs.anthropic.com

2. Anthropic, data privacy and usage policy for Claude.ai. claude.ai

3. McKinsey, CFO role and finance function effectiveness research. mckinsey.com

4. CFO, board reporting best practices and financial communication. cfo.com