You’ve been asking for budget. You’ve sent emails with subject lines like “Reliability Improvement Initiative” and “Proactive Maintenance Strategy Proposal.” You’ve built slide decks with maturity models and benchmarking data. And every time, the CFO nods politely, says something about timing, and moves on to the next agenda item.
The problem isn’t your program. The problem is your pitch.
CFOs don’t think in MTBF. They don’t care about maintenance maturity curves. They care about cash flow, capital efficiency, risk exposure, and return on invested capital. If you can’t translate your reliability program into those terms, you’re not speaking their language. And if you’re not speaking their language, you won’t get funded.
Here’s how to walk into that meeting and walk out with approval.
Start With the Problem, Not the Solution
Most reliability professionals make the same mistake in the first 60 seconds. They lead with the program. They open with “We want to implement a condition-based maintenance strategy” or “We need to invest in predictive technologies.” The CFO immediately hears cost. You’ve lost momentum before you’ve started.
CFOs don’t think in MTBF. They don’t care about maintenance maturity curves. They care about cash flow, capital efficiency, risk exposure, and return on invested capital.
Instead, open with the business problem. Something like: “Last year we spent $2.3 million on emergency repairs that were preventable. That’s money we burned because we didn’t catch failures early enough. In addition, we lost 10% of our production volume due to downtime, which is a loss of an estimated $4.2M.” As Simon Sinek says in his book, “Start with Why”.
That’s a statement a CFO can grab onto. It’s specific, it’s quantified, and it implies a fixable gap. You haven’t proposed anything yet. You’ve just established that there’s a problem worth solving and you’ve spoken in his language; $$$$.
If you don’t have exact figures, estimate conservatively using your CMMS data. Pull total corrective maintenance costs for the past 12 months. Separate emergency and unplanned work from scheduled repairs. That delta is your opening number.
Speak in Dollars, Not Metrics
Reliability engineers love metrics. OEE, MTBF, MTTR, PdM coverage ratios, PM compliance percentages. These are useful inside the maintenance department. They are nearly meaningless in a finance conversation.
The CFO wants to know three things. How much does the current state cost us? How much will the proposed change cost? What’s the expected return, and when?
A single day of unplanned downtime on a critical line can cost more than your entire annual reliability budget.
Frame everything around those three questions. If your reliability program will reduce emergency maintenance by 30%, convert that percentage into dollars. If adding vibration analysis to 50 critical assets will prevent two catastrophic failures per year, estimate the avoided cost of those failures: parts, labor, lost production, expedited shipping, overtime, and any safety or environmental exposure.
Production losses are your biggest lever. A single day of unplanned downtime on a critical line can cost more than your entire annual reliability budget. If you can tie even one avoided downtime event to your program, the ROI math usually works on its own.
Don’t bury this in an appendix. Put it on the first page of your one-pager. Better yet, say it out loud in your opening statement.
Show the Cost of Doing Nothing
This is the move most people skip, and it’s the most persuasive part of the conversation.
CFOs are trained to evaluate risk. They assess downside scenarios all day. So give them one. Show what happens if you don’t invest in reliability. Not as a scare tactic, but as an honest projection based on current trends.
If your corrective maintenance spend has grown 8% year over year for the last three years, show that trendline. If your mean time between failures on critical assets is declining, show that too—but convert it to expected repair costs and production impact. If your aging asset base means more capital replacements are coming, frame the reliability program as a way to extend useful life and defer that capital spend.
The phrase “cost avoidance” has a bad reputation in finance because it’s often used loosely. Be precise. Tie your projections to specific assets, specific failure modes, and specific historical costs. When cost avoidance is backed by real data, CFOs take it seriously.
Keep the Ask Simple
You don’t need a 40-slide deck. You need one page with four elements:
- The problem: What the current state is costing the business, expressed in dollars.
- The proposal: What you want to do, in plain language. Not “implement a holistic asset management strategy.” Something like “Add wireless vibration monitoring to our 40 most critical rotating assets and hire one reliability technician.”
- The investment: Total cost, broken into capital and operating expense. Include tools, training, headcount, and any software. Be complete. Surprises later destroy credibility.
- The return: Expected savings in year one, year two, and year three. Use conservative estimates. If your projections look too good, the CFO will assume you’re inflating them.
If you can fit this on a single page, you’re already ahead of 90% of the proposals that land on a CFO’s desk. Finance people are drowning in information. Brevity signals competence.
Anticipate the Objections
Every CFO will push back. That’s their job. The three most common objections are predictable, and you should have answers ready.
“We can’t afford this right now.” Reframe: You can’t afford the current state. Show the compounding cost of inaction. If the emergency maintenance trend continues, what does next year look like? The year after?
Most reliability programs don’t die because the CFO said no. They die because the reliability team never made a compelling financial case.
“How do I know this will actually deliver results?” Propose a pilot. Pick 10 to 20 bad actor assets and run the program on that subset for six months. Measure the results against a baseline. A pilot de-risks the investment and provides proof of concept before seeking full-scale funding.
“Why can’t maintenance just do better with what they have?” This is the toughest one because it implies the team is underperforming. Don’t get defensive. Acknowledge that the team works hard, then redirect: the issue isn’t effort, it’s strategy. You’re currently spending the majority of your labor hours reacting to failures. This program shifts that ratio toward prevention, which is a fundamentally different approach, not a matter of working harder.
Close With a Decision, Not a Discussion
Don’t end your meeting with “Let me know what you think.” That’s an invitation to delay. End with a specific ask and a timeline. “I’d like approval to launch a six-month pilot on our top 20 critical assets. The total investment is $85,000. Can I get this into the next budget cycle?”
Give the CFO something concrete to say yes or no to. If the answer is no, ask what would need to change for it to become a yes. That’s not a rejection, it’s a roadmap.
The Real Barrier Isn’t Budget
Here’s the uncomfortable truth. Most reliability programs don’t die because the CFO said no. They die because the reliability team never made a compelling financial case. They talked about reliability in reliability terms and wondered why finance didn’t get it.
The CFO isn’t your adversary. They’re your most important stakeholder. They control the resources you need. And they will fund programs that demonstrate clear financial returns with manageable risk.
You don’t need 10 minutes. You need the right 10 minutes. Lead with the cost of the problem. Quantify the solution. Show what happens if nothing changes. Make a specific ask. And stop talking.
That’s how you sell a reliability program.
