Was it the logic test?
Was it the value_if_false?
Or was it me?

Hard to say now, sitting on the couch next to a husband who won’t make eye contact, because apparently, I “weaponized Excel again.”

But I know this: somewhere between “just a quick model update” and “you built what??” I lost the thread.

It Started Like All Great Love Stories Do:

With conditional formatting and quiet judgment.

He asked if I wanted to watch a movie.
I said, “Sure—right after I fix this lookup logic.”
He said, “It’s Saturday.”
I said, “It’s quarter-close.”

He made that face. The one that says, “I married a spreadsheet with Wi-Fi.”

I should’ve stopped right there.
But no. I had one more formula to write.

The IF Statement That Broke Us

It was a simple one.
Elegant, even.

I added it to our shared budget sheet like a passive-aggressive valentine.

He looked at the cell.
Then at me.
Then said, “Are we… okay?”

Naturally, I panicked and pivoted to a cash flow chart.

Reader, We Were Not Okay

Here’s what no one tells you:
A marriage runs on trust, communication, and the mutual understanding that you don’t model your partner’s behavior like a SaaS retention curve.

But I did.

I had tabs.
I had scenario planning.
I had a rolling 12-month forecast for his mood based on sleep, screen time, and the number of Amazon packages that arrived without explanation.

At some point, I stopped being a wife and started being RevOps with a marriage license.

Love Languages: Words, Touch, and Dynamic Ranges

He said I never unplugged.
I said he never appreciated the magic of cell protection.

He said I was emotionally unavailable.
I said, “That’s because you keep overwriting my assumptions without logging the change.”

He asked why I built a slicer for our arguments.
I asked why he didn’t use it.

He walked away.
I conditional formatted the door red.

I Tried Everything

• Added a “Feelings” column to the grocery list
• Built a Gantt chart for household chores
• Created a dashboard labeled “State of the Union (Emotional, Not Federal)”

But no matter how many formulas I wrote, none of them could solve for:

Turns out, no one wants to be indexed like a balance sheet.

The Breaking Point

He opened my hidden tab.

The one labeled: “Scenario_Analysis_Divorce_V2_FINAL.xlsx”

In my defense: it was just a sensitivity test.
In his defense: I had drop-downs for custody schedules and visitation budgets.

He asked if this was some kind of sick joke.
I told him it was actually a really clean model.

He did not find it funny.
Not even the slicer with emoji ratings.

Postmortem

What ended our marriage wasn’t infidelity, money problems, or politics.

It was an IF statement.
And the spreadsheet that came with it.

Because IF statements are only as good as the logic that underpins them.
And if your whole relationship is a nested set of assumptions you never check in with, eventually one of them will error out.

Quietly. Permanently.

What I Learned

1. Love doesn’t work on logic gates.
You can’t automate intimacy. Trust has no toggle.

2. “Technically right” is the fastest path to being emotionally wrong.
Just because your model balances doesn’t mean your relationship does.

3. If you’re modeling your partner, you’ve already lost them.
Especially if the file is titled “Annual Reforecast – Married Life.”

Sooo…

Next time you find yourself staring at a spreadsheet instead of your spouse, remember:

No one wants to be IF’d into affection.
No one wants their love life version-controlled.
And no one wants to compete with a perfectly formatted pivot table for attention.

Choose the moment.
Close the file.
And maybe, just maybe—stop putting your marriage in Excel.

It was a Tuesday. 7:43 p.m. I was still in the office. Someone from ops had just Slacked me asking for a version of the Q2 forecast that accounted for a 5% shift in headcount timing. I was on version 17 of the model. And that didn’t include the copy saved on our shared drive as “Final-Final-v3.”

I was exhausted. The team was frustrated. Our “strategic” insights were buried under 4 hours of data prep every week.

So I made a decision. I stopped trying to scale through brute force. Stopped saying yes to every custom ask. Stopped treating finance like a service function.

And started building FP&A into what it should’ve always been: a strategic partner.

But here’s the thing they don’t tell you:

Becoming strategic isn’t about throwing the model out the window. It’s about changing what the model is for.

That shift took us from reactive to proactive, from spreadsheet jockeys to trusted operators. And it taught me a few lessons I still carry into every engagement.

1. Don’t Just Build the Model—Build the Questions It Answers

In the early days, our models were designed to calculate. Now, they’re designed to clarify.

The difference? Questions.

Before we touch Excel, we define the top 3-5 questions the business needs to answer this quarter:

• Where’s our leverage if revenue underperforms?
• What’s the break-even point by segment?
• How long can we delay that next hire?

Your model doesn’t need to be complex. It needs to be aligned. The more it’s shaped by real decisions, the more strategic your team becomes.

2. Elevate the Conversation—Visually and Verbally

We used to send dashboards. Now we host narrative reviews.

Why? Because metrics alone don’t drive alignment. Context does. Story does.

We learned to:

• Pair every KPI with commentary
• Use visuals to highlight inflection points
• Lead with insights, not tables

One of our CFOs called it “boardroom-ready modeling.” Same data—better delivery.

3. Model Fewer Scenarios, Better

We used to build three scenarios for everything: Base, Upside, Downside.

Eventually we realized:

• Only Base ever got updated.
• Upside was a fantasy.
• Downside was ignored.

Now we start with one scenario—the one we believe—and stress test it ruthlessly:

• What if we miss hiring targets by 30 days?
• What if churn ticks up by 2%?
• What if CAC spikes?

This makes our forecasts more credible. And our conversations more useful.

4. Align to Operators, Not Just Outcomes

Our early models looked great to finance—and foreign to everyone else.

Today, we reverse engineer our models from operating levers:

• Marketing: Cost per lead, conversion rates
• Sales: Ramp time, productivity, quota
• Product: R&D headcount vs. roadmap velocity

When a forecast shifts, we don’t just update numbers. We call the team driving the lever.

That makes FP&A a translator. And that’s where strategy happens.

5. Build Less, Influence More

Here’s a hard truth: If your value comes from building models, AI is coming for your job.

But if your value comes from shaping strategy, asking better questions, and connecting dots across the org—you’re irreplaceable.

We’ve shifted time away from “building” toward:

• Cross-functional planning meetings
• Monthly operator reviews
• Real-time revenue analyses

The model matters. But your ability to drive decisions? That’s what makes you a partner.

What Changed for Us

When we stopped being a reporting function and started showing up as a strategic voice:

• Our forecast accuracy improved
• Our leadership team started looping us in earlier
• Our team morale went up (less fire drill, more thinking time)

We didn’t stop using Excel. We didn’t buy a magic tool. We just stopped thinking like accountants—and started thinking like operators.

If you’re still stuck in the report-refresh-repeat cycle, I see you. You’re not broken. You just need to redefine your role.

FP&A isn’t about being the smartest person with the biggest spreadsheet. It’s about being the calmest person in the room when the forecast changes.

And that starts with deciding that finance isn’t just here to track the story. It’s here to help write it.