"Should we use Salesforce, use HubSpot, or build our own CRM?" is one of the most consequential architectural decisions a growing company makes — and one of the most poorly framed. The right answer depends on questions almost nobody asks during evaluation, and the consequences of getting it wrong compound for years.
We have implemented CRM systems for clients across SaaS, financial services, manufacturing, and B2B services — Salesforce-heavy, HubSpot-heavy, custom-built, and hybrid. This post is the decision framework we use, with real numbers from four recent deployments.
The Five Questions You Need to Answer First
Before any vendor comparison, answer these:
- How complex is your sales motion? A transactional SMB sale ("submit a form, get a demo, sign a contract") is fundamentally different from an enterprise sale with 6+ stakeholders, custom pricing, and 18-month cycles.
- What's your data volume and integration surface? A 50-person team with 10,000 contacts and three integrations is a different problem from a 500-person team with 4 million contacts and 40 integrations.
- Where does your competitive advantage live? Is your sales motion itself differentiated (proprietary scoring, unusual workflow), or is it standard? Custom CRM only makes sense when your process is.
- What's your engineering capacity? Salesforce and HubSpot configuration is itself a specialised skill set. Building custom requires sustained engineering investment.
- What's your tolerance for vendor lock-in? Once you have three years of Salesforce metadata, switching costs are measured in seven figures.
The Salesforce Extension Cost Model
Salesforce is the default choice for enterprise CRM, and for good reason — it scales to the largest deployments on earth and has the deepest ecosystem. But the line-item cost is rarely the real cost.
The realistic total cost of ownership for a Salesforce deployment includes:
- Licence cost. Sales Cloud Enterprise carries a steep per-user list price, with mid double-digit discounts on negotiation. For a 200-user deployment, you are firmly in six-figure annual licence territory.
- Implementation. A serious Salesforce implementation (custom objects, complex automation, integrations) carries a six-figure first-year implementation budget via a consultancy.
- In-house admins. One full-time Salesforce admin per 100–150 users is the rule. That is a fully-loaded mid five-figure cost per admin per year.
- Apex/Lightning developers. Once you're writing custom code, you need Salesforce-specific developers. They command premium hourly rates and are scarce.
- Add-ons. CPQ, Service Cloud, Marketing Cloud, Pardot, Data Cloud — each is its own price tag, often comparable to Sales Cloud itself.
For a 200-user organisation, expect a substantial seven-figure first-year investment with mid-six-figure ongoing run-rate. The economics make sense above ~150 users for complex sales motions and break down quickly below that.
HubSpot: The Mid-Market Default
HubSpot occupies the space where Salesforce becomes too expensive and "no CRM" becomes too disorganised. Pricing is more reasonable per-seat, the UX is dramatically better for non-technical users, and Operations Hub gives you legitimate workflow automation.
Where HubSpot wins:
- Marketing-led sales motions (where the CRM and marketing platform are tightly integrated).
- Teams under 100 users with relatively standard sales processes.
- Organisations without dedicated CRM engineering capacity.
- Use cases dominated by deal management, email tracking, meeting scheduling.
Where HubSpot starts breaking:
- Complex multi-currency or multi-entity setups.
- Custom objects with deep relational requirements (HubSpot's custom objects are usable but less expressive than Salesforce's).
- Heavy reliance on quote-to-cash workflows (no native CPQ comparable to Salesforce CPQ).
- Operations Hub's custom code is JavaScript-only and has tight execution limits (more on this in another post).
When to Build Custom
Building a custom CRM is, in 90% of cases, a mistake. It absorbs engineering capacity that should be going into your actual product, requires you to reinvent solved problems (email tracking, calendar integration, e-signature flows), and creates a system that competes with off-the-shelf products that have 1000+ engineers behind them.
The 10% of cases where custom makes sense:
- The CRM is the product. If you're selling a vertical SaaS that includes CRM functionality to your customers (e.g., a real-estate-specific CRM, a clinical-trial management system), it has to be custom.
- Your workflow is genuinely unusual. Trading desks, market-making operations, regulated industries with audit trail requirements that standard CRMs can't satisfy.
- You have unique data assets to integrate. A proprietary scoring model, a real-time pricing engine, or a network graph that doesn't map onto contact/account/deal.
- Scale beyond off-the-shelf. A handful of companies have CRM data volumes that genuinely break Salesforce or HubSpot. They almost all know who they are.
For everyone else, customising an existing platform — even when it requires significant configuration work — is the rational choice.
The Hybrid Pattern
Increasingly, what we recommend is hybrid: a CRM platform handling the standard sales operations (Salesforce or HubSpot), with a custom application layer for the workflows that are genuinely differentiated. This pattern keeps you off the rocks of "rebuild everything" while letting you build the parts that matter.
A concrete example: a fintech client's deal workflow involves real-time credit checks, regulatory document collection, and a custom approval chain. We built that as a Laravel application that reads/writes Salesforce via the REST API, with a custom UI optimised for the sales rep's actual workflow. Salesforce remains the system of record; the custom app is the system of work.
Real Numbers From Four Deployments
| Company | Choice | Year-1 Cost | Years to ROI | Notes |
|---|---|---|---|---|
| 240-user B2B SaaS | Salesforce + custom layer | large 6-figure | 1.5 | Custom layer for deal-room workflows |
| 85-user fintech | HubSpot Enterprise | mid 6-figure | 0.9 | Migration from Pipedrive |
| 32-user professional services | HubSpot Pro | sub 6-figure | 0.6 | Was on spreadsheets |
| 12-user vertical SaaS | Custom (CRM is product) | mid 6-figure | 2.2 | CRM functionality is sold to end users |
A Simple Decision Tree
- Is the CRM functionality something you sell to your customers? Build custom.
- Are you under 30 users with a standard sales motion? HubSpot Starter or Pro. Don't overthink it.
- 30–150 users, marketing-led sales motion? HubSpot Enterprise + Operations Hub.
- 150+ users, complex enterprise sales, multi-product? Salesforce. Pair with a custom layer for differentiated workflows.
- Heavy quote-to-cash or CPQ needs? Salesforce + Salesforce CPQ.
- Regulated industry with audit-trail requirements that standard CRMs can't satisfy? Custom or heavily customised Salesforce.
- Anything else? Default to HubSpot. The conventional wisdom that you'll "outgrow it" is rarely true under 200 users.
Key Takeaways
- Five questions matter more than vendor comparison: complexity, volume, differentiation, capacity, lock-in tolerance.
- Salesforce all-in cost is 3–4× the licence line for enterprise deployments.
- HubSpot wins under 100 users and for marketing-led sales motions.
- Custom CRM makes sense in roughly 10% of cases — usually when the CRM functionality is itself your product.
- Hybrid (CRM platform + custom application layer) is the right answer more often than people realise.
- Run the numbers on the four-deployment table before assuming "we'll outgrow HubSpot."