The 90-Day Plan for a New CFO Inheriting a Mess

You took the role. The recruiter was honest enough—or you were perceptive enough—to know that the finance function needs work. The close is slow, the reporting is suspect, maybe the prior CFO left under a cloud, and you're walking into a function where you don't yet know which numbers to trust. The first 90 days will set the trajectory for your entire tenure, and the temptation to start fixing everything at once is exactly the trap to avoid.

Here's how to spend that time so you're building on something real.

Days 1–30: Establish what's actually true

Resist the urge to change anything in the first month. Your only job is to figure out what's real. You're going to make decisions based on these numbers, defend them to a board, maybe represent them to a lender—and right now you don't know which of them are trustworthy.

Start with cash, because cash is the one number that's hard to fake and the one that can kill you fastest. Understand the cash position, the near-term obligations, and the liquidity runway cold. Then work outward: what does the balance sheet actually contain, what are the significant estimates and how were they derived, where are the reconciliations current and where are they fiction. You're building a map of what you can rely on and what needs verification.

Talk to people in this phase more than you analyze. The team knows where the bodies are buried—the account nobody reconciles, the estimate that's a stretch, the system that doesn't work. They'll tell you if you ask and listen. The single-point-of-failure person, the process that depends on one undocumented spreadsheet, the report everyone knows is wrong but produces anyway—these surface in conversation, not in the data.

Days 30–60: Stabilize the essentials and find the leverage

Once you know what's true, stabilize the things that can't be allowed to fail while you fix the rest. Make sure cash forecasting is real and you're watching it. Make sure any lender reporting or covenant compliance is accurate and timely—a covenant surprise in your first quarter is a disaster you can prevent. Make sure the close, however slow, is producing numbers you'd stake your name on.

This is also when you identify the leverage points—the few fixes that unlock the most. Usually they cluster: a data layer that's a mess and corrupts everything downstream, a close process whose bottleneck is one fixable handoff, a forecasting process that exists nowhere reliable. You're not fixing these yet. You're identifying the two or three that, fixed, make everything else easier, and sequencing them.

Days 60–90: Commit to a plan and a few visible wins

By the end of the first 90 days, you should be able to articulate a clear assessment and a prioritized plan: here's the state of the function, here's what I'm fixing first and why, here's the sequence, here's what good looks like in a year. This is what your CEO and board want from you, and delivering it credibly is how you earn the latitude to execute.

Pair the plan with one or two visible early wins—a number that's now trustworthy that wasn't, a report that's now timely, a risk that's now monitored. Early wins buy credibility, and credibility buys time for the longer fixes that won't show results for months.

What not to do

A few traps worth naming. Don't restate or change accounting treatments in the first 30 days before you understand why they're the way they are—you may be "fixing" something that was correct and create a real problem. Don't fire the person who's a single point of failure until you've extracted what they know—their departure could take the only knowledge of a critical process with them. Don't promise the board a transformed function in 90 days—you're assessing and stabilizing, not transforming, and over-promising early is how you lose credibility later. And don't try to fix everything; the function that's a mess got that way over years, and trying to fix it all at once just spreads your attention until nothing improves.

The mindset

The first 90 days as a CFO inheriting a mess is not about heroics. It's about establishing ground truth, stabilizing what can't fail, identifying the highest-leverage fixes, and committing to a credible plan. Do that, and you've built the foundation for everything that comes after. Skip it and rush to fixing, and you'll be building on the same quicksand that made the function a mess in the first place.