The Spreadsheet is the Tell

Most of the small businesses I’ve spent time around have a spreadsheet open on a second monitor all day. It sits next to the software they actually pay for — the scheduling system, the accounting package, whichever cloud tool the office runs on — and it’s where the real work happens. The job numbers get tracked there. The corrections get tracked there. The “remember to call Mike on Tuesday about the deposit” gets tracked there. When somebody new asks where to find something, the answer is usually “look at the sheet.”

I want to be careful here, because I’m not about to tell you that your spreadsheet is wrong. Spreadsheets are great. They bend to the work in a way most software won’t. I’ve used them like that…I still do. The question I think is worth asking is a different one.

When did the spreadsheet stop being a workaround and become the system?

Because once it’s the system, the situation has changed underneath you, and most owners I’ve talked to didn’t notice exactly when it happened.

What it looks like when it’s happened

A few things start showing up. None of them feel like a crisis on their own. That’s part of why they’re easy to live with for years.

The same job, customer, or invoice ends up in two places — the software and the sheet — and the two don’t always agree. Somebody usually knows which one to trust for any given situation, but only because they’ve been doing it long enough to remember. New hires get a version of “yeah, but for that one we use the sheet” on their first week. The training is informal because it has to be. None of it is written down.

Things that were supposed to talk to each other quietly stop talking. The connection between the field tool and the office tool worked for a year, and then one day a job didn’t show up where it was supposed to. And when somebody finally went to look, that connection had been broken for two weeks. Nobody got an email about it. Nobody was watching.

What does come across is partial. Half the information you needed shows up in the other system, and the part that’s missing is exactly the part that mattered. Reconciling it by hand takes longer than just typing it twice would have.

The vendor sells you the version of their product that fits the version of the underlying tool you don’t have. The cloud edition assumes you’re on the cloud edition of the accounting package. You’re on the desktop one. Neither of you can quite explain that to the rep on the phone.

And then there’s the tab nobody understands except one person. Usually it’s the office manager. Usually it has formulas going across three other tabs and back. The owner has a low-grade awareness that if she took a real vacation — not a long weekend, a real one — something would quietly stop working by Wednesday.

What the sheet is telling you

The sheet is doing real work. That’s the first thing to take seriously. It exists because the software you bought doesn’t quite fit the way you actually run the business, and someone — probably you, or someone you trust — built the sheet to close the gap. I’ve started calling this kind of sheet a shadow spreadsheet — the manual ledger that’s quietly become the system of record next to the SaaS you actually pay for.

The interesting question isn’t whether the sheet should exist. It does exist. The interesting question is what kind of gap it’s closing. Some gaps are cosmetic — the software does the work, you just don’t like how it asks you to do it, and a different vendor or a small workflow change would handle it. Some gaps are structural — the software was built for a different shape of business than yours, and no amount of vendor switching is going to make it fit. The sheet is the shape of your business, written down. It’s data about how the work actually flows.

That’s worth knowing before the next conversation with a vendor or a developer, because both of those conversations tend to start with someone selling you something, and the more clearly you can describe the shape of the gap, the harder it is to be sold the wrong thing.

A short diagnostic

Five questions. You can run them on your own setup before the next sales call.

1. Does the spreadsheet have a tab nobody understands except one person? If yes, that person is now load-bearing. They probably don’t know that.

2. If that person took two weeks off, would something quietly break? Not “would things be slower.” Would something break — a bill not get sent, a job not get scheduled, a customer not get a callback.

3. Are you re-typing the same number into two systems on a regular schedule? Once a month, once a week, every morning? If yes, the connection between those two systems is you.

4. Does the spreadsheet “fix” something the software got wrong, and has anyone written down what? If the fix lives only in someone’s head, it isn’t a fix…it’s a habit.

5. When something between the two systems breaks, how do you find out? If the answer is “a customer calls,” the system isn’t watching itself. You are.

You don’t need to do anything with the answers right away. The point of the diagnostic isn’t to be alarmed. It’s to be specific. The next time someone asks what your software setup looks like, you can describe the gap instead of describing the software. That’s a different conversation, and it tends to go better than the last one. The spreadsheet stays open on the second monitor. You just know now what it’s telling you.