The short answer: if your business sells through a fairly standard pipeline — leads, opportunities, deals — a subscription CRM like Salesforce or HubSpot is usually the right choice. A custom CRM makes sense when your work doesn't fit that model, when the team avoids the CRM because it doesn't reflect how they work, or when per-user costs have grown significant.
What Salesforce and HubSpot do well
They're mature, well-supported products with large ecosystems. They handle standard sales and marketing processes well, integrate with many other tools, and can be running quickly. For a typical sales team, that's hard to beat.
Where they get in the way
- Your work isn't a sales pipeline. Managing sites, addresses, contractors, service jobs or contracts doesn't map neatly onto “deals.”
- Custom objects everywhere. When configuration becomes heavy customization, you're paying for a product and for development.
- Adoption fails. The team keeps the real information in spreadsheets because the CRM doesn't reflect their work.
- Per-user costs compound as the team grows, and advanced features sit in higher tiers.
What a custom CRM offers
- Records and relationships that match your business
- Stages that match how work actually moves
- Only the fields your team uses
- Direct integration with your website and systems
- No per-user fees; you own the code and data
What a custom CRM costs you
- Higher upfront investment
- Time to build — usually phased
- Maintenance responsibility
- No marketplace of ready-made add-ons
How to decide
| Question | Points toward |
|---|---|
| Is your process a standard sales pipeline? | Subscription CRM |
| Does the team avoid your current CRM? | Investigate why — often fit |
| Do you manage things other than deals — sites, jobs, contractors? | Custom CRM |
| Are you heavily customizing a subscription CRM? | Consider custom |
| Is per-user cost growing faster than value? | Consider custom |
Before switching
If you already use a subscription CRM, ask whether the problem is the product or the setup. A poorly configured CRM can often be fixed without replacing it. If the product's model genuinely doesn't match your work, a custom CRM — starting with the core records and pipeline — is worth exploring.