How much does a custom CRM cost for a small business in the US? A custom CRM for a small US business usually costs from about $18,000 for a focused build, and $45,000 to $110,000 for a mid-scope build with quoting, reporting and integrations. Those are vendor-published ranges, not Eskore prices, and they only mean something once you know the inputs behind them. This guide is for owners and operations leads in New York, Austin, Raleigh, Denver and elsewhere in the US who are weighing a custom build against configuring HubSpot, Zoho, Salesforce or Pipedrive. It covers the assumptions behind a budget, four cost tiers, ongoing costs, a three-year comparison, and a worked example of what slow follow-up costs. All figures are in US dollars. Where a number is illustrative, we say so.
How much a custom CRM costs for a small business: the short answer
Rorixtech's 2026 guide to custom CRM development cost puts a focused build, with contacts, a pipeline and tasks, at $18,000 to $45,000. The same guide puts a build that adds quoting, scheduling and reporting at $45,000 to $110,000, and starts platform builds near $110,000. The Rorixtech breakdown is the source for these three bands. Headline ranges run wider still. One 2026 guide from 0arch.io is titled "How Much Does It Cost to Develop a Custom CRM in 2026? ($15K to $150K)".
The three bands are defined by scope, not just price:
- Focused: one team, a few core modules, few or no integrations.
- Mid-scope: more modules, plus quoting, scheduling, reporting and some integrations.
- Platform: several teams or regions, heavy integration with existing systems, or access and audit rules across divisions.
A quote can land anywhere in these bands. That is why the inputs matter more than the band.
These figures are vendor-published and directional. They are not Eskore pricing. We don't give a single number for a custom CRM before we know the users, modules and integrations. The rest of this article shows how to work those out.
For most teams of 5 to 20 people, the practical first step is to configure an existing platform. A custom build makes more sense when your workflow is what sets you apart and staff are working around the tool in spreadsheets, or when per-seat costs would overtake a build within three years. GTA readers who want Canadian-dollar budgeting will find that covered in our Canadian CRM cost guide. This article stays on US pricing.
What the price depends on: six assumptions every quote should state
Most published ranges hide their inputs. Before you compare any quote, including ours, check that it states these six things.
- Users and roles. How many people log in, and what each one can see and change. A sales rep, a branch manager, a bookkeeper and a client account lead need different permissions. Role design takes longer than most owners expect.
- Modules. Contacts, pipeline, quoting, invoicing, reporting, scheduling and a client portal are each separate pieces of work. Each adds design, build and testing.
- Integrations. Email, phone, website forms, accounting software, and automation tools such as Zapier or Make. Every connection needs field mapping, error handling and monitoring.
- Data migration. Moving records from spreadsheets or an old CRM. Volume matters, but quality matters more. Duplicates, missing owners and inconsistent deal stages take real time to clean.
- Training and rollout. Time for staff to learn the system, and time for old habits to stop.
- Hosting and support. Where the system runs, who watches it, and how quickly someone fixes it when it breaks.
The comparisons below use a baseline: eight active users across sales, operations and management; three core modules (contacts and pipeline, quoting, reporting); two integrations (email and accounting); about 10,000 contact records to migrate from spreadsheets; half a day of training per team; and cloud hosting with business-hours support. This is an assumption for illustration, not a quote.
Four cost tiers: configure, extend, build or platform
| Tier | Typical scope | Typical timeline | Ongoing cost | Best fit |
|---|---|---|---|---|
| Configure a platform | Setup, pipeline design, migration and automations on HubSpot, Zoho, Salesforce or Pipedrive | Weeks for a standard setup, longer with heavy migration | Per-seat subscription plus paid add-ons | Teams with a standard sales process |
| Configure and extend | Platform plus custom layers for quoting, client portal, lead routing or reporting, connected through Zapier, Make or custom code | Several weeks to a few months | Subscription plus upkeep of the custom layers | Teams where a platform fits most of the process |
| Custom build | Purpose-built CRM on a standard web framework and database | Months, rising with scope | Hosting, support, maintenance and changes; no vendor per-seat fee | Specialised workflows, or staff working around the tool in spreadsheets |
| Platform or enterprise | Multi-team, multi-region or heavy integration estate | Many months, usually phased | Larger support and infrastructure commitment | Multi-site operators joining several existing systems |
Timelines run from weeks to months and rise with each tier.
Configure an existing platform first
On HubSpot, Zoho, Salesforce or Pipedrive, the cost has two parts: the subscription and the work to set the system up. Setup covers pipeline stages, custom fields, permissions, email sync, migration and automations. In year one, that labour is often the bigger number.
Subscriptions are charged per seat, and several platforms sell features such as quoting and some reporting as paid add-ons. The headline seat price is rarely the price you pay. Check current pricing on each vendor's own pricing page before you budget. Third-party price roundups often disagree with each other, so don't build a budget from one of them.
Where a platform fits, we scope the configuration work as part of our CRM development service. That includes pipeline design, permissions, migration and automations on platforms such as HubSpot, Zoho, Salesforce and Pipedrive. For a team with a standard sales process, this is usually the most direct route to a working pipeline.
Extend a platform with custom layers
This is the middle option, and it is the one most small firms overlook. You keep the platform for contacts, email and the basic pipeline. Then you add the parts it does poorly: quoting with your own rules, a client portal, lead routing by territory or service line, or reporting that matches how you measure work.
These layers connect through Zapier, Make or custom code, and through telephony and SMS services for calls and texts. Where the bottleneck is repetitive manual work, part of the job may suit our AI automation service.
The cost sits in the connecting layer rather than in a new system. You also take on upkeep. When the platform changes its interface or its API, the custom layer may need to change with it. Plan for that from the start.
Build a custom CRM when the workflow is the product
A custom build pays back when your process is what makes you competitive, and the off-the-shelf version forces you to work around it. Three signs point that way:
- Your intake, referral or dispatch process differs from the one the platform assumes.
- Staff are running parallel spreadsheets because the tool doesn't fit how they work.
- Per-seat costs grow faster than headcount, so every hire makes the platform more expensive.
A custom build is designed around your workflow, so you don't pay for features you never use. Our custom software development work follows the same principle: the software is built around your process, not the other way round. A build is also a system you have to maintain. If your process is generic, a build is usually money spent on something a platform already does well. Examples of past projects are on our case studies page.
Platform and enterprise builds
Platform builds cover multi-team, multi-region or heavily integrated operations. They involve role-based access across divisions, audit requirements, and several existing systems to join. They are rarely the right first step for a 10 to 50 person firm.
If the operation also runs inventory, finance and HR across several sites, look at ERP solutions alongside the CRM. If you think you need a platform build, book a scoping call first and ask for the work to be split into phases. That way you can see the cost of each phase before committing to the whole.
What drives the price up or down
Seven things move the number most:
- Feature count. Each module adds design, build and testing.
- Integrations. Each connection adds mapping, error handling and monitoring.
- User roles and permissions. More roles mean more rules to design and test.
- Migration volume and quality. Clean data moves quickly. Messy data can take weeks.
- Reporting depth. A dashboard of five numbers is a different job from a full reporting suite.
- Client portal. A separate login for clients, with access control and notifications, is a substantial piece of work. We usually scope it as part of our web development work. For how portal costs break down in Canada, see our customer portal cost guide.
- Team location and rates. Hourly rates vary by team and location. A lower hourly rate on a vague scope usually costs more in the end, so compare quotes on scope rather than rate.
Consider a 12-person property management firm in Denver. One quote covers an internal pipeline and reporting. Another covers the same pipeline plus a tenant-facing portal with payments and maintenance requests. Both are described as "a CRM," and the second can cost several times as much. Compare quotes on what is in the scope.
Eskore has offices in Toronto, Thornhill, London and New York. Whoever you hire, ask for the scope in writing before you compare numbers.
Ongoing costs of a custom CRM after launch
The launch is not the end of the bill. Budget for these every year:
- Hosting. The servers or cloud services that run the system.
- Licences and third-party services. Platform seats if you configure, or usage-based fees for email, SMS, mapping and similar services if you build.
- Support. Someone to answer when a user can't log in or a sync stops.
- Maintenance and security updates. Frameworks, libraries and plugins need patching. This is the cost owners most often forget.
- Changes. A new field, a new report, a new integration.
Plan upkeep as a fixed annual line from the day you launch. The model later in this article assumes upkeep at 20% of build cost a year. That is our planning assumption, not a market benchmark. The support terms in your written scope should replace it, and they should state what is covered, the response times and the annual cost.
A custom build needs a support agreement from day one. Otherwise nobody owns the system when something breaks at 4pm on a Friday. Because you own the code and the accounts, you choose who maintains it, including us or another team.
Custom build versus a per-seat subscription over three years
The comparison below states every input. The subscription and build figures are illustrative. They are not vendor price lists.
Assumptions
- Subscription: $75 per seat per month, billed annually, over three years, plus a one-off $5,000 for set-up and onboarding. The $75 is an assumed blended price for illustration. We have not used published vendor list prices. Paid add-ons are excluded.
- Custom build: a one-off $50,000, which sits in the $45,000 to $110,000 mid-scope band cited above. Upkeep at 20% of build cost a year, or $10,000 a year for three years. Build cost does not rise with users in this model, and heavier hosting at high usage is ignored.
| Three-year cost | 5 users | 15 users | 40 users |
|---|---|---|---|
| Subscription, including set-up | $18,500 | $45,500 | $113,000 |
| Custom build, one-off | $50,000 | $50,000 | $50,000 |
| Custom upkeep, three years | $30,000 | $30,000 | $30,000 |
| Custom build, three-year total | $80,000 | $80,000 | $80,000 |
| Lower three-year cost | Subscription | Subscription | Custom build |
On these inputs, break-even sits at about 28 users. Below that, the subscription costs less over three years. Above it, the build does.
Break-even moves with the build cost. At $35,000, which sits in the focused band, upkeep is $7,000 a year and the three-year build total is $56,000. Break-even falls to about 19 users. Before you use either figure, run the same sum with your own user count, seat price and build quote.
The table leaves out three things. First, the subscription excludes add-ons, which can change the total a lot. Second, a custom build can replace several tools rather than one, such as a spreadsheet, a reminder app and a portal. If it does, count those costs as well. Third, the table assumes the build delivers what was scoped. The value of a system that matches your process is hard to put into a spreadsheet, but it is real.
What slow follow-up costs a small business
This example is illustrative. The figures are assumptions, not a forecast for your business. It uses a 10-person service firm in Austin.
Assumptions
- 30 new leads a month from the website and phone.
- An average deal value of $3,000 in revenue.
- Without a pipeline, 40% of leads get a first follow-up within one working day, because they sit in inboxes or get passed around in chat.
- With a pipeline that assigns leads, sends reminders and updates itself, 80% get a follow-up within one working day.
- Leads that get a timely follow-up close at 10%.
- A 50% gross margin, to turn revenue into profit.
The arithmetic
- Extra leads followed up in time: 30 × (80% − 40%) = 12 a month.
- Extra deals: 12 × 10% = 1.2 a month.
- Extra revenue: 1.2 × $3,000 = $3,600 a month, or about $43,200 a year.
- Extra gross profit at 50%: about $21,600 a year.
For comparison, the 15-user subscription in the table above averages about $15,000 a year, including set-up. On these assumptions, the extra gross profit covers it.
This is a model, not a promise. If your close rate on follow-ups is 3% rather than 10%, the answer changes. The point holds even on conservative numbers: the revenue at risk from slow follow-up can exceed the cost of the tool. To run your own figures, have your team log every new lead for two weeks. Record when it arrived, when it was first contacted, and whether it closed. Then put your numbers into the same arithmetic.
When not to build a custom CRM
A custom CRM is not the right answer for every small firm, and we'd rather say so.
If you have a handful of sales reps selling one service through a standard pipeline, a configured HubSpot, Zoho or Pipedrive will usually do the job for less. If your process itself is unclear, a new system will only automate the confusion, so fix the process first. And if nobody has budget for upkeep, don't build. A system nobody maintains becomes a spreadsheet again within a year.
What to do instead:
- Configure first. Set up a platform properly, with clean stages, permissions and imports.
- Measure the workarounds. For four weeks, have staff log every spreadsheet, double entry, manual reminder and missed follow-up.
- Decide from the log. If the same problems keep recurring because the platform can't model your process, you have a case for extending or building. If the problems are about training, permissions or setup, you have a configuration problem, and a build won't fix it.
If the real system is an old in-house tool you'd rather not replace in one risky push, a staged approach is usually better. Our custom software development team can scope that path, and our legacy modernisation guide sets out the options.
What should be in a fixed-price CRM quote before work starts
When you compare vendors, check that the quote includes the following:
- Written scope. Modules, roles, screens, and what is explicitly out of scope.
- Fixed price. With change requests priced before they are carried out. For how fixed-price scopes handle change, see our fixed-price custom software guide.
- A launch date tied to milestones you can check.
- A named list of integrations, showing which systems each one connects to and who holds the credentials.
- A migration plan. Which data moves, what gets cleaned, and who signs it off.
- Training. How many sessions, for whom, and what materials you receive.
- Support terms. Response times, support hours, what maintenance covers, and the annual cost.
- Ownership. Confirmation that you own the code, repositories, domains, hosting and third-party accounts.
A quote missing these is an estimate with a wider range. Compare vendors on what is in the scope, not on the day rate.
Eskore provides written scope, a fixed price and a launch date before work starts. You own the code and the accounts.
How to budget for a custom CRM in the US
- List your users and roles. Count who logs in daily, weekly and occasionally, and what each person needs to see.
- Write down the three workflows that matter most. For example: lead to quote, quote to job, and job to invoice.
- Choose the tier. Configure, extend or build, using the workaround log from the section above.
- Budget migration and training as separate lines. Migration usually takes longer than people expect, and training is what makes the system stick.
- Reserve upkeep every year. Use the support terms in your written scope. Until you have them, the model above uses 20% of build cost as a placeholder.
- Set a review at six months. Check adoption, the number of remaining workarounds, and cost against plan. If people aren't using the system, fix that before adding features.
Get a custom CRM cost for your team
If you want a real answer to how much a custom CRM costs for a small business, book a free scoping call. We'll go through your users, workflows and integrations, then send a written scope and a fixed price before any work starts. You'll own the code and the accounts from the first day.