When a custom CRM makes sense
Most companies should start with an off-the-shelf CRM. If you sell one thing, through one pipeline, with a small team, HubSpot or Pipedrive will do the job for a monthly fee and nobody needs to write code.
Custom starts to make sense when the CRM is fighting you. The signs are consistent: the sales team keeps a spreadsheet next to the CRM because the CRM can't model the deal. Managers export to Excel every Monday to see the real picture. Orders get retyped into accounting. Branches or teams need to see only their own data and the permission model can't handle it. And the monthly bill keeps climbing as you add seats and add-ons you only half use.
If three or more of those are true, you're already paying for a custom CRM. You're just paying for it in hours instead of in software.
What drives the cost
The price of a custom CRM has little to do with contact lists and pipelines. Those are the easy part. The cost sits in the parts that are specific to how you sell.
- Your deal model: a property viewing, a wholesale reorder and a six-month B2B contract are three very different objects. The more your deal differs from a generic opportunity, the more value in building it right.
- Roles and visibility: agents, branch managers, back office, owner. Who sees which leads, who can reassign, who approves discounts.
- Integrations: accounting and invoicing are the big ones, then email, calendars, telephony and your website forms.
- Migration: years of contacts, deals and notes spread across an old CRM, spreadsheets and inboxes.
- Automation and AI: follow-up reminders, drafted emails, lead scoring, and the ability to ask the CRM a plain question like which buyers haven't heard from us in a week.
Typical price ranges
A simple custom CRM for one team with one pipeline and no integrations can be built for a modest budget, but at that size SaaS is usually the better deal. The custom sweet spot is a CRM that is wired into the rest of the company: orders, invoicing, stock, projects or service jobs.
At Company Maxxing, a CRM as part of a Core system is €18,000, with up to five roles, data migration and three months of support. If you need the AI layer, accounting and email integrations, automated follow-ups and a client portal, that's Maxxed at €48,000. Multi-branch and multi-country groups sit in Empire, from €120k. Each extra integration beyond what's included is €4,500.
Compare that to the real cost of your current setup: per-seat licences times headcount times years, plus the hours spent exporting, retyping and reconciling.
How a custom CRM pays for itself
The payback rarely comes from the CRM screens. It comes from what stops happening. Leads stop going cold because nobody owned the follow-up. Orders stop being retyped into accounting, with the typos that come with it. Managers stop spending Monday morning building a report that the system could show them live.
A useful exercise before you talk to any builder: take the last ten deals you lost or that stalled, and trace where they went quiet. If most of them died in a gap between people or tools, a better-shaped CRM will earn its cost back. If they died on price or product, a CRM won't fix that, and you should spend the money elsewhere.
Also count seats honestly. Per-seat pricing is fine at five users. At forty users across three branches, with add-ons for reporting and automation, the annual bill starts to look like a build budget, every year, for software you don't own.
Features worth building, and ones to skip
The best custom CRMs are smaller than people expect. They do fewer things, but they do exactly what your team needs, in the order they need it.
- Build: a deal record that matches your real sale, with the fields your team actually fills in.
- Build: two-way sync with accounting, so orders, invoices and payment status live next to the customer.
- Build: branch or team scoping, so managers see their people and nobody else's.
- Build: follow-up rules that fire on silence, not just on dates.
- Skip: generic marketing automation you'll never configure. Connect your existing email tool instead.
- Skip: dashboards nobody asked for. Start with the three numbers the owner checks every week.
Custom CRM vs customising Salesforce
There's a middle path: take a big platform and customise it heavily. It can work, but be honest about the cost. You pay the licence, you pay a consultant to customise it, and you pay again every time the platform changes or you want something it wasn't designed for. You also don't own the result.
A custom CRM built on a standard stack is yours. No per-seat pricing, no forced upgrades, and any competent team can take over the code. The trade-off is that you need a builder who understands sales processes, not just databases.
How to scope it without a six-month discovery
Skip the requirements workshop. Instead, gather what already exists: the CRM export, the spreadsheet next to it, a few real deals from start to invoice, and the questions the owner asks every Monday.
That's our starting point. We sit with your team, screens shared, map how a lead becomes cash, then quote a fixed price. After kickoff, you get a first working version running on a sample of your real deals within 24 hours. If you're paying for a CRM your team works around, apply and show us the spreadsheet next to it.