Blog

Field notes: the Friday we finally deleted the shared spreadsheet

A laptop, spiral notebook, phone, and pen laid out on a wooden desk.

It had a filename that told you everything about its history: Named_Accounts_Master_FINAL_v3_USE_THIS_ONE.xlsx. Four tabs, nineteen contributors over three years, and a conditional-format rule turning rows red that nobody remembered setting up. On the Friday it died, we'd opened it for the weekly pipeline review and found an account marked "no activity" that had broken ground on a second facility six weeks earlier. One of our reps had driven past the site. He mentioned it in standup, as an aside, the way you'd mention traffic.

The spreadsheet being wrong wasn't the surprise; spreadsheets drift. The information existed the whole time, just not where anyone could find it: in someone's head, in a text thread with a regional manager, in a LinkedIn post that scrolled past at 11pm on a Tuesday. We called it the system of record, but it only got updated when somebody remembered, usually never, usually under deadline, with twelve other tabs open.

We'd tried the usual fixes. A mandatory Monday update ritual that lasted five weeks. A Slack channel for "territory intel" that filled up with screenshots nobody tagged to an account. A rule that reps had to check a dozen watched companies' news pages before QBR, which worked exactly once, for the rep who was about to get a bad review anyway.

The thing about a named-account list is that it isn't a list of companies. It's a list of places. A warehouse that might expand. A plant that might add a line. A competitor's regional office that might be scouting a second site three exits up the highway from your best customer. None of that shows up in a CRM field unless a human notices it and then does the extra work of typing it in, correctly, on a day when they're also trying to hit number.

So the spreadsheet didn't fail because we picked the wrong tool. It failed because we were asking people to be surveillance for forty accounts in their spare time, and spare time is the first thing that goes when quota pressure shows up. The watching has to happen whether or not anyone's looking that week. That's a scheduling problem more than a discipline problem, and we'd been trying to solve a scheduling problem with a pep talk.

What finally stuck was treating the territory itself as the thing to monitor, not the people covering it. A weekly pass over the sites on our list, flagging anything that looked like new construction, an expansion, a change on the ground, each one dated so it drops into the pipeline as an actual event instead of a rumor somebody half-remembers from a hallway conversation. We route those into the CRM against the account record, same as a call log or an email open. If you want to see how that's set up for a territory or a named-account list, the territory monitoring workflow on the homepage walks through the cadence and what gets flagged.

The old spreadsheet is still on the shared drive somewhere, archived, un-updated since that Friday. Nobody's missed it. The red conditional formatting rule outlived the file it was formatting, which feels about right for how most of these tools go. We needed something that watched the territory automatically, every week, whether or not anyone remembered to update a file.

If your list of accounts is big enough that you've stopped trusting anyone's memory of it, including your own, it might be worth putting Territory Watchlist on the same beat.

Join the pilot list