Do You Actually Need a Fractional CFO? Most Churches and Nonprofits Don't. At First.

I heard something recently from a CFO that resonated. One of her controllers asked what it would take to move into a CFO role. Her answer was simple and direct: "A career change."

At first, that sounds a little harsh. But she's not wrong. She wasn't dismissing her controller. She identified something that most organizations don't understand, or if they do, they don't say it out loud: a controller and a CFO are not the same job at different pay grades. They are different jobs, different by design, requiring different instincts and different ways of thinking.

I was still rolling that around when I opened LinkedIn the next morning and saw a job posting for a CFO in my feed. So I read through the description. By the third bullet point, something felt off. By the end of the post, it was obvious that their ad for CFO did not describe a CFO; they were looking for a controller. Reconciliations. Monthly close. Financial statement preparation. Timely compliance filings. Internal controls. All necessary, all valuable, but not CFO work. Maybe they just liked the sound of the title better. Or they thought an ad for CFO would attract better or more qualified candidates. Or more charitably, maybe they genuinely didn't know the difference.

To be fair, a lot of candidates don't know the difference.

But if your LinkedIn ad for a CFO starts with "We are seeking an experienced and detail-oriented Chief Financial Officer to oversee day-to-day accounting operations, including accounts payable, accounts receivable, payroll, and general ledger," you should probably be searching for a controller.

I see this same confusion constantly, and not just in hiring posts. I see it in my own conversations with prospective clients. A pastor or executive director reaches out because someone told them they should consider hiring a fractional CFO. We start talking, and fairly quickly it becomes clear that what they actually need first is something else. Maybe they need a controller. Or maybe an accounting manager. Maybe even a senior accountant or bookkeeper.

And when the role they seek doesn't match what they actually need, somebody ends up frustrated and nobody ends up well-served. Sure, that pastor or ED might need a CFO eventually, but that CFO will bring a lot more value if she's not encumbered with the fundamental details of accounting or bookkeeping.

So which one do you need? Let's talk about it.

Where the Two Roles Overlap

Here's why the confusion makes sense in the first place. Both a controller and a CFO need to understand financial statements and generally accepted accounting principles. Both need to understand the organization, the ministry model, the cost structure, well enough to make sense of the numbers and translate them for people who don't live in spreadsheets. Both need to operate with integrity. That overlap is real and it's significant. It's also where the comparison ends.

What a Controller Does

A controller's core responsibility is to ensure that the financial information is accurate, complete, and timely. Month-end close. Account reconciliations. General financial oversight. Payroll. Accounts payable and receivable. Internal controls. Audit support. Chart of accounts. Financial statement preparation. If that sounds like the unglamorous but foundational backbone of a healthy organization, that's because it is.

The best way I know to say it: a controller builds the financial foundation. And if the foundation is faulty, it doesn't matter how big or beautiful the building is.

What a CFO Does

A CFO uses accurate financial information to help leadership make better decisions. Cash flow forecasting. Scenario modeling. Margin analysis. Debt and capital strategy. Program sustainability. Long-range planning. Board communication. Risk assessment. Where a controller looks backward to ensure that history is recorded correctly, a CFO looks forward and asks what the organization should do next.

The CFO's job is to sit across the table from the pastor, executive director, or board chair and help answer the questions that keep them up at night. Can we afford this hire? Is this program sustainable at current funding levels? What happens to cash if giving drops 20%? Should we wait, borrow, or phase this project differently?

Those are not accounting questions. They are leadership questions with financial dimensions, and that is a very different seat.

A Controller Explains the Numbers. A CFO Helps You Decide What to Do With Them.

The most useful way I've found to frame this for leaders who don't spend their days thinking about finance is this: a controller tells you what happened and makes sure the story is accurate. A CFO helps you decide what story you want to write next. Both matter. But they are not interchangeable, and sequencing them correctly matters enormously.

Why Churches and Nonprofits Feel This More Acutely

Churches and nonprofits operate in a fundamentally different financial environment than for-profit businesses. Good leaders recognize the disconnect, that revenue doesn't always come directly from the people you serve. It comes from donors, foundations, and people who believe in the mission. That puts unusual pressure on leadership to communicate well, steward carefully, and operate with clarity that many organizations struggle to find.

Because most churches and nonprofits run lean, they often don't have a deep finance bench. A part-time bookkeeper. An outside CPA they see at tax time. A board member who was voluntold to be the treasurer. And a senior leader cobbling things together in between.

So when the pain shows up, they reach for the biggest title they know. "We need a CFO." And maybe they do. But when I start asking questions, I more often hear things like: our books are behind, our reports don't make sense, nobody trusts the numbers, payroll keeps creating surprises. Those are not CFO problems. They are controller problems. And naming them correctly is actually good news, because controller problems have controller solutions, and those solutions tend to be more accessible and more impactful than most leaders expect.

The Fractional Version of the Same Problem

This shows up regularly in the fractional services world. A prospect tells me they want a fractional CFO, and then the actual deliverables they describe are things like closing the books each month, reconciling restricted fund balances, cleaning up the chart of accounts, documenting approval workflows, and building a monthly reporting pack. That is not a knock on what they need. It is excellent work. I genuinely love it when that work is done well. But it is work tailored to a controller, not a CFO. Calling it CFO-work sets everyone up for the wrong expectations and, ultimately, a frustrating engagement.

A true fractional CFO conversation sounds different. The client is asking things like: Can you help us model what happens to cash if we open a second site? Can you help us think through our next 13 weeks of cash? Can you help us prepare for a lender conversation? Those are actually two very different needs.

So How Do You Know Which One You Need?

Start with a simple diagnostic question: Do you trust your financial information?

If the answer is anything less than a confident yes, start with controller-level help. Build the foundation. Get the books current, the reports clean, the processes documented. This kind of foundational work is about creating a reliable recipe that anyone on your team can execute consistently. It's not exciting, but it is the work that makes everything else possible.

If your answer is yes, your information is solid and timely, but leadership isn't sure what to do with it, that's when a fractional CFO engagement starts paying real dividends.

There is no shame in needing controller work first. In many organizations, it is the most responsible next step you can take. A CFO operating without reliable numbers is guessing. And guessing with donated dollars isn't stewardship; it's a liability.

The Real Benefit of Getting This Right

If we don't say the benefit out loud, how will they know it's there? The benefit of defining this correctly isn't just semantic tidiness. It's that you hire the right help, set the right expectations, and actually solve the problem you showed up with rather than the problem you thought you had.

Churches and nonprofits don't need inflated titles. They need clarity about what kind of help will actually move them forward. Sometimes that means strategic CFO-level guidance. Sometimes it means controller-level discipline and follow-through. Sometimes it means both, just not simultaneously.

Before you reach out to a fractional CFO, ask yourself two honest questions. Do we trust our financial information? And do we need someone to help us understand what the numbers say, or do we need someone to help us decide what to do next?

The answer to those two questions will tell you more than any job description ever will.