Can you keep Xero and modernise everything around it?
Yes. Xero can stay your system of record while a bespoke, real-time interface gets built on top of it, designed within Xero's own rate limits rather than around them — no rip-and-replace, no accounting migration, and nothing lost from the setup your business 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 Xero, or build around it?
For most £1.5m–£20m+ UK businesses, the honest answer is: build around it.
Xero is usually not the problem. It's an accounting system, and it does that job well — it's one of the most widely used in the UK for exactly that reason. The problem is that Xero was never designed to be a live, cross-business dashboard — it wasn't built to show margin by job, or bottlenecks in your operations, alongside your accounts. The frustration leaders feel ("why can't I see margin in real time?", "why does month-end still take a week?") isn't a reason to tear Xero out. It's a reason to add a layer it was never meant to provide.
Ripping out a working accounting system to solve a reporting and visibility problem is one of the most expensive mistakes a growing business can make: weeks of migration, retraining, data risk, and disruption — to fix something a graft would fix without any of it.
What connecting to Xero actually involves
Xero exposes a well-documented REST API, authenticated with OAuth 2.0, and it's genuinely one of the more pleasant accounting systems to build against. The engineering constraint isn't access — it's volume.
Xero enforces some of the tightest rate limits in accounting software: 60 API calls per minute and 5,000 per day, per organisation, with a maximum of five concurrent calls. That daily ceiling is the number that shapes the design. A dashboard that naively re-queried Xero every few minutes would exhaust a day's allowance before lunch.
So a graft onto Xero isn't built by polling. It's built by holding a synchronised copy of the data your reporting actually needs, updated through Xero's webhooks when records change, and topped up with targeted date-filtered queries rather than full re-reads. That's what makes a live leadership view possible inside limits designed for far less frequent access — and it's also why "just connect it to a dashboard tool" tends to disappoint.
Two further practical notes: Xero's access tokens expire every 30 minutes, so token refresh has to be engineered properly rather than bolted on; and payroll sits behind a separate, region-specific API from the main accounting one, which matters if people costs need to appear alongside financials.
Common questions about modernising around Xero
Can custom software sit on top of Xero?
Yes. A bespoke interface can draw live data from Xero through its API and present it alongside data from your CRM and other systems — giving leadership one real-time view without changing how Xero itself works.
Can I get a real-time dashboard from Xero without replacing it?
Yes. A dashboard can read live from Xero alongside your other systems — built to respect Xero's daily call ceiling rather than exhaust it, which is exactly the kind of thing a discovery session designs around.
Is Xero the problem, or our processes?
Often, neither is fully the culprit. Xero does exactly what a cloud accounting system is supposed to — the real issue is usually that it was never meant to be a cross-business dashboard, and building one around it doesn't require replacing anything.
Can I connect Xero to my CRM and see both in one place?
Yes. Grafting an interface across Xero and your CRM lets customer, invoice and cash position data appear together — designed within Xero's rate limits rather than working against them.
Does keeping Xero limit what AI can do later?
No. Xero's tight rate limits shape how a build is engineered — batching, caching, timing — but they don't touch what's ultimately possible once your financial data is joined with the rest of the business. Fragmentation is the real constraint, not the accounting package.
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 Xero is modernisation without the migration — you move forward on visibility and capability while Xero keeps running within its own rate limits, same as always.
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 Xero