The Renewal That Nobody Questions
Zoho One gets bought for a good reason. A business is paying for a CRM, a helpdesk, a project tool, a document signing service and three other subscriptions, somebody adds up the total, and a single suite that covers all of it costs less than the sum of the parts.
The consolidation happens. The saving is real. And then, in most businesses, the project ends, because the applications that were replacing something specific got implemented, and the rest of the suite sat there.
Two years later the renewal arrives. Nobody questions it, because the original logic still holds and because questioning it would require knowing what is actually being used, which nobody does. The business continues paying for a broad suite and running a narrow part of it.
This article is about closing that gap. It covers why this is not the seat-trimming exercise most licence reviews are, how to audit what you own against what you use, the shadow software that often survives the consolidation, how to decide what to switch on next, and what makes adoption stick. It is written for CFOs, IT managers and founders: the people who sign the renewal.
Why This Is Not a Seat-Count Problem
Worth establishing first, because it changes the entire exercise and most software licence reviews start in the wrong place.
Zoho’s own pricing page for Zoho One lists all-employee pricing, charged per employee per month billed annually, and states that you must purchase a licence for all employees. The same page also lists a separate Flexible User Pricing plan, licensed for any number of users, so what follows applies if all-employee pricing is the plan you are on.
That has a direct consequence. The usual licence optimisation playbook (find the dormant accounts, close the leavers, right-size the tiers) does not apply in the same way. Under all-employee pricing you are not buying seats for the people who use the software; you are buying for the organisation.
So the question is not “how do we pay for fewer licences?” It is a different and more interesting question: you are already paying for all of it, so what are you not using?
That reframing matters commercially. A seat-trimming exercise produces a cost reduction. An adoption and consolidation exercise produces two things: the elimination of other subscriptions you are still paying for separately, and additional value from capability you have already bought. In most businesses the second is larger than the first, and neither shows up unless somebody looks.
Confirm your own licensing position before acting on any of this. Zoho’s pricing page describes the all-employee model; product packaging, editions and regional availability change, and your contract may differ from the published position. That is a five-minute check and it determines which of the two exercises you are actually running.
The Business Problem: Consolidation That Stopped Halfway
- The implementation covered what was being replaced, and stopped there. CRM replaced the CRM, helpdesk replaced the helpdesk. Applications that were not replacing an incumbent were never scoped, so they were never deployed.
- Nobody owns the suite after go-live. The implementation had a project manager. Once the project closed, the applications had administrators but the suite had nobody asking what else it could do.
- Departments do not know what is available. A team buys a point tool for something the suite already covers, because nobody told them it was included. This is the most common and most frustrating form of waste, because it is paid for twice.
- Usage is invisible. Zoho’s Zoho One page describes centralised administrative control and role and permission assignment, and does not describe cross-application usage analytics for administrators. So “who is using what” is not a report you can simply run; it has to be assembled.
- The original business case was never revisited. The consolidation saving was calculated once, at purchase. Whether it was realised, and what has happened since, is not a question anyone has gone back to.
- Leavers and joiners drift. Under all-employee pricing the licence count follows headcount, which is fine, but access assignment does not maintain itself, and people accumulate access to applications they never open while new joiners wait for access they need.
What the Unused Capability Actually Costs
- Subscriptions you are paying twice for. The clearest and most recoverable cost. A separate signing tool, a separate survey tool, a separate form builder, a separate internal chat: each with its own invoice, each duplicating something included in the suite.
- Problems being solved badly by spreadsheets. A process running on a shared workbook that a suite application would handle properly. The cost is the time, the errors and the key-person dependency, none of which appears in the software budget.
- A business case that cannot be evidenced. When the renewal comes, or when a new CFO asks whether the suite is worth it, the answer should be a usage report. Without one, the defence is the original argument, which is now several years old.
- Integration value forgone. The specific advantage of a suite is that applications share records. A business running two suite applications and four external tools is paying for integration it is not getting.
- Adoption debt. Every month an application sits unused, switching it on later becomes marginally harder, because the process it would have supported has calcified around whatever people did instead.
Running the Audit: What You Own Versus What You Use
This is a short exercise and it produces the whole agenda. Plan a week, not a quarter.
- List what the suite includes. Zoho’s own Zoho One page states 45+ applications included, though its page metadata refers to a larger number, so take the figure from your own admin console rather than from marketing material. Produce the actual list of what your organisation has available.
- Establish what is actually in use. Since cross-application usage analytics are not described as an administrator feature, assemble this rather than expecting to run it. Three inputs work: the admin console’s view of which applications are provisioned, a short departmental survey asking which applications people open in a normal week, and the observable artefacts: where do records live, where do documents live, where does the team actually communicate. Classify each application as in production use, partially used, or dormant.
- List every other software subscription the business pays for. All of them, from accounts payable rather than from IT, because the ones IT does not know about are precisely the ones you are looking for.
- Map the overlap. Which external subscriptions duplicate something the suite includes. This is the recoverable cost, and it is usually the first thing that pays for the exercise.
- List the processes running on spreadsheets. Ask each department head for the workbooks the team could not operate without. Each is a candidate for a suite application that is already paid for.
- Produce two lists. External subscriptions that can be retired, ranked by annual cost. And suite applications worth switching on, ranked by the problem they would solve. Both lists should be short. A review that produces twenty recommendations produces none.
The Shadow Software Question
The overlap list is almost always longer than IT expects, and it is worth understanding why rather than treating it as a discipline failure.
Teams buy tools to solve immediate problems. A marketing manager needs a survey out this week. The suite includes a survey tool, nobody told her, and a card-funded subscription takes four minutes. She made a reasonable decision with the information she had.
The duplication is invisible on both sides. IT does not see a departmental card subscription. The department does not see the suite inventory. Neither party is being careless.
Three fixes, in order of effect:
- Publish what is included, in plain language. Not a list of product names, but a list of problems and the application that solves each. “Need to collect responses from customers? That is included; ask IT.” Most businesses have never done this, which is why the duplication persists.
- Route new software requests through a single check. Not an approval bureaucracy, but a question: is this already covered? A lightweight check at the point of request prevents far more duplication than an annual audit recovers.
- Review accounts payable for software spend annually. The subscriptions nobody remembers are visible there and nowhere else.
One caution. Not every duplication should be eliminated. A team using a specialist tool that genuinely does more than the suite equivalent is making a legitimate choice, and forcing a downgrade to realise a small saving is a poor trade. The test is whether the suite application would do the job adequately, not whether it exists.
Deciding What to Switch On Next
The temptation after an audit is to deploy everything dormant. That fails, because capacity to absorb change is the constraint rather than licence availability.
- Rank by the problem, not by the application. The question is never “should we switch on the project tool?” It is “what is our worst process, and is there something included that would fix it?” Applications deployed to solve a named problem get adopted. Applications deployed because they were available do not.
- Prefer candidates that retire an external subscription. They carry a measurable financial return, which makes the next one easier to fund in attention terms.
- Prefer candidates adjacent to what you already run. An application sharing records with one you use well starts with a data advantage and an audience that already knows the environment.
- Deploy one at a time, with an owner and a success measure. A departmental owner, not IT. A measure stated before you start: a spreadsheet retired, a subscription cancelled, a response time improved.
- Sequence over quarters, not weeks. Two or three applications a year, properly adopted, beats eight deployed and ignored. This is an unpopular recommendation and it is the one that determines whether the programme survives its first year.
Making Adoption Stick
The reason dormant applications stay dormant is rarely the software.
- Name an owner for the suite, not just for each application. Someone whose job includes asking, quarterly, what else should be in use. Without this role the audit happens once and the drift resumes immediately.
- Switch off the alternative. An application deployed alongside the spreadsheet it replaces loses to the spreadsheet. There has to be a date after which the old method stops, with a named person who decided it.
- Train on the process, not the product. People do not need a tour of the application; they need to know how their specific task now works. Product training produces attendance and no behaviour change.
- Use the integration explicitly in the first deployment. The suite’s advantage is shared records. If the first thing a team sees is that the customer they are looking at is the same customer the sales team sees, the argument for the suite makes itself.
- Review access assignment annually. Under all-employee pricing this is not about cost, it is about hygiene: people accumulate access they do not use and joiners wait for access they need, and neither is visible unless somebody looks.
- Report adoption to the people who fund it. Applications in production use, external subscriptions retired, spreadsheets replaced. Three numbers, reported at renewal, turn an unexamined invoice into an evidenced decision.
Approaches Compared
| Approach | What it examines | Typical outcome | Effort | Best used when |
|---|---|---|---|---|
| Do nothing | Nothing | Renewal signed on the original argument | None | Never, beyond the first year |
| Seat-count review | Dormant and leaver accounts | Limited under all-employee pricing, since licences follow headcount | Low | Where your contract is per-user rather than all-employee; confirm first |
| Overlap audit | Suite inventory against other software subscriptions | Retirable external subscriptions, usually the fastest return | Low, about a week | The first exercise any business should run |
| Adoption review | Dormant applications against unsolved process problems | Additional value from capability already paid for | Moderate, and ongoing | Once the overlap audit is done |
| Full process review | Every process against suite capability | Comprehensive, and frequently more change than the business can absorb | High | Large organisations with dedicated change capacity |
For most mid-market businesses, the overlap audit followed by a sequenced adoption programme covers the realistic opportunity. The full process review is a bigger undertaking than the problem usually justifies.
Best Practices
- Confirm your licensing model before you start. All-employee pricing changes the exercise from seat-trimming to adoption and consolidation.
- Take the application inventory from your admin console, not from marketing material.
- Pull the external software list from accounts payable, not from IT. The gap between the two lists is the finding.
- Publish what is included as a list of problems solved, in plain language, where departments will see it.
- Add a “is this already covered?” check at the point software is requested.
- Rank deployment candidates by the problem they solve, never by availability.
- Prefer candidates that retire a subscription or sit adjacent to an application you already run well.
- Deploy one at a time, with a departmental owner and a success measure agreed in advance.
- Switch off the alternative on a named date, or the old method wins.
- Report three numbers at renewal: applications in production use, subscriptions retired, spreadsheets replaced.
Common Mistakes
- Running a seat-count review under all-employee pricing. Confirm the model first; the wrong exercise produces nothing and costs credibility.
- Deploying everything dormant at once. Change capacity is the constraint, not licensing, and a failed rollout poisons the next one.
- Taking the inventory from marketing material. Zoho’s own page states 45+ applications while its metadata says more. Use your admin console.
- Asking IT what software the business uses. The subscriptions that matter are the ones IT cannot see.
- Eliminating every duplication. A specialist tool that genuinely outperforms the suite equivalent is a legitimate choice; forcing a downgrade for a small saving is a bad trade.
- Running the application alongside the spreadsheet it replaces. The spreadsheet wins every time.
- Product training instead of process training. Produces attendance, not adoption.
- Never publishing what is included. Guarantees the duplication regenerates continuously.
- No owner for the suite. The audit becomes a one-off and the drift resumes within months.
- Twenty recommendations. A review that recommends everything recommends nothing.
An Illustrative Scenario: A 120-Person Services Business
The following is a composite illustration drawn from patterns common to businesses of this size. It is not an account of a specific Techvaria client, and no figures below come from any real engagement.
Consider a services business of around 120 people that moved to a consolidated suite three years ago, replacing a CRM, a helpdesk and a document signing subscription.
The Trigger
A new finance director reviewing recurring spend asked a straightforward question: what are we getting for this? Nobody could answer it with a number.
What the Audit Found
The suite inventory from the admin console listed considerably more applications than anyone had realised were available. Classified by actual use, a small group were in genuine production use, a few more were partially used by one team, and the majority were dormant.
The accounts payable list was the more interesting half. It surfaced several active software subscriptions that IT had not known about, including a survey tool bought by marketing, a form builder used by operations, an internal chat tool one department had adopted independently, and a project tracker a team had started during a client engagement and never stopped paying for. Each duplicated something included in the suite.
A departmental conversation about critical spreadsheets produced a further list: a resourcing workbook, a client onboarding checklist and a leave tracker, all running on files that one person maintained.
What Was Implemented
The overlap list first, because it carried a measurable return. Three of the four duplicate subscriptions were retired over a quarter, with the teams moved onto the suite equivalents. The fourth was kept: the specialist tool genuinely did more than the included equivalent, and the finance director agreed that forcing a downgrade for a modest saving was the wrong call.
A plain-language list of what was included, written as problems rather than product names, was published on the intranet. A single question was added to the software request process: is this already covered?
For adoption, three candidates were ranked by problem rather than by availability. The resourcing workbook was chosen first because it was the worst process and the most obviously fragile. It was deployed with the operations manager as owner, a success measure agreed in advance, and a date after which the workbook was read-only.
After Two Quarters
The retired subscriptions were the visible result and the one the finance director quoted. The adoption work moved more slowly and the second candidate had not started by the end of the period, which the IT manager considered appropriate rather than disappointing, because the first deployment had been absorbed properly.
The outcome that changed the renewal conversation was the smallest. Three numbers (applications in production use, subscriptions retired, spreadsheets replaced) turned an invoice nobody questioned into a decision with evidence behind it.
Industry Use Cases
- Professional and IT services. The most common profile for this exercise: distributed teams, departmental autonomy, and a high rate of independently adopted tools. See professional services and IT services and ERP.
- Trading and distribution. Operational processes running on spreadsheets are typically the richest adoption candidates here, more so than duplicate subscriptions. See trading and distribution.
- Manufacturing. Office functions adopt independently while operations runs on the ERP, so the duplication concentrates in sales, marketing and HR. See manufacturing solutions.
- Healthcare. Departmental tool adoption carries a data governance dimension as well as a cost one, which usually raises the priority of the overlap audit. See healthcare solutions.
- Education. Multiple departments with separate budgets and a strong tendency to adopt independently, where publishing what is included has outsized effect. See education solutions.
Frequently Asked Questions
Probably not in the way you expect. Zoho’s pricing page describes all-employee pricing, charged per employee per month and requiring a licence for all employees. Under that model, licences follow headcount rather than usage, so seat-trimming has limited effect. Zoho also offers Flexible User Pricing for any number of users, and on that plan a conventional seat review does apply. Confirm your own contract first: it determines whether you are running a cost-reduction exercise or an adoption exercise.
In two places. Other software subscriptions you are still paying for that duplicate something included, usually the fastest and most measurable return. And value from applications you already own but have never switched on, which is larger in most businesses and slower to realise.
Assemble it rather than expecting to run a report. Zoho’s Zoho One page describes centralised administrative control and role and permission assignment, and does not describe cross-application usage analytics for administrators. Combine the admin console’s provisioning view, a short departmental survey, and the observable question of where records and documents actually live.
Zoho’s own page states 45+ applications included, while its page metadata refers to a larger figure. Take the authoritative list from your own admin console rather than from marketing material, since availability can differ by region and plan.
No. Where a specialist tool genuinely does more than the included equivalent and the team depends on that difference, forcing a downgrade to realise a small saving is a poor trade. The test is whether the suite application would do the job adequately for that team’s actual requirement.
One. Capacity to absorb change is the constraint, not licensing. Two or three a year, each with a departmental owner, a success measure agreed in advance and a date after which the old method stops, will outperform eight deployed simultaneously and ignored.
Publish what is included as a list of problems solved in plain language, and add a single question to the software request process asking whether it is already covered. Departments buy duplicates because they do not know, not because they are being careless; the fix is information, not approval bureaucracy.
Conclusion
The renewal nobody questions is the one worth questioning, and the reason most businesses do not is that answering requires knowing what is used, which is not a report you can run.
Start by confirming your licensing model, because it determines the entire exercise. Under all-employee pricing, the familiar seat-trimming playbook has limited effect and the real opportunity is different: you are already paying for the whole suite, so the question is what you are not using.
Two lists answer it. The overlap between the suite inventory and your accounts payable software spend, which is the fastest measurable return and usually surprises IT. And the gap between dormant applications and the processes currently limping along on spreadsheets, which is larger and slower.
Then deploy slowly and deliberately: one application at a time, chosen for the problem it solves rather than because it is available, with a departmental owner, a success measure and a date after which the old method stops. Two a year done properly is a better outcome than eight done at once.
And report three numbers at renewal: applications in production use, subscriptions retired, spreadsheets replaced. That turns an invoice signed out of habit into a decision with evidence behind it, which is ultimately what the finance director was asking for.
Find Out What You Are Already Paying For
Techvaria is a Zoho Premium Partner with more than 350 implementations delivered since 2016, from offices in Bangalore, Ahmedabad and Dubai.
A Zoho One adoption and consolidation review is about a week’s work and produces two short, ranked lists: external software subscriptions that duplicate something you already own, taken from your accounts payable rather than from IT; and dormant applications matched against the processes currently running on spreadsheets, ranked by the problem each would solve rather than by what is available.
It also produces the three numbers worth having at your next renewal, and a plain-language list of what is included that you can publish internally, which is usually what stops the duplication regenerating.
Talk to our Zoho consultants, or see how we approach Zoho One implementations.
Find Out What You Are Already Paying For
Director @ Techvaria | Solutions Architect | Low-Code & AI Automation for Growth | Proven Expertise in Digital Transformation Across Industries