Zoho CRM buyer's checklist: 13 checks, and the 4 answers that are not public

Zoho CRM is one of the easier CRMs to buy and one of the harder ones to size, because the prices are all published and the limits are not. This checklist exists so that the second half does not surprise you in month six.

Every item comes from a page the vendor published, read from the United States on 6 October 2026, or from a gap in those pages that we are naming rather than guessing at.

OUR TAKE: Nine of these thirteen checks are answerable before you speak to anyone. The other four are the ones to get in writing, and three of those four are about ceilings the vendor does not publish.

## 1. Confirm the edition against a requirements list

Standard at $14 per user per month on annual billing covers email and mass email, built-in calling, multiple pipelines, calendar integration, forms, forecasting, data enrichment and custom modules. Professional at $23 adds AI agents, process management, predictive intelligence, inventory, CPQ, portals and unlimited reports. Enterprise at $40 adds multi-team management, reporting hierarchy, approval processes, a developer sandbox and field-level encryption^[1].

Write your requirements first, then pick the row. Doing it the other way round is how teams end up on Enterprise for one feature.

## 2. Check the billing term, and use the monthly option

The pricing page states the service is pay-as-you-go, monthly or yearly, with no contracts or commitments. All four paid editions carry a monthly rate.

So buy a month before you buy a year. Standard is $20 monthly against $14 annually; Professional is $35 against $23.

3. Know what the annual commitment is worth at your edition

30% at Standard. 34% at Professional. 20% at Enterprise and Ultimate.

The incentive shrinks as the bill grows, which means the case for staying monthly gets stronger the larger you are.

## 4. Confirm the currency, in writing

The pricing page served Indian rupees to our United States request on two separate attempts, including a forced fresh render.

Do not budget from a page that is not quoting your currency. Ask for the quote in writing in the currency you will be invoiced in.

5. Ask whether local taxes apply to you

The page states that local taxes such as VAT or GST are charged in addition to the listed prices.

For buyers in those jurisdictions that is a real percentage on every figure, and it belongs in the budget rather than in the surprise column.

## 6. Get four limits in writing

Records. Custom fields. Workflow rules per module. API calls per day.

The vendor publishes limits for the free edition, 10 custom email templates, up to 10 data exports and 5,000 API calls a day, and we found no published ceilings for the paid editions on any readable page. These four numbers are the ones that decide whether you stay on the edition you are buying.

7. Ask about the AI ceiling specifically

Is there a cap on agent runs or predictions at our edition, and what happens when we reach it.

AI agents and predictive intelligence arrive at Professional, and no allowance or consumption rate is published anywhere. Competing vendors publish theirs, so this is a fair question and an answerable one.

## 8. Check HIPAA and encryption against your obligations

HIPAA compliance is named on the Standard card at $14 per user per month. Field-level encryption arrives at Enterprise at $40, alongside the developer sandbox.

Both sit lower in this ladder than in most. If either is a requirement, it may set your edition floor, and it will set it cheaper than you expected.

9. Pilot on the free edition, with real data

Three users, no card, no expiry.

Import your actual records with their duplicates before you pay anything, and note two numbers: your duplicate rate, and which fields are actually populated. That is your configuration specification, and it costs nothing to obtain.

10. Negotiate support explicitly

Support is the largest complaint theme in every pool we could read, at 32% of the English reviews in the company-level corpus with an average of 1.9 stars, and Capterra's summaries describe it as slow and unresponsive.

Ask for a named response commitment in writing. And plan for an internal owner regardless, because on a product this configurable that person is part of your support arrangement whether you plan for them or not.

11. Decide the edition for the team you will be, not the one you are

The two editions most teams choose between are Standard at $14 and Professional at $23 per user per month on annual billing, and the deciding features are specific rather than vague.

You need Professional if you want process management, inventory, CPQ with price rules, customer or partner portals, unlimited reports, or the AI. You can stay on Standard if your requirement is email, calling, pipelines and forecasting.

Nine dollars per user per month separates those two lists. That is small enough that the common mistake is under-buying and then working around a missing feature for a year, which costs more in time than the difference costs in money.

12. Test the export before you commit

An hour's work during the pilot. A CRM you cannot export from is a CRM you cannot renegotiate with, and the best time to learn that is while you are still deciding.

12. Count seats by role, not by headcount

Decide who genuinely works in the system and who only reads from it, and ask what the cheapest legitimate access is for the second group.

Per-seat pricing rewards precision, and a quote built from headcount is always the largest possible quote.

13. Note what you are not paying for

Two charges common elsewhere in this category are absent here, and knowing that sharpens a comparison.

There is no mandatory onboarding fee on any page we read. At least one major competitor charges $1,500 at its mid tier and $3,500 at the tier above, neither shown on its per-seat cards.

And API access is not surcharged. The free edition alone carries 5,000 calls a day, where another major competitor's comparison table adds $25 per user per month for API access.

When you compare quotes, make sure the other vendor's includes both of those lines, because they rarely appear in the first version of a proposal.

14. Check whether the sibling product fits better

The same pricing page sells Bigin, positioned for a first-timer moving from spreadsheets, with pipelines, email and calling, calendar integration, appointment scheduling, social ad capture and payment collection.

We did not read its pricing and publish none. If your requirements list is short, it belongs on the shortlist anyway.

14. Agree who owns the system before you buy it

Three roles, named people. Somebody owns the data and decides what a duplicate is. Somebody owns the process and can define a qualified lead without a meeting. Somebody owns the system and learns it properly.

On a small team that can be one person. It cannot be nobody, and on a product this configurable the internal owner is effectively part of your support arrangement.

15. Ask for certifications and data residency separately

We found no readable page setting out certifications, data residency or retention terms for this product.

If your procurement review needs documents rather than feature names, request them directly and early. The pricing page tells you that field-level encryption exists at Enterprise and that HIPAA compliance is named at Standard; it does not tell you where your data lives or what the retention policy is.

16. Plan the upgrade path, not just the purchase

The jumps are $14 to $23 to $40 to $52 per user per month on annual billing.

Those steps are small enough that teams sit on the wrong edition for years in both directions: paying for Enterprise because of one feature, or straining on Standard because nobody revisited it. Put an annual review in the calendar, and make the trigger a limit or a requirement rather than a sales call.

A worked example: eight seats

Eight people. A pipeline with stages, some automation, reporting a manager will read, and one person who will own the system.

The edition is Professional, $23 per user per month on annual billing or $35 month to month. That is the whole quote; there is no onboarding fee on any page we read.

Three questions decide whether that number holds. Does your jurisdiction add VAT or GST on top. What are the record, field, automation and API limits at Professional, which are not published. And is there a cap on the AI that comes with the edition.

Notice what is not on that list: the rate itself, which you already have. In most CRM purchases the rate is the hard part. Here it is the easy part, and the work is in the three questions above.

The four answers that will not be public

Records, custom fields and workflow rules per module at paid editions. API calls per day above the free tier. The AI cap and what happens at it. And the model provenance, training position, retention and opt-out terms for the AI, none of which appeared on any page we read.

Everything else on this list is published. If a representative cannot answer the published items, that is information about the representative. If they will not answer these four in writing, that is information about the purchase.

The order to work through this

The sequence matters as much as the items, because three of these checks cost nothing and change what the rest are worth.

Start with the free-edition pilot, item nine. It costs no money and no commitment, and it produces the two numbers that make the edition decision real: your duplicate rate and your actual field coverage.

Then do items one, two and three on paper: the edition against a requirements list, the billing term, and what the annual commitment is worth at that edition. Those are published, so they take twenty minutes.

Then send the written questions: the four limits, the AI ceiling, the support commitment, the certifications. Give the vendor two business days, which is both reasonable and a useful test of the thing the review record complains about most.

Only then buy, and buy a month first.

What this checklist deliberately leaves out

Feature comparisons against other CRMs. They belong in a comparison article, and they are the part of a purchase decision most likely to be decided by whoever built the table.

Any judgement about how the product feels to use. We read vendor pages and review pools rather than operating the product, so where this list mentions usability it cites what reviewers said and says so.

And any claim about integration catalogue size, for the same reason: we did not read a countable catalogue page, so we publish no number.

## What a good quote looks like

The edition, named. The term, with the discount stated. The currency, with tax treatment stated. The four limits. The AI ceiling. The support response commitment.

Six lines. The prices you already have, which in this category is unusual enough to be worth saying plainly, and it means your negotiation can be about the things that are missing rather than about the number.