Why Budgeting and Forecasting Still Lives in Excel (and why that says more about planning systems than finance teams)

Another clever meme announcing the death of Excel. Another post warning that spreadsheets are chaos. Another ad from a budgeting or FP&A platform explaining why Excel is risky, uncontrolled, and fundamentally incompatible with modern finance. Refresh LinkedIn a few times and you’ll see them.

This is not an occasional narrative. It’s constant. The message is reinforced every few minutes, wrapped in humor, confidence, and polished screenshots. Over time, that repetition wears on people doing the work. If you’re still relying on Excel, the implication is clear: you must be behind, unsophisticated, or taking unnecessary risks.

I have bought into that story before. As a Controller and CFO, I implemented planning systems with real optimism. Later, in consulting, I watched organizations repeat the same cycle.

And yet, Excel kept coming back. Not always because finance teams failed to change. Not because they cannot learn new tools. It comes back because, in real life, budgeting and forecasting are messier than most systems are willing to admit.

The Promise Breaks Where Real Work Begins

Planning tools are sold on structure and control:

• One model
• One version of the truth
• Defined workflows
• Guardrails that prevent errors

These are all reasonable, admirable goals. The problem is that budgeting is not a linear process. It is iterative, political, and full of exceptions. Assumptions change mid-cycle. Questions surface late. Scenarios appear that no one thought to design for.

The first budget cycle in a new system often goes smoothly. The model reflects what the organization believed it needed at the time. Then the real questions start.

• Can we see this by region and funding source without rebuilding the model?
• What happens if headcount shifts mid-quarter?
• Can we isolate this one program without duplicating everything?
• Why does this variance exist, and can I see the math behind it?

These aren’t one-off exceptions. They’re not edge cases. This is the job. When a system struggles to answer those questions quickly, teams adapt. They export data. They test assumptions elsewhere. They build scenarios outside the tool so they can think.

That thinking happens in Excel.

Formatting Is Where Many Tools Lose the Argument

Formatting is frequently glossed over, treated as cosmetic by planning software vendors. Their highest-producing sales people are often trained to “say yes and stop talking” when prospective customers ask if their very specific output needs can be met by the tool. Finance teams know better.

Budgets and forecasts are rarely consumed inside the system that produced them. They show up in board decks, management reviews, lender packages, and operating discussions. Structure matters. Subtotals matter. Spacing matters. Visual hierarchy matters. When a tool limits how results can be shaped, Excel becomes the place where the work is finished. Over time, that finishing work turns into analysis, explanation, and scenario testing.

At that point, the system is no longer the center of the process. It is just a data source.

Flexibility Is Not the Opposite of Control

Another familiar criticism is that Excel is inherently “unsafe”. Too flexible. Too easy to break. Too risky for serious planning. That argument is conveniently stuck in a much older version of Excel.

Modern Excel, running on Microsoft 365, looks nothing like the file-sharing free-for-all people like to warn about. Version history, permissions, controlled sharing, audit trails, and cell-level protections are now standard. You can see who changed what and when. You can lock structure while leaving inputs open. You can collaborate without passing files around.

In other words, the control problem is no longer a spreadsheet problem. It is a process problem. Unmanaged spreadsheets can still cause issues, just like unmanaged systems can. But flexibility itself is not the enemy. The real question is whether teams are given the right guardrails and governance.

Budgeting and forecasting require experimentation. Finance teams need to test assumptions, layer scenarios, and adjust logic when reality changes. And by the way, they need to do this quickly. They don’t have the luxury of leisurely traipsing through a giant configuration process every time. Rigid models do not fail gracefully under that pressure.

Many planning systems still force a tradeoff. Structure or adaptability. Control or curiosity. Excel survives because it does not force that choice.

The Questions That Push Teams Back

In consulting, I saw the same pattern repeat.

Organizations did not walk away from planning tools because they were broken. They walked away because of the questions those tools made difficult to answer.

Questions like:

• Can we change allocation logic for just this scenario?
• Can we model a one-time event without contaminating the baseline?
• Can we reconcile this view back to actuals without manual mapping?
• Can we explain the variance in plain language, not system logic?

When answering those questions requires workarounds or weeks of redesign, confidence erodes. Not in the math, but in the model’s usefulness. Excel stays because it allows interrogation. You can see the formulas. You can follow the logic. You can change direction without filing a ticket.

Excel Is Not the Dream. It Is the Reality Check.

No finance leader dreams of living in manual, disconnected spreadsheets forever. Teams want reliability, auditability, and less manual effort. They also want to understand what the numbers are doing. Excel persists because it supports how finance actually works. It allows exploration before certainty. It supports explanation, not just calculation.

When planning systems ignore that reality, the result is not modernization. It is fragmentation. The system becomes the place where data is stored. Excel becomes the place where decisions are made. That’s not progress; it’s just yet another layer of complexity in a process that was sufficiently complex in the first place.

A More Honest Conclusion

The real issue isn’t Excel versus planning tools. The issue is whether budgeting systems are designed to support judgment rather than constrain it. Until planning platforms offer transparency, adaptability, and respect for how finance teams think, Excel will remain part of the process.

Not as a failure. As evidence. Evidence that budgeting and forecasting cannot be reduced to workflows and templates alone. They require room for judgment, explanation, and change.

Maybe the goal is not to eliminate Excel. Maybe the goal is to stop pretending that finance work fits neatly inside any single system.

And maybe the real opportunity sits in the space between systems and spreadsheets. When Excel stays connected to live financial data, updates in real time, and allows changes to flow both ways, teams no longer have to choose between flexibility and control.

In that kind of environment, Excel stops being a workaround. It becomes what many finance teams were trying to get to all along: a place where thinking, analysis, and decision-making happen with data that is current, governed, and trusted.

What This Means for CFOs

If you are evaluating or re-evaluating a budgeting or FP&A platform, the question is not whether it replaces Excel. That is the wrong test.

The better question is whether the system respects how finance teams think and work when answers are not obvious. Can you explore before you commit? Can you explain results without translating system logic? Can you adapt the model without starting over?

Excel’s persistence is not a sign of immaturity. It is feedback. Planning systems that listen to that feedback will earn long-term trust. The ones that ignore it will keep watching budgets get exported, adjusted, and understood somewhere else.