I once watched a 60-person industrial supplier buy a CRM to fix a forecasting problem. Six months later the forecast was worse, the reps were logging in once a week to paste numbers into a spreadsheet, and the sales manager had started calling the system “the tax.” Nothing was wrong with the software. The company had automated a pipeline nobody had ever agreed on.
That is the pattern I keep running into. Customer relationship management is usually sold as a tool for tracking deals. In practice it is a tool for making commitments visible. If your team has never agreed on what a qualified lead is, or when a deal counts as won, the CRM will not discover that for you. It will just record the disagreement in more expensive detail.
What a CRM is actually for
Strip away the feature lists and a customer relationship management system does three jobs.
It remembers. Every call, email, quote, and promise sits in one place, attached to a company and a person, instead of living in someone’s inbox or in the notes app on a phone that gets replaced every two years. When a rep leaves, the account history stays.
It reminds. Follow-ups fire on schedule. A deal that has sat untouched for eighteen days surfaces in a list. Renewals show up before they lapse. This is the part that pays for the license in the first month, and it is the part most teams underuse.
It reports. Not dashboards for their own sake, but the ability to answer a specific question on a Monday morning: which of the deals we forecast for this quarter have not had a conversation in three weeks?
Everything else, the AI summaries and the conversation intelligence and the twelve-tab contact record, is optional. Nice when it works. Never the reason the project succeeds or fails.
Why CRM projects stall
The failure modes are boringly consistent. In the rollouts I have been brought into after the fact, four causes account for almost all of the damage.
Nobody owned it. A CRM without a named internal owner becomes everyone’s side project and no one’s job. Six months in, no one can explain why a required field exists. I now ask who will own the system before I ask what the system will do.
The data was dirty on day one. Duplicate accounts, three spellings of the same customer, contacts attached to the wrong company. Migration exposes this, and teams respond by postponing cleanup. That just moves the pain into the system where it is harder to fix.
The fields multiplied. A sales leader asks for one report, an engineer adds four fields to support it, and two years later reps face thirty inputs before they can save a note. Every required field is a small tax on the person doing the work.
Nobody trained the second wave. Launch training covers the people in the room. It rarely covers the hire who starts in month seven, and by then the person who built the system has moved on.
The funnel above is the number I wish more buyers tracked. Seats purchased is a purchasing metric. Users who trust the forecast is the one that tells you whether the project worked.
What it really costs in the US market
For a 20 to 50 person B2B sales team, plan on $40 to $90 per user per month for a mainstream CRM at a mid-tier edition. That is the easy number. The harder ones:
- Implementation: $8,000 to $40,000 for a first build, depending on integrations and how much of your process needs to be rethought.
- Admin time: a half-time administrator once you pass roughly 25 users. If you skip this, the system slowly rots.
- Integrations: $3,000 to $15,000 per meaningful connection, whether that is an ERP, a quoting tool, or your phone system.
- The switching cost later: exporting your own data should be free and is often not.
I have seen a 30-seat deployment land at $54,000 in year one all-in and a comparable one land at $180,000. The difference was almost never the software. It was scope discipline.
Signs you actually need one
You need a CRM when the answer to “what happened with that account” depends on who you ask. You need one when two reps have called the same prospect in the same week. You need one when your forecast is a spreadsheet that three people maintain and nobody believes.
You probably do not need one when you are a team of three selling to people you talk to weekly, and the spreadsheet is accurate. A CRM adds structure. Structure has a cost. If your process is simple enough to hold in your head, hold it there a while longer and spend the money on lead generation.
The rollout I would run
Start with one pipeline and one report. Not four pipelines, not a custom object model, not a territory hierarchy. Pick the deal stages your team already uses in conversation, name them the way your team names them, and load only the accounts that are live right now. Historical data can come later, and often should not come at all.
Then give two reps a week to work real deals in the system while someone sits next to them. Watch where they hesitate. That hesitation is your build backlog, and it is worth more than any requirements document.
Roll out to the rest of the team once those two reps can run a full week without opening the spreadsheet. Not before. A CRM that arrives with unresolved friction teaches everyone to route around it, and routing around it is a habit that is very hard to undo.
If you are still comparing products, the shortlist depends far more on your sales motion than on feature grids. Our guide to choosing CRM software walks through that, and the Salesforce and HubSpot breakdowns cover the two most common paths. If budget is the constraint, start with what a free CRM for small business actually includes before you assume it is enough.
The last thing I will say is the least popular: the CRM is not the strategy. It is the record of the strategy. Companies that get value from it are the ones that decided how they sell before they decided what to buy.
