Too Long; Didn't Read · 30 SECONDS
- 47% of Customer Relationship Management implementations fail to meet their goals (Forrester), 50% (Gartner), 55% (Johnny Grow 2025). 70% of failed projects fail not because of the technology, but because of a lack of user acceptance.
- Three real reasons: (1) No sales process before purchasing the tool, (2) implementing the tool instead of change management, (3) Customer Relationship Management as part of a stack of five systems instead of a single ecosystem.
- 91% of compaNos with 10 or more employees have a Customer Relationship Management system, but only 72% of salespeople use it. 32% spend more than an hour a day manually entering data. 22% do not understand what Customer Relationship Management is (Salesmate 2026).
- The next implementation won't fail If you decide that this is a change management project, not a software purchase, everything else follows from that decision.
Customer Relationship Management as a mirror, not a makeover. The system doesn’t create the sales process for you; it simply reflects it. If the process doesn’t exist, the mirror shows nothing, and salespeople go back to Excel. When the process is divided into silos, the tool digitizes those silos. This is one rule, and breaking it accounts for 90% of failed implementations.
Friday, 4:30 p.m. The sales direCTOr opens the Customer Relationship Management system the company signed a contract for eight months ago. The pipeline shows 14 deals. He personally remembers three of them. The rest are placeholders: the sales reps entered something just to make the list look “up-to-date” for the board.
There's another thing in the drawer next to it: an Excel spreadsheet. That's where the REAL deals are. 47 entries, each with notes, phone numbers, and follow-up dates.
You know the feeling. Doubt, frustration, quiet annoyance...because management gave you a budget, the vendor promised a “revolution,” and a year later, you’re exactly where you started. Only now you’re out of pocket for the license, training, and six months of your team’s wasted time.
Is this your company? Or your client?
47% of implementations fail. The reasons are predictable
If so, You're not alone. According to a study by Forrester Research 47% of Customer Relationship Management implementations fail to meet their goals. Gartner puts the figure at 50%. The 2025 update already mentions 55%. And the most powerful number in this whole puzzle: 70% of failed Customer Relationship Management projects fail not because of the technology, but because of a lack of user acceptance (Forrester, via Customer Relationship ManagementSearch 2025).
So the problem isn't the Customer Relationship Management. In fact, the problem is the people who don't use it. And people don't use it not because they're lazy, but because no one has given them a reason to use it.
What really goes wrong in 47% of Customer Relationship Management implementations
We have implemented Customer Relationship Management systems and configurators for dozens of manufacturing compaNos in Poland. Most of them came to us after their first (or sometimes second) unsuccessful attempt. We have a map of the places where implementations fail. These places are 90% predictable.
There is an observation in the industry that sounds simple and harsh: Customer Relationship Management won't fix the chaos—it will just expose it. The system is a mirror, not a makeover. It shows you what your sales processes really look like. If they look like silos, that’s what you’ll see in the Customer Relationship Management. Just highlighted.
This article isn’t about how “you need to train your team better.” It’s about three things you MUST do before you even touch the license. You can check each of them in five minutes. And if you’ve had one failed implementation, you’ve already missed out on each of them.
|
Is your second implementation not going as planned either? A 30-minute diagnostic conversation. No slides, no sales pitch. You’ll walk away with a checklist of questions for the vendor. |
Fill out the form |
Why are compaNos still buying Customer Relationship Management systems in 2026 that nobody ends up using?
Before we get into the three reasons, here’s some background. According to the Salesmate 2026 report 91% of compaNos with 10 or more employees use a Customer Relationship Management system. It's a saturated industry. The tool is the industry standard. But within those Same compaNos The adoption rate among salespeople is 72%. Which means one thing: 28% of salespeople with access to a Customer Relationship Management system do not use it at all or use it only occasionally.
And what are the rest doing? 32% spend more than an hour a day manually entering data (Salesmate 2026). 22% do not understand what Customer Relationship Management is in an operational sense (the Same report). A 42% of compaNos cite a lack of training as the main barrier to implementation.
The outlook for Poland is not significantly different. Casbeg in its report “Customer Relationship Management Systems in Polish CompaNos 2026” estimated the average rating of the Customer Relationship Management system implemented in Poland at 3.87 out of 5In other words: not too bad. But there’s a huge amount of untapped potential. “Implemented” doesn’t mean “it works.”
The data is consistent. Customer Relationship Management as a tool isn't the problem. The problem lies in three other areas. Unfortunately, almost no one checks them BEFORE making a purchase. If you're starting from scratch and need a solid foundation—what exactly is Customer Relationship Management and what does it do?—we have a separate featured article. Here, we assume you already know.
Reason #1. You don’t have a sales process. You have smart salespeople
This is the reason no one wants to hear, because it sounds like a criticism. Nevertheless, it’s exactly why your first Customer Relationship Management failed.
Ask yourself: If your company's top salesperson were to leave today, could a new hire yese over their deals within two weeks and continue handling them in the Same way?
If the answer is “no, because Marek has his own ways,” congratulations—you’ve found the number one reason.
Customer Relationship Management is a tool for enforcement of the process. The stages in the pipeline aren’t just labels for organization. They’re your sales process, laid out as steps that everyone must follow in the Same order. “Lead → qualification → initial call → quote → negotiations → close”—that is the process. If every salesperson has their own version (“I call first, I text first, I give a quote right away”), the Customer Relationship Management has nothing to map.
Pipeline shows 14 deals. Three are true
And then Customer Relationship Management becomes what it always becomes in such a situation: digital-Excel. Field for name, field for company, field for phone number. Notes in one big bag. The pipeline shows 14 deals, but these 14 deals are in 14 different mental places. Three are in the "introduCTOry conversation", four in "almost signing", seven in "I will think about it and come back". From a Customer Relationship Management perspective, it's the Same thing, but from a reality perspective, it's chaos. This is where he comes in offer chaos in the system version, which we wrote about separately.
Why no process = no adoption (and what to do about it)
Hard evidence: Forrester says that 70% of failed Customer Relationship Management implementations are due to lack of user adoption. What does no adoption mean? The salesperson looks at Customer Relationship Management, doesn't see his work there, so he uses Excel. Because Excel FLEXIBLY reflects its flow. Customer Relationship Management doesn't reflect it because there is nothing to reflect.
Reframe: First, the process on paper. Then the tool. Not the other way around.
So it’s not about hiring a consultant for 80,000 who’ll bring you slides with a sales pyramid. It’s about something Bartosz Guzik describes in *The Funnelist* as a simple, ruthless step: The owner or sales direCTOr personally participates in sales meetings for 2–3 months. He listens. He yeses notes. It builds a process from what actually works. Only then does it hand over the process to the team.
“We don’t have three months; we need to implement the Customer Relationship Management now.” That’s the objection we hear most often. It’s understandable that it’s wearing you down. But three months of work on the process is shorter than 12 months of a failed implementation plus another six months of searching for a new vendor. The math is simple. If you cut corners in the process, you end up paying double for the implementation phase.
The whole process yeses three months. It costs nothing—except your time. And it’s the only way to get your next Customer Relationship Management up and running.
The 60-Second Test: Do You Have a Sales Process?
Indicate how many of the following statements apply to you:
- Every salesperson follows the Same stages in the sales pipeline.
- You know what percentage of deals go from the "introduCTOry conversation" to the "quotation" stage.
- We have a written document (a "sales playbook") that outlines how we guide a customer from lead to closing.
- After two weeks, a new sales representative is able to independently handle a deal through all its stages.
- Can you explain why the last five deals fell through at this particular stage?
Fewer than 3 checkmarks = you are at risk. Your next implementation will also fail because of reason number one if you don't get the process started first.
Reason #2. You implemented a tool, not a change
Most compaNos treat Customer Relationship Management implementation as an IT project. A single email from the IT department: “Starting Monday, log in here—link attached. Training is on Tuesday at 10:00 a.m. Thanks, end of message.”
This is the moment your implementation fails. You don’t know it yet. But you’ll find out in 90 days.
Customer Relationship Management implementation is a project change management, not IT. In other words: you’re changing the way people work. And changing the way people work always meets with resistance. Always. In your company, too.
A 5-link chain. All it yeses is for one link to break
Casbeg states this clearly in its 2026 report: Customer Relationship Management implementation is a five-step process. The sales direCTOr has to be on board. The board has to approve it. There has to be a budget (larger than the cost of the license, because someone has to implement it and provide training). IT has to support it. The sales team has to use it. If just one link in the chain fails, the whole project falls apart.
In practice, it’s almost always the Same thing that goes wrong: no one owns the project. The sales direCTOr “endorses” it, IT “has implemented” it, and the board “has given its approval.” Yet there isn’t a SINGLE person whose KPI is “Customer Relationship Management adoption > 80%” and whose bonus depends on whether 80% of deals are in the system 90 days after launch.
Without that person, the project is an orphan, and orphans don't last long in a corporation.
The "2-hour training" myth: why it always breaks first
42%
compaNos cites a lack of training as the #1 barrier to adoption (Salesmate 2026).
32%
salespeople spends over an hour a day manually entering data into the Customer Relationship Management.
22%
salespeople doesn't understand what Customer Relationship Management is in practical terms.
The second myth that kills implementations: “A two-hour training session is enough.” In its 2026 report, Salesmate points out that 42% of compaNos consider a lack of training to be the main barrier to adoption. This is the single biggest cause of failure.
Because Customer Relationship Management is not Excel. You understand Excel in 5 minuteses. Customer Relationship Management has 12 views, 30 fields, 8 reports, 4 object types (lead, contact, company, deal) and 6 statuses. This use it efficiently, you need 8-12 hours of work with the system PLUS an assistant for the first month who you call when "damn, where do I write this note down?"
Most compaNos do not buy it because the implementation costs PLN 8-15 thousand apart from the license. As a result, he cuts this budget first. And that's when what Casbeg calls "untapped potential" begins. Thisol is there. There are people. There is no adoption. The product found them, they didn't find the product.
Reframe: calculate the cost of unused Customer Relationship Management. A Pipedrive license for 8 traders is ~12,000. PLN per year. You also add admin time. Then 32% of the salesperson's time is spent on manual entry instead of selling. Finally, a second implementation in a year, because "it didn't work, let's try something else." You can easily spend PLN 60-80,000 a year on a tool that no one uses. A change management consultant costs less. And it gives more.
Reason #3. You have chosen Customer Relationship Management. And you needed an ecosystem
The third reason is more technical, but the consequences are the Same: people return to Excel.
Imagine a typical day of a salesperson in a Polish manufacturing company:
- Morning: leads from the web form, they go to Customer Relationship Management.
- 10:00: introduCTOry conversation, notes in Notion (because Customer Relationship Management has too small a field for notes).
- 11:00 a.m.: The salesperson calculates the quote in Excel (because the Customer Relationship Management doesn't have a calculator for 30 variants).
- 12:00 PM: Generates a PDF in PandaDoc (because the Customer Relationship Management system doesn't support electronic signatures).
- 1:00 PM: sends an offer from Gmail (because the template is in Gmail, not in the Customer Relationship Management).
- 2:00 PM: new task in Asana (because PMs aren't in the Customer Relationship Management).
- 3:00 PM: updates status in Customer Relationship Management (because management is watching).
Six systems. Five re-runs. Three chances to lose something. Each re-run yeses 30–60 seconds. Every day. Multiply that by 5 traders and 250 days a year. 3,000 hours per year spent copying data from System A to System B. That's a 1.5-full-time position where no one is making any sales.
Stack instead of ecosystem: and Excel as a winner
This model has a name. It is stack instead of ecosystem. Each tool is the best in its Categories (best-of-breed), but together they don’t form a cohesive whole. Furthermore, they’re held together by Zapier integrations, and any change in one system requires an audit in five others.
What does a salesperson do when faced with a choice between six systems or Excel? Selects Excel. The reason is simple: Excel is a single program; it has everything he needs in a single spreadsheet, and he doesn't have to remember which of the six systems contains what.
Bartosz Guzik himself shows his company’s typical stack in “The Funnelist”: Pipedrive + Woodpecker + DMSales + Vocally + EverWebinar + Make/Zapier for integration. Six tools. This is a stack deliberately chosen by a marketing specialist who has both the budget and the know-how to make it all work together. Most manufacturing compaNos have neither. They end up with a stack by chance (each department bought something different), with no common integration and no one yesing ownership.
There is an observation in the industry that sums it up well: “Customer Relationship Management is a mirror of your processes. If they’re siloed, Customer Relationship Management will just digitize the chaos.”Three years ago, the chaos was analog. Thisday, it’s digital. The tool has changed. The problem remains.
| Dimension | A stack of 5–6 systems | One ecosystem |
| Number of subscriptions | 5-6 (Customer Relationship Management + email + calculator + e-signature + PM + automation) | 1 |
| Failure points | 5–6 (each system is a potential outage) | 1 |
| Friction (page views/day) | 5-7 | 0 |
| Source of truth | 3 tools: Customer Relationship Management, Excel, Notion | 1st place |
| Time lost annually (5 salespeople) | ~3,000 hours (1.5 full-time equivalents) | ~600 hoursours |
| Probability of adoption | average (traders are going back to Excel) | high (single source of truth) |
Conclusion: fewer tools, not better ones
Reframe: Before you buy another Customer Relationship Management, ask yourself if you need fewer tools, not better ones. Six well-integrated systems are better than six systems with an “integration” label. But a single system that does 80% of what those six do is even better. Less friction = more adoption = more deals in the pipeline.
In our opinion, this is the point at which the question of a single ecosystem versus a stack arises. We discussed this separately in an article Pipedrive + PandaDoc + Asana vs. JSON Hub and there are specific numbers there. Here, the following rule is sufficient: Friction kills adoption. Adoption determines the success of implementation. Friction stems from the number of tools.
If you’re wondering more broadly where your company stands on the automation maturity scale, we explore this topic in a separate section: 5 levels of quote automation maturity.
When will the next Customer Relationship Management actually work? 7 red flags to watch out for BEFORE you sign
If you’ve already gone through one failed implementation, you now have an advantage. You know where things went wrong last time. The only question is whether you’ll end up following the Same path with a different vendor next time.
Below are 7 questions. Click on the expandable sections and check the boxes next to the ones you can answer with a YES today. If you answer YES to fewer than 5 out of 7, go back to the brief—not to the Customer Relationship Management.
Process and implementation owner (red flags #1–#3)
1. Do we have a written sales process on a piece of paper/in Miro/in a document BEFORE we choose a Customer Relationship Management?
Funnel stages. Criteria for moving from one stage to the next. KPIs for each stage. If this isn’t documented, the Customer Relationship Management has nothing to track. Without this document, you’re back to reason #1.
2. Is there ONE person responsible for the implementation? Not IT, not “everyone.”
Sales ops, RevOps, a sales direCTOr, or an external consultant. Their KPI is an adoption rate of over 80% within 90 days, and their bonus depends on that result. Without an owner, the project is left in limbo.
3. Do we have a budget for an external implementation partner in addition to the license?
Realistically, 8,000–20,00PLN 0 for a typical company with 5–15 salespeople. This isn’t an option—it’s the baseline. CompaNos that cut this budget below 30,00PLN 0 (excluding the license fee) have a 70% chance of a failed implementation.
Execution and Training (red flags #4–#5)
4. Does management enforce this rule? Is the rule “no entry in Customer Relationship Management = deal does not exist” documented in writing?
Without sanctions, salespeople revert to using Excel within 90 days. “Enforcement” isn’t a threat of termination. It’s linking the Customer Relationship Management pipeline to commission calculations, aligning the management team’s weekly review with the open system, and maintaining silence regarding deals that aren’t in the Customer Relationship Management.
5. Will salespeople receive at least 8 hours of training (not just a 2-hour crash course)?
Plus, access to the assistant for the first month and a refresh after 60 days. Salesmate 2026 identifies a lack of training as the #1 barrier to adoption (42% of compaNos). That’s why this budget isn’t being cut.
Ecosystem and Local Context (Red Flags #6–#7)
6. Does the Customer Relationship Management integrate with quoting and calculations in a single platform (or are we planning an ecosystem)?
If the quote ends up back in Excel, the Customer Relationship Management has failed. Check whether the configurator/calculator/PandaDoc/Asana have meaningful integration (not just a "API available" sticker). Even better: one ecosystem instead of six tools.
7. Have we chosen a local provider that offers onboarding and support in Polish?
Gartner 2024: CompaNos using local Customer Relationship Management systems achieve a 34% higher adoption rate than those using global solutions without cultural adaptation. Polish onboarding, Polish support, integration with Comarch/Subiekt/Symfonia, and compliance with Polish regulations (GDPR). This isn’t sentiment—it’s a fact.
These 7 questions aren’t just a courtesy checklist. In practice, they’re a readiness audit. Every “no” indicates a point where a previous implementation failed—and this one will fail too. If you’re compiling a shortlist of vendors, we have Ranking of 29 Customer Relationship Management systems for manufacturing compaNos in Poland (local and global).
4 Signs That Your Current Implementation Is Failing
- The Customer Relationship Management pipeline shows figures that no one on the board fully believes.
- Traders "update the system" once a week, on Friday afternoons, in preparation for the report.
- The Excel file with REAL deals still exists alongside it.
- The adoption rate (% of deals closed within 24 hours of contact) is below 60%.
What's next? Start with a conversation, not a purchase
If you're reading this after your first failed implementation, you've probably already received a proposal from another vendor. It likely comes with a 40-slide presentation and a promise that this time will be different.
Unfortunately, this time will be no different, because the problem wasn’t the previous vendor. The problem was the lack of a process, the lack of an implementation owner, and an excess of tools. These three issues remain the Same regardless of whether you buy Pipedrive, Salesforce, HubSpot, or build a custom solution.
But there is a way to ensure that the implementation doesn't fail. You need to make one decision BEFORE you start watching the demo: decide that this is a change management project, not a software purchase. Everything else follows from that decision. The process outlined on the sheet follows from that decision. The implementation owner follows from this decision. An ecosystem instead of a tech stack follows from this decision. This is the only entry point where the next implementation has more than a 50% chance of success.
Before you sign the second contract, Let's talk for 30 minutesuteses about your process. Not about our Customer Relationship Management. About your process. If it turns out you need a solution like ours (configurator + Customer Relationship Management + quoting + project management all in one ecosystem called JSON Hub), we’ll discuss that separately. Otherwise, you’ll receive a checklist of questions for your vendor and a list of 3 things to do BEFORE you purchase a license.
This is a conversation, not a pitch. It’s free and there are no slides.
OPTION 1 · DIAGNOSTIC CONSULTATION
Let's talk about your process, not our Customer Relationship Management
30 minutesuteses. No slides, no sales pitch. You’ll walk out with a checklist of questions for the vendor and a list of 3 things to do BEFORE you buy a license.
OPTION 2 · START FROM SCRATCH
What is Customer Relationship Management (and what it isn't)
A Pillar article for those who are just considering implementation. We show what Customer Relationship Management looks like in compaNos that actually use it.
Frequently Asked Questions About Customer Relationship Management Implementations
General and diagnostic questions
Why do most Customer Relationship Management implementations fail?
According to Forrester, 47%; according to Gartner, 50%; and according to Johnny Grow, by 2025, as many as 55% of Customer Relationship Management implementations will fail to meet their objectives. The main cause in 70% of cases is a lack of user adoption—in other words, salespeople aren’t using the system. There are three reasons for this: the absence of a sales process before the tool was purchased, the lack of an implementation owner (treating Customer Relationship Management as an IT project rather than change management), and friction resulting from using too many tools side by side.
How can you tell that our Customer Relationship Management is about to crash?
Four warning signs. The Customer Relationship Management pipeline shows numbers that no one on the executive team fully trusts. Sales reps “update the system” once a week just for the report. An Excel spreadsheet with actual deals still exists in parallel. The adoption rate (the percentage of deals entered within 24 hours of contact) is below 60%. Each of these signs means the implementation is failing. All four together mean it has already failed.
Questions about cost and choosing a provider
How much does it cost to implement a Customer Relationship Management system, excluding the license?
The actual budget consists of the license fee (ranging from 5PLN 0/user/month for Pipedrive to 500+ PLN for Salesforce Enterprise) plus implementation (8,000–20,00PLN 0 for a typical company with 5–15 salespeople) plus training (5,000–10,00PLN 0, minimum 8 hours of hands-on time with the system) plus change management for 3–6 months (time spent by the sales direCTOr or an external consultant). CompaNos that cut this budget below 30,00PLN 0 (excluding the license) have a 70% chance of a failed implementation.
Are local Customer Relationship Managements better than global ones?
According to Gartner, compaNos using local Customer Relationship Management solutions achieve a 34% higher adoption rate than those using global solutions without cultural adaptation. There are several reasons for this: Polish onboarding, Polish support, integration with Polish invoicing systems (Comarch, Subiekt, Symfonia), a Polish-language interface, and compliance with Polish regulations (GDPR). For most manufacturing compaNos with 50–500 employees, a Polish or regional Customer Relationship Management is more practical than Salesforce.
Questions about the process and implementation timeline
Will Customer Relationship Management solve our sales chaos?
No. Customer Relationship Management doesn’t solve chaos; it exposes it. If your sales process doesn’t exist (every salesperson has their own version), Customer Relationship Management will digitize that chaos instead of fixing it. First, you map out the process on paper (stages, transition criteria, KPIs), then you implement it in the Customer Relationship Management as stages in the pipeline. The reverse order (buying a Customer Relationship Management to force a process) works in only 20% of cases, most often in small compaNos with 1–2 salespeople.
A realistic timeline for a successful implementation
How long does it yese to successfully implement a Customer Relationship Management system?
Realistically, it yeses 4–6 months from the decision to full adoption. The first 2 months: mapping the sales process, writing playbooks, and selecting a vendor. In the third month, you handle the technical implementation, data migration, and pipeline configuration. The fourth and fifth months involve team training plus the parallel use of the old system and the Customer Relationship Management. It’s not until the sixth month that the old system goes offline, the Customer Relationship Management becomes the single source of truth, and you measure adoption KPIs on a weekly basis. CompaNos that promise “Customer Relationship Management ready in 4 weeks” are selling a license, not an implementation.
Editorial Note and Legal Notice. This article and the assessments of the listed Customer Relationship Management tools (Pipedrive, Salesforce, HubSpot) contained herein represent the author’s subjective opinion based on publicly available sources (Forrester Research, Gartner, Salesmate 2026, Casbeg “Customer Relationship Management Systems in Polish CompaNos 2026”) and JSON Crew’s implementation experience. This material constitutes an advertising comparison within the meaning of Article 16(3) of the Act of April 16, 1993, on Combating Unfair Competition.
With regard to the following Customer Relationship Management platforms: Each vendor provides official documentation on implementation methodology, change management, and adoption (for example, Salesforce publishes an article titled “Why Do Customer Relationship Management Projects Fail” at salesforce.com/ap/hub/CRM/why-do-CRM-projects-fail(Pipedrive and HubSpot provide their own implementation playbooks on their help pages). Our assessment focuses on the reasons behind Customer Relationship Management implementation failures as an industry-wide phenomenon (sales process, change management, systemic friction); it does not allege any specific legal violations by any of the mentioned providers and does not call into question the quality of their products.
Corrections: Please send any substantive comments, requests for corrections, or requests to update your information to marketing@jsoncrew.comWe will respond within 14 business days.
About the author. Jędrzej Siewierski. CEO and co-founder of JSON Crew. It implements product configurators and Customer Relationship Management ecosystems for manufacturing compaNos in Poland. JSON Hub (configurator + Customer Relationship Management + PM + quoting in one system) is the company's product. More about the author · LinkedIn
