CRM Implementation Partners

How long a Zoho implementation really takes

There are two numbers in every project and people confuse them constantly. "120 hours" is one. "Three weeks" is another. They are not the same claim and the gap between them is almost entirely time spent waiting on the client.

So when you ask a partner how long it will take, ask for both numbers, and ask what they need from you to hold the calendar date. A good answer sounds like: eleven weeks, assuming we get the data export in week one and two testers in week eight.

What the partner quotes 120 hours of effort all of it billable work What it looks like on your calendar 11 weeks waiting on the export waiting on a decision waiting on testers
Orange is work. Pale is your side of the project. The effort estimate never changes; the calendar one does, and almost all of the difference sits in those three gaps.

Rough timings by project shape

ShapeCalendarWhat sets the pace
Under 10 users, spreadsheet data, one pipeline2–4 weeksConfiguration and training, little else
10 to 50 users, coming off another CRM6–10 weeksCleaning data, mapping fields, test imports
50 to 200 users, several teams, a few integrations10–16 weeksGetting teams to agree on one process
Multiple entities or countries3–6 monthsTax, currency, approval cycles
Adding Books, People or Inventory afterwards3–6 weeks eachCross-app data and process design

Where the weeks go

In a ten-week mid-market project the shape is usually something like this. Weeks one and two are discovery: mapping how you actually sell and writing it down. Compressing this phase is the most expensive saving available, and clients ask for it constantly.

Weeks two to five run configuration and data in parallel. Data is where the overrun lives. Weeks five to seven are automation and integrations, and each connected system adds real time, not token time.

Weeks seven to nine are testing and training, which needs your people free. This is where projects stall quietly, because nothing visibly breaks. It just stops moving. Weeks nine and ten are go-live and the fortnight afterwards when things break and someone has to be there.

Nothing in a CRM project fails loudly. It stalls, in testing, while everyone is busy.

What actually makes projects late

Dirty data, mostly. Nobody can size the cleanup until they have seen the export, so ask for a re-estimate once your partner has looked at the real file. A quote given before that is a placeholder.

After that, undecided process. If your sales teams work differently and nobody has ruled on whose way wins, your partner becomes a mediator, and mediation is slow as well as expensive.

Then testers. Testing gets scheduled, then quietly skipped because everyone has a day job. Name two people at kickoff and put the hours in their calendar then, not in week eight.

And integrations without a connector. A ready-made one is a day of work. A custom build against an in-house system is a different project wearing the same name.

Two weeks: when it's real

It is a genuine timeline for a small team with one pipeline, clean data in a spreadsheet, and nothing to integrate. Partners who do a lot of these run them reliably and there is nothing suspicious about the number.

What two weeks cannot absorb is data cleanup, several connected systems, or a process nobody has agreed. If you are quoted two weeks and your project has any of those in it, ask which phase has been compressed. It is nearly always discovery or training, and both reappear later as rework.

Questions I get asked

Phased or everything at once?

Phased. Core CRM live first, then integrations, then the heavier automation. Each phase leaves you with a working system and a natural exit point, and the later phases get specified far better because by then people have opinions based on use rather than imagination.

How much of our time does it take?

A few hours a week from one internal owner, plus two people for testing in the final fortnight. Projects where the client goes quiet for three weeks come back longer and more expensive. That is not a threat, it is just how the arithmetic works.

What happens if it overruns?

Depends entirely on whether you have a fixed price against a written scope. With one, an overrun is the partner's problem unless scope changed. Without one, it is yours. This is the practical reason the scope document matters more than the price.

HK

Harikrishnan

Zoho consultant at Flowpeak Consulting in Chennai, working with clients remotely worldwide. More than ten years in the Zoho ecosystem and over 600 implementations across CRM, Books, Inventory, Creator, People and Payroll.

Got a timeline in a proposal you are unsure about? Send it over: hari@flowpeakconsulting.com

Disclosure: This site is written and operated by Flowpeak Consulting, which sells Zoho implementation work. Weigh the advice accordingly.

Keep reading

What it costs

How the hours are built, and why per-user pricing should make you suspicious.

Read the guide →

The six phases

What happens in a Zoho CRM build, in order, and where most of them come unstuck.

Read the guide →

Migrating to Zoho CRM

What to move, what to leave behind, and the things that quietly break on import.

Read the guide →