Ask a search engine how to stop clients chasing you for updates and you will be recommended a CRM. It is worth understanding why that recommendation is so common and so often wrong: CRM is a large, well-funded software category with an enormous content budget, and "client management" sounds like it covers any problem involving clients. The category was built for a specific job, and it is not this one.
They solve different problems
| CRM | Follow-up tool | |
|---|---|---|
| Central record | A contact or deal | A job or file |
| Question it answers | Who should I contact next? | Where is this work, and who is waiting? |
| Lifecycle covered | Before the sale | After the sale |
| Success looks like | More closed deals | Fewer status questions, faster payment |
| Who sees it | Your team only | Your team, plus a client-facing view |
| Grows with | Number of prospects | Number of active jobs |
The row that matters most is the first. A CRM is built around a person; service delivery is built around a job. One client can have three jobs at three different stages, and a system whose primary record is the contact will represent that badly no matter how many custom fields you add.
Which problem do you have?
The honest test is which of these sentences you have said recently.
| If you say this | You have a | |
|---|---|---|
| "I forgot to follow up on that lead" | sales problem | CRM |
| "Where did that enquiry go?" | sales problem | CRM |
| "I do not know which client is waiting on me" | delivery problem | Follow-up tool |
| "They emailed asking for an update again" | delivery problem | Follow-up tool |
| "That invoice has been out for six weeks" | delivery problem | Follow-up tool |
| "Which files are stuck waiting on documents?" | delivery problem | Follow-up tool |
What happens when you use a CRM for delivery
It does technically work. Most CRMs have custom pipelines, and you can rename the stages from "Qualified / Proposal / Won" to your delivery stages. The problems appear over the following months, and they are consistent.
The record is the wrong shape
A client with three concurrent jobs needs three records. You end up either duplicating contacts or cramming three jobs into one deal, and neither survives contact with a busy week.
Nothing is client-facing
A CRM is an internal system by design. It has no concept of a view you would send to the client, so the status information sits where the client cannot reach it — and they carry on emailing you.
You pay per seat for people who do not sell
CRM pricing assumes seats are salespeople. In delivery the people who need access are everyone touching the work, and the bill scales in a way the value does not.
The reporting answers the wrong questions
Conversion rates, pipeline value, forecast. Useful numbers — none of which tell you which four files are waiting on a client document today.
Setup cost is front-loaded
A week of configuration before it does anything, at which point sunk cost keeps you there long after it is clear it is not fitting.
What about a spreadsheet?
A spreadsheet is a genuinely reasonable answer for a while, and it is worth being honest about that rather than dismissing it. It is free, instantly flexible, and everyone already knows how to use it. Below roughly ten active jobs it is often the correct choice.
| Limit | What it looks like in practice |
|---|---|
| No client-facing view | You retype the sheet's contents into an email, per client, per week |
| No history | You cannot answer "when did we tell them that?" |
| Nothing happens on its own | Reminders depend on you opening the file |
| Concurrent editing | Two people, two versions, one of them wrong |
| Everything is visible | It contains all clients, so it can never be shared with one |
The signal to move is not the number of rows. It is the first time you copy information out of the spreadsheet into a message — because that is the moment the spreadsheet stopped being the system and became a source you now maintain twice.
A decision you can make in five minutes
Choose a follow-up tool if most of these are true
- Your clients have already bought — the work is sold and now needs doing
- You are asked for status updates more often than you would like
- Several jobs are usually waiting on something from a client
- You send invoices that sometimes need chasing
- You would like clients to be able to check progress without asking
- You have fewer than a few hundred active jobs at once
Choose a CRM if most of these are true
- You have more prospects than clients
- Deals take weeks and involve multiple conversations before a decision
- You need a forecast
- More than one person sells, and leads move between them
- Marketing campaigns need to connect to individual contacts
Counting the real cost
Subscription price is the smallest number in this decision. The larger ones are setup time, the ongoing cost of maintaining a system that half-fits, and the status emails you keep writing because the tool cannot show a client anything.
A useful exercise before you buy anything: count the status-only messages you send in a week and multiply by ten minutes. For most small teams that is two to four hours a month per person. Any tool you are considering should reduce that number specifically — if you cannot describe how it will, it is solving a different problem.