Build vs Buy a CRM: Custom CRM Cost, Fields and Workflow Rules
Buy a CRM when your sales process is standard and you need it running this week. Build one when the workflow itself is your edge or the CRM has to be joined tightly to systems no vendor integrates with. For most small and mid-sized B2B teams that want custom fields and workflow rules, the cheaper answer is often neither: keep the CRM you have and put a workflow automation layer on top of it.
This guide sets out what buying costs at today’s list prices, what a custom CRM build actually involves and what drives its cost, how CRMs handle custom fields and workflow rules, and where an automation layer fits.
What buying a CRM costs today
Seat prices are public, so start there. These are list prices from the vendors’ own pricing pages, checked on 30 October 2026. They change, and they exclude discounts you may negotiate.
| CRM tier | List price | One-time fees and add-ons |
|---|---|---|
| HubSpot Sales Hub Professional | Starts at $90 per seat per month, annual commitment | Required one-time onboarding fee of $1,500 |
| HubSpot Sales Hub Enterprise | Starts at $150 per seat per month | Required one-time onboarding fee of $3,500 |
| Salesforce Pro Suite | $100 per user per month, billed annually | |
| Salesforce Sales Cloud Core | $195 per user per month, billed annually | AI can be added to Core and above; Agentforce for Sales from $125 per user per month |
| Salesforce Sales Cloud Advanced / Max | $395 / $550 per user per month, billed annually |
Sources: HubSpot Sales Hub pricing, Salesforce Sales pricing.
What that means for a 10-person team, at list price, before implementation partners, integrations or AI add-ons:
- HubSpot Sales Hub Professional: 10 x $90 x 12 = $10,800 a year, plus $1,500 onboarding in year one.
- Salesforce Pro Suite: 10 x $100 x 12 = $12,000 a year.
- Salesforce Sales Cloud Core: 10 x $195 x 12 = $23,400 a year.
Two patterns matter more than the headline. First, the features small teams usually want most, such as workflow rules, sit on higher tiers: HubSpot’s workflows need a Professional or Enterprise subscription. Second, AI features are increasingly sold as a separate product or on the top tier, so the price you sign is not always the price you pay a year later. Price the tier that has the features you need, plus the add-ons, for three years.
What a custom CRM build actually involves
A custom CRM is not one thing. It is five parts, and the cost of a build depends on how many of them you need and how deep each one goes.
- The data model. Contacts, companies, deals, activities and notes, plus the custom fields and record types your process needs. Designed around your actual sales motion, not a generic template.
- The interface. Pipeline board, record pages, activity feed, search. Sized to what the team uses every day.
- Inbound automation. Leads from forms, emails and calendar bookings, and documents such as purchase orders, read and filed instead of retyped.
- Outbound integrations. Hand-offs to accounting, quoting, support and messaging, triggered by deal stage or activity instead of by manual export.
- Reporting. A few dashboards, or a connection to the BI tool you already use.
What drives the cost of a custom CRM
We do not quote a single figure for “a custom CRM”, because two projects with that name can differ widely in scope. These are the drivers that move the price, so you can compare a build quote line by line with a seat price.
| Cost driver | What pushes it up | What keeps it down |
|---|---|---|
| Data model | Many record types, complex relationships, per-team field sets | Contacts, companies, deals and a short list of custom fields |
| Integrations | Each additional system, two-way sync, systems without an API | One-way hand-offs to two or three systems with good APIs |
| Data migration | Years of messy history, duplicates, attachments, custom objects in the old CRM | Migrating open deals and active contacts only |
| Permissions and audit | Field-level access, regulated data, approval trails | One team, simple roles |
| Interface scope | Mobile apps, offline use, quoting or billing inside the CRM | Web interface for pipeline, records and search |
| Reporting | Custom forecasting, many bespoke dashboards | Three or four reports, or an existing BI tool |
| Ownership after launch | No named owner, frequent process changes, no runbook | A named owner, documented code and a support arrangement |
The last line is the one most build-versus-buy comparisons leave out. A vendor’s seat price includes maintenance, hosting, security patches and someone to call when it breaks. A custom build needs all of those budgeted every year. If nobody can own that, buy.
Custom fields and workflow rules: how CRMs compare
When a US sales team says it needs “custom fields and workflow rules”, it usually means three different things. Separating them shows whether you need a new CRM at all.
Custom fields. Extra properties on contacts, companies and deals, such as contract type, territory or renewal date. Every mainstream CRM supports these on paid tiers. This is rarely a reason to switch or build.
Rules inside the CRM. Assign a lead by territory, create a task when a deal reaches a stage, send a notification when a field changes. Mainstream CRMs do this natively, but often only on higher tiers, as with HubSpot workflows above. Before switching, check what the next tier up costs on your current CRM.
Rules that cross systems. Create the customer in the accounting system when a deal closes, read an emailed purchase order and attach it to the right deal, check stock in the ERP before a quote goes out. This is where CRMs stop. Native integrations cover common pairs; anything specific to your stack needs an integration platform or custom code.
The questions to ask any CRM, or any build proposal:
- Which tier unlocks workflow rules, and are there limits on how many?
- Can a rule call an external system, or only act inside the CRM?
- Is there a log of what each rule did and when, so you can audit it?
- Who can change a rule, and can a change be tested before it goes live?
The middle path: workflow automation on top of your CRM
For many teams the gap is not the CRM, it is everything around it: the leads retyped from emails, the deal details copied into the accounting system, the documents saved by hand. That gap can be closed without replacing the CRM and without a large development project.
The pattern we build at Kwestra:
- The CRM stays the system of record. Your team keeps the interface it knows, and the vendor keeps maintaining it.
- An automation layer listens to it. When a record is created or a deal changes stage, the layer receives the event through the CRM’s API or webhooks.
- The layer does the cross-system work. It reads inbound emails and documents, fills the right fields, routes items by your rules, and pushes data to accounting, ERP or messaging tools.
- A person approves the exceptions. Anything the rules cannot place confidently waits for someone to approve, edit or reject.
- You own the logic. The workflows, code and runbook are yours, so they survive a later CRM change.
This works when your CRM has a usable API and your process is stable enough to write down. It does not work if the CRM itself is the wrong fit for how you sell; then the choice is a different vendor or a build. For a primer on what qualifies as workflow automation, see what is workflow automation, and for why rules-only bots stall on emails and documents, see RPA vs AI automation.
Build vs buy vs extend: a decision table
| Buy and configure | Buy, plus an automation layer | Custom build | |
|---|---|---|---|
| Best fit | Standard sales process, need it fast | Standard CRM, non-standard work around it | The workflow itself is the edge |
| What you own | Your data and configuration | Your data and the automation logic | Everything, including maintenance |
| Main cost drivers | Seats, tier, add-ons, onboarding | Seats, plus the number of integrations and rules | Scope (see the driver table), migration, ownership |
| Main risk | Paying for a tier to unlock a few features | Depends on the CRM’s API | Depends on a named owner |
| Time to value | Days | Weeks per workflow | Weeks to months |
To compare the options on cost, put each on a three-year basis: seats, tier upgrades, add-ons and onboarding for the buy paths; build, hosting, maintenance and internal time for the build path. Our intelligent automation ROI guide covers how to measure the baseline and build a cost case finance will accept, and how much AI automation costs breaks down build and running costs for automation work.
When buying still wins
You need it working on Monday. A custom build takes weeks. A configured CRM can be running the same day.
Nobody will own anything custom. A build that depends on one person who then leaves is worse than a paid subscription.
Compliance requirements are already solved off the shelf. Regulated industries often need audit trails and validated integrations that take months to replicate. Cannabis operators, for example, have to weigh state traceability reporting before going custom; see the cannabis compliance automation playbook.
Your sales motion matches the vendor’s model. If the standard pipeline describes your process accurately, customising a build costs more than the seat.
The risks of building
Ownership is a running cost. Hosting, monitoring, schema changes and support do not stop after launch.
Scope creep. “One more report” and “a quoting module” turn a focused CRM into a half-finished platform.
Migration is the hard part. Moving data, rewiring integrations and retraining the team is usually the most underestimated line.
Vendors still win on some things. Mobile apps, plugin ecosystems and certified enterprise integrations. If any of these matter to your team, weigh them.
Three questions before you decide
1. Can you list what the CRM must do in under ten plain-language bullets? If yes, a build or an automation layer is realistic. If not, a vendor has probably already solved most of it.
2. What is the three-year cost of staying where you are? Seats at your expected headcount, the tier you would need for workflow rules, add-ons and renewals. Most teams have never written this number down.
3. Who will own the system, and what happens if they leave? If there is an honest answer and a plan, building or extending is on the table. If the answer is “we will figure it out”, buy.
Frequently asked questions
01 How much does a custom-built CRM cost?
It depends on a handful of drivers more than on the CRM itself: how many record types and fields you need, how many systems it must connect to, how much data you migrate, how fine-grained permissions are, and who maintains it afterwards. A contact, company and deal model with two integrations is a small project; a CRM that replaces quoting, billing and support is a platform. Get the scope in writing before you compare it with a seat price.
02 Is it cheaper to build or buy a CRM?
For a standard sales process, buying is usually cheaper once you count the time to build, migrate and maintain. Building pays when the workflow itself is your edge, when you would pay for a large tier only to unlock a few features, or when the CRM must be tightly joined to systems no vendor integrates with. Compare three-year cost, including onboarding fees, add-ons and the people who maintain each option.
03 Can we get custom fields and workflow rules without a development project?
Usually yes. Mainstream CRMs support custom fields on every paid tier, and workflow rules are built in, though often only on higher tiers: HubSpot's workflows, for example, need a Professional or Enterprise subscription. Where the rule has to reach other systems, such as your accounting software, ERP or inbox, a workflow automation layer on top of the CRM handles it without replacing the CRM.
04 How do HubSpot and Salesforce prices compare for a small team?
At list prices checked on 30 October 2026, HubSpot Sales Hub Professional starts at $90 per seat per month with an annual commitment plus a one-time $1,500 onboarding fee, and Salesforce lists Pro Suite at $100 and Sales Cloud Core at $195 per user per month, billed annually. Both vendors sell AI features separately or on higher tiers. Prices change, so check the vendor's page before you sign.
Want custom workflows without replacing your CRM?
Tell us which CRM you use and where work is still retyped or copied by hand. We map the workflow, tell you whether a tier change, an automation layer or a build fits, and quote it in writing. Book a 30-minute call. Our AI automation and IT consulting services cover the build and the integration work.