It comes up in nearly every first conversation. Someone has seen Zoho One, done the arithmetic on buying four products separately, and cannot tell whether the bundle is a bargain or an over-commitment. There is a real answer, and it does not depend on taste. It depends on three things you can check in an afternoon.
Start with processes, not apps
The most common mistake is to begin with a shopping list. Someone writes down CRM, Books, People, Desk, and then tries to price it. Start instead with the processes you actually intend to change in the next twelve months: how a lead becomes a customer, how an invoice gets raised, how a new joiner is onboarded, how a field job gets scheduled.
Processes map onto products cleanly. Wish lists do not. Half the apps on a typical shopping list turn out to have no owner, no process behind them and no chance of adoption, and paying for those is what makes a bundle look expensive in year two.
When Zoho One tends to win
Zoho One earns its keep when the change is organisation-wide rather than departmental. If sales, finance, HR and operations are all moving at once, the bundle usually costs less than the same apps bought individually, and you get one identity layer, one admin console and one set of users across everything.
It also wins when you cannot yet name every app you will need. Teams discover requirements as they go, and with One they can pick up an app and try it without a procurement cycle each time. That freedom is worth real money to an organisation in the middle of a change, and it is genuinely hard to price.
The thing to check carefully is the licensing model. Zoho offers both an all-employee arrangement and a flexible-user one, at different per-user rates. If you have three hundred employees and thirty of them will ever log in, that distinction decides the whole question. Confirm the current terms with Zoho before you build a business case on them.
When a shorter list tends to win
Buying two or three products outright is usually right when the need is concentrated. One team, one clear process, and no plan for the rest of the company to follow within the year. In that shape a bundle is mostly shelfware and you are better off buying well in one place.
It is also the right answer when you need depth rather than breadth. Editions matter more than app names: the edition of a product included in a bundle is not always the edition that carries the one feature your process depends on. Check the specific capability against the specific edition, not the logo.
And it is right when you are keeping something you already run. Plenty of our clients have an ERP nobody is replacing, or an industry system that is the heart of the business. In those cases Zoho covers a slice and integrates with the rest, and buying an org-wide bundle for a slice makes little sense.
When the answer is to build
Some processes have no standard product because they are genuinely yours. Dealer networks, field inspections, lending workflows, bespoke manufacturing flows: the object model is particular to your business, and no off-the-shelf app models it without violence. Creator exists for exactly this, and it is the product we have built with most.
The trap runs the other way too. Building a CRM in Creator because the standard one is eighty per cent right is a decision people regret in year two, when they are maintaining something a product team would have maintained for them. Build the part that differentiates you. Buy the part that does not.
Most real systems are a mix
In practice the question is rarely either-or. A typical platform we deliver is standard products for the standard parts — CRM for the pipeline, Books for the finance, People for the team — with a Creator app carrying the one process that makes the business what it is, and integrations out to whatever the client is keeping. Whether that sits inside a bundle or a shorter list is a licensing decision made after the architecture, not before it.
Five checks worth running first
These are the questions we work through during discovery, and you can answer most of them yourself before speaking to anyone.
- List the processes changing in the next twelve months, and name an owner for each. Anything without an owner comes off the list.
- Count the people who will genuinely log in, against total headcount. The gap between those two numbers drives the licensing answer more than anything else.
- For each must-have feature, check the edition that carries it rather than the product name.
- Ask what happens in year two. If three more departments are likely to follow, price for that rather than for today.
- Separate what is distinctive about your business from what is ordinary. The distinctive part is a build. The ordinary part is a product.
Working through this now? Send us the processes and rough headcount and we will come back with a view — including when the answer is fewer products than you expected.