Pitching a Budget Request to Your CFO? Answer These 5 Objections Before They Ask

Here's something to know before you pitch a budget request to your CFO: they've already heard your pitch.

Maybe not your exact request. But they've sat through a hundred versions of it - from sales, from IT, from operations, from HR. And when your job is guarding the organization's money, caution isn't a personality trait - it's the job description. So while you're talking, they're not really listening for why your idea is good. They're listening for the reason to say "Let's revisit after Q1." 

There's a fix - and it's not to bring your CFO's favorite snacks (although perhaps that wouldn't hurt). Think like your CFO before you walk in - so you can answer their objections before they ever say them out loud.

In this week's video, I walk through the same budget meeting twice: once the way that gets punted and once the way that gets a yes.

Below are five objections your CFO is probably thinking (whether they say them or not), plus what to say before they ask. I'm using manager training as the example because it's the request I see punted most. But these work for any ask - headcount, software or a training budget for your team.

1) "Can't this wait a quarter?"

This is the most literal punt - and it works because waiting feels free.

It isn't. If you're already losing good people, paying overtime to cover gaps or watching HR spend a day a week cleaning up manager issues, waiting has a price tag. So say it out loud, in monthly (and money) terms:

"Every month we wait, we're paying about $[X] in [turnover/overtime/HR time] that this is designed to bring down. Pushing it to Q2 doesn't save that money. It just means we keep spending it."

Now, "let's revisit" isn't a neutral choice - it's a choice to keep paying.

2) "What if it doesn't work?"

Your CFO isn't just asking whether this is a good idea. They're asking how bad it'll look if it isn't.

So make it easy to say yes by making it easy to stop. Offer a smaller first step with a clear checkpoint:

"Let's start with a pilot of [one location/one department/our newest managers]. Here's the number we'll watch. If it hasn't moved by [date], we don't expand it."

CFOs approve experiments a lot faster than commitments. And a pilot that works makes next year's ask a whole lot easier.

3) "Can't we just do this ourselves?"

For training, this usually sounds like "Can't HR put something together?" or "Don't we already pay for a learning library?"

Answer with math, not feelings. Building it yourself isn't free - it's just paid for in HR hours instead of dollars. Who's writing it? What's getting delayed to prioritize this? Who's updating it when policies change? Who's chasing managers to actually finish it? Put a number on those hours.

Then pull the usage data on anything you already pay for. If 12 of your 80 managers logged in last year, that's not a reason to skip this. That's the reason you need something different.

"We looked at building this in-house. It would take about [X] hours of HR time to create and keep current - roughly $[Y], before a single manager uses it."

4) "What are we not doing if we do this?"

In a flat budget year, every "yes" is a "no" to something else. Don't make your CFO figure out what - bring your own trade-off.

Start by finding what you're already spending on manager development. It's usually scattered across a few budgets:

- The one-off workshop someone booked last spring

- Conference tickets for a few managers

- Licenses nobody's logging into

- Executive coaching for one or two leaders

- HR's time filling the gaps

Add it up. You may find you're not asking for new money so much as asking to spend existing money on something that works.

"About $[X] of this is money we're already spending on [workshops/licenses/coaching]. I'd consolidate that, so the actual new spend is $[Y]."

5) "Is this really a priority right now?"

Your CFO has a short list of things the CEO and board are pushing on this year. If your request isn't connected to one of them, approving it can hurt their credibility in front of the people deciding their job.

So go find that priority list. It's usually in the strategy deck, the all-hands slides or the last leadership update. Then, connect your ask to it, in their words:

"We've said [margin/growth in the Southeast/customer retention] is the priority next year. Our managers are the ones who have to deliver that - and right now, [the problem] is getting in the way."

And if you can't connect it to anything leadership already cares about? Better to find that out before the meeting than during it.

Play CFO before you pitch

Here's the easiest way to find the objections you're missing: before the meeting, ask someone who thinks like finance to spend a few minutes trying to say no. Not to be nice - to poke holes. Every hole they find is one your CFO doesn't get to.

Then build your pitch so the answers come before the questions. Lead with the cost of waiting, offer the smaller first step and show the trade-off. By the time you get to the ask, there isn't much left to object to.

Need the numbers to back it up? Our brand-new free guide, Shorten the Line, shows you which cost and revenue lines your CFO already tracks, how to put a dollar figure on manager development and how to fit the whole case on one page.

What to do next

Before your next budget conversation, write down every reason your CFO could say no. Then answer each one in your first two minutes.

The goal isn't to win the argument. It's to make sure there isn't one. 

See Manager Method in action: Want to see what happens after the yes? On November 10 at noon ET, two HR leaders are sharing how they put manager development in place without building it themselves. They'll cover what it took from their teams, how their managers responded and how they showed the change to leadership, including their CFO. Register for Promoted, not Prepared here. Can't make it live? Register anyway and we'll send you the recording.