How to fix a broken CRM: setup, pipeline, and sales team adoption

Every company I have walked into has had a CRM. Almost none of them have had a CRM that actually worked. The contacts are in there. Maybe there are some deal stages. But the pipelines are stalled, the automation is broken or nonexistent, and no one really trusts the data.

The instinct is to blame the tool. Switch from HubSpot to Salesforce. Upgrade the plan. Buy an integration. That is almost never the right answer. The tool is fine. There are two problems — and you have to fix both of them. The setup is broken. And your salespeople are not using it.

Most companies focus entirely on the first problem and ignore the second. That is a mistake. A perfectly built CRM that your sales team routes around is worth nothing. Here is how to fix both — and why order matters.

Start with the data, not the automation

This is the step everyone wants to skip. It is not glamorous. It takes time. But it is the single most important thing you can do before building anything on top of your CRM.

If your contact list is messy — duplicates, missing fields, no segmentation, contacts from five years ago who have never been touched — then any automation you build will produce messy results. Garbage in, garbage out. You will end up with leads getting the wrong sequence, deals in the wrong stage, and dashboards that lie to you.

Clean the list first. Organize it. Then build on top of it. Every time.

What this looks like in practice:

• Merge duplicate contacts and companies

• Flag and resolve incomplete records — missing email, missing company, unknown lead source

• Segment by what actually matters: lead source, company size, pipeline stage, relationship status

• Separate cold contacts from warm ones. Separate customers from prospects.

• Suppress or archive contacts that will never be relevant

This is not a one-time task. It is a habit. But you have to do it once, thoroughly, before you build anything else.

Build the pipeline that matches how you actually sell

HubSpot's default deal stages were not designed for your business. Neither were Salesforce's. They are placeholders — a starting point that most companies never update.

Your deal stages should reflect the actual steps in your sales process. Not the ideal process. The real one. What happens between first contact and closed won? What does your team actually do at each step? What information do you need captured before a deal can advance?

The Test

Open your pipeline right now. Can you tell, at a glance, what is happening in your business? Which deals are at risk? Where things are stalling? If the answer is no - your stages are not doing their job.

Two things to configure before you touch automation:

• Deal stages that reflect your actual sales motion — not a template

• Required fields at each stage so deals cannot advance without the right information captured

If you have two distinct sales motions — new business and renewals, for example — they need two separate pipelines. They are fundamentally different processes and should never share a board.

Now build the automation

Once the data is clean and the pipeline is right, automation works. Not before.

The highest-leverage automations to build first, in order:

• Inbound form response — every lead who fills out your website form gets an immediate, personalized follow-up. Not a day later. Immediately.

• Deal stage triggers — when a deal moves to a new stage, the right follow-up tasks are created automatically. Nothing falls through because someone forgot to schedule the next step.

• Cold lead re-engagement — contacts who went dark get a structured sequence. This list exists in almost every CRM and is generating zero revenue. Activate it.

• Internal notifications — your team gets alerted when a contact takes meaningful action. Opens an email. Clicks a link. Revisits the website. Reach out at the right moment.

Here is the part nobody talks about — adoption

You can build the cleanest CRM in the world. If your salespeople are not using it, none of it matters. Deals tracked in spreadsheets. Notes living in someone's inbox. Pipeline reviews that pull from memory instead of data. Sound familiar?

This is not a technology problem. It is a leadership and accountability problem. And it is the reason most CRM investments fail to produce results — not the software, not the integrations, not the price tier.

A CRM your sales team routes around is not a CRM. It is expensive contact storage.

Adoption does not happen because you bought a tool and asked people to use it. It happens because the system is built to make their jobs easier — and because leadership holds the line on using it consistently.

Make the CRM easier than the workaround

The reason salespeople avoid CRMs is almost always the same. Too many fields. Stages that do not match how they actually sell. No visibility into what the system gives them back. If logging a call takes four minutes and adds no value to their day, they will stop doing it.

The fix is to build the system around the salesperson first, not the reporting needs of leadership. That means:

• Only required fields that are actually necessary to advance a deal — not every piece of data someone in ops might want someday

• Deal stages that match the real conversation, not an idealized funnel

• Automated task creation so the rep never has to remember what comes next

• Email and calendar integration so activity logs itself without manual entry

• A dashboard that shows each rep exactly what they need to do today

When the CRM saves time instead of costing it, adoption follows. Not completely — but enough to make the data meaningful.

Leadership has to hold the line

The other half of adoption is non-negotiable. Leadership has to use the CRM as the source of truth — and that means not accepting information that lives outside of it.

If your pipeline review pulls from the CRM, salespeople update the CRM. If your pipeline review pulls from whatever a rep says in the meeting, the CRM stays empty. It is that simple.

The Rule

If it is not in the CRM, it does not exist. No exceptions. No workarounds. This is the single most effective thing leadership can do to drive adoption — and it costs nothing except consistency.

This is not about micromanaging your sales team. It is about having accurate data so you can make good decisions. Which deals need attention? Where is pipeline stalling? Which reps need coaching? You cannot answer any of those questions if the data is not there.

Train to the why, not just the how

Most CRM training is a walkthrough of the interface. Click here to add a contact. Click here to create a deal. This is how you log a call.

That training produces compliance, not adoption. Salespeople who understand why the system is built the way it is — and what they personally get out of using it correctly — are the ones who actually use it.

Show them the automation that fires when they move a deal to the right stage. Show them the re-engagement sequence that reaches out to a cold lead, so they do not have to. Show them the dashboard that tells them exactly where to focus their time. Make the value visible, and the behavior follows.

Put it all together

A CRM that works is not one thing. It is a clean foundation, a pipeline that reflects reality, automation that runs in the background, and a team that actually uses it. You need all four. Missing any one of them and the whole system underperforms.

The sequence matters too. Clean the data first. Build the right pipeline. Layer in automation. Then train your team on a system worth using — and hold the line on adoption from day one.

The companies that say their CRM does not work are usually right — but not for the reason they think. The tool is not the problem. The foundation and the habits around it are. Fix both, and the rest follows.

If you are sitting on a CRM that is more of a database than a sales tool — or a sales team that has learned to work around it — that is exactly the kind of infrastructure problem Hey Jano is built to fix.