CRM Implementation Partners

What a CRM implementation costs, whatever you buy

The licence is the price you see. The implementation is the price you argue about. They are different budgets, they behave completely differently, and confusing them is the most common reason a CRM project blows past what someone told the board it would cost.

Licences are simple. You pay per user per month and the bill scales with headcount in a way anyone can model in a spreadsheet.

Implementation does not work like that at all, and this is the part worth internalising before you read a single quote.

Hours, not seats

Implementation is consulting work sold in hours. The hours come from three places: how many decisions your business has to make about its own process, how bad your existing data is, and how many other systems have to be connected.

Notice what is not on that list. The number of people who will use it.

A six-person team and a forty-person team in the same industry, with the same sales process and the same mess in their spreadsheets, cost nearly the same to implement. The pipeline stages get agreed once. The layouts get built once. The data gets cleaned once. The automation gets written once. Only training scales, and training is a small line.

What actually drives the hours Process decisions how many teams have to agree on one way of selling Data condition duplicates, formats, records nobody has looked at since 2019 Systems to connect the third integration costs more than the first Not on this list: how many people will use it Which is why implementation priced per user tells you the partner has not scoped your project.
Licences scale with headcount. Implementation scales with complexity. A quote that moves when you change the seat count is pricing your budget rather than the work.

How the platforms differ

I should declare my position before this section: I implement Zoho for a living, so treat what follows as an interested party's view rather than a neutral survey. I have tried to describe the pattern rather than argue for an outcome.

Initial build cost is broadly comparable between Zoho and HubSpot. Salesforce tends to run higher, partly because its partner ecosystem is priced differently and partly because more of the work ends up as development rather than configuration.

The bigger divergence is not the build at all. It is what each change costs for the next five years.

On a configuration-led platform, a new field, a new stage or a new report is usually something your own admin can do. On a development-led one, the same request means a developer, a ticket and a release. Over five years that difference compounds into more money than the licence gap, and almost nobody models it when they are choosing.

Ask what a change costs, not what the build costs. You will buy the system once and change it for years.

Rough effort bands

These are hours, not prices, because rates vary by a factor of five or more depending on where your partner sits. A firm in New York and a firm in Chennai can quote the same 200 hours and reach very different totals, and the rate on its own tells you nothing about quality in either direction.

Project shapeEffort
Small team, clean spreadsheet data, one pipeline, no integrations40–80 hours
Replacing an existing CRM, two or three integrations120–250 hours
Several teams, custom logic, phased go-live250–450 hours
Multiple entities or currencies450+ hours

Add meaningfully to each band if your platform needs development for things another platform does with configuration.

Reading a quote

Four questions, in order of how much they reveal.

Is it broken down by phase? A single number cannot be compared, challenged or reduced. Ask for hours against discovery, configuration, migration, automation, integration and training.

Does it say what is excluded? Every proposal lists inclusions; that part is marketing. The exclusions are where change orders come from, and a partner who names theirs quickly has thought about your project.

Is the migration line specific? "Data migration, included" is not an estimate. It should reference record counts and source systems, because that is what the work depends on.

Is there support after go-live? If support starts billing the morning you go live, nobody has a financial stake in the build being right.

Where the money gets wasted

Three patterns, on every platform I have seen.

Paying to migrate data nobody will ever open. Upgrading an edition across the entire headcount to unlock one feature a workaround would have covered. And cutting training, which is the easiest line to delete from a quote and the most expensive to have deleted, because an unused CRM costs you the licences, the implementation and the time.

Questions I get asked

Can we avoid a partner entirely?

If you are a small team with clean data, one pipeline and nothing to integrate, yes, on any of the major platforms. Their own documentation will get you there and the money is better spent training your team properly. The value of a partner rises steeply with data mess, connected systems, and internal disagreement about process.

Fixed price or hourly?

Fixed price once scope is genuinely defined, which usually means after a short paid discovery. A fixed price agreed before anyone has seen your data has the partner's uncertainty priced into it, and you pay that premium whether or not the risk appears.

How much should we budget beyond the first year?

Something ongoing, because the business changes: new products, new teams, new reports. How much depends almost entirely on how configuration-led your platform is. This is the question to ask before you choose, not after.

HK

Harikrishnan

CRM implementation consultant, based in Chennai and working with clients remotely worldwide. More than ten years and 600+ implementations. I specialise in Zoho, which is the bias to keep in mind on any page here that compares platforms.

Send me a quote you have received and I will tell you what I think of the scope, whichever platform it is for: hari@flowpeakconsulting.com

Disclosure: This site is written and operated by Flowpeak Consulting, which sells Zoho implementation work and does not sell Salesforce or HubSpot work. Read the platform comparisons with that in mind.

Keep reading

Why CRM projects fail

Almost never the software. The four failure patterns that repeat on every platform.

Read the guide →

Zoho CRM specifically

The same question answered for Zoho, with effort bands and licence notes.

Read the guide →

Choosing a partner

The five questions that separate firms, and the answers that should end the conversation.

Read the guide →