Every request on the record: who asked, what they asked, what came back.
Sysgraft joins the systems you already run so anyone in the business can ask a question in plain English. Because every question goes through one place, every one is recorded. This page covers that record.
Three questions worth being able to answer.
- How many times has customer data been put into AI by staff this month?
- Which customer or business data did those requests draw on?
- If a supplier questionnaire asked tomorrow what your AI touched, what would you send?
Most businesses can't answer all three yet. That isn't negligence; the tools staff reach for don't keep a record. Sysgraft does, for every request made through it.
| Time | Who | Request | Systems used |
|---|---|---|---|
| 09:15 | Sarah T. · Sales | Summarised a key account's order history | Sage 200, HubSpot |
| 11:40 | James O. · Finance | Listed invoices more than 60 days overdue | Sage 200 |
| 14:02 | Mark R. · Ops | Compared supplier lead times, last 6 months | Sage 200, spreadsheets |
Illustrative — a real record, not a reconstruction from memory.
Three businesses: Orthene Chemicals, Holemaker Technology and Foremost Pro. Each got the same platform underneath, including this record, plus something built for how they work.
What your team uses it for.
- Pulling last month's margin by product line, without exporting anything to a spreadsheet.
- Checking whether a customer's account is overdue before calling them.
- Comparing this quarter's stock turnover against last quarter's.
Your team will actually want to use it.
Not because you told them to. Because it already knows what they'd otherwise have to go and look up.
“What did our biggest customer order last quarter?” — answered from your live system, in one line. No spreadsheet, no export, no asking finance.
Read-only, by design.
The AI itself never writes anywhere — it reads from your systems and nothing more. Where a bespoke module needs to write back — Orthene's schedule export to Winman, Holemaker's nightly enrichment to OrderWise — every field it can touch is named in the specification you approve before the build starts, and nothing beyond it. Most builds need no write access at all; where they do, it's enumerated, not assumed.
That's not a limitation we're apologising for — it's the honest starting point for a system this connected.
Where AI helps a wholesaler, and what to keep it away from →
Questions about the record
Can it change anything in our systems?
The AI itself never writes to your systems. Where a bespoke module needs to write back — always to specific, named fields, agreed in your specification before the build — that's enumerated, not assumed; most builds need no write access at all.
Is a logged request the same as a certified-secure one?
No. The record describes how the system is designed to work — it isn't a certification, and we don't imply it is one. See Security and Data Handling for what's actually in place today.
Can I show the record to an auditor or in a supplier questionnaire?
It's designed to give you something concrete to point to when you're asked what your AI actually touched — a real record, not a reconstruction from memory.