How to Write a 1-Page Strategy Memo for a Skeptical CFO (with AI)

A strategy memo written for a CEO and a strategy memo written for a CFO are different documents, even when they're about the same recommendation. CEOs read memos through a lens of strategic posture, organizational implications, and external optics. CFOs read through a lens of financial logic, embedded assumptions, and downside scenarios. A memo that wins a CEO's interest can fail a CFO's review on grounds the CEO never raised.

This matters because most strategic decisions of any size require CFO concurrence — and on most boards, the CFO's "I have concerns" is the single most-quoted phrase in the deliberation. A consultant who can write a strategy memo that survives CFO scrutiny on first read is a consultant whose recommendations get implemented. A consultant whose memos consistently bounce off the CFO is a consultant whose work generates discussion but not change.

This guide is the one-page format CFOs read with the least friction. The Consultant Strategy Memo Generator produces it from a context input. The thinking — the assumptions, the conviction, the financial logic — is the consultant's.

A note on scope. This article is general guidance for management consultants and finance professionals working with CFOs. It is not financial, tax, or audit advice. Specific accounting treatment, tax implications, and regulatory disclosure of strategic decisions warrant the client's CFO, controller, external auditors, and tax advisors. The memo structure below is a writing format, not a financial-analysis methodology.

Key takeaways

• CFOs read for four things in this order: the number, the assumptions behind it, the downside, and the cost of waiting. A memo that doesn't answer those in the first 200 words has lost the CFO.
• The 1-page structure: recommendation + number + conviction (3 sentences); 3-line financial logic; sensitivity table on load-bearing assumptions; realistic downside paragraph; cost of waiting; decision gating with exit criteria.
• Conviction-with-named-contingency signals honesty. "High, contingent on X" reads as analysis; "high conviction" without a contingency reads as advocacy.
• The realistic downside, not the worst-case theoretical disaster, is what builds CFO trust. Worst-case scenarios read as theater; realistic downsides read as having considered the failure modes.
• The sensitivity table is what most distinguishes a CFO-grade memo from a CEO-grade one. The CFO does mental math while reading; the table either builds confidence or surfaces the conversation the memo needs to have.

What CFOs read for

A CFO reading a strategy memo is usually trying to answer four questions, in this order:

1. What's the number? What is the expected financial impact, in dollars, and over what time horizon?
2. What assumptions is that number resting on? Which assumptions are the load-bearing ones, and how confident is the analysis in each?
3. What's the downside? If the load-bearing assumptions are wrong, what happens?
4. What's the cost of not deciding now? Is there a real cost to delay, or is the urgency manufactured?

A memo that answers those four questions cleanly, in the first 200 words, has the CFO's attention. A memo that meanders through strategic framing before getting to the financials has lost the CFO before page two.

The 1-page structure

The Consultant Strategy Memo Generator supports this structure directly. Run it section by section, then review.

Section 1 — The recommendation, the number, the conviction (3 sentences, top of page)

Lead with the answers to the CFO's first three questions, in three sentences:

Recommendation: [the specific action being recommended, in one sentence]. Expected financial impact: [the headline number, with the time horizon — e.g., "$12–18M in incremental EBITDA over three years, weighted toward years 2 and 3"]. Conviction: [high / mixed / low], with the load-bearing assumption named — e.g., "High, contingent on the assumption that the new pricing tier converts at 8% or higher."

The conviction-with-named-assumption phrase is the CFO-specific touch. CFOs are calibrated for memos that name uncertainty up front. A memo that claims high conviction without naming what it's contingent on reads as advocacy. A memo that names the contingency reads as honest.

Section 2 — The 3-line financial logic

The numbered logic chain that produces the headline number. Three to five lines, no more.

1. The addressable segment is estimated at [N] customers based on [stated source].
2. Conversion at [pricing tier X] is modeled at [Y%] based on [prior comparable / pilot data / industry benchmark, with citation].
3. The implied incremental revenue is [$N], and the EBITDA contribution is [$M] after [stated cost assumptions].

The CFO reads these lines and can challenge any of them. That's the point. A defensible memo invites the challenge, because the challenge improves the analysis. A memo that buries the logic under prose invites the CFO to challenge the consultant's credibility, which is a worse conversation.

Section 3 — The load-bearing assumptions, with sensitivity

A short table or list naming the three to five assumptions the analysis is most sensitive to, and what happens to the headline number if each is off.

Assumption	Base	If 20% worse	If 20% better
Conversion at new tier	8%	$7M EBITDA	$24M EBITDA
Customer-acquisition cost stable	flat	-$3M	+$2M
Ops cost-to-serve scales linearly	as modeled	-$1M	+$1M

The CFO does the mental arithmetic on this table while reading. The arithmetic builds confidence — or, when it doesn't, surfaces the conversation the memo needs to have. Either is better than discovering the same arithmetic in week six of implementation.

A memo without sensitivity is read as a memo that wasn't pressure-tested. The sensitivity section is what most distinguishes a CFO-grade memo from a CEO-grade one.

Section 4 — The downside scenario (one paragraph)

Name the realistic downside, not the worst-case theoretical disaster. Worst-case scenarios read as theater. Realistic downsides read as analysis.

Realistic downside. If conversion at the new tier comes in at 5% instead of 8%, the three-year EBITDA contribution is approximately $5M rather than $12–18M. At 5%, the investment still produces positive contribution, but the payback period extends from 14 months to 26 months. The project remains net positive in this scenario; the strategic argument for it weakens.

The structure: name the assumption that's off, name the implied number, name what changes in the strategic logic. A CFO who sees the downside scenario written this way reads the consultant as someone who has considered the failure modes — which is the credential that allows the CFO to recommend approval.

Section 5 — The cost of waiting (two to three lines)

If there's a real cost to delay, name it. If there isn't, say so — and don't manufacture urgency.

Cost of waiting. Each quarter of delay reduces the three-year EBITDA contribution by approximately [$N], driven by the seasonal pattern of customer acquisition and the competitive entry expected in [timeframe]. There is no near-term regulatory or contractual trigger; the delay cost is opportunity cost.

The honesty about whether the urgency is real is part of the CFO's read on whether the consultant is trustworthy. Manufactured urgency is the single most common reason CFOs reject memos that would otherwise be approved.

Section 6 — Implementation gating and decision rights (closing)

The last block of the memo names what would need to happen for the recommendation to be acted on:

Decision needed: [from whom, by when, and at what level — e.g., "CEO approval, by [date], for proceeding to the implementation planning phase; board notification at the [date] meeting"]. First milestone: [the first observable thing that should happen if approved — e.g., "Engagement of a pilot customer cohort within 60 days, with conversion data reportable at the next board meeting"]. Exit criteria: [what would cause the project to be paused or stopped — e.g., "Conversion below 4% in the pilot cohort triggers a pause for re-evaluation"].

The exit criteria are particularly CFO-friendly. A CFO who can point at a written exit criterion is a CFO who can approve the project knowing there's a defensible off-ramp.

What this approach is not

A few honest limits:

• It's not a substitute for the underlying financial work. The one-page memo is the surface; the model, the assumption documentation, and the supporting analysis are the work product the memo is summarizing. The memo travels; the underlying analysis is what makes the memo defensible.
• It's not a substitute for the CFO's own model. CFOs typically have their own analytical infrastructure. A memo that pre-empts their model will be received as advocacy. A memo that gives them what they need to run their own model will be received as input.
• It doesn't replace conversation. Memos prepare conversations. The decision happens in dialogue, not in writing. The memo is the document the dialogue happens around.

What AI does, and what it doesn't

The Consultant Strategy Memo Generator handles the writing layer: the structural fidelity to the six-section format, the consistent voice, the discipline of leaving out the wrong things, the sensitivity-table formatting.

AI does not:

• Form the recommendation. The consultant's view is the consultant's view, formed from the work.
• Build the financial model. That's the consultant's (or the client's finance team's) work product.
• Name the load-bearing assumptions. Those are judgment calls the consultant makes after pressure-testing the analysis.
• Replace the consultant's professional accountability. The memo goes out under the consultant's name. The numbers are the consultant's. The accuracy is the consultant's.

How to start

The next strategy memo you're producing, write it in this structure first — before writing the version you might have defaulted to. Run the draft through the Consultant Strategy Memo Generator. Pressure-test the load-bearing assumptions yourself. Send the one-page version to the engagement partner or the client's CFO for early read. The feedback you get on this format will calibrate every memo after it.

The consultants who develop CFO-grade memo discipline tend to develop a different reputation in the market over a year or two. Not louder. More serious. That reputation is what compounds.

Next steps

• Consultant Strategy Memo Generator — the six-section structure end-to-end.
• Consultant Executive Summary Generator — for the top-of-memo section when distributed beyond the CFO.
• The Independent Consultant's Pricing Memo Stack — for the engagement-conversation memos that sit upstream of the strategy memo.
• Management Consultant Claude Plugin install guide — to run the workflow from inside Claude.

Frequently asked questions

How do you write a strategy memo for a CFO?

Lead with the recommendation, the financial impact number, and the conviction level — all three in the first three sentences. Then present the 3-line financial logic that produces the number, a sensitivity table on the load-bearing assumptions, a realistic downside paragraph, a cost-of-waiting statement (or an honest "no urgency" acknowledgment), and a closing decision-gating section with exit criteria. The whole memo should fit on one page.

What's the difference between writing for a CEO versus a CFO?

CEOs read through a lens of strategic posture, organizational implications, and external optics. CFOs read through a lens of financial logic, embedded assumptions, and downside scenarios. The same recommendation requires different framing for each. A CFO-targeted memo leads with the number and the assumptions; a CEO-targeted memo can lead with the strategic narrative.

What is a sensitivity analysis in a strategy memo?

A table or list showing what happens to the headline financial number if specific assumptions are off — typically presented with the base case, a -20% downside, and a +20% upside on each load-bearing variable. The sensitivity section is what most distinguishes a CFO-grade memo from a CEO-grade one. It builds confidence when the math is reassuring and surfaces the right conversation when it isn't.

How long should a strategy memo be?

One page, single-spaced, for routine strategic decisions. Some memos legitimately need more — board recommendations, complex M&A analyses, regulatory decisions — but the one-page target is the default. The compression is what forces the discipline that produces a useful memo.

What does "conviction with named contingency" mean?

A statement like "High conviction, contingent on the assumption that the new pricing tier converts at 8% or higher." The phrase pairs the team's confidence level with the specific assumption that confidence rests on. CFOs read this as honest. High conviction without a contingency reads as advocacy and reduces the consultant's credibility over time.

Should a strategy memo include the worst-case scenario?

Include the realistic downside, not the theoretical worst case. "What happens if conversion comes in at 5% instead of 8%" is realistic and informative. "What happens if the company files for bankruptcy" is theater. The realistic downside builds CFO trust because it demonstrates that the failure modes have been considered.

What goes in the decision-gating section of a strategy memo?

Three pieces: who needs to decide and by when (CEO approval by [date], board notification at [meeting]); the first observable milestone if approved (pilot conversion data at the next board meeting); and the exit criteria that would pause or stop the project (conversion below 4% in the pilot cohort triggers re-evaluation). Exit criteria are particularly CFO-friendly — they create a defensible off-ramp.

---

This article is general guidance for management consultants and finance professionals. It is not financial, tax, or audit advice. Specific accounting treatment, tax implications, and disclosure requirements warrant the client's controller, external auditors, and tax advisors.