esköre™

InsightsCRM Development12 min readNovember 15, 2026

Custom CRM vs Zoho for Small Business: Which to Choose

Zoho or a custom CRM? This guide compares three-year costs, go-live times, per-user fees, limits and data ownership, so you can pick the route that fits your team. Eskore tells you which fits before any money changes hands.

CRM Development at Eskore
Photo by Unsplash on Unsplash

A new enquiry comes in through the website form and lands in a shared inbox. Someone forwards it to a salesperson, who copies the details into a spreadsheet. The quote goes out three days later with the wrong product code, and the prospect has already spoken to a competitor. That is lead leakage. When you compare custom CRM vs Zoho for small business, lead leakage matters more than the monthly seat fee.

This article is for owners, COOs and operations managers at 10 to 200 person businesses in New York, Austin, Raleigh, Denver and the GTA. You may already pay for Zoho, be trialling it, or be weighing a custom CRM because leads and quotes sit in inboxes and spreadsheets. We cover the three-year cost, how long each option takes to go live, where Zoho stops being enough, and who owns what when you leave. Eskore configures Zoho when it fits and builds when it doesn’t, and we tell you which before any money changes hands. Never lose a lead in someone’s inbox again.

Custom CRM vs Zoho for small business: quick answer

Find your situation in the first column. Most small businesses land in the first two rows.

Your situation Best fit Why
Standard pipeline, small sales team, the same steps for most deals Zoho Contacts, deals, activities and reports already exist. Configuring is faster than building.
Quoting and approvals that break the standard flow Hybrid or custom Pricing rules and multi-step sign-off are where built-in logic starts to strain.
Field staff, subcontractors or customers who need access Hybrid or custom Per-seat pricing and portal access add up quickly.
The process changes every quarter Custom or hybrid You change code you own, rather than working around a vendor’s rules.
You need to own the code and admin accounts outright Custom In a SaaS CRM you rent access. In a custom build you hold the code and the accounts.

Zoho is usually the faster start. Custom is usually the better fit once the process is the business.

The table is a starting point, not a verdict. The one-week checklist near the end tests it against your own process.

What Zoho and a custom CRM cost over three years

Licence price is the easiest number to compare and the least useful on its own. A three-year view, with recurring costs on both sides, is closer to the real decision.

Zoho publishes its CRM prices in US dollars per user per month on its pricing page. The rates used here, on annual billing, are $14 for Standard, $23 for Professional and $40 for Enterprise. On monthly billing they are $20, $35 and $50. Plans and rates change, so confirm them on the live page before you budget. Local taxes are extra.

Zoho edition (annual billing) Per user per month Ten users, one year Ten users, three years
Standard $14 $1,680 $5,040
Professional $23 $2,760 $8,280
Enterprise $40 $4,800 $14,400

A custom CRM has no per-seat licence, but it has its own recurring costs. A written scope should cover:

  • Build: modules, screens, workflows, integrations and data migration, priced as a fixed fee from that scope.
  • Hosting: the servers or cloud environment the system runs on.
  • Support and security updates: patches, dependency upgrades and fixes after launch.
  • Changes: new fields, reports and workflows as the process moves.
  • An internal owner: the person who approves changes and holds the admin relationship. This is time rather than a line item, but it is real.

We don’t publish a custom build price in this article. A figure without a scope is a guess. Our custom software development scoping produces a written scope, a fixed price and a launch date before any work starts. For how fixed pricing holds up through the build, see our guide to fixed price custom software development.

Worked example: ten users in Austin or Toronto

Take a ten-person sales and operations team, planned over three years. The Zoho figures come from the table above. The custom column stays as scope items until a written scope exists, because we won’t give you a number we haven’t scoped.

Cost over three years (USD) Zoho Standard Zoho Professional Zoho Enterprise Custom build
Licences, annual billing $5,040 $8,280 $14,400 None
Build None None None Fixed price from written scope
Hosting Included in licence Included in licence Included in licence Set out in scope
Support, security and changes Vendor-managed Vendor-managed Vendor-managed Set out in scope
Middleware and add-ons Not included Not included Not included Set out in scope

An Austin, Denver or Raleigh business reads this in US dollars. State sales tax varies by state, and whether it applies to software depends on where you are. A Toronto business converts the US figures at the exchange rate on the day it runs the numbers, then adds HST or the provincial equivalent. As an illustration only, at a hypothetical rate of 1.40 Canadian dollars to one US dollar, the US$5,040 Standard total would be C$7,056 before tax. That rate is not a quote. Toronto owners comparing build and buy costs may also find our guide to custom CRM development in Toronto useful.

Read the table by asking two questions. For Zoho: do you need add-ons or middleware the licence doesn’t cover? For custom: does the written scope cost less over three years than the workarounds it would replace?

The costs a subscription does not show

The licence is rarely the whole Zoho bill. Four costs tend to arrive later.

Middleware. When Zoho doesn’t talk to your accounting, quoting or email tools, a connector such as Zapier or Make fills the gap. These are usually priced by task or volume, so they grow with the business.

Manual reconciliation. Leads copied from a web form into the CRM, then into an invoice, then into a month-end spreadsheet. If two people each spend three hours a week on this, that is six hours a week, or about 312 hours a year, and nobody bills for it.

Workaround upkeep. Custom fields, shadow spreadsheets and temporary workflows built to get around a limit. Each one needs an owner, and each one breaks when someone changes something else.

Add-ons and integration fees. Extra modules, connectors and partner implementation work, all outside the headline price.

A custom system has recurring costs too: hosting, security updates and an internal owner. Put them in the scope rather than treating them as a surprise. The practical test is whether the recurring cost of the system is lower than the recurring cost of the workarounds it removes.

How long each option takes to go live

Configuring a standard pipeline on an existing platform is usually a matter of days or weeks. Treat that as a planning estimate, not a promise. Stages, fields, basic automations and reports are configuration work. Importing data, cleaning it and training the team often take longer than the set-up itself.

A custom build is measured in months for most scopes. The exact time depends on the modules, integrations and data migration in the scope, and we don’t give a timeline without one. We agree the scope, the fixed price and the launch date in writing before work starts, so the date is a commitment rather than a hope. You can see the kinds of projects we’ve delivered on our work page.

There is a middle route that lowers risk. Configure the platform first so the team is live on the standard pipeline, then add custom work for what the platform can’t model, such as quoting rules or approvals. You get a working system early, and the custom work is built against real use rather than a guess. A delay in the custom part doesn’t hold up the sales team.

Where Zoho hits its limits

This section is not a case against Zoho. It lists the points where a standard platform meets a process it wasn’t designed for. Check each one against Zoho’s current documentation for your edition before you commit, because limits change by plan.

Custom fields. Zoho limits the number of custom fields per module, and the limit depends on your edition. A product with many attributes, stored on one record, can hit that ceiling. Check the figure for your edition before you assume the design fits.

Automation and calculations. Workflows and custom functions run within platform limits. Heavy logic is where to check first: a quote built from many line items, volume discounts and approval thresholds, for example. If a calculation can’t finish within the limit, the workaround is usually a spreadsheet, which brings back the handoffs you were trying to remove.

Multi-step approvals. A quote that routes through sales, finance and operations, with rules that depend on deal size and product mix, is where built-in logic strains first. The process still runs, but the workarounds multiply.

For each point, ask whether the limit affects a step you run every week. If it does, you have a fit problem, not a configuration problem.

When per-user pricing gets expensive

Per-seat pricing is clean when everyone uses the CRM every day. It gets expensive when many people need occasional access: field technicians updating jobs from their phones, subcontractors who need to see a deal, or customers logging into a portal. A vendor guide on Zoho makes the same point about large numbers of occasional users.

Take an illustrative Denver services firm with ten full-time sales staff and thirty field technicians who update jobs a few times a week. Thirty occasional users on Standard, billed annually, cost $5,040 a year in licences alone. That is three times what the ten full-time users cost at the same tier, and the technicians may use the system far less. If customer or subcontractor access is the main driver, it is a different kind of build. Our custom software development team can scope it separately, and our guide to customer portal development cost in Canada sets out what drives that quote.

Who owns the code, data and admin accounts

“You own the code and accounts” hides four separate things.

  1. Source code and repositories. In a SaaS CRM, the platform code belongs to the vendor. In a custom build, the code you pay for is handed to you.
  2. Customer data and export rights. Your data is yours in both cases, but ease of export varies. Check which formats exist and how often you can run them.
  3. Admin logins, domains and email connections. This is where owners most often get caught out. Who holds the super-admin login? Who controls the domain and email-sending settings? These should sit in accounts you control.
  4. The hosting relationship. A custom system runs somewhere, under a contract, a bill and a named person responsible for it.

With Zoho you rent access. The platform, the admin layer and the hosting belong to Zoho, and your configuration lives inside it. With a custom build from Eskore, you own the code and the accounts.

Before work starts, ask for the handover list in writing. It should name the repositories, admin credentials, domain and email records, and hosting access that transfer to you at launch. Ask any builder for the same list, including us.

Leaving Zoho without losing history

Many businesses start on Zoho and later move off it. A clean exit is planned, not improvised.

  1. Export. Pull contacts, accounts, deals, activities and attachments. Check Zoho’s data migration overview for current file and volume limits before you plan the move, since they determine how you split the export.
  2. Map fields and modules. Every Zoho field needs a home in the new system. Custom fields are where data most often goes missing.
  3. Deduplicate. Don’t assume the migration tool will clean up duplicates. Check what it does with duplicate records in Zoho’s documentation, and deduplicate before you import, not after.
  4. Rebuild automations. Workflow rules, scheduled actions and custom functions are usually rebuilt in the new system rather than copied across. List every active automation before you start, because this is the part owners most often forget.
  5. Run in parallel. Keep old and new systems side by side for a set period. Reconcile new leads and quotes daily before you switch the old system off.

Most owners underestimate step four. The data moves; the logic has to be rebuilt. Our CRM development and setup service treats migration as its own piece of work, with mapping, deduplication and rebuilt automations written into the scope. If the spreadsheets are doing the real work, our guide to modernising legacy software for a small business covers how to move without a risky rewrite.

The third path: configure, hybrid or build

Many comparisons present this as Zoho or custom. In practice there are three routes.

Configure an off-the-shelf platform. HubSpot, Pipedrive, Zoho or Salesforce. Quick to start, and the vendor runs the platform. The limits described above apply to whichever you pick. HubSpot’s custom objects depend on plan tier, so check its current pricing page before you assume a feature is included.

Build custom software. You own the code, the logic matches how you work, and you carry the running costs described earlier. This is the route for a process that is itself the competitive advantage.

Run a hybrid. The standard pipeline (contacts, deals, stages and basic reporting) stays in a platform. Operational work sits in custom code: quoting rules, approvals, portals and reporting that combines data from several tools. The two connect through the platform’s API or a middleware tool such as Zapier or Make. If quoting, inventory and finance also run on separate tools, our ERP solutions work covers bringing them into one system.

The hybrid often fixes lead leakage without rebuilding everything. The sales team keeps a familiar pipeline, and the step that fails, such as a quote stuck in someone’s inbox, gets the custom treatment. Lead capture on your website feeds the system, and our web development work covers that side.

Which route fits depends on the steps you map in the checklist below, not on a default answer.

A one-week checklist for the decision

You can run most of this internally. Use a shared document and give it a week.

  • Map the path from first enquiry to paid invoice. Include the steps that happen in someone’s head, not just the ones on the process chart.
  • Count the handoffs. Note every point where a lead, quote or invoice moves by email or spreadsheet rather than inside a system.
  • List the weekly reports. Write down each report the owner or manager checks, and where its numbers come from.
  • List the workflows that would need scripting. Multi-step approvals, custom pricing and conditional routing belong here.
  • Decide who holds admin access. Name the people who will hold the admin logins, domain and email settings, and make sure at least two of them can act.

If most steps are standard, configure. If the process is the product, build. If your answer sits in between, the hybrid usually fits.

Custom CRM vs Zoho for small business: talk to us first

If your handoff count is higher than you’d like, the answer to custom CRM vs Zoho for small business is worth a conversation before you switch. We’ll look at your process, tell you whether Zoho fits, and say plainly when it doesn’t. Whichever route you choose, you’ll get a written scope, a fixed price and a launch date before work starts, and you’ll own the code and the accounts. One team covers the software, the design, the cloud set-up and the marketing, with offices in Toronto, Thornhill, London and New York.

Book a free 30-minute scoping call and we’ll tell you which route fits your team.

Questions

Need help with this?

Talk to our crm development team.