Salesforce versus custom CRM: when is your own system cheaper?
Salesforce has been the world's most widely used CRM platform for years for good reason. The ecosystem is huge, the functionality deep and the mobile app mature. Yet we increasingly see companies with 30 to 200 users calculating what their Sales Cloud or Service Cloud will cost over five years, including admin hours and consultancy, and then taking a serious look at a custom CRM. This article explains honestly when that calculation tips and when Salesforce remains the sensible choice.
Discuss your CRM case Go to the cost comparisonWhen Salesforce licences and admins cost more than building your own CRM
The licence price on the website is rarely the whole story. For an honest comparison, add up licences, an internal or external Salesforce Admin, periodic consultancy for Apex and Flow changes, AppExchange packages, sandboxes and data migration costs. Work out that TCO over five years and the result surprises many boards.
A typical B2B company with 60 sales and service staff pays a fixed price per user per month for Sales Cloud Enterprise or Service Cloud Enterprise, and that price almost doubles if you upgrade to Unlimited or want to use Einstein features. On top of that come Sales Engagement, CPQ, Marketing Cloud integrations and various AppExchange add-ons, each charged per seat. In practice, we see total licence costs rise to a multiple of the headline price once all the required modules are included.
Besides licences, you almost always need a Salesforce Admin, either full-time in-house or via a partner. This role is no luxury: without someone who manages Page Layouts, writes Validation Rules, maintains Flow Builder, updates profiles and permission sets and promotes releases between Sandboxes, every Salesforce org becomes unmanageable within a year. For more complex logic you also need an Apex developer, often at consultancy rates. A custom CRM needs this role too, but in the form of a development team or software partner that keeps evolving the system, and that budget can be negotiated up front.
The tipping-point question is therefore not "what does a licence cost?" but "what are our total CRM costs over five years, and how much of that varies with the number of users?" For a growing company with 80, 120 or 200 seats, Salesforce costs rise in step, whereas a well-built custom CRM scales far more gently: hosting, maintenance and further development do not grow one-to-one with the number of users. That is the fundamental economic reason why organisations eventually make the switch.
What really makes Salesforce strong, and why that explains its dominance
Before we look at frustrations: Salesforce did not become the market leader by accident. Three things are hard to match, and they deserve an honest mention.
AppExchange ecosystem
Thousands of certified integrations and industry-specific packages, from DocuSign and Conga to vertical solutions for financial services, real estate and healthcare. Without any development of your own, you get access to a huge library of ready-made functionality.
Mature Lightning mobile app
The Salesforce mobile app has been refined for years, with offline support, push notifications, geo-tracking for field service and an extensive permission layer. For sales and service teams working outside the office, that is a serious advantage over many self-built CRMs.
Established declarative tooling
With Flow Builder, Process Builder (legacy), Validation Rules, Approval Processes and Lightning App Builder, advanced admins can configure a lot of logic without code. For companies without developer capacity, this is a legitimate productivity boost, provided the complexity doesn't get out of hand.
Enterprise security and certification
SOC 2, ISO 27001, FedRAMP, HIPAA readiness, granular sharing rules, role hierarchies and field-level security. For heavily regulated sectors, this compliance documentation stack is often decisive and hard to replicate in a custom build.
Einstein AI and Data Cloud
Lead scoring, opportunity insights, Einstein Bots, Einstein Activity Capture, Prediction Builder and the recent Data Cloud / Agentforce layer. Salesforce is well ahead on AI, although the price bears no relation to self-built alternatives using OpenAI or Azure AI integrations.
Partner and talent network
Thousands of certified Salesforce Admins, Developers and Architects are available worldwide. For an international organisation that needs support on several continents, that is a considerable advantage over a unique custom stack.
Six reasons why companies outgrow Salesforce
None of them is a knock-out on its own. But once several start to bite at the same time, management rightly asks the question: do we keep paying for functionality we don't actually use, or do we build something that fits exactly?
1. Per-seat costs escalate disproportionately
Salesforce charges for almost everything per user per month. Sales Cloud, Service Cloud, CPQ, Sales Engagement, Field Service and most AppExchange packages are all seat-based. As your team grows, your CRM budget doubles without the feature set changing. With a custom build, licence costs are virtually non-existent; you pay for hosting, support and further development, not for adding a twentieth account manager.
2. Vendor lock-in on processes, not just on data
Getting your data out via Data Loader or the Bulk API is technically solvable. The real lock-in lies in the hundreds of Validation Rules, Apex triggers, Flows, Approval Processes and custom objects built up over the years. Business processes have become fused with Salesforce-specific metadata, and translating that knowledge to another stack requires a serious migration project.
3. Admin overhead for a moderately complex data model
A Salesforce Admin spends a lot of time maintaining Page Layouts per profile, Lightning Record Pages per app, sharing rules across role hierarchies and testing releases across Developer, UAT and Full sandboxes. For an organisation with a relatively simple data model, that feels like overhead. A custom CRM with Postgres and clear domain models simply requires less switching work per change.
4. Customisations are slow and expensive
A seemingly small change, such as an extra field that flows through to four reports, a Flow that talks to an external API, or a Lightning Component for a specific workflow, typically requires an Apex developer, a test class with sufficient code coverage, a deployment via SFDX or change sets and a UAT cycle. In a well-built custom CRM, a development team often pushes through the same change in a fraction of the time, because it makes stack choices that suit you.
5. EU data, privacy and data sovereignty
Salesforce has EU data centres and offers Hyperforce regions, but in some sectors (government, healthcare, financial supervision) there is reluctance to place customer data with a US hyperscaler. A custom CRM hosted in a Dutch or EU data centre (for example with Leaseweb, Hetzner or Scaleway) makes data sovereignty and GDPR control easier to demonstrate. Until a few settlements follow, this is a genuine argument in tenders.
6. A UX that no longer fits how your team works
Lightning Experience is an improvement on Classic, but it remains a generic interface that has to serve every industry and every workflow at once. Sales teams complain about the number of clicks for a single opportunity update, service staff about case views that don't match their process. With a custom CRM, you design the screens around your most common tasks, which in practice delivers major time savings and better data discipline.
One caveat we should be honest about: points 1, 3 and 4 can be partly solved within Salesforce itself, by managing licences more tightly, having an experienced Architect clean up Page Layouts and sharing rules, and having a certified partner review your automation. Not every Salesforce frustration has to lead to a migration. But for organisations where three or more of these reasons are pinching at once, an honest business case for a custom solution is worth the effort.
When is custom cheaper on a 5-year TCO?
The calculation depends heavily on the number of seats, the complexity of your data model and how much you use AppExchange packages and Einstein features. The variables below are the building blocks of an honest comparison. We always recommend asking your Salesforce partner or CSM for concrete figures rather than relying on a price list on a website.
The Salesforce side of the TCO
Per-user licence costs for Sales Cloud or Service Cloud (base edition), upgrades to Unlimited or Einstein bundles, AppExchange add-ons (often 5–15 in mature orgs), Sandbox licences (Partial Copy and Full Sandboxes cost substantially more), a Salesforce Admin (in-house or via a partner), Apex developer hours for releases and integrations, and MuleSoft or similar for ESB integrations if those are part of the architecture.
The custom side of the TCO
One-off build costs (depending on scope and number of modules), hosting in an EU data centre, a quarterly or annual development budget, monitoring and an uptime SLA, security audits (annually or after major releases), a backup and DR strategy, and an internal or external product owner who looks after the roadmap and prioritisation. No seat-based licences, which is the structural advantage.
As a rough tipping point for custom CRM software, we see that the business case usually only becomes convincing from around 40 to 60 active users, or with a smaller team that has a strongly deviating data model where Salesforce customisations are relatively expensive. Below that threshold, you usually pay more for a custom build than for Salesforce, simply because the one-off build costs are not spread across enough seats. So be honest in your calculations: for 15 salespeople with a standard pipeline process, Salesforce Essentials or Pro is often cheaper than building your own.
What makes the calculation complex is that many "hidden" Salesforce costs only become visible after you move to a higher edition: an AppExchange package that turned out to be indispensable, a second Sandbox the development team asks for, a few hundred extra MuleSoft hours for an ERP integration. In a custom RFP, you try to get those costs into scope up front, which makes things tighter but also harder to predict perfectly. A good partner therefore works with a fixed-price MVP and a transparent development rate rather than an open-ended consultancy engagement.
What a Salesforce-to-custom migration looks like in practice
A sensible migration rarely happens as a big bang. The pattern we see work time and again combines data export, a parallel run, a phased process cutover and, only at the very end, scaling down your Salesforce licences.
Step 1: Data export and model mapping
Using Data Loader or the Bulk API, you export Accounts, Contacts, Opportunities, Cases, custom objects, Tasks and Activities. At the same time, you document Validation Rules, Flows and Apex logic so the development team can reproduce the business rules in the new stack. Expect a serious discovery phase: the export itself isn't the work, understanding what all those rules actually do is.
Step 2: An MVP of the custom CRM
First build the 70 per cent of functionality that is used most: account and contact management, pipeline, tasks, email integration and basic reports. No full feature parity on day one, as that would undermine the business case. The edge cases follow in iterations once the first teams are live.
Step 3: Parallel run with sync
Both systems run side by side for a few weeks, with a two-way sync or daily delta imports. A first team (often one region or one business unit) already works entirely in the new CRM, while the rest stay in Salesforce. This lets you test real-world performance, edge cases and adoption without business risk.
Step 4: Phased cutover per team
You migrate permanently per business unit, region or customer segment. Salesforce licences are scaled down pro rata at the next contract renewal, and not before, so you don't burn budget on a half-finished solution. Communication, training and change management run in parallel.
Step 5: Rebuilding your integrations
ERP integrations (Exact, Unit4, AFAS, SAP), email (Outlook, Gmail), telephony, marketing automation, finance: everything that used to hang off Salesforce via MuleSoft or point-to-point gets a new endpoint. Many organisations use this moment to modernise the integration layer into an API-first architecture that is easier to replace.
Step 6: Archive org or read-only export
For compliance and historical reporting, many organisations keep a scaled-down Salesforce org as a read-only archive, or export the entire history to a data lake (BigQuery, Snowflake, Postgres). Not glamorous, but essential for audit trails and long-lookback questions from finance or legal.
A successful migration depends less on technology than on people-side change management. Sales teams that have worked in Salesforce for years have muscle memory and their own workarounds, and you need to take those seriously. Plan training sessions, office hours with the product owner and a feedback channel where users get an answer within 48 hours to "where is this field now?". For the integrations between the new CRM and surrounding systems, for example the transition to a Salesforce integration during the parallel-run phase, we typically work with API integrations that later grow into the final architecture.
When you should simply keep Salesforce
It would be unfair to tell only the pro-custom story. For a considerable share of the companies we speak to, Salesforce is not just reasonable but downright the right choice. A few clear signals.
You genuinely use Salesforce's advanced features
Salesforce Field Service for field-service planning with dispatch, scheduling engines and mobile workforce. CPQ for complex product configuration. Marketing Cloud Engagement for multi-channel journeys with extensive segmentation. If these modules are indispensable to your operations, building a comparable system rarely outweighs the licence cost.
True enterprise scale with international teams
With thousands of seats across multiple continents, regional compliance requirements and an established global pool of admin talent, Salesforce is often the pragmatic choice. Partner availability and the fact that new hires already know the system outweigh any licence savings.
You have a well-negotiated enterprise contract
With an ELA (Enterprise License Agreement), a substantial discount per seat, bundled modules and fixed involvement in the roadmap, Salesforce can be surprisingly competitive. Renegotiating such a contract is almost always the first step before you consider custom.
Compliance file for customers or regulators
Some customers or regulators explicitly require a certified CRM platform with SOC 2 and ISO reports. In heavily regulated sectors (financial services, life sciences, public tenders), keeping Salesforce is sometimes cheaper than pursuing comparable certification for a custom build.
Further reading on choosing a CRM
A CRM decision rarely stands alone. These are the pages most often consulted by companies weighing up this choice.
Custom CRM software development
Our main page on custom CRM describes the approach: discovery, MVP, phased rollout and ongoing development. It includes the stack choices (Postgres, TypeScript, Astro or Next.js for the UI).
Building a Salesforce integration
During or after a migration, a Salesforce integration is often still needed, for example to pull read-only data from the archive or to sync bidirectionally during a parallel run.
APIs versus integration platforms
Our comparison of APIs and integration platforms helps you choose between MuleSoft, Workato, a lightweight iPaaS or direct API integrations, which is relevant if you are swapping a Salesforce stack for something new.
What custom software costs
For the broader TCO context, it is worth reading app and software costs. The principles (one-off build versus seat licences, ongoing development) also apply to a custom CRM.
Custom ERP system
Companies that tackle their CRM often do their ERP at the same time. Our page on custom ERP describes how to set up both systems so they work together.
Smart API integrations
For the broader integration questions (Outlook, telephony, marketing automation, ERP), our page on smart API integrations is the starting point. Many migrations begin by building a solid API layer before the CRM is replaced.
Frequently asked questions about Salesforce versus a custom CRM
The questions that come up most often in our conversations with directors and IT managers weighing up this decision.
At how many users does a custom build become cheaper?
There is no fixed number, but in our experience the business case usually only becomes convincing from around 40–60 active seats. Below that, the one-off build cost simply can't be spread widely enough. The exception: smaller teams with a highly unusual data model or heavy customisation in Salesforce, where Apex developer hours tip the TCO early on.
How long does a migration from Salesforce to your own CRM take?
In our projects, an MVP with 60–70 percent of the functionality typically goes live in 4–7 months, running in parallel with Salesforce. A full cutover (including all teams, integrations and archive strategy) often takes 9–18 months, depending on complexity, change management and the number of AppExchange packages that need replacing. We strongly advise against big-bang migrations.
What do we do with our Apex code and Flows during migration?
Apex code isn't carried over literally. The business rules inside it are reimplemented in the stack of the custom CRM (often TypeScript or Python). Documentation matters more than code: have a Salesforce architect (internal or a partner) explain what each Apex class and each Flow does before developers start. That discovery phase isn't overhead; it's half of the migration work.
Can we use Salesforce alongside our own CRM?
Yes, and in practice that's the normal picture during a parallel run. Some organisations keep Salesforce for one specific business unit (for example international sales) and use their own CRM for the other units. This does require clear master data agreements: a single place where the account master lives, sync rules and ownership of customer data.
How do we handle the AppExchange packages we need?
Weigh up each package individually: replace it with a SaaS equivalent that also runs standalone (for example DocuSign, Conga or a telephony integration), build it yourself, or set up standard API integrations. AppExchange packages that are deeply embedded in Salesforce metadata (such as some CPQ extensions) often call for a broader review of the sales process, which is actually a healthy moment to do so during a migration.
What does custom do worse than Salesforce?
Fair question. Three things: (1) matching the AppExchange ecosystem is practically impossible, (2) talent availability for your stack is smaller than the worldwide Salesforce admin network, and (3) compliance certification requires extra investment in a custom build. For some organisations, those drawbacks outweigh the TCO savings, and there's no shame in keeping Salesforce in that case.
How do you guarantee we won't get stuck again in five years?
Three principles: (1) we build on open standards (Postgres, REST/GraphQL, OAuth, OpenAPI) so the system doesn't depend on proprietary tooling, (2) data export to common formats is always built in, never an afterthought, and (3) we deliver the source code and documentation so that, in theory, you can continue with another development partner. That is the fundamental opposite of vendor lock-in.
What if we really need Einstein AI or Agentforce?
We build comparable AI functionality (lead scoring, opportunity insights, conversational agents) in custom CRMs using OpenAI, Azure OpenAI or Anthropic APIs. For most B2B CRM use cases, the quality of those models is now at least equal to Einstein, and the cost structure is fundamentally different: you pay per API call, not per seat. For heavy vector search and Data Cloud-style analytics, we work with Postgres + pgvector, BigQuery or Snowflake.
What's the first step if we want to think about this seriously?
An honest TCO assessment of your current Salesforce situation, including licences, admin, consultancy, AppExchange and sandboxes, followed by a short discovery session in which we walk through the data model and the most-used processes. After that, we can put together a fixed-price MVP proposal with a realistic business case. No sales pitch, no pressure: an honest comparison is either the starting point of a migration or confirmation that Salesforce is the right fit for you.
Want an honest TCO comparison?
Send us your current Salesforce setup (number of seats, edition, AppExchange packages, admin hours) and within a week we'll send you a well-founded 5-year TCO comparison with a custom solution. No sales pitch, just the numbers side by side.
Schedule a no-obligation introductory call