If you run a small team in the US or Canada, you’ve probably been told to “just use HubSpot” or “just use Salesforce”. Often that’s good advice. But some teams sign up, spend months bending the CRM to fit how they work, and still keep a spreadsheet on the side. This post is about telling those two situations apart, and about what a first custom CRM should and shouldn’t include if you go that way.
We build custom CRMs, so we have a bias. We’ll still tell you when an off-the-shelf CRM is the better answer, because it often is.
When an off-the-shelf CRM is enough
HubSpot, Salesforce, Zoho and similar products are mature, well supported and quick to start. They’re usually the right choice when:
- Your sales process is standard. Lead, qualified, proposal, won or lost. Most CRMs model this out of the box.
- You need few integrations, and the ones you need (email, calendar, forms, accounting) already exist in the CRM’s marketplace.
- Your team is small and the seat count is stable, so per-seat pricing stays manageable. Check each vendor’s current pricing page, since tiers and limits change.
- You want marketing tools in the same place, such as email campaigns, landing pages and lead scoring, which off-the-shelf products bundle and a custom build would have to recreate.
- Nobody on your side wants to own software. A product’s vendor handles hosting, security patches and new features.
If that describes you, pick the product that fits your process best and spend your effort on setting it up well.
When teams start looking at a custom build
The teams that ask us about custom CRMs usually describe one or more of these problems:
The process doesn’t fit
Your work isn’t a simple sales pipeline. Maybe it’s a service business where a “deal” becomes a job with site visits, materials and follow-up inspections. Maybe it’s a lender with documents and approval steps, or an agency managing renewals. You can bend a general CRM with custom objects and workflows, but past a point, every change needs a consultant and staff stop using it.
Per-seat cost grows faster than the value
You need 30 people to see customer records, but only five of them use the sales features. On per-seat pricing, the people who just need to look things up can cost as much as the people who sell. A custom app can give different roles different screens without charging per head.
The same data is typed into two systems
A lead comes in through the website, someone copies it into the CRM, then into a job tool or a billing system, then texts the customer from a personal phone. Each copy is a chance for mistakes. If the systems involved don’t connect well, a custom app that sits in the middle, or replaces one of them, can remove the retyping.
You need control over data and location
Some teams want their customer data in a database they own, hosted where they choose, with their own backup and access rules. A custom build allows that.
What a first version should include
The biggest risk with a custom CRM is trying to rebuild Salesforce. Don’t. A good version one is small and fits your real process:
- Contacts and companies, with the fields you actually use, plus search and import from your current spreadsheet or CRM.
- One pipeline with your real stages, not a generic one.
- Roles and permissions, so each person sees what they need: sales, operations, managers, admins.
- A website form that writes straight in, so new leads never get retyped.
- One or two integrations that remove the most manual work, such as email, calendar, accounting or SMS.
- An activity history on each contact: notes, emails, calls and texts.
- Basic reports the team will actually look at.
Leave out marketing automation, complex forecasting, custom dashboards for every role, and a mobile app, unless one of these is the reason you’re building at all. Add them once people are using the core every day.
Questions to answer before you decide
- Which three tasks take your team the most time each week, and does your current CRM help with any of them?
- How many people need to see customer data, and how many actually sell?
- Which systems do you copy data between by hand?
- Who will own the software after launch: an internal person, a vendor, or a development partner?
- What would “working” look like six months after launch?
If most answers point to a standard process and few integrations, stay with a product. If they point to a process nobody else has and a lot of retyping, a custom build is worth pricing.
Calls and texts: Twilio as an integration
For many service businesses, the phone is where customer conversations happen. A custom CRM can use Twilio so that calls and texts are made from the contact record and logged automatically: click-to-call, two-way SMS from a shared business number, appointment reminders, and missed-call follow-up. This is an integration inside the CRM, not a separate phone system you have to manage. See our Twilio development services for that side of the work, or our guide to logging Twilio calls and texts in HubSpot, Salesforce or Zoho if you’re keeping your current CRM.
A middle path worth considering
You don’t always have to choose one or the other. Some teams keep HubSpot or Salesforce for sales and marketing, and build a small custom app for the part that doesn’t fit, such as job scheduling, onboarding or a client portal, connected to the CRM through its API. That keeps the vendor’s strengths and fixes the gap.
What it costs, honestly
We don’t publish a price list, because the cost depends on the number of screens, roles, integrations and data migration involved. A custom CRM has an up-front build cost plus hosting and maintenance. An off-the-shelf CRM has a subscription that grows with seats and tiers, plus setup and admin time. Compare the two over a few years, not just the first month. If you want an estimate, a short call about your process is the fastest way to get one.
If you’re still at the spreadsheet stage, our guide to moving from a spreadsheet to a custom web app covers how to scope that first step.
FAQ
Is a custom CRM better than HubSpot or Salesforce?
Not in general. Off-the-shelf CRMs are better for standard sales processes. A custom CRM makes sense when your process, data or integrations don’t fit them well.
What should a first custom CRM include?
Contacts, one pipeline that matches your process, roles and permissions, a website form that writes in, one or two key integrations, activity history and basic reports.
Can a custom CRM make calls and send texts?
Yes. With Twilio, calls and SMS can be made from the contact record and logged automatically.
Can we keep HubSpot and add custom software?
Yes. A small custom app can handle the part HubSpot doesn’t fit and sync with it through its API.
How do we move our data into a custom CRM?
Usually by exporting from your current CRM or spreadsheet, cleaning the data, and importing it as part of the build.
Talk it through
See what we build on our custom web app and CRM development page, or contact Xsquare and tell us how your team works today. If an off-the-shelf CRM is the better fit, we’ll say so.
