Choose Salesforce, HubSpot or Zoho when your sales process is a standard pipeline and you want fast setup and a large app marketplace. Build a custom CRM when the process is unusual, the CRM must work inside your ERP, data must live somewhere specific, or per-user licences across many users outweigh building and running your own. Many businesses choose a hybrid.
This is not a question of which product is best. The three packaged CRMs are mature and capable. The question is whether your way of selling and serving customers fits the shape they assume, and what it costs, in licences and in workarounds, when it does not. If you are still deciding whether you need a CRM or an ERP at all, start with ERP vs CRM: the difference and which you need.
What do Salesforce, HubSpot and Zoho do well?
All three cover the core of CRM well: contacts and companies, leads, deal pipelines, tasks and activities, email, reporting and mobile access. Each also has a distinct strength. The summary below is based on each vendor's own product pages and documentation, checked in October 2026; features and editions change, so confirm details with the vendor.
| Salesforce | HubSpot | Zoho CRM | |
|---|---|---|---|
| Known for | Lead and opportunity management, forecasting and deep configurability | An easy-to-adopt CRM connected to marketing, sales and service tools | Broad functionality and process automation across a large suite of business apps |
| Customisation and automation | Custom objects that behave like standard objects; Flow Builder for point-and-click automation | Custom objects (on Enterprise editions); workflow automation in paid hubs | Blueprint, which models a process as states and transitions with required steps; workflow rules |
| Ecosystem | AppExchange marketplace of apps and consultants | App Marketplace with a large catalogue of integrations | Zoho's own suite plus a large integration catalogue |
| AI | Agentforce AI agents across the sales cycle | Breeze AI assistant | Zia AI and agents |
| Free option | Free Suite for up to two users | Free CRM tools with no expiry date | A free edition for up to three users |
| Hosting regions | Hyperforce regions in many countries, plus EU and Swiss operating zones | Data centres in the US, EU (Germany), Canada and Australia | Data centres in regions including the US, EU, India, Australia, Japan, Canada, Saudi Arabia and the UAE |
What packaged CRMs give you that a custom build has to earn: speed to first use, a large pool of trained administrators and partners, security and infrastructure run by the vendor, continuous feature releases, and integrations other people have already built.
What drives the cost of a packaged CRM?
The licence is the visible part. The full cost has several categories, and the balance between them is what decides whether building your own is worth considering.
| Cost category | Packaged CRM | Custom CRM |
|---|---|---|
| Licences | Per user (seat), per month or year; rises with every user and edition upgrade | None for the CRM itself; hosting and any third-party services instead |
| Editions and add-ons | Features such as custom objects, advanced automation, AI, forecasting or extra storage are often in higher editions or paid add-ons | Built once to your needs; each new feature is new development |
| Administration | A trained in-house admin or a partner retainer | A product owner on your side and a support agreement with the developer |
| Implementation | Configuration, data migration and training, often through a partner | Discovery, design, build, migration and training |
| Integration | Connectors, middleware and API usage limits | Built directly against your ERP and other systems |
| Change over time | Vendor releases arrive on the vendor's schedule; price and packaging can change at renewal | You decide what changes and when; you also pay for every change |
Two practical points. First, count every user who needs any access, not only sales staff: branch staff, dealers, field agents and managers who only view reports often push seat counts up. Second, price the edition you will actually need in year three, not the one you start on.
When does a custom CRM make sense?
When several of the following are true at once. One signal alone rarely justifies a build.
- Your pipeline is not a pipeline. Admissions with document checks, tenders with compliance stages, property bookings with instalment plans, or loan applications with approvals look more like case management than a sales funnel. Packaged CRMs can be configured for these, but heavy configuration is its own kind of custom build.
- The CRM must live inside operations. Sales staff need live stock, credit limits, delivery status, production dates or contract terms on the same screen, and orders must flow straight into the ERP. If integration is the bulk of the work, building the CRM around the ERP can be simpler than syncing two systems.
- Data must live in a specific place. Some sectors and governments require data in-country or on your own servers. Check the vendors' hosting regions first, since they cover many countries; a custom build matters when none of them meets your requirement.
- Per-seat economics at scale. Hundreds of light users, such as dealers, agents or branch staff who log a few activities a day, multiply licence costs while using a fraction of the features.
- Offline or WhatsApp-first selling. Field teams in areas with weak coverage need a mobile app that works offline and syncs later; customers who buy over WhatsApp need conversations tied to orders, not just to contacts.
- Multiple entities with different processes. A group whose companies sell in different ways may need one customer view with several distinct workflows underneath.
- The CRM is part of your product. If customers or partners use it, through a portal or as part of a service you sell, you will want control over its roadmap and design.
When does a packaged CRM win?
More often than vendors of custom software like to admit. Choose Salesforce, HubSpot or Zoho when:
- Your sales process is a recognisable lead-to-deal pipeline
- Marketing automation, email campaigns and landing pages matter as much as sales tracking
- The team is small enough that licences are a modest cost
- You have no one who can own a custom product's roadmap
- You need to be running within weeks
- The integrations you need already exist in the vendor's marketplace
- You would rather the vendor carry infrastructure, security patching and upgrades
Is there a middle option between custom and packaged CRM?
Yes: keep a packaged CRM as the record for contacts and pipeline, and build custom pieces around it. Common patterns include a custom integration that syncs orders, invoices and credit status between the CRM and your ERP; a customer or dealer portal that reads from both; a purpose-built mobile app for field staff; or a custom module on the vendor's own platform.
The hybrid keeps the packaged CRM's strengths while removing the gaps that hurt most. Its risks are API usage limits, changes in the vendor's platform that break integrations, and paying both licences and development. Our systems and API integration work is usually where this option starts.
Custom vs packaged CRM: a decision scorecard
Score each factor from 1 (strongly favours packaged) to 5 (strongly favours custom), and weight the ones that matter most to your business.
| Factor | Favours packaged (1) | Favours custom (5) |
|---|---|---|
| Sales process | Standard lead-to-deal pipeline | Case-like, multi-stage, rule-heavy |
| Integration depth | Light sync with email, calendar, accounting | Real-time with ERP, stock, production or billing |
| Data location | A vendor region meets your rules | In-country or on-premise required and not covered |
| User numbers and type | Few users, mostly full-time sellers | Many light users across branches, dealers or agents |
| Connectivity and channels | Office-based, email and phone | Offline field work, WhatsApp-led selling |
| Entity structure | One company, one process | Several entities with different processes |
| Internal ownership | No product owner available | A named owner with time and authority |
| Time to first use | Needed within weeks | A phased build is acceptable |
How to read it: if most heavily weighted factors score 4 or 5 and you have an owner, a custom build is worth scoping. If scores are mixed, look hard at the hybrid. If most are 1 or 2, a packaged CRM is the sensible choice, and for a very small team our free Timeline CRM for Windows may be enough to start.
What should you know about WhatsApp-led sales in any CRM?
Whichever CRM you choose, WhatsApp integration runs through Meta's WhatsApp Business Platform, and Meta's rules apply equally to packaged and custom systems.
- Templates outside the customer service window. Meta's developer documentation states that when a customer messages you, a 24-hour customer service window opens, and outside it you can only send pre-approved template messages. Templates are reviewed by Meta when created or edited.
- Opt-in. The WhatsApp Business Messaging Policy requires you to obtain opt-in before messaging people, so the CRM must record when and how each contact opted in.
- Business verification and limits. Meta notes that verifying your business portfolio factors into higher messaging throughput and Official Business Account status, and messaging limits on how many people you can reach in a day grow with quality and volume.
Plan for template approval time, store consent with each contact, and design a fallback channel. Avoid unofficial tools that automate the WhatsApp app outside the Business Platform, since they are not supported by Meta and put the number at risk.
How do you migrate to a new CRM without losing history?
Treat the move as a data project, not an export and import. A checklist:
- Deduplicate contacts. Normalise phone numbers to international format and emails to lower case, then match on email, phone and company name. Agree which record survives and merge the rest.
- Decide what activity history moves. Calls, emails, notes and meetings with their original dates and authors are valuable for open accounts; very old history may be better archived and searchable than migrated.
- Map ownership. Map every old user to a new one. Reassign records owned by people who have left before import, not after.
- Map pipeline stages and fields. Old stages rarely match new ones one to one; agree the mapping with sales managers.
- Carry consent. Migrate opt-in status, source and date, especially for WhatsApp and email marketing.
- Keep an ID crosswalk. Store old record IDs so integrations, attachments and audit questions can be traced.
- Trial load and reconcile. Load into a test environment, compare record counts and open deal values, and let users check their own accounts before cut-over.
When is a custom CRM the wrong choice?
When the reasons are mostly about cost alone. Building and maintaining software is a long-term commitment: someone must own the roadmap, fix defects, keep dependencies patched and train new staff. A custom CRM is also the wrong choice when the process is still changing every month, when no one can spare time to define requirements, or when the main need is marketing automation, where packaged tools are strong. Our software requirements brief template is a useful test: if you cannot fill it in yet, you are not ready to build.
Exploring a custom or hybrid CRM with Timeline Digital
If your scorecard points toward custom or hybrid, we can review your process and integrations and recommend which route fits. Timeline Digital starts with a free pilot of 2 to 3 key modules before the full project, so you can test a working CRM against your real pipeline. Learn more about our CRM development services.