Skip to main content Scroll Top

Zoho Consultant and Developer: CRM Setup, Integrations and Custom Apps

Updated November 2026 · Written and maintained by the Progression Agency strategy team

A Zoho consultant turns the way your team sells, serves and bills into a working Zoho setup: modules and fields, Blueprint stages, workflow rules, integrations on the Zoho CRM API, and Deluge code where point and click runs out. Two published limits shape those choices before anything is configured. Each Zoho CRM edition caps what can be built, from custom modules to Blueprints to test sandboxes, and every integration spends from a daily pool of API credits that Zoho sizes by edition and user count. Progression’s consultants and developers are based in New York and set up, repair and extend Zoho for companies across the US.

On this page · 14 sections
  1. A nightly sync that spent 40,000 API credits
  2. What a Zoho consultant sets up, repairs and extends
  3. Edition limits decide the build before anyone configures it
  4. API credits: the daily budget every integration spends
  5. Workflow rules, Blueprint, then code: the order Zoho recommends
  6. Zoho developer work in Deluge, Python, Node.js and Java
  7. Connecting Zoho to the rest of the stack
  8. Moving into Zoho CRM from spreadsheets or another CRM
  9. Custom apps on Zoho Creator when CRM modules run out
  10. Reports and dashboards that tie Zoho to revenue
  11. Testing changes before they reach the live org
  12. Running Zoho after launch
  13. What Zoho consulting and development costs
  14. How Progression’s Zoho team works with yours

Not on Zoho yet? Still comparing Zoho with HubSpot, Salesforce and the rest? Our CRM consultant page covers choosing a platform before any one of them is set up.

Examples marked “Illustrative example.” are hypothetical, and no real business or Zoho account is shown.

A nightly sync that spent 40,000 API credits

Picture a hypothetical plumbing supply distributor on Zoho CRM Standard with 20 user licenses. Its new order system pushes 40,000 customer and order records into the CRM every night, one record per API call.

Two drawn boxes. The first shows a hypothetical nightly sync sending 40,000 records one per call and using most of a 55,000 credit daily budget. The second shows the same records sent 100 per call for 4,000 credits.Two drawn boxes. The first shows a hypothetical nightly sync sending 40,000 records one per call and using most of a 55,000 credit daily budget. The second shows the same records sent 100 per call for 4,000 credits.
Illustrative example. A hypothetical nightly sync, sent one record per call and then in batches of 100.

The sync logic was right, and the way it called the API was the problem. Zoho allows up to 100 records in a single insert, update or upsert request, so batching is the first thing to check when an org keeps hitting its daily ceiling. Nothing about the data changed between the two versions; only the size of each request did.

A bar chart comparing a 55,000 credit daily budget with a sync that uses 40,000 credits sent singly and 4,000 credits sent in batches of 100.A bar chart comparing a 55,000 credit daily budget with a sync that uses 40,000 credits sent singly and 4,000 credits sent in batches of 100.
Illustrative example. The same 40,000 record sync, sent singly and in batches, against a Standard edition credit budget.
  • Count the calls each integration makes in 24 hours.
  • Send writes in batches of up to 100 records.
  • Move very large loads to the asynchronous bulk APIs.
  • Watch the remaining credit header once use passes half the daily allowance.
  • Give each integration its own credentials so its usage can be traced.

What a Zoho consultant sets up, repairs and extends

Most Zoho projects come down to a short list of jobs. Some are configuration inside the CRM, some are code, and some connect Zoho to the systems around it. The table pairs each job with the Zoho feature that does it and the edition rule that limits it.

Zoho jobs, the feature behind each and the edition rule that applies
The jobZoho featureWhat it handlesEdition note
Shape the dataModules, fields and layoutsRecords for what you sell and who buys, beyond leads, contacts and dealsCustom modules run from 10 on Standard to 500 on Ultimate
Enforce the sales processBlueprintAn online replica of a process, with each stage change checkedProfessional and higher
Automate routine stepsWorkflow rulesAlerts, tasks, field updates, webhooks and functions when a condition is metEvery edition, with more rules per module as editions rise
Run custom logicFunctionsServerless scripts in Deluge, Python, Node.js or JavaTriggered by rules, buttons, schedules or HTTP calls
Change the screenClient Script and widgetsBrowser side JavaScript and embedded components built with Zoho’s SDKClient Script on Enterprise and Ultimate
Connect other systemsREST API, Zoho Flow and webhooksSync with ERPs, billing, website forms and ad platformsAPI credits per 24 hours, sized by edition
Build beyond the CRMZoho CreatorInternal tools, customer portals and core systems, with phone appsA separate Zoho product

Configuration comes first because an administrator can maintain it. Code comes in where configuration stops, and integrations come last, once the data model they write into is settled. For a wider view of the CRM market before committing to Zoho, our CRM examples page sets the main platforms side by side.

Zoho CRM on its own, or the whole Zoho One suite?

Zoho One bundles 45 or more Zoho apps, CRM among them, under licensing that Zoho requires for every employee in the business. It suits companies that will also run finance, support or HR on Zoho. A sales team that only needs a CRM usually starts with Zoho CRM alone, and the choice also sets the API credit tier, since Zoho One shares Enterprise’s credit rules. Teams weighing Zoho against a marketing first platform can also see how a GoHighLevel agency sets up pipelines and workflows.

  • Finance on Zoho Books, Invoice or Expense.
  • Customer support on Zoho Desk.
  • Hiring and HR on Zoho Recruit and People.
  • Projects and stock on Zoho Projects and Inventory.
  • One admin console for users, apps and device permissions.

Edition limits decide the build before anyone configures it

Zoho publishes a feature comparison of its CRM editions, and several of its ceilings decide what a project can include. A process that needs a dozen record types, an enforced approval path or a separate test copy rules some editions out before the first field is created.

Zoho CRM edition limits that shape a build
LimitFreeStandardProfessionalEnterpriseUltimate
Custom modulesNone1025200500
BlueprintsNoneNone350100
Validation rules per layoutNoneNone51025
SandboxesNoneNoneNone3 configuration, 2 with data7 configuration, 3 with data
Records per import batch1,00020,00050,000100,000200,000
Client ScriptNoneNoneNoneIncludedIncluded
A bar chart of custom modules by edition: 10 on Standard, 25 on Professional, 200 on Enterprise and 500 on Ultimate.A bar chart of custom modules by edition: 10 on Standard, 25 on Professional, 200 on Enterprise and 500 on Ultimate.
Custom module limits by Zoho CRM edition.

Which Zoho CRM edition does a custom process need?

Start from the process, not the license price. Count the record types the business tracks beyond the standard modules, decide whether any stage must be enforced rather than suggested, and decide whether changes will be tried on a copy before they reach the live org. Enforced stages point to Professional or higher, and a test copy points to Enterprise or Ultimate.

  • List every record type the team tracks today, spreadsheets included.
  • Mark the stages that must happen in a fixed order.
  • Note which changes need testing before release.
  • Estimate how many records the first import will load.
  • Count the integrations and their nightly volume.
  • Check the edition against all five before buying licenses.

API credits: the daily budget every integration spends

Zoho CRM measures API use in credits across a rolling 24 hour window. Most calls cost one credit, heavier operations cost more, and the pool each org receives depends on its edition and the number of user licenses. Zoho’s API limits page publishes both the formula and the charge for each kind of call.

Zoho CRM API credits per 24 hours, by edition
EditionCredits per 24 hoursCeiling
Free5,0005,000
Standard or Starter50,000 plus 250 per user license, plus add-ons100,000
Professional50,000 plus 500 per user license, plus add-ons3,000,000
Enterprise or Zoho One50,000 plus 1,000 per user license, plus add-ons5,000,000
Ultimate or CRM Plus50,000 plus 2,000 per user license, plus add-onsUnlimited
A bar chart of daily API credits for 20 user licenses: 55,000 on Standard, 60,000 on Professional, 70,000 on Enterprise or Zoho One and 90,000 on Ultimate.A bar chart of daily API credits for 20 user licenses: 55,000 on Standard, 60,000 on Professional, 70,000 on Enterprise or Zoho One and 90,000 on Ultimate.
Daily Zoho CRM API credits for 20 user licenses, by edition.

How many API credits does a 20 user org get?

Under Zoho’s formula, 20 user licenses give 55,000 credits a day on Standard, 60,000 on Professional, 70,000 on Enterprise or Zoho One and 90,000 on Ultimate, before any purchased add-on credits. Trial editions follow the same limits as the paid edition they preview, so a trial is a fair place to measure an integration.

What common Zoho CRM API operations cost in credits
API operationCredits charged
Most single calls, such as reading users, roles or module metadata1
Insert, update or upsert1 for every 10 records, up to 100 records a call
A query returning up to 200 records1
Convert a lead5
Send mail20
Merge records50
Start a bulk read job50
Mass convert leads200
Start a bulk write job500
Create a custom module500

Batching records instead of sending them one by one

Batching is the cheapest fix available. One hundred records in one upsert cost 10 credits, where the same records sent singly cost 100. Starting a bulk write job costs 500 credits, so bulk jobs pay off for overnight loads in the tens of thousands rather than for a few hundred changes.

  • Upserts carrying up to 100 records a call.
  • Composite requests that combine up to five calls in one.
  • Notification APIs that report changes instead of polling for them.
  • Queries that return up to 200 records for a single credit.
  • Bulk read and write jobs for very large loads.

Workflow rules, Blueprint, then code: the order Zoho recommends

Zoho’s own Functions overview puts the rule plainly: prefer workflow rule actions, Blueprint transition constraints or macros whenever they meet the requirement, because Functions add scripting overhead and belong where point and click automation reaches its limit. That order keeps an org maintainable by an administrator rather than only by the person who wrote the code.

A five step figure ordering Zoho tools from workflow rules to Blueprint, Functions, Client Script or widgets, and Zoho Creator apps.A five step figure ordering Zoho tools from workflow rules to Blueprint, Functions, Client Script or widgets, and Zoho Creator apps.
Zoho tools in the order to reach for them, lightest first.

What a Blueprint enforces that a workflow rule cannot

A workflow rule reacts after something changes. A Blueprint, in Zoho’s description, is an online replica of a business process: it settles the point at which a deal may move from one stage to the next, such as from negotiation to an approved discount, and adds validation and automation to each move. Users need the Manage Automation permission on their profile to build one.

  • Workflow triggers: a record created, edited or deleted, a date field, a score change or a note.
  • Workflow actions: email alerts, tasks, field updates, webhooks, functions, new records and messages to Cliq, Slack or Cisco Webex.
  • Scheduled actions that run at a set time after the trigger.
  • Blueprint: ordered stages with a checked move between each.
  • Organization ceiling: 2,500 workflow rules, 2,000 of them active.

Zoho’s workflow rules help lists those triggers and actions in full. Rules that send email deserve the most care, since a wrong condition reaches customers rather than staff.

When is a Function worth the scripting overhead?

When the job reaches outside the record. Zoho’s list of cases includes calling a third party REST API, sending data to an ERP, creating a Zoho Books invoice from a won deal, raising a Zoho Desk ticket from a CRM record, running scheduled cleanups and exposing CRM logic as an API for other systems and AI agents.

Starting on Zoho?Tell us how your team sells today and which systems must connect. You get a free proposal with the edition, the modules and the integrations mapped.

Get a free proposalTell us about a project you’d like help with.

Zoho developer work in Deluge, Python, Node.js and Java

Code inside Zoho CRM runs as Functions, a serverless platform where Zoho manages the servers, scaling and isolation. Each run gets its own environment, so one faulty script cannot slow the CRM or other scripts. A Zoho developer can write Functions in four languages, and the editor keeps the last 30 saved revisions for rollback.

Languages for Zoho CRM Functions
LanguageWhere Zoho says it fits best
DelugeNative CRM operations, links to other Zoho services and quick automations
PythonData processing, machine learning pipelines and teams that already write Python
Node.jsAsynchronous workflows and JavaScript teams
JavaEnterprise logic and teams with existing Java code

What is Deluge, and who should write it?

Deluge stands for Data Enriched Language for the Universal Grid Environment. It is Zoho’s own scripting language and links more than 50 Zoho products, with tasks such as invokeURL for calls to outside services and send mail for notifications. It is also the most deeply integrated language in CRM Functions, with direct access to Zoho’s CRM namespaces, so most Zoho logic starts there. Zoho built it with little jargon, which makes small scripts approachable for an administrator; larger ones still need a developer’s habits of testing and error handling.

Client Script and widgets inside the CRM screen

Client Script is JavaScript that runs in the user’s browser rather than on Zoho’s servers. It can validate a field as it is typed, fill in data based on conditions, show alerts and correct entries, and it needs the Enterprise or Ultimate edition plus developer permission on the user’s profile. Widgets are embeddable components built with Zoho’s JavaScript SDK, such as a dial pad or a panel showing figures from another system.

  • A won deal that creates an invoice in Zoho Books.
  • A website form that checks for an existing contact before creating a lead.
  • A scheduled Function that closes stale tasks each night.
  • A button that sends a quote request to an outside pricing service.
  • A widget that shows shipment status from a logistics system.
  • An endpoint that lets another system read approved CRM data.

Teams that want engineers added to their own bench for Zoho and other platforms can bring in dedicated developers, and AI features inside a CRM process are covered on our AI in software development page.

Connecting Zoho to the rest of the stack

Four routes connect Zoho CRM to outside systems, and most projects use more than one. The right mix depends on how fresh the data must be, how many records move each day and who will maintain the connection.

Ways to connect Zoho CRM to other systems
RouteBest forWhat to watch
Zoho FlowConnecting apps without code; Zoho lists more than 1,000 cloud and on premises appsEvery flow is one more moving part to monitor
Zoho CRM REST API, version 8Custom two way sync with an ERP, billing or order systemCredits, OAuth tokens and the 100 record batch size
Webhooks from workflow rulesPushing a change to another system the moment it happensDaily webhook call limits by edition
Functions calling outside servicesA lookup or update in another system in the middle of a processError handling and retries inside the script

Zoho Flow is Zoho’s integration platform, with triggers from polling, webhooks, emails and RSS feeds and an agent for reaching systems on a company’s own servers. For anything Flow cannot express, the Zoho CRM v8 APIs take over, and our API development and AI integration services teams build the outside end of the connection.

OAuth tokens and where they must never appear

The Zoho CRM API authenticates with OAuth 2.0. An access token is valid for one hour and only for the scopes it was granted, and a refresh token lasts until the user revokes it. Zoho warns never to expose an access token in public forums, public repositories or client side code such as a website’s HTML or JavaScript. Tokens therefore live on a server, and each integration gets its own client with the narrowest scopes it needs.

Composite, bulk and notification calls

Zoho’s v8 API includes a Composite API that combines up to five calls in one request, bulk APIs that push and pull data asynchronously, notification APIs that report data changes as they happen and a query API that reads records with SQL style SELECT statements. Picking the right one is most of the difference between an integration that fits the credit budget and one that starves the rest of the org.

  • Name the system of record for every synced field.
  • Decide which direction each field flows.
  • Log every failed call with the record ID and the error.
  • Retry with a growing pause instead of hammering the API.
  • Alert a named person when a sync stops.
  • Test the sync against a trial or sandbox before the live org.

Moving into Zoho CRM from spreadsheets or another CRM

A move into Zoho is mostly a data job. Each edition caps how many records one import batch can carry, from 1,000 on Free to 200,000 on Ultimate, and import history stays visible for 60 days, so large moves run in planned batches with a log of what loaded.

Eight checks to finish before the first import into Zoho CRM.Eight checks to finish before the first import into Zoho CRM.
A drawn card of eight checks before importing into Zoho CRM: field map, owners, duplicates, picklists, relationships, history, batch size and rehearsal.

Rehearsing the import in a sandbox

Enterprise includes three configuration sandboxes and two that can hold data, and Ultimate seven and three. A rehearsal load in a data sandbox shows broken relationships and mismatched picklists before the live org sees them. On editions without one, the rehearsal runs on a small slice of real records that is deleted and reloaded until it comes out clean.

Duplicates, owners and history

Duplicates are cheaper to merge in the source file than inside Zoho. Every record also needs an owner who still works at the company, or the assignment rules and reports built afterward start from a false picture. Decide early how much history moves: open deals and recent activity usually earn their place, while years of closed tickets often belong in an archive.

  • Freeze edits in the old system during the final load.
  • Load accounts before contacts, and contacts before deals.
  • Spot check 20 records by hand after each batch.
  • Keep the old system read only for an agreed period.
  • Record which batch each record arrived in.

Moves that also shift servers or websites sit with our cloud migration and website migration teams.

Custom apps on Zoho Creator when CRM modules run out

Zoho Creator is Zoho’s application platform. Zoho describes four uses: internal tools that automate approvals and tracking, portals that give customers, vendors and other outside users one point of access, core systems built around a business’s own process, and extensions of existing Zoho or third party systems. Apps built on the web get native iOS and Android versions automatically.

Custom module or Creator app?

A custom module fits when the new record type belongs to the sales and service story, such as properties, projects or contracts that hang off accounts and deals. A Creator app fits when the work has its own users, screens and logic, such as a vendor portal, a field inspection form or a stock tool that sales only reads.

  • Custom module: shares CRM users, reports and permissions.
  • Custom module: counts toward the edition’s module limit.
  • Creator app: its own users, including outside users through portals.
  • Creator app: phone apps without separate builds.
  • Either one: connected to the CRM with Deluge and the API.

Larger builds sit with our low-code app development, web portal development and inventory software teams, and the trade between configuring a platform and building from scratch is weighed on our page on custom software versus off the shelf.

Reports and dashboards that tie Zoho to revenue

Zoho CRM’s editions include standard and custom reports, scheduled reports and custom dashboards, with 100 custom reports on Standard and no cap from Professional upward. The reports leadership trusts depend on decisions made much earlier: stage definitions, required fields and the source recorded on every lead.

Connecting won deals to marketing spend

Lead source fields filled at capture, campaign data passed from forms and ad platforms, and honest closed won dates are what let a dashboard show revenue by channel. Without them, reports count leads instead of money. Our marketing analytics and Google Analytics consulting teams connect the website side.

  • Pipeline by stage and owner.
  • Win rate by lead source.
  • Days spent in each Blueprint stage.
  • Revenue by campaign and channel.
  • Overdue tasks by owner.
  • Credit use and failed syncs for the administrator.

Reporting that has to blend CRM data with finance or operations systems is built by our dashboard development team.

Testing changes before they reach the live org

Changes to a Blueprint, a workflow rule or a Function can touch every record that meets their conditions the moment they go live. Testing first, on a sandbox where the edition has one and on a few marked test records where it does not, keeps a configuration slip from emailing customers or reassigning a pipeline.

What to test before switching a Blueprint on

Run a record through every transition, including the ones that should be refused. Check that required fields block the move, that the right people see the right buttons, and that records already partway through the process when the Blueprint goes live land in a sensible stage.

  • Every transition, forward and back.
  • Moves that must be refused.
  • Records already open on launch day.
  • Workflow rules that fire on the same fields.
  • Function errors and their log entries.
  • Email alerts sent to test addresses only.
45+: Apps in Zoho One. Licensed for every employee in the business.
50+: Zoho products Deluge links. Zoho's own scripting language.
1 hour: Life of an API access token. Refresh tokens last until revoked.
100: Records per write call. Insert, update or upsert in one request.
5: Calls in one Composite request. Combined into a single API call.
30: Function revisions kept. Restore any of them from the editor.

Zoho org that nobody trusts?Send a list of the rules, Functions and integrations you know about. The free proposal covers what to repair, what to retire and what to rebuild.

Get a free proposalTell us about a project you’d like help with.

Running Zoho after launch

A Zoho org keeps changing after go live: new fields, new rules, new staff and new integrations. Light, regular administration costs far less than a rebuild two years later, when nobody remembers why a rule exists.

Who owns the org day to day?

Name an internal administrator with the Manage Automation permission for small changes, and route anything involving code, integrations or Blueprints to the people who built them. Keep a written register of every rule, Function and integration with its owner and purpose.

  • Monthly: review API credit use and failed syncs.
  • Monthly: merge new duplicates.
  • Quarterly: retire unused fields and rules.
  • Quarterly: match user licenses to active staff.
  • Before each release: test on a sandbox or test records.

When a Zoho consultant stays on after launch, agree the change routine in writing: who requests a change, who approves it and how each release is tested. Marketing work that runs from the same data, such as nurture emails and lead scoring, connects to our marketing automation agency work.

What Zoho consulting and development costs

Zoho bills its licenses directly; consulting and development are separate. The bands below are market figures for CRM and integration work in the US, from the typical low to the published high. Small automation jobs sit at the bottom, and custom integrations or Creator applications sit far higher.

Published US price bands (market ranges only)
WorkTypical low to published high
CRM workflow automation project$2,000 to $8,000 per project
CRM to ad platform integration$3,000 to $12,000 per project
Full lifecycle automation build$4,000 to $18,000 per project
Ongoing CRM and automation support$1,500 to $8,000 a month
Custom integration or internal tool$30,000 to $100,000 per project
US contract developer rates$100 to $200 an hour
Horizontal range bars for CRM workflow automation, CRM to ad platform integration, a full lifecycle automation build and a custom integration or internal tool.Horizontal range bars for CRM workflow automation, CRM to ad platform integration, a full lifecycle automation build and a custom integration or internal tool.
Published US price bands (market ranges only) for CRM automation, integration and internal tool projects, typical low to published high.

Progression’s price for Zoho work depends on scope, is set in the written proposal and is subject to change. Zoho’s own license fees, add-on API credits and extra storage are billed by Zoho and sit outside the project.

Pricing depends on scope and is confirmed in a written proposal. Published prices are subject to change.

How Progression’s Zoho team works with yours

Progression’s consultants and developers configure Zoho CRM and Zoho One, write Deluge and other Functions, build integrations on the Zoho API, move data in from other systems and build Creator apps. The team is based in New York, works with companies across the US by video and shared screens, and holds on-site sessions on request.

What this page leaves out: the Progression Method, proprietary and reserved for clients. Reach out to learn more

Frequently asked questions

What work does a Zoho consultant take on?
A Zoho consultant turns a company’s sales, service and operations process into a working Zoho setup: modules and fields, Blueprint stages, workflow rules, integrations, data moves and, where needed, custom code.
How is a Zoho consultant different from a developer on Zoho?
The consultant designs the setup and configures what Zoho offers without code, while the developer writes what configuration cannot do, such as Deluge Functions, Client Script, widgets and API integrations. Most projects need both.
Which Zoho CRM edition includes Blueprint?
Professional and higher. Zoho’s feature comparison lists 3 Blueprints on Professional, 50 on Enterprise and 100 on Ultimate, and none on Free or Standard.
How many custom modules can Zoho CRM hold?
It depends on the edition: 10 on Standard, 25 on Professional, 200 on Enterprise and 500 on Ultimate, according to Zoho’s feature comparison.
What are Zoho CRM API credits?
They are Zoho’s measure of API use across a rolling 24 hour window. Most calls cost one credit, heavier operations cost more, and each org’s pool depends on its edition and number of user licenses.
Why does our Zoho integration keep running out of API credits?
Usually because it sends records one at a time or polls for changes. Batching up to 100 records per call, using notification APIs and moving large loads to bulk jobs cut credit use sharply.
Is Deluge hard to learn?
It is one of the gentler languages to start with, since Zoho designed Deluge as a scripting language with little jargon. Larger scripts still need a developer’s discipline in testing and error handling.
Can Zoho CRM run Python or JavaScript?
Yes. Zoho CRM Functions run Deluge, Python, Node.js and Java, and Client Script runs JavaScript in the browser on the Enterprise and Ultimate editions.
Should we buy Zoho One or only Zoho CRM?
Zoho One makes sense when finance, support, HR or projects will also run on Zoho, since it bundles 45 or more apps and is licensed for every employee. A sales team that only needs a CRM usually starts with Zoho CRM.
Can you move our records from another CRM into Zoho?
Yes. The move is mapped field by field, rehearsed on a sandbox or a small slice of records, and loaded in batches sized to the edition’s import limit, from 20,000 records a batch on Standard to 200,000 on Ultimate.
Does Zoho CRM have a test environment?
Yes, on Enterprise and Ultimate. Enterprise includes three configuration sandboxes and two that hold data, and Ultimate includes seven and three.
What can Zoho Flow connect to?
Zoho says Flow connects more than 1,000 cloud and on premises apps, including Zoho apps, third party apps, AI platforms and ERP systems, with most flows built without code.
When does a Zoho Creator app beat a custom module?
When the work has its own users, screens and logic, such as a vendor portal or a field inspection tool. Record types that belong to the sales story usually stay as custom modules.
How long does a Zoho CRM API access token last?
One hour. A refresh token issues new access tokens and lasts until the user revokes it, and Zoho warns never to place access tokens in client side code.
Can Zoho connect to our ERP or accounting system?
Yes, through the REST API, Zoho Flow or Functions. Zoho lists sending data to ERP systems among the standard uses of Functions.
Can a won deal in Zoho create an invoice automatically?
Yes. Zoho’s own example of a Function is creating a Zoho Books invoice from a won deal, and the same pattern reaches outside billing systems through their APIs.
How much does a Zoho consultant cost?
Published US bands run from $2,000 to $8,000 for a CRM workflow automation project up to $30,000 to $100,000 for a custom integration or internal tool, and $100 to $200 an hour for US contract developers. Progression sets its price in the written proposal.
Are Zoho license fees part of the project price?
They are billed separately by Zoho. Licenses, add-on API credits and extra storage go on the Zoho invoice, and consulting and development go on the project.
Can you fix a Zoho setup that someone else built?
Yes. The work starts with an inventory of modules, fields, rules, Functions and integrations, then retires what nobody uses and repairs what breaks.
Can Progression’s Zoho team work with a company in another state?
Yes. The team is based in New York and works with companies across the US by video sessions and shared screens, with on-site workshops on request.
Can a Zoho developer join our in-house team for a project?
Yes. Progression’s Zoho developers can work inside your team’s own tools and release routine for a scope set in the written proposal.

Starting on Zoho?Tell us how your team sells today and which systems must connect. You get a free proposal with the edition, the modules and the integrations mapped.

Get a free proposalTell us about a project you’d like help with.

Get a free marketing proposal

Tell us what you are trying to grow and we will come back with a plan, not a pitch deck. Same-day reply on weekdays.

Privacy Preferences
When you visit our website, it may store information through your browser from specific services, usually in form of cookies. Here you can change your privacy preferences. Please note that blocking some types of cookies may impact your experience on our website and the services we offer.
Contact Us