Can you keep HubSpot and modernise everything around it?
Yes. HubSpot can stay your customer and pipeline system of record while a bespoke, real-time interface gets built on top of it — no rip-and-replace, no CRM migration, and nothing lost from the setup your team already runs on. This is what Sysgraft calls a graft: a precise join between a new intelligent layer and the systems you already own.
Should you replace HubSpot, or build around it?
For most £1.5m–£20m+ UK businesses, the honest answer is: build around it.
HubSpot is usually not the problem. It's a genuinely capable CRM, and for pipeline, marketing and customer communication it does that job well. The problem is that a CRM was never designed to show whether a deal is actually profitable once delivery cost, stock position, or finance data gets factored in. The frustration leaders feel — pipeline value that doesn't reconcile with what finance later books, a deal marked "won" with no visibility into whether it can actually be fulfilled on time — isn't a reason to tear HubSpot out. It's a reason to add a layer that joins it to the systems holding the rest of the picture.
Ripping out a working CRM to solve a visibility problem is one of the more disruptive mistakes a growing business can make: months of retraining the one system your revenue team touches daily, painful historical pipeline migration, and real risk to deals mid-flight — to fix something a graft would fix without any of it.
What connecting to HubSpot actually involves
HubSpot's CRM data — contacts, companies, deals, tickets, and how they're associated with each other — sits behind a documented REST API (the crm/v3 endpoints, with associations now on v4). Authentication is by bearer token: a private app access token for a single account, or OAuth 2.0 for anything that needs to span multiple HubSpot portals.
The number that actually shapes a build is the rate limit, and it scales with subscription tier: 100 requests per 10 seconds on Free and Starter, rising to 190 per 10 seconds on Professional and Enterprise, on top of a separate daily cap running from roughly 250,000 up to a million calls depending on tier. Search endpoints carry their own, stricter limit again.
None of that is unusual by CRM standards — Salesforce, Pipedrive and Zoho have each moved to some version of a consumption-based budget rather than a flat request count, for the same reason HubSpot has. But it's exactly the kind of detail that decides whether a build syncs cleanly from day one or needs proper batching and backoff designed in from the start, and it's confirmed against your account's actual tier during discovery, not assumed.
Common questions about modernising around HubSpot
Can custom software sit on top of HubSpot?
Yes. A bespoke interface can draw live data from HubSpot's CRM API — contacts, companies, deals and their associations — and present it alongside data from your ERP and other systems, giving leadership one real-time view without changing how HubSpot itself works.
Can I get a real-time dashboard from HubSpot without replacing it?
Yes. A dashboard built on HubSpot can show pipeline and deal value updating live, sat alongside your finance and delivery systems — closing exactly the gap a CRM alone can't.
Does deal value in HubSpot ever match what finance sees?
Not always, and that's usually the real problem behind "we don't trust our CRM numbers." HubSpot tracks deal value as your sales team enters it — it doesn't know your cost of delivery, your stock position, or what finance later books. Grafting HubSpot's pipeline view together with your finance system's actuals is usually what closes that gap, not replacing either system.
Can I connect HubSpot to my ERP and see both in one place?
Yes. Grafting an interface across HubSpot and your ERP lets pipeline, delivery and finance data appear together — the single view that neither system gives you alone.
Does keeping HubSpot limit what AI can do later?
No. HubSpot's rate limits are a build-time engineering question, not a ceiling on what's ultimately possible. What actually limits AI usefulness is fragmented data, not which CRM you run.
Modernising isn't migrating
The software industry has trained businesses to believe that "modernising" means a large, disruptive replacement project. It doesn't have to. Grafting a new layer onto HubSpot is modernisation without the migration — you move forward on visibility and capability while your pipeline keeps running in HubSpot exactly as it does today.
See how the whole process works, step by step →
Get your AI Exposure snapshot Find out where your real constraint is — most often it isn't AI, and it isn't HubSpot