Every sync is tested end to end against a sandbox, and a person approves each write to your ERP.
Nothing changes inside the ERP
Satellite apps live in their own repository and reach the ERP through its API with scoped credentials. Nothing changes inside the ERP, so its upgrade path stays as it is.
A person approves every write
Reads from the ERP flow freely. A change that writes to it is an external change under the merge policy, so a person approves it before it merges.
We run it on our own ERP
We are replacing our own ERP with Steer, module by module: invoicing, projects and allocation moved first, each piece specced, evidenced and approved before the next.
The ERP keeps the books the whole time, and the next app starts again at Discover.
Customizations inside the ERP get harder to carry with every upgrade. A satellite app lives in your own repository and talks to the ERP through its API, so the core and its upgrade path stay as they are.
See internal tools →The quoting rules, credit checks and approval chains that make your business different are rarely on a vendor's roadmap. We build them for your process, and a piece with a clear scope gets a fixed price before any code exists.
See how we price →Orders, inventory and customers move between the ERP and the systems around it as events, tested end to end against a sandbox. Every pull request shows the tests that ran, so you can check that a sync works instead of hoping it does.
See the evidence →✳ We build around NetSuite, SAP, Odoo, Microsoft Dynamics and other ERPs with an API. The free audit shows which parts of yours are worth extending first.
A discovery session documents the ERP records, fields and APIs the app needs, plus the spreadsheets and email threads it replaces. All of it goes into the project's Context, versioned.
Each feature becomes a goal with acceptance criteria, like “quotes over the customer's credit limit route to finance” or “approved quotes become sales orders in the ERP.”
Claude Code agents build in fresh isolated sandboxes, against the ERP's sandbox or a test instance with scoped credentials, not your production books.
An independent review model and a forward deployed engineer check each pull request against the spec, and the evidence report shows the integration tests that ran against the ERP.
A pull request that creates or updates records in the ERP is classed as an external change, so a person on your team or ours approves it before it merges.
Who approved what, when and on which evidence is kept in the project's audit trail, which your team can read and export.
Gated: 2 merge3 ask a person0 report
Whether it's one integration or a full satellite app, the ERP stays the system of record and every pull request carries its test results.
Every ERP extension or integration includes:
3 modules
We run Steer on ourselves first: invoicing, projects and allocation moved off our old system one bounded piece at a time, each specced, evidenced and approved before the next.
8 days
A custom agent workflow wired into systems that were never designed for agents, with end-to-end behavioral tests included.
Pento forms a pod of forward deployed engineers for your work, for example four engineers or whatever machine learning, software, DevOps and MLOps talent you need. They work with Steer alongside, and the fee depends on the pod's size.
For integrations and smaller projects you can scope up front. After the free audit we write the scope with you as goals with acceptance criteria and fix the price. Evidence on every pull request shows when each goal is done.
Not covered here? Bring the question to a discovery call. An engineer reads every request.
Book a discovery callContact us
Tell us which ERP you run and what lives in spreadsheets around it. The audit is free: we map the workflows, the APIs and the first app worth building, and quote it, at a fixed price when the scope is clear. An engineer reads every request.