What 1000 Implementations Actually Taught Us

After working through roughly 1,100 implementations, mostly in CRM and project management software, we've seen the same mistakes play out again and again. Not because teams aren't smart. But because the thinking behind the transition is usually off from the start.

Here's what we've learned.

Most businesses don't fail at choosing a CRM. They fail at everything that comes before it.

The spreadsheet trap

Spreadsheets aren't bad tools. They're just the wrong tool once your business grows past a certain point.

The problem isn't the data, it's the assumption that comes with it. A lot of teams think: "If we just move this into a CRM, we're sorted." But what you end up with is a digital version of the same broken process. Faster, maybe. But still broken.

Moving to a system like Pipedrive or Monday.com isn't a data migration exercise. It's a process redesign. And the sooner you treat it that way, the better the outcome.

Preparation is where the real work happens

The businesses that get the most out of their systems do most of the hard thinking before they touch a single setting.

That means understanding your actual workflows not how you think they work, but how they actually work. It means mapping out every step, decision point, and handoff. And it means getting the right people in the room early: sales, operations, marketing, leadership.

A tool like Miro is great for this. Get your process on a board. Make it visible. Agree on it as a team before you build anything.

Here's a pattern we see constantly in engineering and construction firms: the sales process only "starts" when a client asks for a quote. But there's a whole world of relationship-building and lead qualification that happened before that moment and it's completely invisible in the system. That's a gap. And gaps mean bad data, inconsistent stages, and reports you can't trust.

Build the process first. Then build the system around it.

The CRM won't fix it — but it will amplify it

If the process is broken, the system makes the mess more visible. If the process is clear, the system makes everything faster.

A few things that consistently derail implementations:

No shared definition of success. What does "deal won" actually mean for your business? Is it the signed contract? The deposit? The delivery? If your team has three different answers, your pipeline data is already unreliable.

Assuming it's plug-and-play. It's not. Every business needs some degree of customisation, automation, and ongoing adjustment. The out-of-the-box setup is a starting point, not a solution.

Ignoring the people side. Resistance to new systems is rarely about the system itself. It's about people feeling like something's being done to them, not with them. That's a comms and culture problem and it needs as much attention as the technical setup.

Get the right people invested

Top-down mandates don't stick. What does stick is having people across the business who genuinely believe in the system and can help others use it.

Build a small champions group. Include someone from sales, someone from ops, someone from leadership. These are the people who answer questions on the ground, flag issues early, and help the system become part of how work actually gets done.

The best champion isn't always the most senior person in the room. It's usually the most approachable the one people actually go to when they're stuck.

Regular comms, clear training, and genuine feedback loops make the difference between a system people use and a system people work around.

Design for outcomes, not features

It's easy to get distracted by what a system can do. Automations, custom fields, pipeline stages, integrations the options are endless.

The better question is: what do you actually need this system to deliver?

Start there. Map your ideal customer journey. Identify where things slow down or fall through the cracks. Then build the simplest version of the system that solves those problems.

Complexity is the enemy of adoption. The cleaner the workflow, the more people will use it  and the better the data you'll get back.

When that happens, everything improves: visibility for leadership, handoffs between teams, and reporting that actually tells you something useful.

It's never really finished

The businesses that get the most long-term value from their systems treat them as living tools, not one-time projects.

That means regular check-ins on data quality. Collecting feedback from the people using it every day. Making small adjustments as the business evolves. Keeping training fresh as the system changes.

This isn't extra work. It's what keeps the system relevant; and what keeps your team trusting it.

Where to start

If you're thinking about making the move or wondering why your current system isn't delivering  the first step isn't picking a tool. It's sitting down with your team and walking through how work actually flows through your business.

Draw it out. Find the gaps. Agree on what "done" looks like at each stage.

Then build the system around that.

That's how you get a CRM your team actually uses and results you can actually measure.

‍