CRM Systems: Buy, Customize, or Build From Scratch?
"We need a CRM" is one of the most common requests we get, and it's also one where the right answer is least likely to be "let's build you one." A CRM is one of the few categories of software where the off-the-shelf options are genuinely excellent, well-funded, and built by teams who've thought about sales processes far longer than any one custom project will.
Start with off-the-shelf, seriously
HubSpot, Zoho, Pipedrive, and a dozen others cover the vast majority of sales processes: pipeline stages, contact history, follow-up reminders, email tracking, reporting. If your sales process looks roughly like "lead comes in, gets qualified, moves through stages, closes or doesn't," you almost certainly don't need custom software — you need one of these, configured properly.
When customization is the right layer
Most CRM platforms support custom fields, custom pipelines, and increasingly, custom automation and API integrations. This is where we spend most of our CRM-related project time: not writing a CRM, but connecting one to the rest of your business — pulling in data from your website forms, triggering WhatsApp messages on stage changes, syncing with your billing system.
When a fully custom CRM actually makes sense
- Your sales process doesn't map to a linear pipeline — multi-party deals, recurring contract renewals, or a process that genuinely differs between customer segments.
- You need to combine sales data with operational data — inventory, delivery logistics, service history — into one system, and no CRM vendor's data model was built to hold what you're tracking.
- Per-seat SaaS pricing stops making financial sense at your headcount.
- Data ownership and residency requirements mean you can't put customer data in a third-party vendor's cloud at all.
The question isn't whether you could build a CRM. It's whether your sales team's time is better spent adapting to a tool built by specialists, or waiting on custom software to catch up to what that tool already does well.
How we actually approach this with a new client
We map the actual sales process first — every stage, every handoff, every piece of data someone needs at each step — before recommending anything. Half the time, that mapping exercise alone reveals the process is simpler than the client thought, and this is exactly the kind of readiness check we describe in signs you're ready for workflow automation.
If you're mid-conversation with your team about whether to buy or build, the fastest way to get an honest answer is to write down your actual sales process, stage by stage, before looking at any tool.
Talk to us
Have a project in mind? Tell us about it.
Four quick questions and we'll reply within one business day with an honest view on the fastest way to ship it, whether that's our own products, a custom build or an integration.
Start your project
Let’s build something great
Which industry does your business belong to?
Pick the closest match — we'll tailor the rest for you.
Keep reading
Do You Actually Need Custom Software, or Would a SaaS Tool Do?
About a third of the 'build us custom software' conversations we have end with us recommending a $30/month tool instead. Here's how we tell the difference before quoting anything.
AutomationSigns Your Business Is Ready for Workflow Automation (and Signs It's Not)
We turn away automation projects more often than people expect — not because we can't build them, but because automating a broken process just breaks things faster.
Custom SoftwareIntegrating Payment Gateways: What Breaks and Why
Every payment gateway's docs make integration look like an afternoon's work. The afternoon's work is the easy 80%. The other 20% is where real projects slip.
