Systems of record were the temples. Agents end the religion.
Start with a provocation from my friend Sameer Patel. For thirty years the system of record was the temple of the enterprise. The CRM, the ERP, the HR system. We built them to hold the sacred account of what happened, and every day we sent our people in to make their offerings, a logged call, a closed stage, a filled-in field. Sameer's argument is that agents end the religion. The system of record gives way to the system of outcome, software that doesn't just store what happened but goes and gets the thing done. Read his piece, he has a lovely example about shipping oranges out of Florida that I won't spoil.
We're taking every client we have down this road, for their own processes and for the ones they run on behalf of their customers. Which made it a little awkward that our own contacts were scattered across a dozen Google Sheets held together with hope. Time to eat what we cook. Time to reengineer our own CRM.
Why the CRM exists, and why reps actually hate it
So let's do it properly, starting with why the thing exists at all.
Sales automation was never really built for the salesperson. It was built to protect the company from the salesperson. Before it existed, the rep's contacts lived in a Rolodex and a local spreadsheet, and when the rep quit, the relationships walked out the door with them. Automation moved that knowledge into a system the company owned. The second job was forecasting, giving leadership a way to see the quarter coming. Helping the rep sell was how it got sold in. It was never the reason the budget got approved.
That original sin is why the CRM is a pain in the neck for the rep. The benefit flows uphill. The rep does the typing, management reads the reports, and keeping it current becomes the oldest fight in the building. Nobody ever fired a rep blowing the top off their target for a messy pipeline.
Ironically that makes it worse for sales leadership, not better. The forecast you're staring at is only as accurate as the rep's data entry, and the rep's data entry is late, thin and strategically vague, because they're paid to sell, not to feed your dashboard. So leadership makes calls on numbers that were half-invented on a Friday afternoon (you know that's true!). A record nobody wants to keep is a record you can't trust.
Back to first principles: what does a contact record actually need to do?
Back to first principles then. Strip away the software and ask what we actually need our contact record to do. Not much, it turns out. Know who we know. Know what was said and what we promised. Know what to do next. That's the whole job. Everything else the CRM adds is feature-bloat.
So, could we eliminate the data entry?
Yes, because the data already exists. It's sitting in our email, in our recorded calls, in our posts, in our subscriber list. Nobody needs to retype what the company already has a copy of. The tool reads what already happens. It ran back over months of our email and handed us around 600 contacts, populated, without a single form being filled in.
Could we eliminate the enrichment too?
Mostly. The same harvest fills in the gaps as it goes, and where it needs the relational map, who works where, who knows whom, it points at LinkedIn, which is already the best-maintained contact database on earth and one we don't have to keep ourselves.
Which leaves the last question. How do you decide what to do next without reports and dashboards?
Because let's be honest, who ever genuinely loved a dashboard? The BI vendors loved them. The rest of us squinted at a chart, exported it to a spreadsheet, and made the decision in our heads anyway. A report is just a waiting room you sit in before the decision. So we skipped the waiting room.
