// PRODUCT
12 MIN READPlatform Info
What ORiON is, what the agents do in your ERP, how connections work, and where it fits for a finance and operations team at 100 to 1,000 people. Written to be read end to end before a call.
What ORiON is
ORiON is an AI platform that automates the manual ERP work finance and operations teams do every day. It sits on top of the systems the team already runs (ERP, CRM, billing, payroll, email and chat), reads them in real time, and puts agents on any process that today means copying data from one system into another. Every write waits for a person to approve it.
The important structural point: ORiON is not a system of record. It does not want to own your data or become the place your team logs work. Your ERP stays your ERP. Your CRM stays your CRM. ORiON reads across all of them and does the manual work between them.
If you can describe a step your team does by hand in the ERP, ORiON can automate it. For example: CRM to ERP setup, close prep, AR follow-up or AP matching.
The problem it solves
Somewhere between 100 and 1,000 employees, most companies end up with the same shape of problem. The systems are all in place and they all work. What's missing is anything that does the work between them, so data is copied from one system into another by hand and the close lives in four tabs, two exports and one person's spreadsheet.
Companies typically solve it one of three ways, and all three have a known failure mode:
Buy more ERP modules
Each module automates a narrow slice and is priced per module. The work between the ERP and the CRM, billing and payroll systems still falls to people copying data by hand.
Wire it together with automation tools
Fast to start, and genuinely useful. But you accumulate dozens of small brittle flows that nobody owns, and when one breaks quietly the first sign is a wrong number in the close.
Hire another person
The most reliable option and the most expensive one. As volume grows it means another hire, and every recurring task keeps a person and a queue in front of it.
Three ways in
The core is agents doing the manual ERP work; answers and dashboards sit beside them on the same live data. They're not separate products — an answer from one becomes the input to another.
Hand an agent a goal, like AR follow-up. It runs on demand or on a schedule and holds its writes for approval.
Type the question. The answer is drawn from live systems, with the sources attached.
Assemble a dashboard from the widget library, or describe it and have ORiON build the whole board.
What the agents do
An agent in ORiON is given a goal rather than a script. It plans the steps, reads what it needs across your connected systems, and carries the work through — including multi-stage work that spans the ERP and several other tools. Agents run when you ask, or on a schedule you set.
Broadly they do three things:
Automate the manual ERP work
Any step done by hand. For example: CRM to ERP setup, close prep, AR reminders, matching bills to POs and receipts.
Take action in your tools
Create the ERP record, draft the reminder, update the CRM, in the connected system where the work already lives, not in a parallel copy of it.
Analyze and find the pattern
Trends and anomalies across systems that no single system can see on its own — the kind of thing that only shows up when the ledger, billing and CRM sit in the same view.
Reading is automatic. Writing is not. When an agent wants to change something in a connected system or send something on your behalf, it stops and shows the actual record, values or recipient for a person to approve, approve in part, or discard. Routine workflows run unattended only once you choose.
The integration layer
ORiON connects to the ERP at the center (NetSuite, SAP, Microsoft Dynamics 365, Oracle, Sage Intacct, Acumatica, Infor, Epicor, M3, Odoo, QuickBooks, Xero) and the systems around it: CRM, billing, payroll, Google Workspace, Microsoft 365 and Slack. Anything else with an API connects through the Model Context Protocol, and web tools without one through the ORiON Companion.
Connection is per-user OAuth where the system supports it, so ORiON sees exactly what the connecting person is permitted to see — no more. Nothing is migrated, there are no ERP modules to buy, and no system changes how it's used.
SEE THE FULL INTEGRATION LIST →Dashboards and reports
Alongside the agents, the workspace is a canvas for reporting. You drag widgets onto it from a library of 39, arrange them how you think, and save as many boards as you need: one for the close, one for cash, one for AR. Widgets read from your live connections, so a saved board is current every time it's opened rather than current as of the last export.
You can also skip the assembly entirely: describe the view you want and ORiON builds the board. Any board exports as a PDF report, which is usually how it ends up in front of a board or an investor.
Trust and traceability
A number nobody can trace is a number nobody will defend in a meeting. The Context Graph shows which systems and which records an answer was drawn from, so any figure can be followed back to its source. If a number looks wrong, you can see why it says what it says.
Underneath, each organization's data is isolated at the database level rather than in application code, and integration credentials are stored encrypted and never exposed to the browser. The Security & Architecture document covers this properly, including a plain list of what we don't claim.
What it is not
Being clear about this saves everyone a bad evaluation.
- ✕Not a replacement for your ERP, CRM, billing or payroll system
- ✕Not a data warehouse — ORiON reads across systems, it isn't where you model your data long-term
- ✕Not a general-purpose BI tool for arbitrary custom modelling
- ✕Not an autonomous system that acts without oversight — writes wait for approval by design
- ✕Not a migration project — if a vendor is proposing you move your data, that's a different kind of purchase
Deployment
Because nothing is migrated, deployment is mostly a matter of connecting accounts and deciding which manual process to automate first. The sequence is the same for everyone:
Connect the ERP and the systems that feed it, usually CRM, billing and email. Minutes per system, by one admin.
Turn on the first workflow, for example CRM to ERP setup or close prep, with every write held for approval.
Put routine workflows on a schedule, or let them run unattended once you trust them.
Add systems and processes as you go. Any manual ERP step is a candidate for the next workflow.
Who it's for
ORiON is built for the people who own the manual work around the ERP: a controller, a VP Finance, a VP of Operations, a head of business operations. The common thread is accountability for outcomes across systems they don't administer themselves.
It fits best where volume is growing faster than the team: the systems are real, the work between them is done by hand, and the usual answer to more volume is another hire.
// NEXT