When HubSpot starts to pinch
HubSpot got you going. Forms fed the CRM, emails were tracked, the pipeline was visible. As the business grew, the things that make it different started to matter more: projects that run for months after the deal, multiple sites per customer, equipment you service, contracts with renewal terms, approvals before a quote goes out. Custom objects and properties helped for a while. Now there are dozens of properties, several pipelines used for things that are not really deals, and a spreadsheet that holds the parts HubSpot cannot.
And each time you need one more feature, the answer seems to be moving up a tier.
Why the fit changes
HubSpot's model is built around contacts, companies, deals and tickets, with marketing at its heart. That suits a great many businesses. It fits less well when the centre of your operation is something else, such as a job, a contract, a property or an asset, and the sales pipeline is only the front door.
Pricing that scales with seats and tiers is fair when you use what each tier adds. It becomes frustrating when you pay for a whole tier to get one capability, or when people who only need to look up a customer need a paid seat.
Comparing the options fairly
| Option | When it makes sense | Trade-off |
|---|---|---|
| Reconfigure HubSpot | The model fits and the setup has drifted | Needs someone to own the setup afterwards |
| HubSpot plus a custom app | Sales and marketing fit HubSpot; operations do not | Two systems to keep in sync through the API |
| Custom CRM | Your core process does not fit contacts and deals | You own the build and its maintenance |
| Different off-the-shelf CRM | Another product matches your model better | Migration effort, new limits to learn |
Keeping HubSpot for marketing while moving operational records into a custom system is common and often sensible. HubSpot's marketing tools are strong, and replacing them with custom code rarely makes sense.
How we work through it
- Walk through your process end to end, from first enquiry to delivery and renewal, and mark which parts live in HubSpot, which in spreadsheets and which elsewhere.
- Audit the HubSpot account: properties, pipelines, custom objects, workflows and integrations, noting what is used and what is clutter.
- Identify the core record your business revolves around and whether HubSpot can hold it comfortably.
- Lay out the options with what each would involve, and recommend the lightest one that removes the workarounds.
- If building, design the custom system around your core record, connected to HubSpot through its API where HubSpot remains useful, and to your accounting and operational tools.
- Migrate carefully: HubSpot's APIs and exports allow contacts, companies, deals and activity history to be moved or synced, and we plan the cutover so nothing is lost.
What you end up with
A clear system of record for each part of your business. Marketing keeps the tools it relies on. Operations gets a system built around how work actually happens rather than squeezed into deal stages. The spreadsheet beside HubSpot is retired. And decisions about paying for more seats or tiers are made on what you actually use.
Just as importantly, the choice is made on evidence. Many businesses swap CRMs in frustration and find the same problems follow them, because the root cause was setup or process rather than the product. Working through your process first means that if you do move, you move for a reason that the new system actually addresses, and if you stay, you stay with a cleaner HubSpot that the team is happier to use.
Is this where you are?
- You use deal pipelines for things that are not really deals.
- HubSpot holds sales and marketing, but operations run in spreadsheets.
- You have considered a tier upgrade for a single feature.
- Property lists have grown so long that nobody knows which fields matter.
- Staff who only need to look things up need paid seats.