Zoho implementation and configuration: why doing it yourself usually costs more
You create a free trial account, import a list of contacts, set up a few fields and within a day you have something that works.
Zoho is easy to start with, and that is exactly the problem
That is no illusion: Zoho is deliberately built that way, and for a small team that only needs a place to keep track of customers, it is often enough.
The problem starts eighteen months later. By then three more departments have joined, the same customers are in the system in two different ways, nobody can explain why certain fields exist, and it turns out that the report management wants can't be produced because the data was never captured that way. At that point, "quickly setting it up again" is no longer an afternoon's work but a project with data migration and users who have to unlearn their habits.
So the question is not whether you can get Zoho working yourself. You can. The question is whether what you build will still be right in three years' time.
What doing it yourself really costs
The comparison people make is: licence costs versus licence costs plus implementation costs. That is the wrong sum, because the biggest cost item isn't in it.
The five decisions you make at the start and can hardly reverse later
This is the heart of the argument. An implementation consists of hundreds of small choices and a handful of big ones. You make the big ones in week one, usually without knowing they are big choices.
-
Your data model
How do accounts, contacts, locations, contracts, products and projects relate to each other? Do you work with one account per company or with branches underneath it? This determines what you can and cannot report on in two years' time. Changing it afterwards means data migration and rebuilding reports and automations.
-
Your data centre region
When you create your Zoho account, you choose the region where your data is stored. For Dutch organisations the EU region is almost always the right choice, especially with GDPR requirements, a data processing agreement and sector-specific obligations in play. Once you are in the wrong region, moving is a migration project, not a setting.
-
Your licence structure
Individual apps, CRM Plus or Zoho One, and with Zoho One the choice between licences for all employees or only for active users. The tipping point between them depends on how many of your staff actually use the software, and that is something you work out properly once instead of finding out afterwards.
-
Your roles and permissions model
Who sees which customers, which amounts, which files? In a small team that seems irrelevant; with growth, several branches or sensitive data it becomes decisive. A permissions model laid over existing data afterwards always brings surprises.
Faster, better and cheaper in the end
| Working it out yourself | With a partner | |
|---|---|---|
| Lead time | Months, spread over evenings and spare moments | Weeks, focused |
| Effort from your own people | High and invisible | Limited and planned |
| Data model | Grows as you go | Designed for your reporting questions |
| Licence choice | Gut feeling | Calculated |
| Use of functionality | A fraction | Whatever is in your licence |
| Integrations | Often postponed | Part of the design |
| Adoption | Dependent on one enthusiast | Training and guidance planned in |
| Chance of a rebuild within two years | Considerable | Small |
| Continuity | Gone when that one colleague leaves | Documented and transferable |
So the "cheaper" in the heading does not refer to the invoice in month one. That is lower if you do it yourself. It refers to the total cost over three years, including your own people's hours, the wrong licences, the rebuild and the return you miss out on with a system that isn't used properly.
Why larger organisations need different guidance
With ten users, an implementation is mainly configuration work. From a few dozen users onwards the nature of the work changes, and that is where many providers drop out.
We run this kind of project with our own development department on hand, which means we don't have to say no to that one question that falls outside the standard. Configuration where possible, low-code where it fits, and custom development where it is really needed: from one team and with one point of contact.
Why international operations need extra attention
If you work from several countries, with several entities or with foreign branches, questions come up that don't play a role in a national implementation.
-
One environment or several?
The choice between all entities in one Zoho organisation with separate permissions, or separate environments per entity, is far-reaching and hard to reverse. It depends on how centrally you steer, how much data needs to be shared and which local requirements apply.
-
Data location per entity
Your data centre region is one choice per organisation. If you have entities with different data storage requirements, you need to include that in the design instead of running into it later.
-
Currencies, languages and time zones
Multiple currencies with exchange rate management, an interface and communication templates per language, and reports that are correct across time zones. That can be set up, but not as an afterthought.
-
Local tax and legal requirements
Invoicing obligations, VAT rules and retention periods differ per country. That mainly affects the integration with your accounting, where you need to determine per entity where a transaction lands.
-
Roll-out across countries
An implementation in the Netherlands and Belgium at the same time is something else than two implementations one after the other. You need local key users, training in the right language and a roll-out order that takes into account who learns from whom.
-
Support that fits
Your French or German colleagues need to be able to get help without everything going through head office. We work in Dutch and English, and tailor our guidance to the countries where you operate.
The implementation had a clear plan and we always knew where we stood. Our team worked with the new system from day one.
How we approach an implementation
What you keep doing yourself afterwards
This is part of it, because it determines whether the investment pays off. Day-to-day management (fields, reports, users, small workflow changes) should sit with your organisation. Zoho is well suited to that, and we set it up so that it can.
What we keep doing is the work you need us for: integrations, bigger extensions, new apps, custom development, and thinking along at the moments when your environment needs to take the next step. A partner who makes you dependent on them for every small request serves their own revenue, not your organisation.
The time you save is not the reason
Working it out yourself is not impossible and it isn't foolish. It is just rarely the cheapest route, because the most expensive mistakes in a Zoho implementation are not technical but structural, and because you only see them at the moment you are least able to fix them.
What you buy with a partner is not implementation capacity but the five decisions on this page, right first time. After that, the rest is a lot simpler than you think.
Frequently asked questions about implementing Zoho
-
Technically, yes. The question is whether what you build will still be right in three years' time. The most expensive mistakes are not in the configuration but in a handful of decisions you make in week one: your data model, your data centre region, your licence structure, your permissions model and the choice of which app runs which process. Those can only be reversed afterwards with a migration project.
-
That depends on the number of apps, users and integrations and the size of your data migration. A well-defined CRM implementation for one team with a limited migration takes a few weeks; a company-wide roll-out with several departments, ERP integrations and entities in several countries runs to months. Alongside licences, always budget for implementation, integrations, data migration and training, and press any provider that only talks about licence prices on those items.
-
For a first well-defined step, for example CRM for your sales team, a few weeks is realistic. A complete environment with sales, service, marketing, projects and integrations is built up in phases over months. We deliberately work in phases: a working first version delivers a return sooner than one big delivery where everything is new at once.
-
If you choose so, yes. Zoho offers an EU data centre region, and for Dutch organisations that is almost always the right choice because of the GDPR and sector-specific requirements. Important: you choose that region when you create your account. Switching afterwards is a migration project, not a setting. So this is one of the decisions you want to get right in week one.
-
Yes, and that is a large part of our work. We start with an audit: what is there, what is being used, where the pain is and what the underlying cause is. Sometimes it is a matter of reconfiguring within the existing environment, sometimes a partial rebuild is wiser. We will tell you honestly, including what it costs.
-
Yes. That involves specific choices: one environment with separate permissions or separate environments per entity, the data centre region, multiple currencies and languages, local tax requirements and the roll-out order across countries. You make those choices in advance, because they are hard to revise later. We work in Dutch and English and tailor our guidance to the countries where you operate.
-
Not for day-to-day management. We set up the environment so that your own team can adjust fields, reports, users and small workflow changes themselves, and we train key users to do that. For integrations, bigger extensions and custom development, we are there when you need us. A partner who makes you come back for every small request serves their own revenue.
-
That depends on how many apps you use and how many of your staff work with them. Individual apps are good value for one or two products; from around three apps a bundle such as CRM Plus becomes interesting, and for company-wide use Zoho One. With Zoho One there is also an important distinction between licences for all employees on the payroll and licences for active users only. That tipping point is something you work out properly once with your own numbers.
Already running into problems, or just getting started?
Mobile XL is a Zoho partner with fifteen years of experience, its own development team and offices in Geleen and Utrecht.