All Get Chosen

The CRM in Plain Language

Strip the acronym: a CRM is a list of people, each with a stage and a next step. When a spreadsheet is genuinely fine, when it stops being fine, and the person-not-deal rule.

Few tools are simultaneously as oversold and as misunderstood as the CRM. The industry sells it as a "revenue platform" with dashboards like a cockpit; practices hear "sales software" and conclude, reasonably, that it's for salespeople — which they are not. Both framings miss what the thing actually is, which is almost embarrassingly simple:

A CRM is a list of people, where each person has a stage and a next step. Who they are, where they stand with you (enquired, booked, active, past), and what happens next (who acts, by when). That's the entire concept. Everything else — automations, dashboards, "pipelines" — is elaboration on those three columns, useful only after the three columns are true.

The person-not-deal rule

One design decision matters more than any tool choice. Sales-flavoured CRMs organise the world around deals — opportunities with dollar values marching through stages toward "closed-won." For a professional practice, that frame is quietly corrosive: your clients aren't transactions to close, they're relationships with a current state — and the relationship continues, crucially, after the money: into the second sale, the referral, the win-back. Model the person, with stages that span the whole relationship (enquiry → active → past → returning), and the same list that runs this cluster's conversion work runs Keep Your Customers' retention work. Model deals, and every client vanishes from the system the day they pay — exactly when the profitable half of the relationship begins.

When a spreadsheet is genuinely fine

Honest answer the CRM industry won't give: a spreadsheet kept honestly beats a CRM kept badly, and for many small practices it's genuinely enough. One row per person, columns for stage, source, next step, date — the states that beat the inbox, the "how did you hear" answers — maintained as a daily two-minute habit. A solo practice with a dozen enquiries a month can run excellently on this for years.

It stops being fine at recognisable moments: when re-typing appears (the sheet doesn't talk to the form, the booking, the invoice — connection is what real CRMs buy you); when a second person needs the list and versions start drifting; when follow-up needs to happen automatically rather than when someone remembers; or when volume makes the glance impossible. The upgrade trigger is friction you can name — never the vendor's argument that you've "outgrown" anything.

Choosing without the demo-trance

When the moment comes, practices lose months comparing feature grids. Shortcuts: pick the person-first tool, not the deal-first one; pick the one that connects to what you already run (the connections are the point); pick the one whose free-or-cheap tier you'll actually keep updated — the best CRM is the one that's true on a Tuesday afternoon. And own the account, whoever sets it up.

Questions practices actually ask

Isn't this overkill plus my calendar and email? Calendar and email are channels; the CRM (or sheet) is the state. The overkill isn't the list — it's buying an enterprise platform to do what three columns do. Match the tool to the truth: everyone has a stage and a next step, somewhere.

What about client confidentiality? Real concern, ordinary solution: the list holds relationship state, not case substance — name, stage, next step, source. The confidential work stays in your practice-management or file system; the CRM just knows where the relationship stands.

Do the AI features matter? Increasingly, but only on a true list — AI drafting follow-ups from wrong states is wrong faster. Foundations first; magic second.

Who keeps it updated in a busy practice? Whoever touches the moment: the form writes new entries automatically; whoever replies moves the stage. If updating takes more than seconds per event, the setup — not the discipline — is wrong.


Part of Get Chosen — the conversion chain.

Explore further

Based on the themes in this article, you might find these topics interesting.