CRM for coaches: what you actually need, and what you do not

Almost every CRM you will be shown was built for a sales team. It thinks in pipelines, deal stages, quotas and forecasts, because it was sold to a manager who needed to see whether eight people were hitting their numbers. You are not eight people. You are one coach with a calendar, and the thing you actually need is much smaller and much less glamorous: a reliable memory of every person who has ever raised their hand, and what happened last. This guide is about telling those two things apart, because buying the first one to solve the second is how coaches end up spending an hour a week maintaining a database that has never once made them money. Disclosure up front: we make Drry, which includes the contact layer described near the end. Everything before that applies wherever you run your practice.

A coaching CRM is a memory, not a pipeline

Here is the honest job description. Somebody hears you on a podcast, downloads your guide, and does nothing for five months. Then they reply to an email. The only question that matters at that moment is: who is this, what did they come for, and what did I say last time? A system that answers that in four seconds has done the whole job. A system that instead asks you to drag them from Qualified to Proposal Sent has invented work.

The distinction is not pedantry, it is the difference between a tool you keep using and one you abandon in month three. A memory is maintained as a side effect of doing the work: somebody books, the record updates. A pipeline is maintained by you, in a separate session, and the moment you are busy it stops being true. An out-of-date pipeline is worse than none, because you will make decisions from it.

The sales-team shape and why it hurts

Sales CRMs are priced and designed around a few assumptions that are all false for a coaching practice. They assume several users, so they charge per seat. They assume a long qualification process, so they give you stages. They assume the rep and the person delivering the work are different people, so the record stops at the sale and knows nothing about what happens after it.

That last one is the expensive assumption. For a coach, the interesting half of the relationship starts AFTER somebody pays: did they show up, did they finish module two, are they about to lapse. A tool that treats the sale as the finish line cannot answer any of that, so you end up with a CRM that knows about leads, a course platform that knows about progress, an email tool that knows about opens, and a payment processor that knows about money. Four systems, four partial views, and no single place that can tell you which paying clients have not logged in since August.

The five things that earn their keep

Strip away the sales furniture and a genuinely useful contact layer for a coaching business comes down to five things. If a tool does these well, the rest of its feature list is decoration.

• One record per person, with how they arrived. Name, email, the date, and the SOURCE: did they come from a webinar, a lead magnet, an event invite, a purchase, or did you add them by hand. Source is the field people skip and then wish they had, because it is the only one that tells you which of your efforts is working.
• Tags you control, not a fixed taxonomy. A tag is how you record the things nobody could have designed a field for: attended the retreat, asked about the corporate package, wants the beginner version. A tool that makes you pick from its own list of statuses has decided what your business is.
• Saved segments that recompute themselves. The useful question is never "who is on this list", it is "who joined in the last 90 days and has not bought". If the answer is a static list you built by hand, it is wrong by next week. It has to be a rule that re-runs.
• The ability to actually mail them. A contact record you cannot send anything to is an address book. The point of segmenting somebody is to say something to that group, and if that means exporting a CSV and uploading it somewhere else, you will do it twice and then stop.
• An export you have tested. Not a promise of one. Download it in week one and look at the columns. This is the only feature whose value is entirely in whether it works on the day you are angry.

What you can safely ignore

Deal stages and probability-weighted forecasting: you have perhaps a dozen live conversations and you can hold them in your head. Lead scoring: a score is a guess dressed as a number, and with thirty enquiries a month you should read all thirty. Territory management, quota tracking and team leaderboards: there is no team. Call recording and transcription inside the CRM: if you want notes from a session, take them where the session happens.

The one to think about rather than dismiss is AUTOMATION. It is genuinely useful and it is also the feature most often bought too early. An automated sequence sent to a list of forty people is four hours of setup to save nine minutes. The threshold where it starts paying is roughly when you cannot personally answer everybody the same week, which for most practices arrives well after the contact record itself becomes necessary. Buy the memory first.

When a spreadsheet stops being enough

A spreadsheet is a completely respectable CRM, and saying otherwise is usually somebody selling software. It fails at exactly three moments, and none of them is about the number of rows.

The first is when you start forgetting. Not losing the data, which a spreadsheet holds fine, but forgetting to open it. The second is when you need to write to a group: a sheet cannot send email, so every message means an export, an upload, and a list that is stale the moment you make it. The third is when a second person is involved, at which point there are two versions and no way to know which is real.

The hidden cost is the seams, not the subscriptions

Coaches usually compare CRMs on price and pick the cheapest that has the features. The larger cost sits somewhere else entirely: in the integrations holding a separate CRM, an email tool, a scheduler, a course platform and a payment processor together.

Every one of those joins is a place where a fact has to be copied. When a copy fails, nothing alerts you, because from each system’s own point of view everything worked. You discover it when a cancelled member gets the renewal email, or when a segment called "active clients" quietly starts returning people who left in spring. The work of maintaining those joins is invisible on any pricing page and is the single most common reason a coach’s stack becomes untrustworthy.

So the question to ask of any CRM is not "does it integrate with X". It is how many facts will have to be copied, and the best possible answer is none, because the record lives where the facts already happen. This is the same argument as moving an email list, one layer down: what hurts is never the data, it is the plumbing around it.

Watch how the bill is shaped

• Per seat. Built for teams. For a practice of one it is usually the worst value on the page, and it punishes you for bringing in a VA.
• Per contact. Reasonable in principle, since a bigger audience costs more to hold and to mail. The trap is that it charges you for dead weight: unengaged contacts you never write to still push you into the next tier.
• Paying twice for the same person. If your CRM and your email tool both count contacts, every subscriber is on two bills. This is the most common avoidable cost in a coach’s stack.
• A cut of your revenue. Rarer in CRMs and common in the all-in-one platforms sold alongside them. A percentage has no ceiling, which is a different kind of bill from a subscription. There is a longer argument about that in platform fees.

Whatever the shape, price it at three times your current list rather than at today’s. Three times is roughly where switching stops being a weekend job, so it is the size at which you are committed.

The all-in-one CRMs sold to coaches

A category of tool markets itself to coaches as a CRM and is really a marketing operating system: funnels, pipelines, SMS, calendars and automation in one account, usually built for agencies running many clients. They are powerful and they are not wrong for everybody. The question is whether you will run the machinery, because the price assumes you will. If you want to see how two of them weigh against each other, the head-to-heads are ClickFunnels against GoHighLevel and GoHighLevel against Kajabi, and there is a fuller version of the argument in GoHighLevel alternatives.

How this works in Drry

There is no separate CRM product here, and that is the point rather than a gap. Every person who touches your business gets a contact record automatically: somebody who joins the community, buys something, books a call, RSVPs to an event or fills in a form. The record carries how they arrived, so the source is recorded without anybody typing it, and it sits in the same system as the payment, the course progress and the email history, so none of those facts has to be synced from anywhere.

On top of that you get your own tags, saved lists, and segments built from a fixed menu rather than a query language: subscription status, how recently somebody joined, where they came from, a tag you invented, and whether they opened or clicked over the last 30 or 90 days or on one named campaign. A segment is a rule, so it re-runs every time you use it. You can import a CSV, undo an import that went wrong, and export the whole list whenever you like.

The contact layer is on every plan including free, which holds 500 contacts and 700 marketing sends a month. Creator, at $29 a month, holds 3,000 contacts and 60,000 sends, and adds automations; Growth holds 25,000. New-content emails to members are not metered on any plan. Nothing takes a percentage of what you charge, on any tier.

If you take one thing from this: buy for the follow-up you keep failing to make, not for the dashboard you imagine yourself reading. The coaches who get value from a contact system are the ones whose system tells them something true without being maintained, and the coaches who abandon one are almost always the ones who bought a pipeline. Start with the memory. Add the automation when answering everybody personally stops being possible, and not a month before.