Works with your systems

Sysgraft reads live from the systems you already run. Nothing is migrated or replaced. Below is exactly where each system stands today.

If a system offers a way to read its data, it's in scope. The AI only ever reads. Where a bespoke module needs to write back, every field it can touch is named in the specification you approve before the build. Most builds need no write access at all.

Three honest states, so you can see the difference between “we've done this” and “this can be done”:

1 · Running at a client today

Built on, live, in daily use.

Winman

Running at Orthene Chemicals, where Sysgraft was built onto Winman ERP, connected in both directions, and live in 14 days. What Sysgraft does with Winman →

OrderWise

Running at Holemaker Technology, where Sysgraft was built onto OrderWise and live in 11 days. What Sysgraft does with OrderWise →

2 · Connected and tested

Sysgraft has connected to these already.

Sage 200

Read live through Sage's standard connections, without changing how Sage itself works. What Sysgraft does with Sage 200 →

Microsoft 365

Connected and tested. Which parts of your Microsoft 365 setup are worth connecting is settled in discovery.

Barbour ABI

Connected and tested, so construction project data can sit alongside your own customer and sales records.

Zoho

Connected and tested. Your Zoho data feeds the same answers as finance and operations, not a separate report.

3 · A documented connection route

Their vendors publish a way in. Sysgraft hasn't built on them yet.

Each of these offers a documented, standard way to read its data, which is what a Sysgraft connection needs. Discovery confirms exactly what's possible for your setup, in the specification you approve before you commit to anything.

CRM and e-commerce

HubSpot · Salesforce · Pipedrive · Shopify