Business System Connector
Your business system, inside Claude.
Ask your ERP questions in plain English. Make routine changes without rekeying them. Nothing changes without a yes from someone on your team.
What you get
Your data answers back. Your changes stay under control.
Answers in seconds.
Your system’s data is synced to a read-only reporting copy every few minutes. Ask a question in plain English inside Claude and get the answer from your own numbers, without running a report.
Routine changes without rekeying.
The changes your team types in by hand every day are requested in chat. The connector writes them through your system’s own business logic, then re-reads the record to confirm the change landed.
Nothing changes without a yes.
Every change is queued and previewed first. Only a named approver on your team can approve it, and every approved change is recorded in an audit log.
How a change happens
- Change requested in chat.
- Preview of exactly what will change.
- Named approver says yes.
- Written through your system’s own business logic.
- Re-read to verify, then logged.
Security
- Runs on your server, behind access controls.
- Read-only guard on every reporting query.
- Approvers and the access list managed by your admin.
- Your team uses its own Claude licenses.
Proof
In production at a wholesale distributor.
Running on Sage 100: 250+ changes approved, written, and verified across 15+ change types. Client names shared on request.
Built by forward deployed engineering, the same way we build everything else: with the people who do the work.
Questions
Can anything change in our system without approval?
No. Every change is queued and previewed first, and only a named approver on your team can say yes. The change is then written through your system's own business logic, re-read to confirm it landed, and recorded in an audit log.
Where does it run?
On your server, behind access controls, with a read-only guard on reporting queries. Your team uses its own Claude licenses.
Which systems can it connect to?
It runs in production today on Sage 100 at a wholesale distributor. Other ERPs and accounting systems are scoped on the call: we look at how the system can be reached and which changes your team rekeys most.
What does it cost?
Pricing depends on the system, whether you want read-only answers or write-back, and how many change types you need. We set it after the fit call, in writing, before anything is built.
What happens on the fit call?
We cover three things: which system you run, the top five changes your team rekeys by hand, and who should approve changes.
Start with a fit call.
Bring three things: the system you run, the top five changes your team rekeys by hand, and who should approve changes. Pricing comes after the call.