CRM & Sales

CRM tooling ranges from a well-organised spreadsheet to enterprise systems that model an entire revenue organisation, and the failure mode is identical at every scale: a system nobody updates. A CRM containing stale data is worse than no CRM, because decisions get made from it.

For small teams and solo founders, the correct starting point is far simpler than the category implies. What you actually need is a record of who you spoke to, what was said, what happens next and when. Tools that make logging an interaction take seconds, ideally from the inbox where the interaction happened, get used. Tools that require opening a separate application and filling in six required fields do not, regardless of what they can do.

The most valuable integration in this subcategory is email, and the difference between good and bad implementations is large. A CRM that reads your mail and associates threads with contacts automatically stays current with no discipline required. One that requires you to copy an address into a blind field stays current for about three weeks.

For teams, pipeline structure is where most of the pain lives. Stages should describe the customer's state rather than your activity, and each transition should have a definition someone can apply consistently. "Contacted" is an activity; "has confirmed a budget and a timeline" is a state. Pipelines built the second way produce forecasts that mean something.

Automation is genuinely useful for the mechanical parts — logging, reminders, assigning by rules, escalating something untouched — and harmful when it sends messages that appear to be personal and are not. Recipients can tell more often than senders assume, and the cost of being caught is larger than the time saved.

Data hygiene is the maintenance burden nobody plans for. Duplicates, dead addresses and contacts who left their company accumulate steadily, and a system that makes merging and archiving easy stays usable for years longer than one that does not.

On privacy, remember that a CRM is a database of personal information about identifiable people, with the corresponding obligations: a lawful basis for holding it, a real deletion path, and reasonable retention. Tools that treat data subject requests as a first-class feature are saving you real work later.