Cost to Build a CRM App Like HubSpot or Salesforce in 2026

A custom CRM MVP costs $45K to $100K and takes 12 to 20 weeks. This guide breaks down the full cost across phases, explains how the activity timeline and data model actually work in plain language, covers build-vs-buy thresholds against HubSpot and Salesforce, and shows why white-label scripts end up costing more than custom builds.

22 min read ·
In this article

Short answer

Building a CRM app like HubSpot or Salesforce costs $45K-$100K for a core first version (12-20 weeks) covering contacts, pipelines, activity timeline, email sync, and reporting. Adding a marketing automation layer with email sequences, lead scoring, and an automated follow-up system adds $40K-$85K. A full white-label platform for many clients runs $150K-$230K (24-36 weeks). Monthly running costs run $1.5K-$3K.

Key takeaways

  • A custom CRM is a schema problem first and a UI problem second: how your customer data is organised matters more than how it looks on screen. The data model decisions you make in week 2 cost six times more to fix in week 12.
  • Your V1 (first version) needs contacts, pipelines, the activity timeline (the running history of calls, emails, and notes on each contact), email sync, reporting, and role-based access (controlling who can see and change what). Everything else is V2 (second version).
  • Build custom when your annual HubSpot or Salesforce bill passes $50K, when your pipeline logic does not fit their data model (how they organise your customer data), or when CRM is a revenue feature inside your own product.
  • Email deliverability is the failure mode nobody budgets for. SPF, DKIM, DMARC (the email checks that prove your mail is genuine), and a 4 to 6 week IP warm-up (gradually building a reputation for your sending address so mail reaches inboxes) are engineering work, not configuration.
  • White-label scripts (ready-made CRM software sold under your brand) like SuiteCRM cost $5K to $20K upfront but hit four architectural walls (built-in limits you cannot work around) at scale, and the $30K to $80K true-up (the extra bill to fix the limits) usually exceeds a clean custom build.
  • At 50 users on Salesforce Core ($117K per year), a $55K to $95K custom build pays back inside 12 months.

A mortgage brokerage in Texas runs 12 loan officers. Every officer manages 40 to 80 active deals at once, each with its own compliance milestones, document collection stages, and lender-specific follow-up sequences. They tried HubSpot. The pipeline stages did not map to the loan lifecycle. The custom fields hit a limit. The sequences could not branch based on lender type. They spent eight months and $30K in HubSpot configuration fees before a consultant told them what we would have told them on day one: HubSpot is not built for this workflow. No amount of workarounds would make it fit.

That is the moment a custom CRM stops being a nice-to-have and becomes the obvious move. Not curiosity about the technology. A clear, measurable failure of the off-the-shelf product against your actual pipeline.

The cost, up front

A core CRM MVP costs $45K to $100K and takes 12 to 20 weeks. Here is the full range:

ScopeTimelineCost
Prototype (clickable demo to validate the idea before a full build)variesfrom $10K
Core CRM MVP (contacts, pipelines, activity timeline, email sync, reporting, roles)12-20 weeks$45K-$100K
Marketing and automation layer (email builder, sequences, lead scoring, workflows)+8-14 weeks+$40K-$85K
Full multi-tenant or white-label platform (tenant isolation, SSO (single sign-on), API tier)24-36 weeks$150K-$230K
Monthly running costs (hosting, email sending, maintenance)ongoing$1.5K-$3K/month

The range inside each tier moves with how complicated the data is to organise (data-model complexity), the number of other systems it connects to (integration count), how deep the workflow builder goes (workflow builder depth), and compliance requirements. A bare-bones build (contact management and deal tracking only, no automation) can start near $24K, but that is a database with screens (a UI), not a CRM your team will live in.

According to Gartner's CRM market forecast, the global CRM market reached $89B in 2024, driven largely by mid-market businesses replacing spreadsheets and fragmented SaaS tools with purpose-built systems. Salesforce holds about 22% of that market. The other 78% runs on alternatives, vertical platforms, and custom builds.

Who actually builds a custom CRM

Four types of buyers consistently get their money back on a custom build. Everyone else should keep paying for seats.

The vertical SaaS company adding CRM as a product feature. You have hundreds or thousands of customers on your platform. They export data to HubSpot to manage pipelines, then ask you to "just build CRM in." Every month they bridge two systems, your churn risk rises. Building a CRM layer inside your product itself (natively), with your own data model (how your data is organised) and pricing you control, turns a feature request into a reason customers stay (a retention engine). This is the most common buyer we see: commercial real estate SaaS needing listing records (listing objects) and commission pipelines, legaltech needing matter records, proptech needing owner and tenant workflows.

The agency white-labeling CRM for clients. You run a marketing or sales enablement agency with 10 to 30 clients. Each client costs you $300 to $600 per month in HubSpot seats, which is $54K to $216K per year in pass-through costs you cannot add your own margin to (cannot margin). Building once and launching it under your own brand (deploying) converts that variable cost into a fixed hosting bill, typically $2K to $4K per month for 30 clients. The math closes within 12 months, and you own the asset permanently.

The regulated-industry company that cannot use off-the-shelf tools cleanly. Healthcare, legal, insurance, and financial services all have CRM data subject to rules that standard SaaS handles imperfectly. A healthcare staffing company cannot put clinician credentialing data in HubSpot without significant compliance work. A law firm cannot put matter history in Salesforce without a carefully scoped BAA (a signed agreement covering how client data is handled) and data residency agreement (rules about where the data is stored). A custom platform with compliance designed in from day one (the compliance architecture) is usually cheaper over three years than bending a general tool into shape.

The company that has outgrown per-unit pricing. You pay $4K per month for 50 HubSpot seats and add 10 seats per quarter. In two years that is $115K per year before contact overages. A custom platform built for $120K, hosted for $1.5K per month, pays back inside 14 months and keeps compounding. The signal to watch: when your customization budget approaches your license budget, you are paying twice for the same capability.

"The number one reason CRM implementations fail is that the system is built around how the company wants to sell, not how the team actually does sell. You have to observe the behavior first, then encode it."

  • Paul Greenberg, author of CRM at the Speed of Light

How a CRM actually works: the activity timeline is the product

Every CRM demo shows you contact records and pipeline boards. Those are the easy parts. The part that decides whether your team lives in the system or routes around it is the activity timeline, and how the data underneath it is organised (the data model).

The timeline is the core data model. Open any deal in a good CRM and you see one chronological record: every email sent and received, every call logged, every meeting booked, every note, every task, every document, every stage change, in order. That single view is what keeps a rep inside the system instead of their inbox. Without it, you have a fancy spreadsheet with a login page. With it, the CRM becomes the shared memory of the sales team. Everything else in the build, the pipeline views, the reports, the automation, reads from this timeline. Get the timeline wrong and every downstream feature inherits the problem.

Custom objects are where CRMs become vertical. HubSpot gives you contacts, companies, and deals. A mortgage brokerage needs loan files with compliance milestones. A law firm needs matters with parties and opposing counsel. A healthcare practice needs patients with treatment plans. These are proper business records in their own right (first-class business objects) with their own stage logic (their own rules for moving through stages), not custom fields bolted onto a contact record. The moment your workflow needs even one custom object, you have outgrown the standard way the data is organised (the standard schema), and every workaround after that is interest on a debt you took on day one.

Custom fields need an architecture, not a settings page. Salesforce lets admins add a field without touching code. Replicating that takes an Entity-Attribute-Value model: field definitions stored as rows rather than columns, so new fields do not require database migrations. Build it naively with a JSON blob per record (a JSON blob is an unstructured lump of data stored with each record) and you lose the ability to filter or sort on custom fields at scale. Teams that discover this six months after launch spend $40K to $60K fixing it, after the damage to adoption is already done. This is the single most expensive line item to get wrong, and it is invisible in every demo.

Dedup and merge logic is where "single source of truth" breaks. The same person enters your system four ways: as a web lead, as an email thread, as a CSV import, as an API event. Each carries a different identifier. The CRM has to decide these are one person, merge them without losing history, and define survivorship rules for conflicts (which phone number wins when three records disagree). This matching of records to one person (identity resolution) runs constantly in the background. Skip it and your reports double-count pipeline within 90 days, and nobody trusts the dashboard again.

Email sync is a hard behind-the-scenes problem (a distributed systems problem) dressed up as a simple feature. Gmail and Outlook deliver webhook events (automatic alerts sent between systems) out of order and with duplicates. An email sent at 2:04 PM can arrive before the one sent at 2:03 PM. The same event can arrive three times. Emails sent from outside the CRM have to appear in the timeline; emails sent from the CRM have to appear in the sent folder. Each failure mode needs explicit handling, which is why this one module takes 4 to 6 weeks and why teams that budget two weeks for it end up debugging it with live users on the system.

Multi-tenant isolation is a week-one decision. If agencies or SaaS companies will ever sell this CRM to their own customers, each tenant's data must be kept separate where the data is stored (at the database layer). Row-level security (rules that stop one customer seeing another customer's rows) enforces the separation. Done when the data is first organised (in the schema design), it adds 4 to 6 weeks. Added later to a system built for one customer (retrofitted onto a single-tenant system), it is a rewrite. There is no middle option, which is why the white-label question has to be answered before the first sprint, not during the third.

This is the teardown we run in discovery before we ever quote you. If a vendor cannot explain how the activity timeline, custom objects, and dedup logic should work for your data, they have not thought about your product yet.

Where the budget actually goes

A core CRM MVP splits roughly like this:

BuildShare of budgetWhat it includes
Web app (pipeline, records, timeline UI)25-30%Contact and company views, Kanban pipeline, activity timeline, reporting dashboards
Backend and data model30-35%Schema design (how the data is organised), EAV custom fields (fields you can add without rebuilding the database), dedup and merge logic, role-based access (each person sees only what their job allows), API (the connection other software uses)
Email sync and deliverability15-20%Bidirectional Gmail and Outlook sync (two-way sync, both directions), SPF/DKIM/DMARC (the email authentication records that prove mail is really from you), bounce and complaint handling, IP warm-up (gradually building trust for a new sending address)
Integrations10-15%Calendar sync, CSV import, one or two native connectors (Stripe, telephony)
Workflow automation (if in V1)10-15%Trigger-action engine (if this happens, do that), sequence runner with reply detection (it spots replies and pauses the sequence)

Email sync is the line item buyers question most and regret cutting first. It is also the module with the widest gap between "looks done in the demo" and "works in production," which is why it gets its own budget line instead of hiding inside the backend.

What drives the price up or down

Data-model complexity. Contacts plus pipeline is the floor. Every custom object (matters, patients, loan files, properties) adds schema design (planning how the data is organised), screens (UI), permissions, and reporting surface (more reports to build). Two custom objects roughly add 20 to 30% to the MVP. Five or more means you are building a platform for one industry (a vertical platform), and you should price it as one.

Workflow builder depth. This is the widest cost range in the build. A trigger-action system (if deal reaches stage X, send email Y and assign to rep Z) costs $15K to $25K and covers 80% of real-world use cases. A visual builder with a node canvas (a drag-and-drop diagram of steps), conditional branching (different paths for different answers), parallel branches (steps that run at the same time), and real-time processing (steps that run straight away) costs $40K to $60K. Start with trigger-action. Build the visual builder when users ask for it by name.

Multi-tenancy. Designing tenant isolation (keeping each customer's data separate) into the schema (how the data is organised) from week one adds 4 to 6 weeks. Adding it later (retrofitting it) is a rewrite. Answer the white-label question before the first sprint.

Email deliverability infrastructure. SPF, DKIM, and DMARC on every sending domain, and dedicated IP warm-up (gradually building trust for a new sending address) over 4 to 6 weeks. Bounce suppression (stopping mail to addresses that bounced), complaint handling, and List-Unsubscribe headers (the unsubscribe link email apps show) are part of the same work. Budget 3 to 6 weeks of engineering. Teams that treat this as configuration discover the problem 60 days after launch when 40% of automated emails land in spam, and recovery takes 8 to 12 weeks.

Integration count. Each native integration (calendar, telephony, billing, marketing tools) takes 1 to 3 weeks to rebuild (replicate) if you are replacing a HubSpot or Salesforce connector (a ready-made link between the systems). More than three integrations adds $40K to $60K before you have touched pipeline logic. Count the integrations your team actually uses daily, not the ones on the vendor's marketplace page.

Compliance architecture. HIPAA-eligible data handling (handling health data to the standard the law requires), data residency controls (rules about where data is stored), and audit logging (a record of who did what) all add real scope. So does SSO (single sign-on, one login). A build with a BAA in place (a BAA-ready build) for a healthcare practice is a different project than the same CRM for a mortgage brokerage. Scope compliance in discovery or it becomes a mid-build surprise.

AI lead scoring. Scoring, forecasting, and next-best-action need 12 or more months of clean historical deal data to train on. Attempting them before that produces noise, not signal. Budget them as V3, and only after the timeline has been collecting clean data for a year.

V1, V2, V3: what to build and when

A core CRM MVP needs exactly six modules. Everything else is V2 or V3. The teams that replace Salesforce successfully build only what their team uses in the first 90 days. The ones that fail try for feature parity and run out of budget before anything is shippable.

Feature priority by version

  • V1

    Core CRM ($45K-$100K, 12-20 weeks)

    The six modules your MVP needs. Ship with these and nothing else.

    • Contact and company records with custom fields
    • Deal pipeline with configurable stages and Kanban views
    • Activity timeline: calls, emails, meetings, notes, tasks
    • Bidirectional email sync (two-way sync, Gmail + Outlook)
    • Reporting: pipeline by stage, deal velocity, rep activity
    • Role-based access control (each role, admin, manager, rep, sees only what it needs)
  • V2

    Automation layer (add post-launch, +$40K-$85K)

    Add these after V1 is stable and the team is using it daily.

    • Email campaign builder with deliverability infrastructure
    • Automated sequences with reply detection
    • Lead scoring with adjustable point values
    • Form builder and landing pages
    • Workflow automation engine (automatic if-this-then-that rules, trigger-action first)
    • Segmentation and dynamic lists (groups that update themselves as records change)
    • Calendar sync and third-party integrations
  • V3

    Platform (add at scale, +$80K-$130K)

    Multi-tenant and intelligence features. Only after the data exists to justify them.

    • Multi-tenant data isolation (each customer's data kept separate) with row-level security (rules that stop one customer seeing another's rows)
    • White-label branding, custom domains, per-tenant config (settings per customer)
    • SSO (single sign-on: SAML 2.0 / OAuth 2.0, the login standards behind it) and audit logs (a record of who did what)
    • API tier (a documented way for other software to connect) for tenant integrations
    • Custom objects beyond Contact/Account/Deal
    • AI lead scoring (needs 12+ months of clean data)

The V1 email sync note deserves emphasis. It is the single feature sales reps care most about. They will not open a CRM that does not automatically capture their emails. If email sync slips from V1, adoption slips with it.

How the timeline breaks down

PhaseDurationWhat happens
Discovery and schema sprint2 weeksDomain objects (your business records, like deals and matters) mapped, EAV field architecture (the flexible field system) designed, integration plan, fixed-price proposal
Core build (V1)10-14 weeksData model, records, pipeline, timeline, reporting, roles; email sync runs in parallel as its own track
Email deliverability setup3-6 weeksSPF/DKIM/DMARC, dedicated IP warm-up started early so reputation builds during the build
Hardening and migration2-4 weeksDedup rules, CSV import, parallel run with the old CRM read-only
Beta with real reps2-4 weeks5-10 users on live deals before company-wide rollout

Total: 12 to 20 weeks to a working V1. The schema sprint (the two weeks spent planning how the data is organised) is the fortnight that matters most in the project. Decisions made there cost six times more to fix in week 12.

Build vs. buy: the actual thresholds

Keep HubSpot when you have fewer than 20 people and spend under $30K per year on it. Configuration takes days. If your pipeline stages map cleanly to a standard funnel and your contact database is under 50K, HubSpot is the right tool and building is an expensive hobby.

Keep Salesforce when you depend on Agentforce agents (Salesforce's AI agents), AppExchange integrations (ready-made links to other tools), or complex CPQ (the tool that builds quotes with pricing rules). Those are years-long engineering investments no 12-month build replicates. Also keep it when your team is under 25 users and the annual bill is $25K to $40K: the payback stretches past three years.

Build your own when the annual license bill passes $50K. At 50 Salesforce Core seats ($117K per year), a $75K build pays back in about 8 months. At $50K per year on HubSpot, payback lands under 24 months. The math is not close at these levels.

AI is now a second meter on top of seats. Salesforce Flex Credits run about $0.10 per standard action ($500 per 100K credits), and HubSpot agents bill in HubSpot Credits: $0.50 per resolved conversation and $1 per recommended lead, with extra credits at $9 per 1,000. HubSpot also charges a mandatory one-time onboarding fee: $1.5K on Professional and $3.5K on Enterprise. Add credit consumption and onboarding to the year-one comparison before you call the $50K threshold: Sales Hub runs $90 per seat per month on Professional and $150 on Enterprise, billed annually.

Build your own when your workflow needs data structures that cost more than $40K to configure in Salesforce or HubSpot. If you are already spending that on consultants, a custom build is cheaper over a two-year window, and you own the result.

Build your own when CRM is a revenue feature inside your product. You cannot resell HubSpot seats as your product's CRM module. The API rate limits (caps on how often your software can ask HubSpot for data) are not yours, the data ownership terms are not yours, and the per-unit pricing becomes your margin problem at scale.

If you are weighing this decision against a services partner instead of a build, our custom CRM development team scopes the build-vs-buy math as part of discovery: current license trajectory, configuration spend to date, and the payback window for your seat count.

White-label scripts vs. custom build

SuiteCRM and vTiger are the most common "cheap" alternatives, and the math deserves a fair hearing before you dismiss it.

White-label scriptCustom build
Upfront cost$5K-$20K$45K-$100K
Time to first demo1-2 weeks12-20 weeks
Multi-tenant for agency useNo (one install per client)Designed in
Custom objectsCore surgery (changing the system's own code), breaks on updateNative (built in, EAV architecture: the flexible field system)
Email deliverability infraNone (an SMTP relay, a basic mail server that just passes mail on, and hope)Built in: warm-up, bounce handling, suppression
Workflow engine depthBasic triggers onlyTrigger-action now, visual builder later
Total cost at 12 months$35K-$100K+$45K-$100K

The script looks cheaper at the start. Four design limits (the four architectural walls) surface within the first six months. There is no multi-tenancy (one install per client, so every client needs its own). The contact model is flat (contacts with no custom record types). There is no deliverability infrastructure. And the pipeline logic cannot be extended (no extensible pipeline logic). The $30K to $80K true-up usually exceeds the clean build. You also inherit a codebase that fights the original system's assumptions on every update.

Where CRM builds go wrong

The schema is designed for today's data. A SaaS company builds contact and deal models that fit current customers. Twelve months later a new segment arrives with different objects, and the schema cannot accommodate them without breaking changes. The fix is a six-week migration touching every downstream query. Avoidable: design extension points in from the start (places where new record types can be added later), custom object types, field definitions, relationship tables that add new kinds of records (entities) without altering existing ones.

Email deliverability treated as configuration. New sending domains need 4 to 6 weeks of warm-up starting at 50 to 100 emails per day. Missing authentication records put legitimate mail in spam. High bounce rates from imported lists damage the domain. Teams discover this 60 days after launch, and recovery takes 8 to 12 weeks of careful sending while the sales team loses faith in the system.

Scope escalation before launch. The MVP list starts at six modules and reaches 22 before the first line of code. Everyone adds a must-have. The result is a 12-month, $150K project that launches to a team finding it too complex to adopt. The fix is a written MVP scope signed before the project starts, with everything else on a documented V2 list.

No owner for data quality. When nobody defines entry standards, the system fills with inconsistent records inside 90 days, reports stop being trustworthy, and reps go back to spreadsheets. Appoint a CRM owner before launch. It is an operational role, not a technical one.

How to spend less without building junk

Start with trigger-action automation. The $15K to $25K trigger-action engine covers 80% of real workflows. The $40K to $60K visual builder can wait until users ask for it by name.

Delay the mobile app. It adds 6 to 8 weeks. If your reps are desk-based, the responsive web app is enough for V1.

Defer AI scoring. It needs 12 months of clean data. Budget it as V3 and spend the money on data hygiene first.

Limit V1 integrations to two. Calendar sync and one billing or telephony connector. Every additional native integration is 1 to 3 weeks. Count what the team uses daily.

Run the schema sprint seriously. Two weeks of data-model design before code is the cheapest insurance in the project. Everything downstream depends on it.

Do not build Service Hub in V1. Ticket management, knowledge base, and customer portal belong 12 to 18 months out, when ticket volume justifies them.

Does this cover HubSpot, Salesforce, Zoho, and Pipedrive?

Yes. Every mainstream CRM runs on the same architecture this guide describes: records, pipeline, timeline, automation. What changes is where each one breaks for your workflow.

VendorBest forWhere it breaksCost signal
HubSpotB2B teams under 200 seats, standard linear funnelsNon-linear pipelines, custom objects need Enterprise ($3.6K/mo); per-contact fees explode past 200K contacts$24K-$60K/yr for 10 seats; $60K-$90K/yr past 200K contacts
Salesforce500+ seats, complex territories, deep ecosystem needsVertical data models (data organised for one industry) need $30K-$80K customizations that break on platform updates$195/user/mo Core; 50 users = $117K/yr; Health Cloud $300/user/mo
Zoho CRMBudget-conscious teams, standard pipelinesFragile custom-module schemas (custom record types that break easily), thin cross-object reporting (reports that struggle to combine data from different record types), inconsistent API docs (the guides for connecting other software)$14-$52/user/mo; white-label adds revenue-share obligations
Pipedrive10-person B2B teams, simple deal trackingNo custom objects, no real automation, no territory managementCheapest of the four; wrong tool outside simple pipelines

If you are building to replace one of these, the cost bands in this guide still apply. The budget moves with data-model complexity (how complicated the data is to organise), integration count (the number of other systems it connects to), and compliance, not with which logo you benchmark against.

How RaftLabs approaches CRM builds

We build embedded CRM for SaaS companies and vertical CRM platforms for industries where general-purpose tools do not fit. Our engagements run on fixed-price contracts, and every one starts the same way.

Weeks 1-2: schema sprint. We map your domain objects, the relationships between them, and the fields each object needs. We design the EAV custom-field architecture (the flexible field system that lets you add fields without rebuilding the database) and review it with your team before writing any application code. The sprint output is a fixed-price build proposal. You know the cost and timeline before the first developer is assigned.

Weeks 3-12: V1 delivery. Contacts, pipeline, activity timeline, email sync, reporting, roles. Staging at week 8 for your review, production at week 12. Email deliverability setup (authentication, warm-up, bounce handling) runs as its own track from week 3 so reputation is building while we build.

Week 12+: V2 and beyond. After real users are in the system, we scope the automation layer based on what they actually ask for. V2 is priced fixed before V2 development starts.

We have shipped CRM platforms for a healthcare staffing marketplace that needed credential tracking alongside contact management, a commercial real estate SaaS that needed listing objects and commission pipelines, and a marketing agency that white-labels CRM to 200 clients.

Most of the demand we see for CRM work starts as a services conversation, not a cost question: teams want to know whether to build, buy, or customize, and what the engagement looks like. Our custom CRM development practice handles exactly that, from the build-vs-buy math through delivery.

If you are paying more than $50K per year in CRM licenses, running workarounds alongside your CRM because the tool does not fit, or planning to embed CRM inside your own product, Start your scope. We will tell you directly whether a custom build makes financial sense, and give you a fixed-price range before we commit to anything.

Ask an AI

Get an instant summary of this post from your preferred AI assistant.

Frequently asked questions

Straight answers to what buyers ask before they scope. Still stuck? .

A core CRM MVP (contacts, pipelines, activity timeline, email sync, reporting, role-based access) costs $45K to $100K over 12 to 20 weeks. Adding a marketing automation layer with email sequences, lead scoring, and a workflow engine adds $40K to $85K. A full multi-tenant white-label platform (one platform sold under many brands, each client's data kept separate) with SSO (single sign-on: one login for all company tools) and an API tier (a way for other software to connect to your CRM) runs $150K to $230K over 24 to 36 weeks. Monthly running costs (hosting, email sending, maintenance) run $1.5K to $3K.
A core MVP takes 12 to 20 weeks with a team of 3 to 5. The automation layer adds 8 to 14 weeks on top. A full multi-tenant platform takes 24 to 36 weeks. The two biggest timeline variables are multi-tenant data isolation (keeping each client's data completely separate), which adds 4 to 6 weeks if not planned from the start, and email deliverability infrastructure (the setup that makes sure your emails reach inboxes), which adds 3 to 6 weeks. A clickable prototype to validate the concept starts at $10K.
Keep HubSpot when you have fewer than 20 people, spend under $30K per year on it, and your pipeline stages map cleanly to a standard funnel. HubSpot configures in days and its workflow builder works without engineering support. Build custom when you are an agency with 10 or more clients, a vertical SaaS company, or hitting per-contact pricing walls above 200K contacts.
When you have 50 or more users on Salesforce Core (about $117K per year at 50 seats), a vertical workflow the platform handles poorly (field service, healthcare, staffing), data sovereignty requirements (rules that your data must stay in a particular country), or an annual bill above $50K. A $55K to $95K custom build pays back inside 12 months at that scale. Keep Salesforce if you depend on Agentforce agents (Salesforce's AI assistants), AppExchange (its marketplace of approved add-ons), or complex CPQ (its quote-and-pricing tool).
SuiteCRM and vTiger cost $5K to $20K to install and customize, but they fail at scale on four specific points: no multi-tenant architecture (one system cannot serve many clients: 20 clients means 20 separate installs), a flat contact model with no custom objects (contacts stored in one rigid format, with no way to add your own record types), no email deliverability infrastructure (no setup that makes sure your emails reach inboxes), and a workflow engine (the system that runs follow-ups automatically) that cannot model compound branching (if-this-then-that rules with several conditions). The $30K to $80K true-up when these limits surface usually exceeds a clean custom build.
Two problems. First, custom field architecture (letting admins add their own fields to a contact without code): Salesforce lets admins add fields without code, and replicating that needs an Entity-Attribute-Value model (a flexible way of storing extra fields). Get it wrong and teams spend $40K to $60K fixing it post-launch. Second, bidirectional email sync (two-way sync: emails sent from Gmail or Outlook appear in the CRM, and vice versa): Gmail and Outlook webhooks (notifications from Gmail and Outlook) arrive out of order and with duplicates, so every event needs explicit deduplication logic (checks that spot the same email twice). Budget 4 to 6 weeks for email sync alone.
Budget $1.5K to $3K per month for hosting, email sending infrastructure, and routine maintenance. Plan 10 to 20 percent of the build cost per year for ongoing updates and feature additions. If you add LLM-powered features (AI features) like lead scoring (ranking leads by how likely they are to buy) or conversation summaries, API fees (fees charged by the AI provider for each use) add $500 to $5K per month depending on usage.
The schema (how your customer data is organised), then email. Schema decisions made in week 2 cost six times more to fix in week 12, because every search, report, and follow-up relies on them. Email deliverability crises hit around day 60: the platform sends, the emails land in spam, and the team loses confidence while engineering tracks down what looks like a software bug but is actually missing SPF, DKIM, or DMARC records (the email checks that prove your mail is genuine).
Agentforce AI agents (Salesforce's AI assistants; needs years of training data you do not have), the AppExchange library (1K+ approved add-ons), complex CPQ logic (quote-and-pricing rules; took Salesforce years and an acquisition), and enterprise territory management (assigning sales regions across a large team). These are years behind, not months. Build around what Salesforce does badly for your vertical, not what it does well.
Export in phases, not all at once. Start with contacts and companies, then deals with their stage history, then activity records. Dedup (remove duplicates) before import: the same person usually exists as a lead, a contact, and three email threads. Budget 2 to 4 weeks for a migration under 200K records including dedup rules (rules for spotting the same person twice) and a parallel-run period (a period where both systems run side by side) where both systems stay live. Run the old CRM read-only for 30 days after cutover (the switch to the new system) as a safety net.