Why CRM rollouts fail at distributors, and what to do differently

The short answer. In the published figures on CRM implementation failure, a project that never goes live is the less common result. The more common one is a system that goes live and then goes quiet. We group the causes at a distributor into six reasons you can check before you sign and again in the first 60 days: the CRM does not hold the customer the way the customer buys, the rep gets nothing back for typing, the quotes are written somewhere else, the system stops working where the visits happen, the first import was dirty, and nobody owns the rollout after launch day. Our recommendation: start with one team and one job, prove it in 30 days, and measure use every week.

One caution before the numbers. The failure rates quoted in most articles on this subject are between 8 and 25 years old, and each one measured something different. We read the sources. They are in the next section.

Sources in this article were read on October 8, 2026: the research on the publishers' own pages, the vendor facts on the vendors' own pricing, legal and help pages. We build a CRM for industrial & MRO distributors, so read our view with that in mind.

How often do CRM projects fail?

We found no current, measured answer, and no figure for distributors that we could read at its source. Here is what the often-quoted numbers say when you go back to them.

Source	Year	What it says	What it measured
Gartner, as quoted by ZDNet	2001	"Through 2006, more than 50 percent of all CRM implementations will be viewed as failures from a customer's point of view"	A forecast of how projects would be viewed, not a count of failed projects
AMR Research, as quoted by ZDNet	2005 to 2007	18%, 31% and 29%	Respondents who had experienced an implementation failure that kept them from going live
Forrester, report summary (ZDNet lists it under 2009)	2008	"28% of enterprises and 47% of the midmarket organizations surveyed agreed that their expected business results were met or exceeded"	A survey of 133 organizations. The 47% often repeated as a failure rate is the share of midmarket organizations that agreed their expected business results were met or exceeded
CIO magazine	2017	About one-third of CRM projects fail	An average of at least a dozen analyst reports whose results ran from 18 percent to 69 percent, with different methods and standards
Harvard Business Review, Scott Edinger	2018	Repeats the one-third figure, then says that when he asks his clients' executives whether the CRM is helping the business grow, the failure rate is closer to 90%	The author's experience with his own clients, not a survey

Two things follow. First, the answer depends on the question. A project that never goes live is the less common result in those figures. A project that goes live and does not fully meet expectations is the common one. Second, the Harvard Business Review article gives a cause that fits a distributor's field team: CRM systems "are too often used for inspection, rather than creating improvement in the sales process." A rep who is asked to type so that a manager can check on them will type as little as possible.

So do not plan around a failure rate. Plan around the specific ways a rollout goes quiet.

Why do CRM rollouts fail at distributors?

Six reasons, each with a sign you can see early and the thing to do about it.

Why it stalls	The early sign	What we recommend
1. The CRM does not hold the customer the way the customer buys	Reps type the department into the contact's name or the notes field	Decide the account structure before the first import
2. The rep gets nothing back for typing	Visit notes arrive in a batch on Friday afternoon	Make the first job one that helps the rep: the next follow-up date, the customer's history before the visit
3. The quotes are written somewhere else	The pipeline total is far from what inside sales quoted in the ERP last month	Decide who records a quote and its outcome, and where
4. It stops working where the visits happen	Notes are written on paper in the truck and typed in later, or not at all	Test the phone app with no signal before you sign
5. The first import was dirty	A rep finds the same customer twice in the first week	Clean one team's customers first and import only those
6. Nobody owns it after launch day	The sales meeting still runs from a spreadsheet	Name one owner, and run the weekly meeting from the CRM

1. The CRM does not hold the customer the way the customer buys

A general CRM starts from a company, a contact and a deal, the point we made in our buyer's guide. A distributor's customer is often a mine, a mill or a municipality with several departments, each with its own budget and its own contact. When the system has one place for all of them, the rep works around it, and the workaround is the first thing that breaks. We covered the choices in account hierarchy in a CRM for distributors. Settle that structure before any data goes in, because changing it later means touching every record.

2. The rep gets nothing back for typing

Salesforce's State of Sales research, a survey of more than 7,700 sales professionals published in December 2022, reported that reps spend 28% of their week selling, with most of the rest going to tasks such as deal management and data entry. That is a vendor's own survey, and it is not specific to distribution. A CRM that adds typing to that week and returns only a report for the manager is the "inspection" problem in the Harvard Business Review article above.

The fix is to choose a first job that pays the rep back the same day. Two we would start with for a field rep: the next follow-up date appears when a visit is logged, and the customer's last quote and last visit are on one screen before the rep walks in.

3. The quotes are written somewhere else

At many distributors the outside rep finds the opportunity and inside sales writes the quote in the ERP. If the CRM expects the rep to enter the deal, the pipeline is empty or wrong, and the manager stops trusting it. Decide in advance who records the quote, where the quote value comes from, and who records what was ordered. CRM vs ERP for distributors sets out which system should hold what.

4. It stops working where the visits happen

Plant floors, basements and mine sites often have no signal. Vendors handle this differently, and the difference is on their help pages:

• HubSpot documents two routes. Its offline-access page (last updated October 6, 2026) describes a read-only mode, currently a beta that a Super Admin opts the account into: "Offline access is read-only. You cannot edit, create, or delete records, properties, or activities while offline." It "must be turned on manually in mobile app settings before going offline." Separately, its Mobile Notetaker page (last updated October 5, 2026; Sales Hub or Service Hub Professional and Enterprise, with an assigned seat) says "Users can record when they're offline and associate the recording with the corresponding meeting and CRM record when they're back online."
• Salesforce's help page describes "two levels of offline access: caching frequently accessed records, so users can view data while offline, and Offline Edit, so users can create, edit, and delete records while offline." An administrator manages both from Setup.
• Pipedrive's help page (last updated September 3, 2026) says that without a connection "you will still be able to move deals along your pipeline, add notes, activities and anything you would normally do within the Pipedrive mobile app", and that the data syncs when the phone reconnects.

Do not take any of this from a page, ours included. Put a phone in airplane mode during the trial, log a visit, reconnect, and check that it arrived once.

5. The first import was dirty

A rep who opens the new system and finds a customer twice, or finds a contact who retired in 2019, decides in that minute how much to trust it. Vendors match duplicates by rules you need to know before the import. HubSpot's help page, for example, says it deduplicates contacts by email address: on import, a row with the same email updates the existing contact, and without an email or another unique identifier "each row of your import file will be imported as a new contact record." HubSpot also describes custom unique-value properties for matching on import, and on Professional and Enterprise a duplicates tool that compares records daily and lets you merge pairs. If your counter contacts have no email on file, that rule matters.

Data quality is a general problem too. Validity, a vendor of email and CRM data tools, says its report "The State of CRM Data Management in 2025" draws on 602 CRM users and stakeholders, and that 76% said less than half of their organization's CRM data is accurate and complete. Treat that as a vendor's survey of its own market, and treat your own export with the same suspicion.

6. Nobody owns it after launch day

Salesforce puts it plainly on its own adoption page: "adoption and implementation are two different processes." It adds that after implementation "your company leadership must set a timeline to ensure effective adoption across teams." Microsoft's implementation guide for Dynamics 365 says "Training isn't the only factor in meaningful user education and adoption."

We recommend the sales manager, not IT, as the owner. A simple sign that the rollout has an owner is which document is open in the Monday sales meeting.

What do CRM vendors say about adoption on their own pages?

The large vendors do not hide the risk. Microsoft's Dynamics 365 implementation guide says in its change management chapter (page last updated October 25, 2023): "It's a widely embraced fact of our industry that implementation projects can go wrong." A Salesforce guide on why CRM projects fail, on its India site, advises against a big-bang implementation: "Start with one business unit and get that right, then steadily roll out to other areas of the business."

That advice costs nothing and applies to any CRM, including ours: one unit first.

What onboarding help comes with the licence?

Onboarding help is a real part of the cost and the outcome, and it differs a great deal between vendors. Read on each vendor's own pages on October 8, 2026. Prices are as the page states them, before tax.

Vendor	Onboarding help named on the vendor's page	Price stated
HubSpot Sales Hub	Remote access to an onboarding specialist, by phone, video call and email, "to assist with the setup and/or implementation" of the subscription. HubSpot also sells higher onboarding tiers	"Onboarding is required for a one-time fee of $1,500" on Professional, and of $3,500 on Enterprise (US dollars)
Zoho CRM	An onboarding program for paid customers: four one-on-one online sessions of 60 minutes each. Zoho says of its experts that "they will not implement Zoho CRM for you". Separately, a paid implementation service called Jumpstart	The four sessions are "at zero extra cost". Jumpstart was listed at $200 per hour on our visit (the page gives no currency code or date and varies by region) for one implementation expert, with a minimum of 10 hours. Zoho says the final cost depends on scope
Salesforce	Three Success Plans. Standard is self-guided resources. Premier adds expert guidance and onboarding. Signature is the top tier	Standard is "Included in all licenses". Premier is "30% of net license fees" and bundled with Unlimited Edition. Signature: "Contact your account executive"
Microsoft Dynamics 365	FastTrack for Dynamics 365, for customers who meet a minimum annual licence spend (the amount is not stated on the page) and work with a qualified implementation partner. Others are pointed to self-guided resources	Not stated on the pages we cite
Pipedrive	A customized onboarding plan with a customer success manager for qualifying customers "spending over $1000", based on monthly recurring spend	Not stated on the page we cite

Read the table for what it does not say. Standard vendor onboarding helps your team set up and learn the product. It is not the same as someone designing your departments, equipment records, territories and quote flow inside it. Microsoft says its FastTrack architects review a project in workshops, and is direct about the limit: "we have no formal role on the project and we don't design or develop a solution for the customer." With any vendor, ask who does that design work, how many hours they estimate, and what it costs. That work is commonly a partner's invoice. Get it quoted next to the licence.

What does a 90-day CRM rollout look like at a distributor?

This is the sequence we would follow with any CRM. It is a plan, not a guarantee.

When	Do this	You know it is working when
Before you sign	Spend two days watching the work: outside reps, the counter, inside sales. Write down five real accounts, as in our buyer's guide. Have each vendor load one of them	The vendor's screen shows your customer's departments, not a sample company
Days 1 to 30	One team, one job. Import only that team's customers, cleaned by the reps who own them. The one job: every visit is logged with a next follow-up date	Every rep on the team logged at least one visit this week, without being asked twice
Days 31 to 60	Add quotes: who records them, and what was ordered. The manager runs the weekly meeting from the CRM and from nothing else	The pipeline total is close enough to the ERP's quotes that nobody argues about it
Days 61 to 90	Bring in the second team, with the first team's reps showing them. Fix what the first team complained about before adding features	The second team's first week looks like the first team's fourth

Five numbers to watch every week

1. Reps who logged a visit this week, as a share of reps in the rollout.
2. Visits logged with a next follow-up date, as a share of visits.
3. Quotes with a recorded outcome: won, partly won or lost, with the reason.
4. Duplicate customers reported by reps. It should fall to zero and stay there.
5. Meetings run from the CRM. Either the Monday meeting uses it or it does not.

We are not giving target percentages, because we have not published any and the sources above do not support one. Watch the direction. If number 1 falls for three weeks in a row, go back to the six reasons and find which one it is.

When is a general CRM the better choice for a rollout?

Often. Choose a general CRM when:

• Your sale is a standard one. One buyer per customer, quotes written by the rep, little equipment to track afterwards. A general CRM fits that with little configuration, and a simple rollout is easier to land.
• You want vendor onboarding at a published price. HubSpot and Zoho both state what their onboarding includes and what it costs, as in the table above.
• You have an administrator on staff, or a partner you trust. Salesforce and Microsoft Dynamics 365 are highly configurable, and both vendors publish structured guidance and success programs for larger projects.
• You need a formal training and change program across many branches. The large vendors and their partners have the people and the materials for that.

AlterFlow is not the right fit if you want to sign up online and start the same day, you want a per-seat list price to compare, or you need a network of certified partners and a training academy. We publish none of those. We are also not a fit if most of your business is one-off orders with no relationship after the sale.

How does AlterFlow approach a CRM rollout?

The method is on our industrial & MRO CRM page, in four steps:

1. "Two days in your building." We sit with the reps, the counter, the sales support desk and the service side, and watch the work.
2. "A clickable prototype before a contract." You get something you can drive, shaped around your business, while the decision is still open. It is the cheapest moment to find out we understood you wrongly.
3. "Build in slices, each one usable." The first release does a real job for a real person, and priorities can change between slices.
4. "Land it with the people who resisted last time." The page says: "Adoption is the design constraint. A system the field will not open is a system that failed, no matter how correct it is underneath."

Several parts of the sales and territory CRM exist because of the six reasons above. All of them carry the label Production build, in delivery, which means built and being deployed to a live team, not a product with a long customer list:

• Organization, department and contact hierarchy, with equipment held at the department that owns it (reason 1).
• Follow-up regeneration: logging an outcome creates the next date, and a miss stays visible (reason 2).
• Quote records with partial wins captured against what was ordered, and the reason for the gap (reason 3).
• Capture in the field that works with no signal, holds on the device, and arrives exactly once (reason 4).

The public demo shows the first and third of these at the level described at the end of this article. Follow-up regeneration and no-signal capture are production-build claims the demo does not show.

On data, our page describes an import pipeline that runs in production today for a dealer in another industry: column mapping, duplicate handling, a report on every row that failed, and a one-click reversal if a whole import was wrong (reason 5). On sign-in, it says staff without an email address can sign in, because many counter and service people have no personal mailbox. A live connection into your ERP is work we scope per engagement, not something already built.

Frequently asked questions

What percentage of CRM implementations fail? We found no current, measured figure. The survey numbers in circulation run from 18% to about 70% and come from studies dated 2001 to 2009, which CIO magazine averaged in 2017 into about one-third. They measured different things, from projects that never went live to projects that did not meet expectations. A 2018 Harvard Business Review article adds one consultant's "closer to 90%" from his own clients.

Why do sales reps stop using a CRM? In our view, mostly because it takes time and gives them nothing back. If the first thing the system does is help the rep, for example by setting the next follow-up date or showing the customer's history before a visit, we expect use to hold up better than when its first job is a report for the manager.

Should a distributor roll out a CRM to every branch at once? We recommend against it. A Salesforce guide on its India site says to avoid a "big bang" implementation and start with one business unit. Start with one team and one job, and add the next team when the first is using it without reminders.

What should we measure in the first 90 days? Five things, weekly: reps who logged a visit, visits with a next follow-up date, quotes with a recorded outcome, duplicate customers reported, and whether the sales meeting ran from the CRM.

Is the onboarding included in the licence enough? It depends on what you need. Standard vendor onboarding helps your team set up and learn the product. Designing your account structure, equipment records and quote flow is separate work, done by your own administrator, a partner or the vendor's paid services. Ask for that estimate in writing.

Can a stalled CRM rollout be rescued? In our view it often can, if the cause is one of reasons 2 to 6: narrow the rollout to one team and one job, clean that team's data, and name an owner. If the cause is reason 1, the structure, the fix is a rebuild of the records inside the same CRM or a different system.

---

See the structure before you plan a rollout. The working demo is open with no form and no sign-up: a prototype on sample records. Open a customer to see its departments, the equipment on a department with a service due date, and a won deal that records a partial win and the reason. Or book a walkthrough and bring the account your last CRM handled worst.

Sources, read October 8, 2026. Research: ZDNet, CRM failure rates: 2001-2009 (Michael Krigsman, August 3, 2009). Forrester, Answers to five frequently asked questions about CRM projects (public summary, August 29, 2008). CIO, What to do when your CRM project fails (David Taber, September 18, 2017). Harvard Business Review, Why CRM projects fail and how to make them more successful (Scott Edinger, December 20, 2018; summary and opening). Salesforce, State of Sales research announcement (December 8, 2022). Validity, The state of CRM data management in 2025. Vendors: Salesforce CRM adoption, why CRM projects fail, Success Plans, work offline with the Salesforce mobile app. Microsoft change management, training strategy, FastTrack overview, FastTrack eligibility. HubSpot product and services catalog, access records offline, Mobile Notetaker, deduplication of records, manage duplicate records. Zoho CRM onboarding, Jumpstart. Pipedrive do the mobile apps work offline?, onboarding. Prices, plans and features change; check the vendor's page before you buy.