Predictika · CRM software plans

An AI sales agent's Zoho CRM edition plan, checked before it goes out

An AI sales agent sets up a Zoho CRM plan for a customer: an edition (Free, Standard, Professional, Enterprise or Ultimate), the number of users, and what the customer needs configured, such as custom modules, deal pipelines, profiles and roles, workflow rules, blueprints and the CPQ tools, with the module limit the plan states for that edition. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the per-edition limits Zoho publishes and returns a verdict, every reason and the figures it computed.

Scope: Zoho CRM editions (Free, Standard, Professional, Enterprise, Ultimate): the published per-edition limits on users, modules, fields, pipelines, security, automation and CPQ tools. See everything this validator covers

This validator models a Zoho CRM edition plan, based on the limits in Zoho's public edition comparison table, not just the scenarios shown below.

  • Edition and users — the Free edition is for up to 3 users; every plan needs at least one user.
  • Customization limits — custom modules, custom fields in a module, deal pipelines and currencies in multi-currency, each checked against the edition's published limit (for example 10, 25, 200 and 500 custom modules on Standard, Professional, Enterprise and Ultimate).
  • Security and structure — profiles, roles, user groups and territories against the edition's limits (territories are listed only for Enterprise and Ultimate).
  • Automation and CPQ — workflow rules in a module (total and switched on), blueprints, active approval processes in a module, custom buttons in a module, and the CPQ tools: price rules, product configurations and guided selling flows.
  • Stated module limit — the number of custom modules the plan says the edition allows must equal the published figure. The Ultimate edition, which Zoho describes as tailored for large-scale, bespoke deployments, always goes to a person to confirm.

Any Zoho CRM edition plan that touches these limits is in scope — not only the scenarios pictured here. Not covered: prices (Zoho shows prices by currency and region, so this page shows no price build-up), monthly or annual billing, add-ons and other Zoho products such as Bigin and CRM Plus, storage and API limits, and any limit not in the rows listed above.

The AI sales agentBuilds the plan from the conversation and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

7 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch

What the agent proposes

The AI sales agent says

Illustrative agent statement. The validator receives the structured request below.

Proposing agent: AI sales agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      

        
        
        
      

      
Waiting for the call.

      
    

  

  
  

    
Where rules-based CPQ gets it wrong
Click to expand
    
Our assessment of what a typical rules-based CPQ (product rules, price rules and validation rules, as in Salesforce CPQ) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

    
What the validator caughtTypical rules-based CPQPredictika
Per-edition limits across about twenty featuresOnly with workarounds
Each edition has its own number for each feature, and the table changes when Zoho changes it. A rules-based CPQ needs a lookup table or a rule per edition and per feature, and every update means editing them.		The edition arrives in the request and every limit is read from the published table on every call.
Several limits exceeded at onceOnly with workarounds
Rules tend to fire as a step is saved, so a person fixes one limit and then meets the next.		All findings come back together, whatever order the choices arrived in.
The Free edition's 3-user cap together with its other limitsOnly with care
The cap, the single pipeline and the missing features are separate rules that depend on the edition chosen.		The edition, the users and every limit are compared together.
The module limit the plan statesOnly with care
The stated limit comes from the agent's own text, so a rule has to compare it with the published row for the edition chosen.		The stated limit is a field in the request, compared with the table figure on every call.
Upgrading one edition and finding the next problemOnly with care
A fix to the edition changes every limit at once, so earlier passes tell little about the new choice.		The same plan is re-checked in full against the new edition.

  

  

    
What this validator catches: findings from its test cases
Click to expand
    
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the quote; approval findings need a person to sign off; everything else is computed.

    
1The plan has 0 users; at least 1 is needed.
2The Free edition is for up to 3 users; the plan has 4 users.
3The plan needs 2 deal pipelines; this edition allows 1.
4The plan needs 1 custom module; this edition allows 0.
5The plan needs 3 roles; this edition allows 2.
6The plan needs 11 custom modules; this edition allows 10.
7The plan needs 6 currencies in multi-currency; this edition allows 5.
8The plan needs 6 deal pipelines; this edition allows 5.
9The plan needs 11 custom fields in a module; this edition allows 10.
10The plan needs 31 workflow rules in a module; this edition allows 30.
11The plan needs 16 workflow rules switched on in a module; this edition allows 15.
12The plan needs 1 blueprint; this edition allows 0.
13The plan needs 1 CPQ price rule; this edition allows 0.
14The plan needs 1 CPQ product configuration; this edition allows 0.
15The plan needs 1 guided selling flow; this edition allows 0.
16The plan needs 1 custom button in a module; this edition allows 0.
17The plan needs 21 user groups; this edition allows 20.
18The plan needs 26 custom modules; this edition allows 25.
19The plan needs 4 blueprints; this edition allows 3.
20The plan needs 11 currencies in multi-currency; this edition allows 10.
21The plan needs 11 deal pipelines; this edition allows 10.
22The plan needs 16 profiles; this edition allows 15.

  

  

    
Scenarios and results
Click to expand
    
The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.

    
1. Standard to Professional: Standard edition for a 40-user sales team

    
The agent's request. Please set up the Zoho CRM Standard edition for 40 users. The customer needs 2 currencies in multi-currency, 14 custom modules, 3 deal pipelines, 4 profiles, 5 roles, 12 user groups, 8 custom fields in a module, 20 workflow rules in a module, 10 of them switched on and 3 blueprints. The plan says the edition allows 14 custom modules. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Too many custom modules for the edition. The plan needs 14 custom modules; this edition allows 10.
    • 
      
  • Too many blueprints for the edition. The plan needs 3 blueprints; this edition allows 0.
    • 
      
  • Stated module limit does not match. The plan states that the edition allows 14 custom modules; the comparison table gives 10.
    • 
    

    
2. Standard to Professional: The agent resubmits after fixing the errors

    
The agent's request. Please set up the Zoho CRM Professional edition for 40 users. The customer needs 2 currencies in multi-currency, 14 custom modules, 3 deal pipelines, 4 profiles, 5 roles, 12 user groups, 8 custom fields in a module, 20 workflow rules in a module, 10 of them switched on and 3 blueprints. The plan says the edition allows 14 custom modules. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Stated module limit does not match. The plan states that the edition allows 14 custom modules; the comparison table gives 25.
    • 
    

    
3. Standard to Professional: The agent resubmits after fixing the errors

    
The agent's request. Please set up the Zoho CRM Professional edition for 40 users. The customer needs 2 currencies in multi-currency, 14 custom modules, 3 deal pipelines, 4 profiles, 5 roles, 12 user groups, 8 custom fields in a module, 20 workflow rules in a module, 10 of them switched on and 3 blueprints. The plan says the edition allows 25 custom modules. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Edition summary. This edition allows 25 custom modules, 10 deal pipelines and 155 custom fields per module.
    • 
    

    
4. Enterprise to Ultimate: Enterprise edition for 180 users with CPQ and territories

    
The agent's request. Please set up the Zoho CRM Enterprise edition for 180 users. The customer needs 12 currencies in multi-currency, 120 custom modules, 8 deal pipelines, 30 profiles, 300 roles, 40 user groups, 200 territories, 200 custom fields in a module, 90 workflow rules in a module, 50 of them switched on, 20 blueprints, 4 active approval processes in a module, 20 custom buttons in a module, 60 CPQ price rules, 30 CPQ product configurations and 20 guided selling flows. The plan says the edition allows 200 custom modules. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Too many profiles for the edition. The plan needs 30 profiles; this edition allows 25.
    • 
      
  • Too many roles for the edition. The plan needs 300 roles; this edition allows 250.
    • 
      
  • Too many price rules for the edition. The plan needs 60 CPQ price rules; this edition allows 50.
    • 
      
  • Too many territories for the edition. The plan needs 200 territories; this edition allows 150.
    • 
    

    
5. Enterprise to Ultimate: The agent resubmits after fixing the errors

    
The agent's request. Please set up the Zoho CRM Ultimate edition for 180 users. The customer needs 12 currencies in multi-currency, 120 custom modules, 8 deal pipelines, 30 profiles, 300 roles, 40 user groups, 200 territories, 200 custom fields in a module, 90 workflow rules in a module, 50 of them switched on, 20 blueprints, 4 active approval processes in a module, 20 custom buttons in a module, 60 CPQ price rules, 30 CPQ product configurations and 20 guided selling flows. The plan says the edition allows 500 custom modules. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • Ultimate edition to confirm. Zoho describes the Ultimate edition as tailored for large-scale, bespoke deployments with consultation from experts and migration assistance; a person should confirm the scope before the plan goes out.
    • 
      
  • Edition summary. This edition allows 500 custom modules, 50 deal pipelines and 500 custom fields per module.
    • 
    

    
6. Free to Standard: Free edition for a 12-user team

    
The agent's request. Please set up the Zoho CRM Free edition for 12 users. The customer needs 3 currencies in multi-currency, 2 deal pipelines, 2 profiles and 2 roles. The plan says the edition allows no custom modules. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Free edition is for 3 users. The Free edition is for up to 3 users; the plan has 12 users.
    • 
      
  • Too many currencies for the edition. The plan needs 3 currencies in multi-currency; this edition allows 0.
    • 
      
  • Too many deal pipelines for the edition. The plan needs 2 deal pipelines; this edition allows 1.
    • 
    

    
7. Free to Standard: The agent resubmits after fixing the errors

    
The agent's request. Please set up the Zoho CRM Standard edition for 12 users. The customer needs 3 currencies in multi-currency, 2 deal pipelines, 2 profiles and 2 roles. The plan says the edition allows 10 custom modules. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Edition summary. This edition allows 10 custom modules, 5 deal pipelines and 10 custom fields per module.
    • 
    

  

  

    
Narration transcript
Click to expand
    
The text of the narrated walkthrough, step by step.

    
    
      
  1. Welcome to a demo of Predictika's Validator. An AI sales agent sets up a Zoho CRM plan for a customer: an edition (Free, Standard, Professional, Enterprise or Ultimate), the number of users, what the customer needs configured, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the per-edition limits Zoho publishes and returns a verdict, every reason and the figures it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please set up the Zoho CRM Enterprise edition for 180 users. The customer needs 12 currencies in multi-currency, 120 custom modules, 8 deal pipelines, 30 profiles, 300 roles, 40 user groups. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with four findings, all in one answer. The plan needs 30 profiles; this edition allows 25. The plan needs 300 roles; this edition allows 250. The plan needs 60 CPQ price rules; this edition allows 50. The other one is on screen.
    6. 
      
  6. The validator returned four blocking findings in one answer. A check that reads one field at a time would pass most of this; it shows only when the choices in the quote are checked against each other.
    7. 
      
  7. What this shows: for per-edition limits across about twenty features, a rules-based CPQ can do this only with workarounds.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the edition to ultimate and the custom modules the plan says the edition allows to 500.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Not blocked, but held for a person.
    12. 
      
  12. The four blocking findings are cleared; one approval remains for a person: Ultimate edition to confirm.
    13. 
      
  13. Four problems caught in one call, fixed in one pass, and the corrected quote now goes to a person for approval. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.
    14.