What each option is
HubSpot is a hosted customer platform. Its CRM holds contacts, companies, deals and tickets, and its hubs add marketing, sales, service and content tools on top, sold in tiers. Configuring it means setting up pipelines, properties, automation and reports so that the product matches your process.
A custom CRM is software built around how your company finds, wins and looks after customers. It models whatever you sell and whoever you sell it to, and it is often joined to quoting, delivery or billing in ways a general product is not.
The two options at a glance
| HubSpot configuration | Custom CRM | |
|---|---|---|
| Time to first use | Quick. A basic pipeline can be running almost at once | Slower. Design and build come before the first login |
| Data model | Contacts, companies, deals and tickets as standard. Custom objects require an Enterprise subscription | Any records and relationships your business has |
| Marketing tools | Email, forms, landing pages and ads tracking in the same product | Connected to a marketing tool, or built only if needed |
| Automation | Workflows in a visual editor, with more available on higher tiers | Any rule you can describe, written as code |
| Integrations | A large marketplace of connectors, and an API whose request limits depend on your tier | Direct connections to your own systems, built for your data |
| Cost shape | Per seat and per tier, rising with features and with contact volume | A build cost, then hosting and maintenance, with no per-seat fee |
| Where data is held | By HubSpot, in the hosting region assigned to your account | Wherever you choose to host it |
| Who maintains it | An administrator on your team | A developer or a partner, with admin screens for daily changes |
Tiers, limits and hosting regions are HubSpot's to set and are revised regularly. These points were checked against HubSpot's product catalog and help pages when this comparison was reviewed.
When each one fits
Configure HubSpot when
- Leads become deals, and deals close or do not
- Marketing and sales should share one view of each contact
- The team is small enough that seat pricing is comfortable
- You want to be working this month, not designing
- An administrator, not a developer, will look after it
Build a custom CRM when
- You track projects, assets, policies or sites more than contacts
- Quoting, scheduling or delivery must live in the same system as sales
- Many staff need access, and most would use a fraction of a seat
- Data must sit in a country or a system the product does not offer
- The top tier is needed for one feature, and the price follows
Where Salesforce fits
Salesforce is the other package most buyers consider. It is less a finished CRM than a platform for building one, with custom objects, automation and code available to shape it closely to a business. That depth comes with per-user licensing by edition, a need for a trained administrator and, for most companies, an implementation partner.
Salesforce suits you when
- The sales organization is large, with territories, forecasts and approvals
- You need deep customization and want a vendor's platform under it
- A dedicated administrator or team will own it
- Partners and add-ons from its marketplace matter to you
It is more than you need when
- A handful of people sell through one simple pipeline
- Nobody will be responsible for administering it
- The customization you want is really an operations system
- License cost per user would exceed the value each user gets
The comparison with custom software is the same in outline as for HubSpot. The closer your process is to selling in the usual sense, the better a package serves you. The more your CRM is the place where the work itself gets done, the stronger the case for building it.
Signs a package no longer fits
- Deals are being used to hold something else. Projects, shipments or contracts are stored as deals because nothing closer exists on your tier.
- The real data lives in spreadsheets beside the CRM. People update the CRM for reporting and do the work elsewhere.
- Integrations fail quietly. Scheduled syncs hit request limits or map fields badly, and the numbers drift apart.
- The bill grows faster than the team. New seats and a higher tier are bought for a few features.
- Reports need exporting. Management questions are answered in a spreadsheet built from an export.
A worked example
A software reseller and an elevator maintenance company
Both companies are invented.
- The software resellerTwelve salespeople follow leads from the website through demos to signed orders. Marketing runs email campaigns to the same contacts.
- Its decisionHubSpot, configured over a few weeks. Its standard objects describe the business exactly.
- The maintenance companySells service contracts on 4,000 elevators. What matters is each unit, its inspection history, its contract and the technician's next visit.
- Its decisionA custom system in which the elevator is the central record, joined to scheduling and invoicing. Contacts and deals were a small part of the picture.
The reseller sells in the way packages expect. The maintenance company manages assets and visits, and only calls it CRM out of habit.
A checklist to decide
Tick what applies. The first four favor a package. The last four favor custom software.
Package or custom CRM
0 of 8 checkedWhat to do next
Draw your process on one page and name the record at its center. If it is a contact or a deal, try a package first. If it is something else, read how we approach custom CRM development.
Already on a package and working around it? Tell us where it strains. Sometimes the answer is better configuration, and we will say so.
Common questions
Is HubSpot's free CRM enough for a small business?
Often, at the start. It covers contacts, companies, deals and basic reporting, which is what a small sales team needs first. The limits appear when you want more automation, more reporting, more seats or objects of your own. Begin with the free tier, note what you miss during real use, and upgrade or look elsewhere based on that list, not on a feature comparison.
When do we need HubSpot's Enterprise tier?
The most common trigger is custom objects, which HubSpot's own documentation places on Enterprise subscriptions. If your business has a central record that is not a contact, company, deal or ticket, you will want them. Price the Enterprise tier for all the seats you need before you rely on that feature, and compare the total with a custom build.
Can a custom CRM still use HubSpot for marketing?
Yes, and it is a common arrangement. The custom system holds the records and the operational workflow, and the marketing platform sends campaigns and captures leads. The two are connected through the platform's API, within its request limits. Decide which system owns each field, so that contact details are edited in one place and copied to the other.
Is Salesforce a better choice than a custom CRM?
For a large sales organization with complex territories, forecasting and approvals, usually yes, because those features exist and are maintained for you. For a company whose CRM is mainly an operations tool, customizing a sales platform until it does the job can cost more than building what you need. The deciding question is what the central record of your business is.