The competitor we stopped competing with

Someone on the sales team asked why we still had a slide about a company we hadn't seen in a deal since February. Nobody had a good answer. The honest one was that the slide had been there since the deck was built, and removing things from a deck requires a decision, while leaving them there requires nothing.

We checked. Eleven names on the tracked list. Four of them had shown up in a closed-lost reason in the past two quarters. Two had quietly moved upmarket and out of our path entirely. One had been acquired and folded into a platform we'd never once discussed.

Lists only grow

Every competitive program I've watched has an intake ritual and no exit ritual. A rep loses a deal, names a company, and it gets added. Someone finds a startup with an uncomfortably similar homepage, and it gets added.

Nothing has the opposite trigger. Dropping a competitor feels like a bet with an obvious downside — what if they come back? — and no visible upside. So the list grows, the attention per name shrinks, and eventually the whole thing has the texture of the quarterly review nobody trusts.

The cost isn't the noise

Here's the part I got wrong. I assumed a bloated roster was a mild efficiency problem — a few extra tabs, some pages checked that didn't need checking. Annoying, not dangerous.

The damage is on the other side. A roster that never gets revisited stopped being a decision, and a list that isn't a decision never gets asked the question that matters: who's on here that shouldn't be, and who isn't on here that should be? Those two only get asked together. Skip the pruning and you skip the adding too.

The company that ate into our mid-market pipeline last year was never on the list. It hadn't been rejected. It had never been considered, because nobody had opened the list in a way that invited considering anything.

What actually changed

We didn't build a process. We added one line to an existing meeting: read the roster out loud, name by name, and say why each one is still there. It takes four minutes. Two names came off the first time, one came off the second, and we added three that had been sitting in someone's head.

Tooling doesn't solve this part. Seeto watches the public surfaces of whoever you point it at and turns the diffs into discrete change events — useful once the roster is right, and it makes a bloated list cheap to carry, which is exactly why it can also hide the problem. All eleven names had clean, current change feeds. Every one of those feeds was working. Four were reporting on companies that had stopped mattering.

Monitoring answers what changed. It has nothing to say about who counts, and the second question is the one that goes stale in silence. If you're baselining a new competitor this quarter, the same sitting should decide who leaves.

When was the last time a name came off your list?