The team you cannot afford
A controller, an analyst, an admin and someone who understands compliance. Large companies hire all four. Smaller ones run on spreadsheets and hope, and the gap shows up at the worst possible moment.
AIO · Enterprise · Production · internal
Talk to your business. The agent does the work.
Enterprise systems are not hard because accounting is hard. They are hard because the work is buried in hundreds of screens nobody has time to learn. AIO puts an agent in front of that: you say what needs to happen, by text or by voice, and it happens — under a control layer that writes down what it is about to do before it does it.
01
What it costs to not have this
The four problems every company of this size has, stated without drama.
You find out afterwards
A supplier turned out to be fraudulent. Someone went around an approval. An audit arrives and asks who authorized a payment. In most systems these are discovered later, from records written after the fact.
Operations talent is expensive and scarce
The people who can run these systems well cost more every year and are hard to find. Meanwhile competitors automate the same work and quietly lower their cost per order.
Hundreds of screens, half of them unused
Enterprise software is usually capable enough. The problem is that using it requires months of training, so teams use a fraction of it and keep the rest in side spreadsheets.
02
You say it, the agent does it
Real operations on real records — not answers about your data. Left: what a person says. Right: what actually happens in the system.
Who owes us more than fifty thousand?
A list with amounts, straight from the ledger — plus the query it ran, so the
number can be checked rather than trusted.
Create an order for Acme, one hundred units. Invoice it. Record the payment.
Three linked documents from one sentence. Each step still passes the gate
separately — batching the request does not batch the permission.
Any purchase over one hundred thousand needs director approval.
A real approval rule configured in the system, not a note in a document.
Described in a sentence instead of specified for a developer.
Who bypassed the approval process last month?
Answered from the records, including the reasoning captured before each
action — which is the part most systems cannot produce at all.
Compare sales in May and June. Who dropped, and why?
The comparison, the accounts that fell, and the documents behind the change —
without waiting for a report to be built.
How do I set up a bill of materials for a new product?
Retrieved from indexed documentation with the source attached, so the answer
can be verified instead of believed.
03
Why the control layer is the product
An agent that can act inside a business is only worth having if what it did can be proven afterwards. That part is deterministic code, not a model.
Intent on the record
Facts are gathered, risk is classified, and the reasoning is written to immutable storage before the action runs. A refusal is documented as carefully as a success.
Approval bound to facts
A risky operation stops and shows the amount in words, the document and the reason. The approval applies to those exact facts — if they change, it no longer counts.
Checked by something else
A separate process compares the record against what actually changed and flags any disagreement. The component that did the work is not the one that certifies it.
The same gate applies to a person working in the system directly, not only to the agent. In practice the larger risk in an enterprise is not the model — it is an authorized human doing something irreversible without a record of why.
04
Every department, one way in
The same agent, different tools behind it. Nobody has to learn a new interface to get an answer.
- Leadership
- Position, receivables and margin without waiting for a report to be assembled.
- Finance
- Reconciliation, statements, and a straight answer on who went around an approval.
- Sales
- Pipeline, quotes and follow-ups by voice, without opening a separate system to log them.
- Procurement
- Requests, approvals and budget checks applied as rules rather than as reminders.
- Stock
- Positions across locations, transfers and reservations, including a spoken stock count.
- People
- Leave, attendance and payroll documents, with working-time rules treated as constraints.
- Operations
- Approval flows, assignment and recurring documents configured by description.
- Support
- Tickets against their response targets, and answers drawn from your own documentation.
05
What the alternatives cost
List pricing for a fifty-person company, as published by each vendor. Voice and long-term memory are counted only where they come with the product, not as an add-on project.
| Approach | Cost, 50 users | Voice | Memory | Records stay yours |
|---|---|---|---|---|
| Large ERP with an AI assistant | High five figures to set up, then per user | Limited | Session only | Vendor cloud |
| Office suite with a copilot | Thousands per month | Text first | Session only | Vendor cloud |
| CRM with a built-in assistant | Thousands per month | CRM scope only | Limited | Vendor cloud |
| Mid-market ERP, self-hosted | Low thousands per month | Add-on | None | Yours |
| Custom development | Six figures, months of work | If specified | If specified | Yours |
| AIO | $999 per month at this size, not per seat | Included | Long-term, per person | Yours, readable directly |
One difference is worth stating plainly: none of the alternatives records why an action was taken before taking it. That is the part we built, and it is the reason this exists as a product rather than as a chat window.
06
Pricing
Every tier carries the whole product — voice, memory, knowledge base and the control layer. Tiers differ in volume, never in features, and seats are never billed per person.
Solo
$49
per month · $50 to join
One company, five people. 10,000 AI messages, 900 voice minutes, 50 document pages and 30 knowledge-base documents a month, on shared infrastructure.
Genesis rate. $99 per month and $100 to join once the Genesis places are taken.
Standard
$199
per month · $200 to join
Three companies, twenty-five people. 30,000 AI messages, 1,800 voice minutes, 500 document pages and 200 knowledge-base documents a month.
Genesis rate. $399 per month and $400 to join afterwards.
Business
$999
per month · $1,000 to join
Fifteen to twenty-five companies, one to two hundred and fifty people. 150,000 AI messages, 6,000 voice minutes, 5,000 document pages and 2,000 knowledge-base documents a month.
Genesis rate. $1,500 per month and $1,500 to join afterwards.
Enterprise
Custom
dedicated infrastructure
No volume ceilings, a dedicated voice channel and dedicated servers. Moving off an existing ERP, isolated deployment, and integration with the systems you already run.
- Entry fee
- One month up front, once — and it is a membership rather than a setup charge. Nobody is billing you for configuration hours. What it buys is entry to the ARES ecosystem: your rate held at the Genesis price for as long as you stay, and the benefits that arrive as the other products in the ecosystem come online.
- Why we charge it
- It filters. Free entry brings people who came to look around, to copy what can be copied, or to scrape what can be scraped. Anyone for whom one month up front is a genuine obstacle is not who this was built for. Serious buyers read the fee as a signal rather than a barrier.
- What is not billed
- No per-seat fees, no charge for voice, no separate license for the control layer, and no feature held back for a higher tier.
- How you buy
- Access is granted directly today: self-serve signup and billing are being finished properly before they open. Slower for us, honest for you.
07
Under the hood
The parts that exist and run in production. Named plainly, so an engineer on your side can evaluate them.
A graph, not a prompt
Routing, extraction, conversation and tool execution are separate nodes, each running on the model that fits that step — so cost and speed are decided per step, not once for everything.
Long-term, per person
Preferences, facts, summaries and past episodes persist across sessions, isolated per user and per organization.
Isolated execution
Each tool runs in its own isolated function behind a single gateway, with permissions granted per tool rather than per system.
Speech in, speech out
A streaming voice channel that reasons and calls the same tools directly, without dropping to text and back in between.
Answers with a source
Your documentation indexed for semantic search, so an answer arrives with the passage it came from attached.
Content and prompt filtering
Managed guardrails for content moderation, denied topics, personal data detection and prompt injection — applied before a request reaches a tool.
08
Honest boundaries
What AIO is not, so nobody discovers it later. This section exists on purpose.
We did not rebuild the ERP
The system of record underneath is ERPNext, an established open-source platform. We built the agent layer and the control layer above it, and your data stays in a database you can read directly.
Nobody is forced through the agent either. Anyone who prefers the ERP screens keeps using them, and the same control layer applies to what they do there.
Pilot, and we say so
The control layer runs in production and records every operation. Enforcement is being calibrated against a full reference company before it starts blocking work — so today it observes and documents rather than refuses.
That order is deliberate: a gate that misfires teaches people to route around it, and a gate people route around is worse than no gate at all.
It does not sign anything
AIO prepares, checks and records. It does not file returns, does not give legal or tax advice, and does not replace the person who is accountable for the decision.
That line matters more as the system gets better, not less. An agent that drafts the filing, reconciles the figures and flags what looks wrong is doing the work — but the approval still carries a name, and the record shows whose it was. Where something needs a licensed professional, the agent says so rather than producing an answer that is confident and wrong.
Automation is welcome to remove the labor here. It is not permitted to blur who answers for the outcome.
The compliance certificates are our provider's
Our infrastructure runs in data centers that hold SOC 2 and ISO 27001 certifications. ARE5 itself does not yet hold an audited certification, and we will not imply otherwise — anyone claiming it at this stage is describing their hosting provider.
In practice the platform controls we build on — physical data-center security, encryption in transit and at rest, network isolation — are inherited from that certified infrastructure. The parts that are ours to audit we will certify when it is worth its cost at our size, and we will put a date on it when it happens rather than a promise now.
Your data trains your model. Not ours.
Memory, documents and retrieved knowledge are isolated per organization, and no shared or general-purpose model is trained on your records.
What your data does build is a dataset that stays yours, in your own storage. That training is not running yet, and when it does it will be under an agreement stating plainly that the dataset and the resulting model belong to you.
You can leave, and take it with you
Because the system of record is standard ERPNext in a database you control, leaving is not a rebuild. The data exports in open formats, the same ERP keeps running elsewhere, and the agent layer is simply the part you stop paying for — not a hostage you negotiate to get your own records back.
We would rather earn the next month than fence the exit. A product that keeps customers by making departure expensive is admitting it cannot keep them any other way.