And Somewhere, an FP&A Model Just Started Lying

The number dropped.
Below 200,000.

Cue the headline writers polishing the word resilient like it’s a participation trophy.

But if you work in FP&A, that number doesn’t mean “things are fine.”
It means nothing is giving way.

And nothing costs more than pressure that refuses to release.

The number everyone reads wrong

Weekly jobless claims come from the U.S. Department of Labor.
They’re not vibes. They’re behavior.

Claims below 200,000 mean companies are doing something very specific:

They are not firing people — even when they want to.

That’s not confidence.
That’s fear of replacement costs.

The corporate stalemate nobody budgets for

Here’s what this actually looks like inside companies:

Executives want margins back.
Managers want to keep their teams intact.
Employees know they’re expensive to replace.

So no one moves.

No layoffs.
No relief.
Just salaries creeping up like ivy on an old building.

Every forecast quietly assumes this breaks at some point.

It doesn’t.

Why FP&A gets blamed later

FP&A models are polite.
They assume the labor market will behave rationally.

Headcount slows.
Wage growth cools.
Productivity magically picks up the slack.

But a tight labor market doesn’t snap.
It grinds.

Instead of layoffs, you get:
Higher retention bonuses disguised as “one-time”
Market adjustments that never roll off
Roles frozen but costs still inflating

The spreadsheet still ties.

Reality doesn’t.

The most dangerous phrase in finance

“Labor stability.”

Stability is what you call it when nothing explodes.
It’s not what you call it when costs keep compounding quietly.

Low jobless claims mean:
You can’t hire cheaper
You can’t downshift easily
You can’t pretend attrition will save you

That’s not upside.
That’s a locked door.

Where good FP&A separates itself

Not by predicting recessions.
By refusing fairy tales.

Strong teams stop modeling headcount like a thermostat and start modeling it like a pressure system.

They ask:
Which roles are price-inelastic?
Where does wage inflation persist even if hiring stops?
What assumptions break if this market stays tight another year?

They don’t sell comfort.
They sell accuracy.

The punchline no one wants

This headline won’t hurt you today.
It hurts you six months from now — when margins miss and everyone swears the forecast “came out of nowhere.”

It didn’t.

The warning was sitting there at 200,000.

The labor market isn’t breaking.
And that’s exactly the problem.

That’s the problem.

We’ve all been told that modern Excel formulas are smarter — that dynamic arrays make reporting faster, cleaner, more “automated.”
But some automation hides danger better than any manual error ever could.

And nothing proves that more than =UNIQUE().

Why =UNIQUE() Can Quietly Wreck Your Model

On the surface, =UNIQUE() feels like progress.
It removes duplicates from a list instantly — no filters, no pivot tables, no VBA cleanup.

The trouble?
It doesn’t verify what it filters.
It just assumes the source data is pure.

If there’s one stray duplicate, one extra space, one inconsistent capitalization, =UNIQUE() won’t alert you.
It will happily serve a “clean” list that isn’t actually clean.

That’s how models break quietly.
One missed duplicate, and suddenly your bookings total is off by millions — but the output still looks right.

Clean Isn’t the Same as Correct

This is the silent danger of modern Excel.
The more seamless the syntax, the easier it becomes to trust appearances.

=UNIQUE() gives a beautiful result.
But beauty isn’t validation.

A clean list doesn’t mean your data’s correct — it just means Excel stopped showing you what’s wrong.

How to Audit Every UNIQUE Range (and Sleep Better)

Here’s what I do now.

After every =UNIQUE() range, I add a sanity check using COUNTIFS().
That one step can save hours of debugging — or a missed audit finding later.

Example:

If any count returns greater than 1, you’ve got a duplicate hiding in your “unique” list.
That’s your cue to investigate before you trust the summary.

Want to go one step further?
Combine UNIQUE() with SORT() and FILTER() so your results stay dynamic — but always visible and verifiable.
Automation should never mean blindness.

The Real Lesson

Every formula has a philosophy.
UNIQUE() says: Trust me, I’ve got it handled.
But in finance, trust without verification is malpractice.

The strongest analysts aren’t the ones who make their models look perfect.
They’re the ones who leave proof trails — systems that show their math every time.

Because the job isn’t to make the numbers look clean.
It’s to make sure they tell the truth.

And in Excel, truth deserves visibility — not assumptions.

If your finance models need a rebuild or automation pass, contact me.
I help FP&A teams design Excel systems that think for themselves.

It seemed harmless at first.
A quick fix here, a logic tweak there — a little “if this, then that” to make a stubborn report behave.

But one day, I opened a model with 1,742 nested IFs.
No macros. No VBA. Just raw logic chaos.

The workbook didn’t need automation.
It needed therapy.

That was the day I learned something hard:

Every IF() is a symptom of indecision.

Each one whispers, “We didn’t design for clarity, so we designed for exception.”

Because every time you patch a formula to handle “just one more scenario,” you’re not solving complexity — you’re encoding it. You’re embedding hidden logic no one can see or trace. And over time, those tiny exceptions compound into fragility.

The model still runs.
But no one truly understands why it works.

Why IF() Becomes Dangerous

The =IF() formula isn’t evil — it’s misunderstood.
Used sparingly, it’s great for quick validation or basic flags.
But when every line of your model depends on it, you’re no longer modeling a system — you’re writing software without structure.

And here’s the problem:
Finance teams aren’t trained to debug logic trees.
So when something breaks, people don’t fix the root cause — they stack another IF on top.
It’s how spreadsheets quietly become spaghetti code.

The Cure: Replace Logic with Design

Here’s the rule I live by now:

→ Replace logic with structure.
If your IF statements are mapping relationships, move them to a structured table with lookup functions like =XLOOKUP() or =INDEX(MATCH()). Let the data define the rule, not the formula.

→ Replace rules with drivers.
Every “if X, then Y” condition is an opportunity to model a driver instead. What variable actually determines the outcome? Build that into your assumptions.

→ Replace IFs with systems that already know what to do.
Instead of teaching your model how to react, design it to know. Use dynamic references, named ranges, and data validation to eliminate manual logic altogether.

The best models don’t argue with themselves.
They just flow.

And when your spreadsheet stops needing IFs to make decisions,
you’ll know you’ve finally designed a system that can think for itself.

It means systems that think, not just calculate.
That interpret, not just automate.

Across finance, a quiet revolution is unfolding.
Teams aren’t using AI to replace themselves — they’re using it to reason with reality faster than ever before.

And it’s happening quietly — one variance, one model, one assumption at a time.

The Shift No One Predicted

Everyone assumed AI would make finance more efficient.
Few expected it to make finance more intelligent.

What’s emerging isn’t just automation.
It’s agency — AI that acts, questions, and learns like a junior analyst who never sleeps.

The result?
FP&A is evolving from a back-office function into the neural network of the business — a system that senses change and signals how to respond.

It’s not support anymore.
It’s surveillance of the future.

The Rise of Agentic FP&A

Here’s how it looks in practice.

• Autonomous Variance Explanations.
  AI traces the story behind forecast deviations — linking CRM, ERP, and HR data — then writes a two-sentence summary any executive can understand.
• Self-Healing Models.
  When assumptions drift, models recalibrate automatically. The AI even flags what changed and why.
• Dynamic Scenarios.
  A CFO can ask, “What if renewal rates drop 5%?” and see the full impact on ARR, margins, and cash — in seconds.
• Predictive Cash Agents.
  They monitor receivables, spot liquidity dips, and recommend corrective actions before finance feels the crunch.
• Executive Q&A.
  Leaders ask natural-language questions and get visual, contextual answers instantly.

Each one collapses time between signal and decision.
And in finance, time is the rarest currency we have.

What This Means for FP&A

Speed isn’t just convenience.
It’s now a competitive advantage.

AI doesn’t just save hours — it compounds insight.
When cycles shrink, opportunity expands.

The teams winning today aren’t chasing accuracy.
They’re chasing adaptability.

Because accuracy is a snapshot.
Adaptability is a movie.

From Reporting to Reasoning

Traditional FP&A thinks like a mathematician: structured, linear, deliberate.
AI thinks like nature: fluid, adaptive, self-correcting.

It’s a little like teaching a river how to flow around rocks — not by building walls, but by guiding the current.

That’s the new finance mindset.
Less control, more coaching.
Less rigidity, more responsiveness.

And strangely, the more we automate, the more human the work becomes.
We stop reconciling spreadsheets and start reconciling perspectives.

The Market Momentum

The numbers tell their own story:

• 58% of finance functions already use AI in some form (Gartner, 2024).
• The AI in FP&A market will grow from US$240 million in 2024 to US$4.7 billion by 2034 — roughly a 35% CAGR.
• Yet only 6% of companies have embedded AI deeply into FP&A (EY, 2025).

That means the competitive moat is still wide open — but not for long.

The Maturity Curve

Most finance teams sit somewhere between:

Automation → Prediction → Agency.

Automation saves time.
Prediction improves foresight.
Agency creates leverage.

The last one isn’t about new tech.
It’s about new trust.

Trusting systems enough to let them challenge assumptions.
Trusting humans enough to make the final call.

That’s what separates adopters from operators.

Building the Bridge

How do teams cross that gap?

Start with clarity.
AI without purpose burns cash. Choose one pain point — forecasting latency, cash visibility, driver sensitivity — and solve that first.

Clean the foundation.
No algorithm can outsmart bad data. Integrate systems. Fix definitions. Build trust in the inputs.

Pilot with governance.
Test small. Define metrics that matter: speed, accuracy, and decision quality.

Retrain the people.
Analysts become interpreters. CFOs become orchestrators. Everyone learns to question not just what the AI predicts, but why.

Scale through learning.
Every pilot should teach the system something.
That’s how FP&A evolves — not by rolling out tools, but by compounding intelligence.

The Human Edge

Here’s the paradox.
The more AI we deploy, the more judgment matters.

Because numbers don’t drive belief — people do.

You can automate reporting, but you can’t automate trust.
You can model a future, but you still need courage to act on it.

That’s the frontier of modern FP&A: where data ends and conviction begins.

A Lesson from the Field

A mid-market SaaS company I worked with built a “cashflow copilot.”

At first, it just forecasted balances faster.
Then it started noticing anomalies before accounting did — late receivables, skewed expense timing, subtle demand shifts.

By quarter’s end, leadership had cut reaction time by 80%.

Their CFO said,

“It didn’t make us faster accountants. It made us calmer decision-makers.”

That’s what transformation really feels like — not flashier dashboards, but quieter confidence.

The Future Advantage

By 2026, AI-native FP&A will be the new baseline.
The edge will come from something harder to copy — feedback loops.

The teams that win will be the ones teaching their models to learn from every decision outcome, not just every dataset.

That’s how finance moves from forecast accuracy to decision accuracy.
Not “Did we predict it right?”
But “Did we respond right?”

It’s a small linguistic shift.
And a massive strategic one.

My Take

AI isn’t an upgrade.
It’s a mirror.

It shows us what FP&A was always meant to be — a discipline of curiosity, not control.

The spreadsheet was never the villain.
It was the cocoon.

And what’s emerging now is the butterfly — finance unbound from repetition, focused on reasoning.

This is the moment to stop defending precision and start designing adaptability.
Because when FP&A stops chasing the perfect number, it starts creating the perfect response.

Closing Thought

One day, someone will ask:
“How did finance get so fast?”

The answer will be simple.

We stopped controlling the numbers.
And started teaching them to think.

And honestly, I’m still not sure if I should thank my forecasting model or apologize to it.

Because if you’ve ever spent 11 p.m. whispering “please balance” to a deferred revenue schedule, you know — this job isn’t for the faint of heart.

The email said the awards celebrate “the superheroes of the business world.”
Which sounds glamorous until you realize our superpower is reconciling three systems that refuse to speak to each other.

No cape. No spotlight.
Just 47 tabs open, a cup of reheated coffee, and a dream that one day Power Query will actually refresh without breaking.

But here’s why this nomination matters.

Finance isn’t background noise — it’s the pulse.
When the business hits turbulence, FP&A is the calm voice in the cockpit saying, “We planned for this.”
We’re not chasing perfection; we’re engineering resilience.

And that’s what this award celebrates.
Not just accuracy, but judgment.
Not just balance sheets, but balance under pressure.

Datarails says winners get certificates, designer swag, and a global feature story.
Which is great — but let’s be honest.
Every FP&A pro knows the real trophy is surviving budget season without turning into a conspiracy theorist about version control.

So yes — I’m proud.
Proud to be part of a community that sees the story behind the numbers, not just the numbers themselves.

And if there’s ever a new category next year, I have a humble suggestion:
“Best Supporting Spreadsheet in a Drama.”

Because some of us deserve awards just for getting through “final_final_v4.xlsx” alive.

Here’s to every finance superhero keeping the lights on — and the models honest.

We’d spent the week chasing late renewals and cleaning up deferred revenue schedules, but when I opened the dashboard at 10:42 p.m., it hit me: the model was right, the data wasn’t.

Classic SaaS problem.

Salesforce said one thing, NetSuite said another, and the spreadsheet was Switzerland — pretending to be neutral while quietly making things worse.

I’ve learned that every SaaS CFO has that “oh no” night. The one where your forecast looks solid until the formulas start whispering back lies.

Mine taught me this: no report is accurate until you can explain every difference.

So here’s what I did.

1. Rebuilt the ARR bridge from scratch.
Booked ARR, recognized revenue, deferred balance — line by line. No macros. No shortcuts.

2. Added a “truth column.”
Each source system got its own version of ARR. I forced them to reconcile in one sheet — live, ugly, and impossible to ignore.

3. Built a simple “trust score” dashboard.
Any metric with more than a 2% variance between systems went red. The first week, it looked like a Christmas tree.

4. Moved all reconciliation logic upstream.
If the data broke in Salesforce, we fixed it there — not with an Excel bandage.

The first run took all night. The next one took twenty minutes.

The mistake I made?
Believing accuracy was about the model. It’s not.
It’s about the plumbing.

You can’t forecast clean if your pipes are dirty.

Here’s the analogy I use with my team now:
Building SaaS reports is like making espresso. The machine matters less than the grind — bad input ruins everything downstream.

When we finally presented the ARR bridge the next morning, the board barely blinked.
But for the first time, I didn’t have to bluff confidence.

And that’s when I realized: in SaaS finance, peace of mind isn’t the absence of errors.
It’s knowing exactly where they live.

We’d been running with a simple rule: assume “steady-state churn” based on last quarter’s average. It worked fine — until enterprise renewals started slipping into the next quarter, and the illusion broke.

ARR looked flat.
But cash told the truth.

That’s when we learned the hard way: averages in SaaS finance are like seatbelts in a taxi — comforting, but rarely used correctly.

So we went back to zero and rebuilt churn from behavior, not history.

Here’s what actually worked:

1. Segment by behavior, not logo size.
SMB churned on pricing. Mid-market on ROI. Enterprise on relevance. Different diseases, different cures.

2. Measure churn at the rep level.
Sales told us the story. FP&A told us the math. When we overlaid the two, we found one rep responsible for 23% of gross churn.

3. Separate “slip” from “loss.”
Delayed renewals distorted the story. We started tracking a new metric — “net churn excluding slips” — to isolate operational failures from customer intent.

4. Tie renewal probability to NPS trends, not scores.
Static scores lie. Directional movement doesn’t.

The mistake we made early on was assuming churn was a lagging indicator.
It’s not.
It’s the earliest sign your story has stopped making sense to the customer.

Once we modeled churn as behavior instead of math, forecast volatility dropped by 40%. And the renewal team finally had a signal they could act on, not just explain after the fact.

Here’s the analogy I use with founders now:
Churn is like blood pressure. You can’t fix it by looking at last quarter’s reading. You fix it by understanding the habits that drive it up in the first place.

Our board doesn’t ask for churn “assumptions” anymore. They ask what changed in customer behavior.

And honestly? That’s progress.

Because in SaaS finance, you don’t earn trust with precision.
You earn it by refusing to let averages tell your story.

Every ping feels urgent. Every spreadsheet feels late. And by 6 p.m., you realize you’ve spent the day managing inputs, not outcomes.

That’s the quiet tax of context switching. It kills clarity before it kills time.

I hit that wall last quarter — investor call prep, headcount freeze, churn modeling all in the same afternoon. My brain felt like a browser with 47 tabs open.

So I stole one move from pilots: sterile cockpit time.
No Slack. No meetings. Just two-hour windows for high-impact work.

Here’s what changed:
• Board decks got built in half the time.
• Forecast reviews actually ended on schedule.
• I stopped missing the “why” behind the numbers.

Now I run my week using a simple framework:

1. Prioritize by consequence, not urgency.
2. Protect two deep-work blocks per day.
3. Treat Slack like air traffic — only clear to land what matters.

My mistake?
I used to think the answer was better tools. Turns out it was better boundaries.

And the best part — once I stopped trying to control every tab, the team stopped waiting for me to.

Funny how clarity scales faster than headcount when you give it room to breathe.

You start with a clean build. A few modules. Smooth integrations. Then scale hits — 3x headcount, 4x customers, 9x data.

Suddenly, your ERP isn’t helping operations. It’s holding them hostage.

You’ve got NetSuite scripts looping into oblivion. Salesforce fields that stopped syncing three weeks ago. And an FP&A team duct-taping exports at 11:47 p.m. before the board pack is due.

I’ve seen it.
The “system of record” becomes the system of excuses.

Then comes the fallout:
That board call where ARR missed by 10%.
Cash forecast off by $2M because deferred revenue was parked in the wrong subledger.
And the controller who hasn’t smiled since migration.

So what do we do?
We start pretending.
We say it’s an “ERP maturity curve.”
But really—it’s chaos management in a tailored suit.

Here’s what I did when our own system rebelled:
I stopped treating ERP as sacred.
I built a reconciliation layer outside it.
Python + Power Query + Parabola — anything that put me back in control of data flow.
Then we used the ERP for what it should do: validation, not origination.

The analogy?
Running your SaaS ERP is like flying a commercial jet with homemade autopilot. It works — until turbulence hits.

And when it hits, you’ll wish you knew every manual control by heart.

Because the biggest ERP risk in SaaS isn’t downtime — it’s believing it’s “done.”

It’s never done. It’s alive. It’s political. It’s evolving under your feet.

This is why SaaS finance breaks when the story outruns the numbers.

DM me if you’re exploring this and want to build an ERP that scales before it revolts.

Then the board asks why revenue missed by 8%.

Cue the CFO’s favorite lie: “It was timing.”

No, it wasn’t. It was hubris.

We built our forecast on last quarter’s win rates like they were gospel — ignoring that our pipeline was bloated with deals that only close in PowerPoint.

By Q2, churn spiked, net retention collapsed, and the “timing” excuse got real quiet.

Here’s what I actually did:
I tore the model apart. Every assumption went on trial. Sales input? Junk. Marketing lead velocity? Optimistic fiction. Even our “steady-state churn” looked like a fairy tale.

I replaced it with behavior-based modeling: renewals weighted by rep, segment, and deal source. Pipeline probability tied to close rate variance, not average.

It wasn’t pretty. But it stopped the bleeding.

I’ve seen SaaS boards melt down over a $200K variance — not because of the money, but because of the illusion it shatters: that we’re in control.

We’re not. We’re managing chaos with spreadsheets.

Forecasting in SaaS is like predicting hurricanes with a cocktail napkin — every model looks brilliant until the storm hits.

So the next time your forecast misses, don’t blame the weather.
Blame the bar where your assumptions got hammered.

And maybe — just maybe — stop worshiping precision and start modeling reality.

Because the smartest CFOs don’t build perfect forecasts.
They build resilient ones.