How First Principles Thinking Transforms the CFO Role

A Tale of Two Finance Leaders

It’s a Tuesday morning. Both leaders get the same Slack message from their CEO: “EBITDA is down $800K vs. last month. What happened?”

Finance Leader A opens four different systems. She pulls an ERP export, a production report, a labor summary, and a spreadsheet her ops team maintains manually. She spends her weekend knee-deep in Excel spreadsheet tabs, reconciling dates, writing XLOOKUP matching job codes, and emailing plant managers to verify numbers. She gets to the root issue, but is exhausted, and still needs to make a plan on how to react. Meanwhile, the problem isn’t solving itself.

Finance Leader B gets an automated alert with the drill-down already attached. Labor variance at Plant 3. Tied to job order #4471. Traceable to an equipment downtime event on the 4th. She’s in a conversation with the plant manager about a corrective action before lunch.

Same company size. Same problem. Same data, theoretically.

What’s different isn’t the data. It’s how each leader built their finance function.

First Principles Thinking

In the early days of SpaceX, Boeing and Lockheed were quoting Musk $65M per rocket. While that had been the going rate for decades, it didn’t mean it wasn’t outrageous. Elon knew it was outrageous. But instead of jumping into negotiations, he asked a different question entirely.

What are the raw materials in a rocket actually worth?

About $2M— a 32.5x markup.

Now do you agree $65M is an outrageous price? This markup wasn’t a rationale one, but rather a result of assumptions baked into the aerospace supply chain over decades. Not immovable facts. Assumptions. SpaceX rebuilt the manufacturing process from scratch. They now launch for roughly $6M.

That’s first principles thinking: break a problem down to its most fundamental, undeniable truths, then rebuild the answer from scratch, without carrying forward the inherited assumptions of how things have always been done.

Here’s the thing. I’ve talked to over a dozen finance leaders at industrial and manufacturing companies, from $4M to $650M in revenue, and almost none of them apply this thinking to their own finance function.

They accept:

• “Month-end close takes 15 days.”
• “We don’t know our true margin until the 20th.”
• “Our systems don’t talk to each other.”
• “That’s just the way it works here.”

These feel like facts. They’re not. They’re assumptions, inherited from whoever built the function before them, compounded by years of workarounds and Excel files that nobody wants to touch.

Let’s Apply First Principles to the Finance Function

Start with the most fundamental question: What is the actual job of a CFO or VP of Finance?

It’s not to produce reports. It’s not to close the books. Those are tasks in service of the real job, which is: provide accurate, timely financial insight to drive better business decisions.

That’s it. That’s the job.

Now ask the second question: What percentage of your team’s time is actually spent doing that?

In our research across 12 finance leaders at mid-market industrial companies, the answer is brutal. Finance teams spend 40 to 60% of their time gathering and reconciling data, not analyzing it. Not interpreting it. Not advising the business. Just moving numbers from one place to another.

“Every month is a mystery… actuals just funnel in and it’s like, ‘What the hell happened?’” — VP of Finance, Aerospace

“I could be severely behind budget and not know it 3 to 4 weeks into the month.” — VP of Finance, Aerospace

“I felt about 80% confidence on my P&L. The operations side is a black hole. I could still be off $2 to $3M on profitability.” — CFO

This is the Elon Musk problem. If you designed the finance function from scratch, knowing what you know now, would you build it this way? Of course not. You’d ask: what work actually requires human judgment, and what doesn’t?

The answer: everything recurring and rule-based should be automated. Month-end close checklists. Routine reconciliations. Data pulls from the ERP. Intercompany eliminations. These are not strategic activities. They are tax on your team’s time.

What’s left for humans? Interpretation. Pattern recognition. Strategic action. That’s where the value is.

What Systems-Thinking Finance Leaders Actually Do Differently

I want to be specific here, because “think like a systems thinker” is useless advice. Here’s what it looks like in practice.

They Ruthlessly Inventory and Automate Recurring Tasks

The first move is a simple audit: write down every recurring task your team does. Every report that gets pulled. Every reconciliation that happens. Every spreadsheet that gets emailed.

Then ask, for each one: does this require human judgment, or is it rule-based?

If it’s rule-based, if a sufficiently detailed set of instructions could tell a computer exactly what to do, it should be automated. Full stop. The systems-thinking finance leader treats their team’s cognitive bandwidth as a scarce resource and protects it aggressively.

The CFO who accepts “close takes 15 days” hasn’t done this audit. If they did, they’d find that the vast majority of those 15 days is manual Excel ETL: extracting data from disconnected systems, transforming it to match, loading it into a model. That’s not finance work. That’s data plumbing.

They Build Dashboards That Show Details Under the Metrics, Not Just KPIs

“Operations drives finance, not vice versa.” — FP&A Analyst, Milliken

This one is underrated. Most finance dashboards show summary KPIs: revenue, gross margin, EBITDA, variance to budget. That’s fine for a board deck. It’s useless for running the business.

Summary KPIs tell you something is wrong. Only the details tell you WHY.

EBITDA was down $800K. Okay. Was that revenue-driven or cost-driven? If cost-driven, which cost category? Which plant, which department, which job order? Was it a volume issue or a rate issue? A one-time event or a trend?

The systems-thinking finance leader builds visibility all the way down, so when a number moves, they can trace it to a root cause in minutes, not weeks. Not because they’re smarter. Because they built the infrastructure to support that kind of interrogation.

They Define and Track Leading Indicators

Most finance functions are inherently backward-looking. The P&L shows you what already happened. By the time you see a margin problem in the financials, it happened 3 to 6 weeks ago.

The systems-thinking finance leader asks a different question: what leading indicators predict business outcomes before they show up in the P&L?

In manufacturing and industrial businesses, those leading indicators often look like:

• Quote-to-order ratio (predicts revenue pipeline)
• On-time delivery rate (predicts customer retention and revenue risk)
• Equipment uptime / downtime events (predicts labor variance)
• WIP aging (predicts cash conversion and margin bleed)
• Freight cost per unit (early signal on logistics margin compression)

These numbers exist somewhere in the business. They’re just not usually sitting in the finance function’s line of sight. A systems thinker builds that visibility proactively, not because it was asked for, but because they understand that by the time it shows up in the P&L, the damage is already done.

They Treat Variance Analysis as Diagnosis, Not Reporting

This is a mindset shift as much as a process one.

Most cost variance analysis in mid-market companies is a reporting exercise: “Gross margin was 34.2% vs. 36.8% budgeted. Unfavorable variance of 260 bps.” That goes in a slide. The CFO presents it. Meeting over.

The systems-thinking finance leader treats variance as the beginning of the conversation, not the end. The question is never “what was the variance?” It’s:

1. What caused it? (Not an explanation, a root cause)
2. Is this a one-time event or a structural issue?
3. What lever can we pull to address it?
4. Who owns that lever?

That fourth question is critical. Finance doesn’t control production schedules. Finance doesn’t set pricing. Finance doesn’t manage labor. But finance can identify exactly which business owner needs to make a decision, and arm them with the data to make it well.

That’s the actual job.

Why Does Finance Transformation Always Hit a Data Problem?

Here’s what happens when a finance leader actually tries to apply first principles thinking to their function. They get excited. They map out what they want to automate. They sketch the leading indicators they want to track. They design the drill-down dashboard in their head.

Then they hit the wall.

The data isn’t there. Or it’s in five different systems. Or it’s three weeks old. Or the ERP codes don’t match the production system codes. Or nobody’s maintaining the master data so the reports don’t tie.

Every single finance leader I’ve talked to has hit this wall. And this is the insight that most transformation efforts miss: fixing the data layer is the prerequisite to everything else.

You can’t automate what you can’t connect. You can’t drill into details you don’t have. You can’t track leading indicators that aren’t being captured. And AI, no matter how powerful, cannot help you if the underlying data is wrong, stale, or siloed.

“I could still be off $2 to $3M on profitability.” — CFO

That CFO isn’t struggling because he lacks finance skills. He’s struggling because the operations side of his business is a black box to his finance systems. Until that changes, no amount of analytical sophistication will get him to confidence in his P&L.

The systems-thinking finance leader recognizes this. They don’t just accept “our systems don’t talk to each other” as a permanent condition. They treat it as the root problem: the constraint that everything else depends on solving.

In first principles terms: if your job is to provide accurate, timely financial insight, and you can’t do that because your data is wrong and disconnected, then fixing the data is your highest-leverage investment. Not better Excel models. Not more headcount. Connected, reliable data.

What This Looks Like in Practice

I built Go Fig because I kept seeing the same problem: brilliant finance leaders trapped doing Excel ETL, manually bridging the gap between disconnected operational systems and their financial models.

That work should not exist. It is entirely automatable. And when you remove it, when you actually connect the ERP to the production system to the job costing module to the financial model, the finance leader’s job transforms. The close accelerates. The variance analysis becomes diagnostic. The leading indicators become visible. The CFO stops explaining the past and starts influencing the future.

That’s the systems-thinking finance function. Not a buzzword. Not a framework. A specific set of choices about what to automate, what to measure, and where to focus human attention.

Ready to Think in First Principles About Your Finance Function?

If any of this resonated, if you’re spending more time gathering data than analyzing it, or you’re finding out about budget variances three weeks too late, I’d love to show you what a connected finance function looks like.

See demo now →

Or if you want to start with a gut-check on your data infrastructure: Take the Data Readiness Scorecard →. It takes about 5 minutes and will tell you exactly where your data gaps are costing you the most.

The close doesn’t have to take 15 days. The P&L doesn’t have to be a mystery. Those are assumptions. And assumptions can be changed.