What CRM Implementation Actually Costs

Why Company Size Is the Wrong Thing to Quote On

Most quotes get built off headcount or contact volume, and both are close to irrelevant.

Moving eighteen thousand contacts is barely harder than moving eight hundred. It is the same export, the same mapping, the same import. The row count changes almost nothing about the effort.

What actually varies is how tangled the setup is. A company with two thousand contacts, six pipelines, forty automations, and three systems holding customer data is a much bigger job than one with twenty thousand contacts, one pipeline, and four automations.

So when a quote arrives after a single question about your list size, you are being priced on the easy part. The real number shows up later, usually as a change order.

What the Ranges Look Like

Rough bands, and they vary by market, but this is the shape of it.

A simple move. Contacts and companies only, one pipeline, a handful of automations, clean data, no history needed. Low thousands. Some capable people do this in a week.

A typical build. Contacts plus deals with owners, two or three pipelines rebuilt, ten to twenty automations recreated, and a real conversation about process. Mid five figures is common, and this is where most $1M to $5M companies land.

A complex rebuild. Multiple source systems, deal history required, email archiving, heavy automation, several teams with different processes. Upper five figures and occasionally beyond.

The gap between the first and third is not company size. It is how much of your operation has accumulated inside the old system.

The Costs Nobody Puts in the Quote

Three of them, and together they often exceed the invoice.

Your team's time. Somebody has to answer questions about how the process actually works, and it has to be someone who knows. Budget a few hours a week from your key people. This is not optional and it is the most common reason builds slip.

The overlap period. You will run both systems briefly. That means two subscriptions for a month and a team splitting attention across both, which is genuinely disruptive for a few weeks.

Adoption. The build ending is not the same as the system working. If nobody drives the new habits for the first two months, you have bought an expensive database. This is the cost that most often turns a good build into a wasted one.

None of these appear on a quote. All of them are real, and the last one decides whether the money was well spent.

Where Software Savings Fit

Moving from a per-seat enterprise platform to something lighter can cut a monthly bill substantially, and for some companies that alone justifies the project.

The useful way to frame it is not as a saving but as a reallocation. One client took their software spend down and put the difference into building the system properly. They were not adding an expense to the budget, they were moving one. That framing is what got it approved.

But be careful with the maths. If you move to a cheaper platform and keep the same broken process, you have paid less for the same problem, and you have also spent a month migrating.

Savings are what can fund the build. They are not the reason to do it.

When Not to Spend the Money

Sometimes the honest answer is that this is not your problem.

If your team avoids the CRM, a migration will not fix that. They avoid it because it asks for input and returns nothing, and that is true on any platform. Fix the process where you are and save the budget.

If your data is a mess, cleaning it in place is cheaper than cleaning it as part of a move.

If nobody has defined your pipeline stages, no tool can reflect a process that does not exist. That work costs a whiteboard and two hours.

A cleanup inside your existing platform is frequently the better answer, and it is a fraction of the cost. We say that as people who get paid to run migrations.

How to Tell a Real Quote From a Guess

You can usually tell inside the first conversation.

A real quote comes after questions. How many pipelines do you run. Do deals need their values and owners carried across. What other systems hold customer data. How many live automations do you have. What does your team do differently once this exists.

A guess comes after one question, usually about contact count, and arrives the same day.

Ask any prospective partner what happens if the scope turns out to be bigger than expected. Someone who has done this will have a clear answer, because it happens. Someone who has not will tell you it will be fine.

Ask them what does not transfer. If they do not mention email history unprompted, they have not run a migration.

And ask what they would do if, halfway through, it became clear you did not need the migration at all. The answer tells you whether they are selling a project or solving a problem.

Our own CRM Growth Sprint starts at $7,500 and gets scoped before the clock starts, precisely so the number is settled before anything moves.

Step one. Count your pipelines, your live automations, and every separate system holding customer data. Those three numbers do more to set your price than your headcount does.

Step two. Decide whether you need deal history and email archive, or whether a clean start is genuinely fine. This single decision can halve the scope.

Step three. Add up your current stack cost across every tool touching customer data. That is the number a platform change actually affects.

Step four. Get two quotes and compare the questions they asked, not just the numbers they gave.

Step five. Before you sign anything, ask what happens to your team's time during the build. If nobody has raised that, it has not been planned for.