The question keeps coming back to the executive table: “Should we go with HubSpot, Salesforce, Pipedrive — or build our own CRM?” And the pressure is real on both sides. SaaS vendors show you immaculate demos. Development agencies explain that nothing replaces a tool designed for your processes. Both are partly right. Neither is entirely right.
For SMEs and mid-market companies with 20 to 200 employees, this choice can weigh tens of thousands of euros over 5 years and determine whether your sales team works with the tool or against it. Yet in practice, the decision is too often made on secondary criteria — the sales director’s preference, a seductive demo, a peer’s recommendation.
This article is a decision method, not a sales pitch. You’ll find when a standard CRM is the right answer (and it is in the majority of cases), which concrete signals impose going custom, the total cost calculation over 3 to 5 years, the hidden risks of custom that no one tells you about, and the hybrid option that many agencies leave unspoken because it pays less.
At Seganiko, we build custom CRMs for clients who really need them, and we recommend standard solutions to other clients when that’s what suits them. The criterion for deciding is your profile — not our order book.
Why a standard CRM is enough in 80% of cases
Let’s set the ground honestly. For the majority of SMEs, a standard CRM (HubSpot, Pipedrive, Salesforce, Zoho, monday CRM) addresses real needs well. Here’s why.
First, the commercial processes of most companies look like those of their competitors: prospecting, qualification, opportunity, quote, negotiation, signing, customer follow-up. SaaS CRMs encapsulate this logic. They are ten years ahead of any in-house solution in terms of UX, standard automation, and integrations.
Second, the “hidden cost” of custom is real: initial development, sure, but mostly maintenance over time. A €30,000 custom CRM easily costs €6,000 to €12,000 per year in maintenance, security updates, evolutions, support. Over 5 years, you reach €60,000–90,000.
Third, modern CRMs have become extensible. HubSpot has a solid API, Salesforce has its platform. You can add custom objects, custom fields, workflows, integrations — without touching the core. For 80% of “specific to my company” needs, there is already a configuration possible in a standard CRM.
The trap is to confuse “our process is unique” with “our process isn’t in the HubSpot manual.” Most of the time, the process isn’t unique. It’s just different. And a well-configured standard CRM handles it.
The 4 signals that force going custom
That said, there are cases where a standard CRM does not hold up. Here are the four concrete signals that should make you seriously consider going custom.
Signal 1: your business process is structurally different
Not “slightly different”: structurally. Typical example — a production company that must link quotes, product configuration, production orders, raw material stock, delivery and invoicing, all with build-to-order logic. No SaaS CRM covers this flow natively. You can try Salesforce Manufacturing Cloud, but you quickly reach over €200/user/month, and half the functionality still has to be coded.
Signal 2: you have more than 30 users over 3 years, and the per-seat price is killing you
Salesforce Sales Cloud Enterprise sits around €165/user/month. HubSpot Professional starts at €90/user/month. At 50 users over 3 years, you’re talking €150,000 to €300,000 in licences. At that level, a custom CRM becomes mechanically competitive — you pay back development in 12 to 18 months, then you only pay maintenance.
Signal 3: your data must not leave the EU or your infrastructure
For certain activities — defence, healthcare, public sector, financial — compliance or internal policy requires 100%-controlled infrastructure. Even though HubSpot and Salesforce have EU servers, they remain subcontractors in the GDPR sense. A custom CRM hosted on-premise (or in a private EU cloud) settles the question at the source.
Signal 4: you’ve already tried a SaaS CRM and the team doesn’t use it
It’s the most underestimated signal. If you’ve paid for HubSpot for 18 months and salespeople still fill in Excel on the side, it’s a sign. Either the setup was bad (redoing the configuration fixes the problem), or the tool doesn’t fit how your people work (and then a custom CRM matched to your reality becomes relevant).
If you tick 2 out of 4 signals, going custom deserves serious study. At 3 out of 4, it’s probably the right answer.
TCO over 3 to 5 years: licences vs development
Let’s run the concrete calculation for a 40-user team.
Scenario A — HubSpot Sales Hub Professional + Service Hub + integrations
- Licences: 40 × €90 × 12 months = €43,200/year. Over 5 years: €216,000.
- Initial onboarding + configuration (consultant): ~€8,000 one-off.
- Standard integrations (Stripe, Slack, GA4): ~€0 (included).
- Continuous evolutions and adaptation: ~€10,000/year (internal or external consultant).
- 5-year total: ~€264,000.
Scenario B — Salesforce Sales Cloud Enterprise
- Licences: 40 × €165 × 12 months = €79,200/year. Over 5 years: €396,000.
- Implementation (certified integrator): €25,000 to €50,000 one-off.
- Maintenance and evolutions: ~€15,000/year.
- 5-year total: ~€496,000 to €521,000.
Scenario C — Custom CRM (build)
- Initial development (12 to 16 weeks): €40,000 to €80,000 depending on scope.
- Hosting (managed EU cloud): €6,000 to €12,000/year.
- Maintenance and evolutions (partial team): €18,000 to €30,000/year.
- 5-year total: ~€160,000 to €290,000.
At 40 users, the custom CRM becomes competitive against HubSpot and significantly cheaper than Salesforce. But careful: at 10-15 users, HubSpot remains unbeatable. The tipping point is generally between 25 and 35 users, or earlier if your specific needs require a lot of side development on the standard CRM.
Important note: this calculation does not include your team’s internal time to pilot the project. That’s typically 0.5 to 1 FTE during the construction phase and 0.2 FTE in run. If your team can’t free that time, go back to SaaS.
Hidden risks of going custom
What you’re not told enough when someone sells you a custom CRM.
Risk number 1 — invisible technical debt. A poorly architected custom CRM becomes in 3 years an impossible-to-evolve weight. If the original team leaves, if documentation is thin, you end up with a critical system no one understands. The fix: require documented architecture, tests, and a contractual knowledge transfer.
Risk number 2 — agency lock-in. Once built, who maintains it? If it’s only your development agency, you’re captive. Negotiate from the start a maintenance contract with continuity commitment, full code ownership, and the ability to move the run to another provider.
Risk number 3 — SaaS “free” features that become paid to code. HubSpot gives you natively: email tracking, sequences, integrated calling, integrations with 500+ tools. Recreating half of that in custom is expensive. The discipline: only develop what is truly specific to your business — and leave the rest to standard integrated tools.
Risk number 4 — security. A custom CRM is as secure as the team that built it. HubSpot has 300 people in security; your agency maybe two. If you go custom, require: regular security audits, secret management, tested backups, MFA, logging, GDPR by design. Non-negotiable.
Hybrid architecture (HubSpot + custom modules)
The solution few agencies propose — because it pays less — but which is often the best: hybrid architecture.
You keep HubSpot or Salesforce as the foundation (standard objects: contacts, deals, companies, activities, emails). You develop in custom only the modules that touch your business core: product configurator, specific pricing calculation, deep ERP integration, regulatory workflows. The whole connected via API.
Advantages:
- you benefit from native SaaS features (emails, sequences, dashboards, mobile app, integrations);
- you avoid reinventing the wheel;
- you keep freedom on the part that’s critical for your business;
- you can iterate fast on custom modules without touching the foundation.
Honest drawbacks:
- you still pay SaaS licences (but on a lower plan, sometimes);
- you manage a live integration between two systems;
- you need clear governance — who is the source of truth for each piece of data.
For 60% of SMEs who think “I need a custom CRM,” hybrid architecture is actually the right answer. It combines the best of both worlds at the cost of architectural rigour.
Decide in 1 meeting
To make it operational, here’s the grid to fill in during a 1.5-hour meeting with your CEO, your sales director, and your CIO or an external consultant.
Block 1 — Current and target scope:
- Number of users today and in 3 years.
- Volume of leads/customers/deals per year.
- Critical business process (a diagram, not a spec document).
Block 2 — Differentiation:
- Which processes are strictly “like everyone else”?
- Which processes are genuinely differentiating?
- Are there regulatory or data sovereignty constraints?
Block 3 — Internal capacity:
- Do you have a CIO or internal tech lead?
- Can you free 0.5 FTE for 4 to 6 months for the project?
- Do you have a recurring budget for maintenance and evolutions?
Block 4 — Total cost:
- Calculate the three scenarios (HubSpot, Salesforce, custom) over 5 years.
- Compare to your financial capacity in run and in investment.
If at the end of the meeting you have the four blocks filled, you have your decision. If you’re stuck on a block, you’re missing a key piece of information — and that’s when an external audit is useful.
In practice
There is no universal right answer. There is your profile, your number of users over 3 years, your level of business differentiation, and your capacity to pilot a technical project. The grid above gives you the method to decide.
At Seganiko, we build custom CRMs for clients who really need one — we supported a Cyprus company with a complete enterprise management CRM and a German brewery on a CRM driven by production processes. For other clients, we recommend a well-configured HubSpot. First audit to decide: free, 1.5 hours, you leave with a reasoned recommendation.
Planning an e-commerce project?
We build WooCommerce stores optimized for conversion and performance.
See our WooCommerce service →
