Choosing a Zoho implementation partner
I am a Zoho partner, so take this page with the appropriate amount of salt. I have written it the way I would want it written if I were the one buying, which means some of the criteria below are ones my own firm would have to answer for.
The questions that actually separate partners are not about Zoho. Everyone who has been doing this a while knows the product. What varies is who does the work, what happens when something breaks, and whether the scope document is specific enough to argue with.
Who is actually doing the work
The person in the sales conversation is frequently not the person who builds your system. That is not inherently wrong, large firms work that way for good reasons, but you should know before you sign rather than discover it in week two.
Ask for the name of the lead consultant and a short conversation with them. If that is declined, or if the answer is a team rather than a person, treat it as information. Someone has to own your project and be reachable; a rotating pool is how details get dropped between people.
What the scope document excludes
Any proposal will tell you what is included. The useful question is the inverse: what is specifically not in this, and what would it cost to add?
The usual suspects are data cleanup beyond a stated number of records, integrations beyond a named list, training sessions beyond a count, and post-go-live support beyond a window. A partner who can name their exclusions quickly has thought about them. One who says everything is included either has not read your requirements or will be issuing change orders later.
What happens the week after go-live
Things will break. The question is whether anyone is contractually obliged to care.
You want to know the response time, the channel, who is on the other end, and how long the included period runs. Two weeks of close support after go-live is a reasonable ask. After that, a monthly retainer or a block of hours is normal and usually worth having for the first quarter. Be slightly wary of a partner who waves this away as unnecessary, because it suggests they have not been present for many go-lives.
A reference you choose, not one they choose
Every partner has two or three references ready. Those are real but curated. Ask instead for a client in your industry, at roughly your size, who went live in the last year. If that does not exist, ask for the closest match and ask what made it different from yours.
When you get the call, ask the reference one specific question: what went wrong, and how was it handled. Every project has something. A reference who says nothing went wrong either did not notice or is not being candid, and either way the answer tells you little.
The tier question
Zoho's partner tiers reflect sales volume and certification counts. They tell you a firm is established. They do not tell you whether the consultant assigned to your project has built anything resembling your business before.
What I would weigh more heavily: have they worked in your industry, can they describe a problem specific to it without being prompted, and do they ask you questions in the sales conversation that you have not been asked before. That last one is the best signal available, because it means they are thinking about your business rather than reciting their deck.
Fixed price or hourly
For a first implementation, fixed price against a detailed written scope is usually safer. An overrun becomes the partner's problem rather than yours, provided the scope was specific enough that both sides agree what changed.
That caveat is doing a lot of work. A fixed price against a vague scope is not protection, it is a disagreement scheduled for later. If the scope document is two pages of bullet points, ask for the detailed version before you compare prices between partners, because you are otherwise comparing numbers attached to different amounts of work.
For ongoing changes after go-live, hourly or a retainer makes more sense, because nobody can specify in advance what you will want to adjust once the system is live.
Answers that should end the conversation
A quote given without looking at your data. Nobody can size data cleanup without seeing the export, so a firm number before that point is a guess dressed as a commitment.
Implementation priced per user. Your user count does not determine how much configuration work exists. Pricing that way means pricing your budget rather than the job.
A refusal to put the scope in writing, or a reluctance to name what is excluded. Both suggest the gaps are intentional.
And a promise of a specific business outcome, a revenue increase or a productivity gain by a particular percentage. Nobody can honestly promise that, because it depends on whether your team uses the system, which is mostly in your hands rather than theirs.
Questions I get asked
Local or remote?
Implementation work is remote whichever you pick, so geography matters less than time zone overlap. Aim for three or four hours of shared working day, particularly through testing and go-live when you need quick back and forth. A partner twelve hours out can still do good work, but every question costs a day.
How many quotes should I get?
Three is enough. More than that and you spend more time comparing than the difference is worth. Make sure all three are pricing the same scope, which usually means writing your requirements down yourself first rather than letting each partner define them differently.
Can I switch partners mid-project?
You can, and it is not rare, but it is expensive. The new partner has to learn what was built and why, and documentation is usually thin. If you are considering it, ask for a handover document and the admin credentials before the relationship ends rather than after.
Disclosure: This site is written and operated by Flowpeak Consulting, which sells Zoho implementation work. This page is advice on choosing between firms like mine, so weigh it accordingly.
Keep reading
What the work involves
The phases of a Zoho CRM build, and where they come unstuck.
Read the guide →