Finance and ops are the same conversation. Why are they in different tools?
Finance answers two questions: what happened, and what’s possible.
Operations answers one: what are we doing about it.
These aren’t separate problems. They’re two halves of the same loop. The numbers tell you what to do. The doing produces new numbers. Repeat, forever, until the company either compounds or doesn’t.
So why do finance and ops live in completely different tools?
The artificial split
The split exists for historical reasons, not logical ones.
In the 1990s, accounting software was built to satisfy auditors. Operations software, where it existed at all, was built to schedule factory floors. They had different buyers, different vocabularies, and different release cycles. The split made sense.
Then SaaS happened. Every function got its own vertical tool. Finance got NetSuite, QuickBooks, Brex, Pigment, a hundred others. Operations got Asana, Linear, Monday, Notion, another hundred. The vendors had no incentive to talk to each other. The split deepened.
Today, the split is no longer historical. It’s structural — baked into how every modern company operates. Finance lives over here. Ops lives over there. They share a Slack channel, occasionally an exec meeting, and a quarterly board deck. Otherwise, two parallel systems.
This is fine when nothing important is happening. It breaks the moment something is.
Where the seams hurt
Watch where the friction shows up.
A hiring decision. The finance team knows the budget. The ops team knows the role. The founder knows the strategy. Putting these three things together requires a meeting, a spreadsheet, and at least one person to manually carry context between two systems. Half the time, the decision gets made on partial information because somebody didn’t get pulled into the meeting.
A vendor renewal. Finance has the contract terms. Ops has the actual usage data and the team’s satisfaction with the tool. Combining them is a manual exercise that someone runs once a year, badly, under time pressure.
A runway-driven prioritization. The cash position is in one system. The roadmap is in another. The hiring plan is in a third. Reconciling them in real time is functionally impossible — so it gets done quarterly, in slides, after the relevant decisions have already drifted.
Every important moment in a company’s life sits at the seam between finance and ops. And every important moment is more expensive than it needs to be.
The 2am board packet
The clearest symptom is the board packet.
Every operator has assembled one. You pull numbers from the finance system. You pull commentary from the ops tools. You stitch them together in slides. You spend the night before the board meeting arguing with a chart that won’t render properly. You ship it. The board thanks you. You go to sleep.
The reason this is hard isn’t that board packets are inherently complex. It’s that the packet requires context that is split across two completely different systems — and the only place those systems get unified is in the slides themselves. Built once. Discarded. Rebuilt next quarter from scratch.
This isn’t a packet problem. It’s a substrate problem.
What unification actually looks like
The unification isn’t “one tool that does everything.” That’s the failure mode — a single product that’s mediocre at everything because it tries to be everything.
The unification is one substrate underneath the tools. A layer where every number connects to the decision that produced it, every decision connects to the work that executes it, every piece of work connects back to the numbers it changes. The tools on top can be specialized. The context underneath has to be unified.
When this is in place, the seams disappear. The hiring decision happens with full context, automatically. The vendor renewal pulls usage and contract data without anyone stitching anything. The board packet generates itself — because the underlying data was always in conversation with the underlying decisions.
The company starts running on one loop instead of two parallel ones. Finance and ops stop being two separate departments and start being two views into the same operating reality.
That’s the whole point. Not fewer tools. Fewer seams. And one continuous conversation between the numbers and the work — because that’s what actually running a company has always been.