Run this search and look at who wrote the results. The top of the page is CRM vendors' own guides to choosing a CRM, which answer the question they would like you to be asking. They are not wrong about what the software does. They are just the wrong people to ask whether you need it.
So here is the version from a company that sells the opposite, and does not want you buying a platform you will use one corner of.
Start from the job, not the category
Most searches for this term come out of a specific frustration, and it is worth naming yours before you shop. The common ones, in the order they tend to bite a service business:
- Work comes in, gets done, and nothing happens afterwards. No review, no repeat booking, no referral.
- Leads arrive from three places and you lose track of which you replied to.
- You cannot remember what you quoted someone six weeks ago.
- Two people in the business have different versions of the same customer list.
- You want to know which of your marketing produced paid work.
A CRM is built for the last four. It is a shared record of people and deals, which is a real thing to need once more than one person is selling and the sales cycle is long enough to forget. If your pain is in that list, buy one, and buy the simple one.
The first item is different. It is not a record-keeping problem at all, it is a sending problem, and it is the one most often answered with a CRM because that is the aisle the shopper walked into.
The follow-up problem is one send, not a system
A home services business finishes a job, the customer is pleased, and that is where it stops. Nobody asks for the review. The fix is a message that goes out after the work is done, with a link in it, to every customer and not a hand-picked few.
You do not need a pipeline, lead stages, a shared inbox, a webchat widget, lead scoring or a mobile app with a dashboard to do that. You need the customer's email address, the moment the job closed, and something that sends. That is the whole of it. How to ask customers for reviews is the wording half, and the request templates are free to copy whether you buy anything or not.
Timing is the only subtle part, and it is subtle in a way a CRM does not help with: ask while the work is still fresh in the customer's mind. When to ask goes into what that means for jobs that run long.
Why the bigger tool costs more than its price
The honest argument against buying a platform for this is not the invoice. It is the three things that follow it.
Setup is work you do before any value arrives. A CRM wants your customer list imported, your stages defined, your fields mapped and your team trained. Done properly that is a project. Done at the pace a busy owner actually has, it is a half-populated database that nobody trusts, which is worse than a spreadsheet because now two records disagree.
Then there is the surface area. Every feature you do not use is still in the navigation, still in the onboarding emails, still something a new employee has to be told to ignore. Software you use a tenth of trains you to avoid opening it.
And the commitment. The reason a platform wants an annual deal is that the setup cost is sunk into year one and the renewal is where the margin lives. Which is a fine business model and a bad trade for a buyer who is not sure yet. If you are not sure, the thing to protect is the ability to stop: we publish our pricing and cancel in one click, month to month, on purpose, because a buyer who can leave is a buyer who does not need a sales call first.
What we are, so you can rule us out
This product is not a CRM and we are not going to tell you it is one. It holds the customers you choose to ask, sends a review request by email, and tracks whether the link was opened. There is no inbox, no pipeline, no deal stages and no chat widget, and the review link it sends is the plain Google one that the link generator will produce for you without an account.
If your problem is the first item on that list, that is the right size of tool. If your problem is three of the other four, a CRM is the right answer and you should go read the vendor guides, with the caveat that they are vendor guides.
The test
One question sorts it. Does the work you are losing need remembering, or does it need sending?
Remembering is a database problem, and a database is what a CRM is. Sending is a trigger and a message, and buying a database to solve it leaves you with a database to maintain and the message still unsent. Word of mouth is downstream of the message either way, and it does not care which logo is on your software.