Forty apps included. Four in use.
Zoho One is genuinely good value until somebody switches on twenty apps because they came free. Every active one is another place a customer record can quietly disagree.
Thirty minutes · no predetermined package
The first one usually is the whole engagement.
Most Zoho work is deciding what to switch off, not what to switch on.
Fewer apps, used properly
Decide the system of record, switch off what is not used, and make the remaining apps agree. Usually the whole engagement.
Build the gap properly
Custom applications inside the estate, written to be maintained rather than assembled once and abandoned.
Connect what is elsewhere
Zoho stays, and the systems it does not talk to are connected properly rather than through a chain of Flows.
Not all of it
Rarely the whole estate. Usually one domain — the sales floor, or the customer-facing side — where the model does not fit.
What a sprawling Zoho estate feels like from inside.
Zoho One was bought for the price, and four of the forty apps are actually in use.
Two apps hold the same customer and neither is authoritative.
A Deluge script does something important and one person understands it.
Flow was set up by a partner who has since disappeared.
Reporting stops at the boundary of one app, and the question spans three.
Creator was used to build the thing CRM could not model, and now nobody maintains it.
Six questions before adding another app.
The second one is usually answered with two names, which is the finding.
Five stages, and the audit comes first.
Audit the estate
the findingsEvery active app, every Deluge script, every Flow, and what depends on each. Written up whether or not we do the work.
Name the system of record
the ruleOne app authoritative per entity. Everything else reads. This decision resolves most of the disagreements on its own.
Switch off what is unused
simplerDeactivating an app is free and removes a place data can drift. Most estates lose a third of their surface here.
Rewrite the fragile parts
maintainableDeluge and Flow logic documented, refactored and made legible to somebody other than its author.
Hand over the map
transferableWhat each app is for, what it owns, and what breaks if it changes. The absence of this is how estates get here.
The apps differ. The disagreement does not.
Professional services
Projects, timesheets and invoicing across three apps that each hold part of the client.
Retail and e-commerce
Inventory, Commerce and Books with stock counts that diverge quietly.
Manufacturing and distribution
Quote-to-order across CRM and Inventory, usually with Creator filling the gaps.
Financial services
Compliance and retention requirements the bundle was not designed to satisfy.
What people ask about Zoho consulting and implementation.
What does a Zoho consultant do?
Decides which apps you actually need, makes them agree about the customer, and documents the automation. Most engagements reduce the estate rather than expand it.
What is Zoho One and is it worth it?
A bundle of around forty apps for a per-user price. It is excellent value if you use six and a liability if you switch on twenty, because every active app is somewhere data can diverge.
Do we need a Zoho implementation partner?
For a straightforward CRM rollout, often not. For a multi-app estate with Deluge and Flow, the value is in the modelling decisions rather than the configuration.
What is Deluge and why does it become a problem?
Zoho's scripting language. It is capable, quick to write, and easy to leave undocumented. Undocumented Deluge is the single most common finding in an inherited estate.
Should we use Zoho Creator or a custom application?
Creator when the gap is a form and a workflow inside the estate. A custom application when it needs to be fast, integrated outward, or maintained by engineers.
How does Zoho compare with Salesforce or HubSpot?
Cheaper per seat and broader in scope, with a smaller consultant market and shallower object modelling. The trade is breadth against depth.
Can you take over a Zoho estate someone else built?
Yes, and it is most of what we are asked to do. It starts with reading every Flow and Deluge script and writing down what nobody documented.
What is the most common Zoho mistake?
Switching on apps because they are included. Every active app is another place a customer record can exist, and nothing forces them to agree.
How do you decide the system of record in Zoho?
Per entity, not per app. CRM usually owns the customer, Books owns the invoice, Desk owns the ticket — and everything else reads rather than writes.
Can Zoho integrate with systems outside the estate?
Yes, through its APIs. Flow is fine for simple triggers and a poor foundation for anything that has to be reliable or auditable.
What does Zoho implementation cost?
It scales with the number of apps and the amount of Deluge, not with user count. A single-app rollout and a full estate consolidation are very different projects.
Do you take commission from Zoho?
No. No commission, referral fee or partner margin on any software we recommend, which is what lets us tell you to switch apps off.