What I Got Wrong About Judging a Business From the Numbers Alone

The Assumption I Carried for Years

Early in my career, I believed that if you understood capital markets, you could understand almost any business fast. Give me the balance sheet, the cash flow statement, and an hour, and I thought I could tell you whether a company was built to last. That confidence came from years spent underwriting deals and structuring debt. The numbers told a clean story, and I trusted clean stories.

That assumption held up fine as long as I stayed inside banking, where the language of the deal and the language of the business were the same thing. It fell apart the moment I started building and selling software to banks and construction firms. Suddenly the spreadsheet wasn't the business. The business was a loan officer trying to close a file before five o'clock, or a superintendent trying to get a draw request approved before a crew walked off a job site. None of that showed up in a financial model, and all of it decided whether the software actually got used.

Where That Broke Down

I remember sitting across from a bank operations manager who had no interest in our architecture or our pricing. She wanted to know if the system would slow down her tellers during the lunch rush. That question told me more about whether our product would survive than any projection I had built. I had spent years learning to read numbers and almost no time learning to read a workday.

It took longer than I'd like to admit to realize that the numbers are a record of decisions, not a substitute for understanding them. A company can look sound on paper and still be one key person's resignation away from falling apart. A contract can look airtight and still depend on a relationship that nobody wrote down.

What I Do Differently Now

These days, before I commit capital to anything, I try to talk to the people who actually do the work, not just the people who report on it. If it's a lending business, I want to hear from someone who approves loans, not only the executive who presents results. If it's a manufacturer, I want someone who has walked the floor recently, not a summary from a consultant who walked it once.

This isn't about distrusting management. It's about recognizing that financial statements compress a lot of reality into a small number of lines, and some of what gets compressed out is exactly what determines whether a business holds up under stress. A due diligence process that stops at the data room is reading half the file.

A Short Example

On one evaluation, the projections were strong and the growth story was easy to believe. A conversation with a regional manager, though, surfaced that the company's best customers were being served almost entirely by two salespeople who had been there since the founding. Nothing in the filings flagged that. It wasn't a disqualifying fact on its own, but it changed how I weighted the growth assumptions, and it was the kind of thing you only learn by asking someone who lives inside the business.

Why This Still Matters

Markets reward people who can move fast on a good number. I understand the appeal. But a number without context is just a number, and context lives with the people doing the work, not in the report describing it. The habit I built, treating the financials as a starting question rather than a final answer, came from getting it wrong first in my own business, where I was the one answering those uncomfortable operational questions from the other side of the table.

I don't think this makes me slower than I used to be. If anything, it has saved time, because it surfaces the real risks earlier, before they're buried three layers deep in a model that looks fine on the surface. The spreadsheet still matters. It's just no longer where I start, and it's definitely not where I stop.