How to Talk to Executives About the Numbers (Without Shooting Yourself in the Foot)

Yesterday I spent an hour and a half training one of my senior finance leads on financial forecasting. We went through our residential and commercial forecasts line by line — the unit counts, the ARPU mix, the project percent-complete assumptions, the sensitivity on work-type P&L — all of it. Standard operational CFO work.

But about forty minutes in, the conversation shifted. We stopped talking about the forecast and started talking about how to PRESENT the forecast. Because that's the harder skill, and the one that separates the finance professionals who make the jump to the C-suite from the ones who ceiling out.

This post captures what I shared with him. It came from a specific failure mode I've watched in myself and in the finance leaders I've hired: being technically correct, presenting the numbers accurately, and still losing the room. If you're a controller, VP of Finance, or sitting CFO and you've ever walked out of a board meeting or E-Team review wondering why your good analysis didn't land — this is for you.

The Core Problem: Seeds of Doubt

Here's the pattern that got my tail handed to me over and over again early in my career. I'd walk into a board meeting with a forecast. The numbers were correct. The analysis was rigorous. And then somewhere in the presentation, I'd plant a seed of doubt in my own work.

“The model shows we'll hit $45M this quarter, but obviously there's a lot of uncertainty in the townhome mix.”

“This looks good but I want to go back and check the percent-complete on Governor's Club — something might be off.”

“We're showing positive EBITDA in Q2 but I wouldn't bank on it until May closes.”

Each of those statements was technically true. And each of them silently undermined my credibility as the person in the room who was supposed to know the answer. I wasn't being humble. I was planting doubt. And the board was listening — cataloging each hedge — and by the end of the meeting they trusted me less than when I walked in.

That's the failure mode. Finance leaders who confuse humility with hedging. Who treat every caveat as professionalism when it's actually self-sabotage.

Eight Rules for Executive-Level Financial Communication

1. Take a position. Own it.

When you present a forecast, you are making a professional judgment call. That's what you're paid for. Have the courage to say “I believe we will do 380 units at $11,200 ARPU in April” — not “Jeremy says 500 but I'm not sure.”

If your forecast differs from what the field is telling you, own the difference. “Jeremy is forecasting 500 units. I'm modeling 450. The delta is my hedge on townhome completion timing — if the mix shifts 20% toward single-family, I move to 480.”

Notice the structure: you're not disagreeing with Jeremy. You're explicitly documenting YOUR judgment, with YOUR reasoning, and the trigger condition that would change it. That's operational CFO posture. The board now trusts your judgment because you showed them your judgment.

2. Hedge through the math, not through the narrative.

If you're worried a number is too optimistic, adjust the number. Don't deliver the optimistic number and then talk it down.

In the forecasting session with Raniel yesterday, we took the field team's revenue projection and hedged it down by 20% — not because they were wrong, but because their historical accuracy was around 80% and a conservative operational CFO accounts for that. The field team gave us 500 units. The forecast went out at 400.

But when we presented 400 to executives, there was no caveat about “well, actually the field says 500 and I just don't trust it.” The hedge was in the number. The presentation was confident. The judgment was documented in the supporting analysis for anyone who wanted to go deeper.

Hedging-in-the-math preserves your credibility because you only present what you're willing to defend. Hedging-in- the-narrative destroys your credibility because you're telling the board, in real time, that you don't believe your own numbers.

3. There's a floor on hedging. Don't cross it.

The flip side of hedging is overhedging. Let me tell you a story from a previous company I ran finance at.

I started teaching my PMs to give me realistic dates instead of aspirational ones. Good habit, right? Except I didn't realize they'd started listening.

One day I'm in a forecast meeting with a PM and I say, “Are you REALLY sure that date's going to happen? Let's push it out two months to be safe.” He nods. We push it out two months.

What I didn't understand was that he was ALREADY giving me a realistic date. He had already done the calibration. My second-guess layered ANOTHER hedge on top of a hedge that was already there. We ended up four months conservative from reality.

Three months later, a flood of revenue hit. Projects we were forecasting for August closed in April. The P&L looked like we were doing amazing work — but it was an artifact of an overhedged forecast, not real outperformance. I got praised for numbers that shouldn't have made me look good. And the next cycle, I got pilloried when executives extrapolated the flood and the reality reverted.

Calibration is a two-sided game. Underhedge and you oversell. Overhedge and you undersell — which creates an even more dangerous credibility problem because the reconciliation looks like either incompetence or sandbagging.

The operational CFO's job is to hedge just enough to account for known error in the inputs, and no more. Know the historical accuracy of your inputs (80% for Jeremy, 90% for Brandon, 70% for the new PM). Adjust accordingly. Stop there.

4. Don't confess your uncertainty. Route it.

Sometimes you genuinely don't know. A forecast that depends on a still-pending contract. A margin that depends on an unknown change order. A cash flow that depends on a collections outcome nobody can yet predict.

The amateur's move is to confess that uncertainty in the meeting: “This number could be wrong — it depends on whether we win the Westhaven deal.”

The operator's move is to ROUTE the uncertainty into a scenario. “The base case assumes we close Westhaven. If we lose it, revenue drops $2.1M in Q3 and EBITDA drops $400K. That's the downside scenario. We'll have the deal outcome by May 15 and I'll update the forecast then.”

Same underlying uncertainty. Radically different reception. The first version positions you as uncertain. The second positions you as rigorous. The uncertainty is identical; the perception is not.

5. When you're wrong, own it fast — without self-flagellation.

Every finance leader is going to be wrong eventually. A forecast misses. A working capital projection breaks. An acquisition model turns out to overstate synergies. The question isn't whether you'll be wrong — the question is what you do when you are.

Bad response: “I'm so sorry, I feel terrible about this, I should have known, let me explain all the reasons it went wrong...”

Good response: “Here's what happened. Here's what I missed. Here's what I'm doing going forward to prevent it.”

The difference is owning the miss without making it about your emotional state. Boards and CEOs want to know the CFO is accountable, clear-eyed, and already working on the fix. They don't want to manage your anxiety in the meeting.

6. Governance over AI. Always.

This one came up in the training session and I want to flag it for a different reason. We're automating a lot of our forecast process at CHE. Percent-complete calculations, ARPU mix, sensitivity analysis — all getting moved into a custom system. It's real progress.

But here's the critical point I made to Raniel: the automation doesn't replace the senior judgment. It enables it. When an AI-generated forecast says the Governor's Club project is 73% complete, the operational CFO looks at it and asks: “Does that LOGICALLY make sense? Have they shown meaningful cost activity in the last 30 days? Is the PM holding costs in his chest that should be released?”

The AI isn't the decision-maker. It's the starting point. The operational CFO's job becomes MORE important, not less, when the inputs are AI-generated — because the AI doesn't have context, doesn't have skepticism, and doesn't know that project managers have incentives to report generously.

When you're presenting to executives: be the professional skeptic. Translate “the AI said” into “I evaluated the AI output against these other signals and here's my actual judgment.” That's the operator speaking. That's the voice that earns the seat.

7. Know who holds the purse, and work them.

In project-based businesses, the PMs hold the purse. The raw data feeding your forecast comes from them. Their biases become your forecast's biases if you don't push back.

The operational CFO pushes back with specificity. “You said Governor's Club is 73% complete. You haven't billed any costs in four months. Are you holding costs in your chest? Is there punch-list work blocking closeout? What would it take to declare victory at 95% and move on?”

That's operator language. You're not asking for the number — you're asking for the story behind the number. And when you bring that story to executives, you're bringing operator-grade intelligence, not just finance output.

8. Your team absorbs your posture. Be careful what you model.

This is the hardest one to see but the most important. When you plant seeds of doubt in front of executives, you're also teaching your team to plant seeds of doubt. They see you hedge. They hear you caveat. They absorb the pattern.

Then when THEY present to you, they do the same thing. And you start losing confidence in THEIR judgment. The organizational immune system starts underselling at every layer.

The inverse is also true. Teams absorb confident, calibrated, accountable communication and start modeling it themselves. Within 12 months your direct reports are presenting to you the way you present to the CEO. Within 24 months they're ready for bigger seats.

The way you talk about the numbers with executives is the way your team will talk about the numbers with you. Which means if you want to build a high-performing finance function, the work starts with how you present.

A Word About Confidence vs. Arrogance

I want to be explicit about this because it's easy to misread. The call in this post is for CONFIDENCE, not arrogance. The difference is substantial.

Confidence: “Here's my judgment. Here's my reasoning. Here's what would change my mind.”

Arrogance: “I'm right. The numbers say so. Next question.”

Confident people update when they're shown new information. Arrogant people double down. Confident people acknowledge what they don't know and route it into the analysis. Arrogant people pretend certainty they haven't earned.

The operational CFO's posture is confidence, not arrogance. And that posture is signaled primarily by how you present, not by what you present.

The Uncomfortable Thing

I'll close with the uncomfortable admission from my own career: I got this wrong for a long time. I presented forecasts with seeds of doubt. I confessed uncertainty. I overhedged to protect myself. I modeled anxiety instead of accountability. And I got my tail handed to me in board meetings year after year until somebody finally gave me the feedback.

The feedback was some version of: “Josh, you're technically right and you're losing the room.”

It took me years to internalize what that meant. Now I'm trying to shortcut that learning curve for the senior finance leaders I work with — including Raniel — by naming the pattern directly. If you see yourself in this post, that's the start. The next step is practicing. The meeting after next is where you'll feel the difference.

Confidence without arrogance. Hedge in the math, not the narrative. Own the judgment. Route the uncertainty. Be the professional skeptic. Work the PMs. Watch what you model for your team.

This is the voice of the operational CFO. It's learnable. And it's the biggest predictor of whether you'll make the jump to the seat you want next.