I used to believe that too.

Until a friend of mine who works at a 120-year-old manufacturing company told me how they completely transformed their forecasting—and turned that narrative on its head. Hearing their story taught me something about where the real forecasting value comes from—and why most companies, old or new, miss it.

This is their story. And if you’re a CFO or operator thinking your forecasting is “good enough,” I’d take a closer look.

The Setup: Complexity Hiding in Plain Sight

The company made precision-engineered components. Big industrial clients. Global supply chains. Multiple product lines.

On paper, they had forecasting “covered”:

• Monthly P&L forecasts
• Variance reports by region
• Management reporting deck

Looked fine. Except—sales kept surprising to the upside or downside. Inventory swings caught them flat-footed. Cash flow forecasts were off by 10-15% regularly.

The board was asking questions. Operators were frustrated. Finance was tired.

That’s when my friend’s team decided to change things.

The Problem: The Forecast Was Too Pretty

Here’s what they found:

• The forecast was driven by a single, consolidated model—beautifully formatted.
• Inputs came from high-level rollups—often averages of averages (aka spreadsheet fantasy math).
• There was little input from actual operators.
• Scenario planning? Nonexistent.

In short, the forecast was too pretty. It smoothed over complexity instead of surfacing it.

You could almost hear the board collectively nodding—right up until the numbers blew up.

Sound familiar?

The Shift: Building Forecasting Value from the Ground Up

They didn’t overhaul everything overnight. They started with mindset shifts—then tactical changes.

1. Reframe Forecasting as an Operating Tool

First, they had to stop treating forecasting as a Finance-owned report. They reframed it:

Forecasting = Operating Decision Support

That meant operators had to own inputs. And Finance had to facilitate, not dictate.

Or as my friend put it: “We stopped being the spreadsheet police and started being copilots.”

2. De-layer the Model

They decomposed the monolithic model:

• Product-level drivers for Sales
• SKU-level inventory forecasts
• Region-specific FX and COGS assumptions
• Cash forecasting tied to actual receivables/payables behavior

Was it messier? Yes. Was it more accurate? Absolutely.

And bonus: once operators saw their own assumptions reflected, they started caring. A lot.

3. Implement Scenario Planning

They added structured scenario planning:

Now Finance and Operators had a shared language for planning.

As my friend put it: “No more deer-in-headlights in ops meetings.”

4. Tighten the Forecasting Cadence

The old cadence? Monthly, and mostly for board reporting.

They shifted to:

• Monthly formal re-forecast
• Bi-weekly business review forecasts (lighter)

Why? In volatile markets, waiting 30 days to update your view is like driving a race car while staring in the rearview mirror.

5. Align Forecasting with Business Questions

They stopped asking: “Is the forecast accurate?”

They started asking: “What decisions does this forecast inform? And is it good enough for that?”

Examples:

• Inventory build decisions for Q4?
• Hiring plans for a new production line?
• FX hedging levels for Europe?

Forecast accuracy isn’t the goal. Decision usefulness is.

The Result: Forecasting Became a Competitive Weapon

Here’s what changed in six months:

And the biggest win? They navigated a global supply chain shock far better than peers—because they had already modeled the scenario and knew where their exposure was.

Or, as my friend said after one tense board call: “We looked like we had a crystal ball. We didn’t. We had practice.”

Lessons Learned: Forecasting Value Comes from the Process, Not Just the Model

What this old company taught me:

• Forecasting value = alignment + insight + agility.
• The prettiest model in the world is useless if it’s not tied to operator reality.
• The Finance team that asks better questions wins.

And here’s a funny analogy I use with CFOs now: Your forecast isn’t a crystal ball. It’s a flight simulator. The more you train in it, the better you handle turbulence.

Why This Matters for CFOs and Operators

Too many companies think they’ve “checked the forecasting box.”

But here’s the test:

• Is your forecast built with operator input?
• Does it inform key operating decisions?
• Does it adapt as reality changes?
• Can your team run scenarios fast when needed?

If the answer isn’t a clear yes—you’re leaving value on the table. And in volatile markets, that’s a dangerous place to be.

Forecasting Is a Muscle You Build

This article took real time to write because I want more CFOs and operators to see forecasting not as an obligation, but as a competitive edge.

If you found value in it, please share.

And if you want to go deeper—whether it’s redesigning your forecasting process, building smarter models, or up-leveling your Finance team’s decision support game—I offer 1:1 consulting for Finance pros ready to level up. DM me if you want to talk.

And I’ll leave you with this question: If a board member asked tomorrow, “What’s the scenario plan if X happens?”—how fast could your team answer?

If that question makes you sweat—it’s time to fix it.

That’s the one thing I’d change.

Too many functions are still structured like it’s 2003—hierarchies built to deliver variance reports and close books, not to influence what actually happens next.

I’ve worked inside these teams. I’ve consulted for them. And here’s what happens:

• The monthly close gets faster—but no one knows what’s driving the numbers.
• The dashboards get flashier—but the models don’t drive decisions.
• The headcount grows—but the impact doesn’t.

The result? A finance function that’s technically sound and strategically irrelevant.

It doesn’t have to be that way. In fact, the best CFOs I work with are already rebuilding their functions—from reporting centers into operating partners.

Here’s what I’d change—and how to do it.

The Problem: Reporting-Centric Structures Kill Agility

Most finance orgs today are built around this flow:

You see the gap, right?

Insights and action are afterthoughts.

Everyone’s busy closing books and building decks. But no one owns connecting the numbers to decisions.

That’s the structural flaw I’d fix first.

The Shift: From Reporting Factory to Decision Support Engine

If I were designing a modern finance org from scratch, here’s how I’d structure it:

The key shift? Finance Business Partners as core operators—not reporting clerks.

Why It Matters: The Speed of Business Has Changed

When leadership needs to pivot:

• Pricing model breaks?
• Churn spikes?
• New geo opens?
• COGS shifts?

They can’t wait for a quarterly variance review.

They need Finance in the room before decisions get made—running scenarios, stress-testing assumptions, pressure-testing plans.

And that requires a structure built for it.

Practical Tips for Building a Modern Finance Org

Here’s what I’ve seen work in the best finance teams I’ve worked with and consulted for:

1. Split Reporting vs. Decision Support

• Create clear swim lanes.
• Reporting team owns accuracy + timeliness.
• Business partners own insights + decision support.

Why: Different muscles. Different mindsets.

A quick story: One client had a talented FP&A analyst who built gorgeous decks. But they kept getting sidelined in pricing discussions. Why? Because leadership saw them as a “reporting resource.” We restructured. Moved them into the business partnering team. Within one quarter, they were leading pricing scenario discussions—not just reporting on them. One shift in role framing changed their strategic impact.

2. Build Data Pipelines That Scale

• Invest in Power Query or BI tools early.
• Automate routine data prep.
• Free analysts to model, not clean data.

Why: Analysts stuck in spreadsheet purgatory can’t be strategic.

3. Push Finance Closer to Operators

• Embed business partners with key leaders.
• Have them attend product, marketing, sales reviews.
• Tie their performance to business outcomes, not just reporting deadlines.

Why: Proximity = relevance.

4. Train Analysts to Think Like Operators

• Teach them to ask: “So what?” and “Now what?”
• Focus on implications and options, not just accuracy.

Why: CFOs don’t promote number crunchers. They promote decision influencers.

5. Invest in Modeling as a Core Skill

• Build a modeling academy internally.
• Focus on Excel and business modeling.
• Teach dynamic scenario planning.

Why: Fast, flexible modeling is what makes Finance indispensable.

One Example: A $75M SaaS Company I Worked With

They had a classic reporting factory. Strong FP&A team—but stuck in the variance-reporting cycle.

Revenue growth had plateaued. Board was frustrated.

We restructured:

• Split reporting vs. decision support teams.
• Embedded Finance partners with product and GTM.
• Automated core data prep.
• Trained analysts to drive scenario modeling.

Result? Within two quarters:

• Time-to-insight dropped by 70%.
• Finance became the first team product called when exploring pricing changes.
• Board feedback shifted: “Finance is driving strategy now.”

Why CFOs and Operators Should Act Now

Here’s the risk: If your Finance team is structured like it’s 2003, your operators will build their own shadow models.

That’s how trust erodes. That’s how Finance gets sidelined.

The opportunity? Build Finance as a decision support engine:

• Trusted.
• Fast.
• Embedded.
• Forward-looking.

That’s the model that wins boardrooms today.

Design for Impact, Not Just Accuracy

I wrote this because I see too many Finance teams trapped in old structures—and burning out good people trying to keep up.

It doesn’t have to be that way.

You can build a Finance org that’s:

• More accurate.
• More agile.
• More trusted.
• More impactful.

But it takes conscious design.

If this article gave you new ways to think about your Finance function, please share it. I put real time into this because I want more CFOs and operators building modern, trusted, strategic Finance teams—not just faster reporting factories.

And if you want to go deeper—whether it’s building a better Finance org, sharpening your team’s modeling game, or scaling your own career impact—I offer 1:1 consulting for Finance pros ready to level up. DM me if you want to talk.

And here’s one last question: If your operators are building their own models—why aren’t they calling Finance first?

If they’re not—it’s time to change that. Now.