Develpreneur: Become a Better Developer and Entrepreneur ERP and CRM Implementation: Why Most Projects Fail Before They Start
Most ERP and CRM implementation efforts don't fail during execution—they fail before the project even begins.
In this episode, the hosts sit down with Dustin Domerese, who brings nearly two decades of experience in SAP and Microsoft consulting. Early in the conversation, a clear pattern emerges: companies jump into ERP and CRM implementation without fully understanding what these systems actually are—or what they require from the business.
If you've ever seen a project spiral out of control, take years instead of months, or fail to deliver value after launch, the root cause usually starts here.
About Dustin DomereseDustin Domerese is a recognized thought leader in the Microsoft ecosystem, specializing in CRM, ERP, and software transformation. He helps organizations recover failing initiatives and build scalable systems that deliver real results.
Drawing on experience with Microsoft, Barclays, EMC2, HP, and multiple successful ventures, Dustin brings a proven track record of guiding businesses through complex technology decisions.
What ERP and CRM Actually Mean (And Why That Matters)One of the first breakdowns in ERP and CRM implementation is a simple one: misunderstanding the tools.
CRM—Customer Relationship Management—started as little more than contact tracking. Sales teams logged calls, tracked accounts, and managed pipelines. Over time, that expanded into something much broader. Today's CRM platforms handle marketing automation, customer service interactions, and full lifecycle engagement.
ERP is even more misunderstood.
Most companies think ERP is just accounting—general ledger, invoicing, maybe some reporting. But ERP (Enterprise Resource Planning) goes much deeper. It includes supply chain management, inventory, manufacturing processes, fulfillment, and operational workflows.
The distinction matters because ERP and CRM implementation isn't just installing software—it's reshaping how a business operates.
And that's where most companies get into trouble.
Why ERP and CRM Implementation Projects Fail So OftenThe numbers behind these projects are hard to ignore:
- 66% of projects fail
- 17% threaten the survival of the business
- 70% of those that launch fail to deliver expected outcomes
These aren't edge cases—they're the norm.
The instinct is to blame the software. But that's not where the problem starts.
Callout:
ERP and CRM implementation doesn't fix broken processes—it exposes them. If your workflows are unclear or inconsistent, the system will surface those issues immediately.
Companies often assume that software will improve efficiency automatically. In reality, systems introduce structure. If your business doesn't already operate with clarity, that structure creates friction instead of improvement.
The SaaS Illusion: Easy Setup, Difficult RealityModern SaaS platforms have changed the landscape completely.
Today, a company can spin up an ERP or CRM system in minutes. Platforms like Microsoft, Salesforce, and NetSuite make it incredibly easy to get started. From the outside, it feels like progress—like the business is leveling up.
But there's a hidden problem.
Callout:
Just because you can launch an ERP or CRM system doesn't mean your organization is ready to operate it.
Smaller companies now have access to tools that used to be reserved for large enterprises. They can deliver polished customer experiences, manage complex operations, and automate workflows.
But access to tools doesn't equal readiness.
This creates a gap between what the software can do and what the business is capable of supporting. The result is frustration, poor adoption, and systems that never deliver on their promise.
The Process Problem Most Companies IgnoreOne of the biggest misconceptions in ERP and CRM implementation is the belief that processes are already defined.
Leadership teams often assume their workflows are clear and consistent. But when you actually examine how work gets done, the reality looks very different.
Different employees handle the same tasks in different ways. Critical workflows rely on personal habits or undocumented steps. Reporting often depends on spreadsheets owned by individuals.
In some cases, entire business functions are held together by workarounds.
This becomes a major issue when implementing structured systems.
Callout:
If you don't understand your current processes, you're not ready to systematize them.
ERP and CRM systems require consistency. Without it, they don't improve operations—they expose how inconsistent those operations really are.
When Software Becomes a Magnifying GlassA useful way to think about ERP and CRM implementation is as a magnifier.
The parts of your business that work well will continue to work well. Experienced employees will still find ways to get their job done. But the weak areas—the unclear processes, the inconsistent decisions, the gaps—become impossible to ignore.
Sales is a perfect example.
Most organizations believe they have a defined sales process. But when you talk to individual salespeople, each one follows their own approach. What leadership sees as a "standard process" is often just a loose guideline.
When a CRM system is introduced, that inconsistency becomes a problem overnight.
The Readiness Gap No One Talks AboutOne of the most important insights from this part of the conversation is the gap between tool availability and organizational maturity.
Software vendors are incredibly good at building and selling products. They continuously add features, improve capabilities, and expand access to new markets.
But they don't control how those systems are adopted.
That responsibility falls on the business—and many organizations simply aren't ready.
This leads to two common outcomes:
- Companies adopt systems too early and struggle to keep up
- Companies delay adoption too long and become stuck in manual workarounds
Neither path leads to success.
The Real Starting Point for ERP and CRM ImplementationThe biggest takeaway from this part of the conversation is simple:
ERP and CRM implementation should not start with software.
It should start with understanding.
Before evaluating tools, businesses need to answer basic questions:
- How do we actually operate today?
- Where are our processes inconsistent?
- What problems are we trying to solve?
Without those answers, even the best system will struggle to deliver value.
Final ThoughtsERP and CRM implementation isn't just a technical project—it's a business transformation.
The tools themselves are powerful, but they assume a level of clarity, consistency, and alignment that many organizations haven't achieved yet.
That's why so many projects fail before they even begin.
The companies that succeed aren't the ones with the best software—they're the ones that understand their business first.
Simple TakeawayBefore starting an ERP and CRM implementation, don't ask:
"What system should we buy?"
Ask:
"Are we ready for one?"
Stay Connected: Join the Developreneur Community👉 Subscribe to Building Better Developers for more conversations on momentum, leadership, and growth. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development.
Additional Resources