Your First 90 Days as CFO: The Financial Playbook

Stop Showing Up With Your Greatest Hits

When I started at my current company, I spent 30 days rebuilding a P&L model nobody asked for. I'm an FP&A guy. Accrual accounting, variance analysis, financial modeling. That's what made me successful before, so that's what I defaulted to.

Meanwhile, we nearly missed a payment because I wasn't tracking weekly cash. The business was a cash management operation. I was building a monthly P&L variance analysis.

Wrong CFO for the first 30 days. That experience taught me something every new CFO needs to hear: your first 90 days aren't about being the CFO you've always been. They're about figuring out what type of CFO this business needs right now.

Here's the playbook I wish I'd followed.

Days 1-30: Listen, Audit, Understand

The instinct is to build. Resist it.

Your first 30 days should be almost entirely about intake. You're not here to fix things yet. You're here to figure out what's actually broken, which is rarely what the interview process suggested.

Week 1: Map the landscape

Sit through every walkthrough anyone will give you. Revenue recognition. Cash management. Month-end close process. Accounts receivable aging. Don't build anything. Take notes.

Meet with every department head one-on-one. Not a "getting to know you" coffee. Ask specific questions: What financial data do you need that you don't have? Where do you feel blind? What's the one number you check every morning?

Their answers tell you what type of CFO this business needs.

Week 2: Assess your team

This is the part most CFOs skip because it feels premature. It's not.

You can't be the right CFO if your team can't execute what the business requires. Can they build a 13-week cash forecast? Do they understand the company's revenue model deeply enough to explain it to a board member? Are they defaulting to their own greatest hits the same way you are?

Don't make personnel decisions yet. Just understand your bench.

Weeks 3-4: Identify the real priority

By now you should have a clear picture of where the gaps are. Not five gaps. One. The one thing that, if it stays broken, will cost the company real money or real credibility.

For me, it was cash management and the credit facility. For you, it might be a forecast the board doesn't trust, a close process that takes 25 days, or a billing system that's leaking revenue.

Write it down. That's your Days 31-60 project.

Days 31-60: Build the Reporting Foundation

You've identified the priority. Now ship something.

Pick one deliverable that proves you understand the business.

This isn't about a quick win for the sake of optics. It's about demonstrating that you listened during Days 1-30 and actually understood what you heard.

If the business is cash-constrained, build the 13-week cash forecast and present it to the leadership team. If the board has lost confidence in the numbers, redesign the monthly reporting package and walk them through it. If the sales team is flying blind on unit economics, build the analysis that gives them visibility.

The key is specificity. Don't try to overhaul the entire finance function. Don't launch a systems implementation. Don't reorganize your team. Those all might be needed, but not in Days 31-60.

Build the reporting cadence. This is also when you establish rhythm. Weekly flash reports. Monthly close timeline. Forecast update schedule. The cadence matters as much as the content because it sets expectations and builds the habit of data-driven decision making across the organization.

Get your team involved in building this. Two reasons: first, they know the data sources and quirks better than you do. Second, you need to see how they perform under a real deliverable, not just maintenance work.

Have the hard conversations. By Day 45, you know whether each person on your team can execute at the level the business needs. If someone can't, start documenting. You don't need to make a move yet, but waiting until Day 90 to acknowledge a performance gap is too late.

Days 61-90: Deliver the First Forecast and Strategic Plan

This is where trust gets built or lost.

Deliver the forecast. Not a perfect forecast. A defensible one. One where you can explain every major assumption, point to the data source, and articulate the risk factors.

The forecast should cover at minimum:

• Revenue by segment or product line with clear growth assumptions
• Operating expenses with headcount plan baked in
• Cash flow projections for the next 13 weeks (at least)
• Two or three scenarios showing what changes if key assumptions miss

Don't present a single number. Present a range. The CEO and board will respect the intellectual honesty, and it protects you when reality lands somewhere between your scenarios.

Outline the finance roadmap. You've been there 90 days. You know what's broken. Now put it on paper. What are the top three initiatives for the next 6-12 months? Maybe it's implementing a new FP&A tool, maybe it's rebuilding the chart of accounts, maybe it's hiring a controller.

Keep it to three priorities. More than that and nothing gets done.

Build trust through delivery, not decks. Here's what LinkedIn won't tell you: trust doesn't come from stakeholder meetings or strategy presentations. It comes from delivering what you said you'd deliver, not breaking what's already working, and showing you understand what business you're actually in.

The Mistakes I See New CFOs Make

Defaulting to what worked before. If you're the cost-cutting CFO, you show up looking for costs to cut. If you built your reputation on perfect closes, you rebuild the close process. If you're the systems person, you audit the tech stack. Everyone plays their greatest hits. The business doesn't care about your greatest hits. It cares about what it needs right now.

Trying to change everything at once. You see twelve things that need fixing. You start seven initiatives. None of them finish. Pick one. Ship it. Then pick the next one.

Ignoring the team. Your team determines your ceiling. A brilliant CFO with a weak team will underperform an average CFO with a strong one. Assess early. Invest in the people who can grow. Make the hard calls on those who can't.

Waiting too long to deliver. Some new CFOs spend 90 days in "listening mode." That's 60 days too many. By Day 30, you should know the priority. By Day 60, you should have shipped something. By Day 90, you should have a forecast the leadership team can use.

The Real Lesson

Experience doesn't eliminate the learning curve. It just changes what you need to learn. I'm a 20-year finance veteran, and I still walked into a new company knowing nothing about what that specific business actually needed.

The question that matters: what type of CFO does your business need right now? Not what you're comfortable being. What they actually need.

Answer that honestly, and the first 90 days get a lot simpler.