Every lead-tracking spreadsheet I've ever seen started out working fine. Someone built three or four columns — name, email, source, status — and for a while, it did exactly what it needed to. That's usually the problem. It worked well enough, for long enough, that nobody noticed the day it stopped.

The moment it quietly stops being true

A spreadsheet doesn't fail loudly. There's no error message. It fails by going slightly out of date in a way that's invisible until someone checks. The person who used to update "Status" after every call goes on leave, or gets busy, or changes role, and for two weeks the column just... doesn't move. Nobody notices, because a spreadsheet doesn't tell you what it doesn't know. It just sits there looking exactly as authoritative as it did the day it was accurate.

By the time someone opens it and asks "wait, is this lead actually still open?", there's no way to tell from the sheet itself. Was it contacted and the column never got updated? Was it never touched at all? The spreadsheet has no memory of which.

Why nobody notices immediately

A spreadsheet looks the same whether it's current or three weeks stale. There's no timestamp forcing anyone to ask "when was this last true?" There's no owner field that makes it obvious whose job it was to update row 214. And because everyone technically has edit access, nobody in particular feels responsible for keeping it honest — which in practice means nobody is.

I've watched this exact pattern play out with a lead-tracking sheet that started clean, four columns, one owner. Eight months later it had eleven columns, three different status vocabularies because two other people had started adding their own conventions, and no reliable way to tell which of forty "in progress" rows were actually still moving.

What a real system needs that a spreadsheet doesn't

The specific software matters less than these four things being true:

  • An owner on every row. Not "whoever gets to it" — one named person, assigned automatically when the lead comes in.
  • A timestamp that updates itself. Not a status a human has to remember to change, but a system that logs when a lead was last actually touched.
  • Routing that doesn't depend on memory. A new lead should land with its owner without anyone having to notice it arrived.
  • One shared view, not several private copies. The moment someone exports a copy "just to check something," you have two sources of truth and neither is reliable.

None of that requires expensive software. It requires the tracking to stop depending on someone remembering to do the manual part.

How to tell if this is already happening to you

Ask whoever owns the sheet to tell you, right now, how many leads from the last two weeks haven't been contacted yet. If the honest answer involves scrolling and guessing, the sheet has already stopped being a system — it's just a record of what people meant to do.

What to do about it

This doesn't have to mean a big CRM rollout. Often the right fix is small: a lightweight tracker with automatic ownership and timestamps, sized to the actual team using it. That's the shape of an Operational Workflow MVP — one defined workflow, built to be used, not administered.