Lead with the number, the payback, and the risk — then stop.
What they’re listening for
The number, up front
Cost, savings, or revenue impact in the first sentence — not buried after the rationale.
Payback period and ROI
“Pays for itself in four months” lands harder than “boosts productivity.”
The risk, named by you
Naming the downside yourself signals you've done the thinking — and earns trust.
A bounded ask
One decision, one amount, one deadline. Ambiguity reads as unfinished work.
What makes them tune out
Hype adjectives
“Game-changing,” “revolutionary,” “synergy” — each one quietly lowers your credibility.
Benefits with no figure
“Improves morale” is real, but without a number it can't be weighed against budget.
Jargon without impact
Team-speak that doesn't ladder to cash, margin, or risk is noise.
A buried ask
If the decision is in paragraph four, you've already lost half the room.
Watch it in action
An engineering lead asking for budget to adopt a new observability tool.
Before
Hey — the team is really excited about bringing in a new observability platform. Our current logging is a nightmare and it'd be a huge quality-of-life improvement. It's kind of a game-changer for how we debug. Can we get budget for it?
Tuned for CFO
Requesting $24k/yr for observability tooling. It cuts average incident resolution from ~90 to ~30 minutes — about 40 engineer-hours/month (~$6k), so it pays back in roughly four months. Main risk is adoption; I’ll own rollout and report usage at 60 days. Can I get approval to start the annual plan this quarter?
Try it
Have a message to send a CFO?
Paste it into Appree and tune it to this channel — same meaning, reframed in the voice they’re wired for.
Need a different audience?
Search for anyone you need to reach — we’ll point you to the channel, or you can tune a message to them directly.
Common questions
What tone works best with a CFO?
Direct and quantified. Warmth is fine, but every paragraph should earn its place with a number or a decision.
How long should an email to a CFO be?
Short. Lead with the ask and the number; put supporting detail below or in an attachment they can choose to open.
Do I always need numbers?
Yes — even an estimate with your assumptions stated beats a vague benefit. CFOs reason in ranges and risk, not adjectives.
Tune another channel