Enterprise AI agents: integration, security, pricing

Enterprise AI agents from Mirage connect to the ERP, TMS, WMS and document systems you already run (more than 200 connected so far), follow your own rules with a person approving the exceptions, run in your infrastructure, your cloud or Mirage's, and are priced as a platform by volume rather than per user: from $10,000 to launch and $1,000 a month, after a fixed-price pilot you can stop.

It connects to what you already run

Mirage connects the ERP, TMS, WMS, maintenance, telematics and document systems already in place, more than 200 so far, and writes back into them. Nothing is migrated and nothing is replaced.

With an interface
Where a documented interface exists, Mirage connects to it.
Without one
Where none exists, our engineers build the connector during deployment.
Construction
Project management and document control platforms such as Procore and Autodesk Construction Cloud, estimating spreadsheets, and ERP and accounting systems such as SAP, Oracle and Sage.
Logistics
TMS and freight systems: in production with Logitude World at OFRET Groupe, and CargoWise through its eAdaptor interface.
Manufacturing
ERPs: in production with SAP Business One at Biodéal, and Dynamics 365 Supply Chain Management.

Configured on your rules, not ours

Mirage models your operation's own objects and rules: orders, shipments, assets, sites, suppliers, quantities. The agents follow the way your team already works rather than a generic template.

What you give
Your workflow, its rules and exceptions, your codes and document conventions, and the checks your team does by hand today.
Autonomy
Configurable for each workflow: what runs on its own and what waits for a person's approval.
Approval
Role-based access and human approval flows. A person on your side decides the exceptions.
Audit
Every agent action is traceable to the input and the rule that produced it.

Deployed where you decide

Mirage can run in your infrastructure, in your own cloud account, or hosted by Mirage. The architecture decides who holds the data, the keys and the access.

Data
In your infrastructure or your cloud, data and processing stay in the environment you control, and nothing is transferred outside it.
Keys
In those deployments, the encryption keys are your responsibility.
Access
Mirage's access is strictly limited, or removed after deployment, depending on the architecture you choose.
Review
A non-disclosure agreement on request, and answers to your security questionnaire for the architecture you are considering. No certification or audit report is listed.

Engineers who deploy it and stay with it

Forward-deployed engineers build each workflow inside your systems, with your team, then Mirage operates, monitors and improves it in production.

First reply
Within two business hours.
Proof of concept
On your own documents and data, one week after the first meeting.
Pilot
Engineers on site, one workflow, at a fixed price. You can stop after it.
Production
The first workflow in production in 4 to 6 weeks, operated, monitored and improved by Mirage.
Next workflows
Added on the same platform. Transwin started with one document workflow and now runs five systems in production.

How much do enterprise AI agents cost?

A fixed-price pilot first. From $10,000 to launch, then an annual subscription from $1,000 a month, priced by volume; the exact amount depends on the workflow and the volume and is quoted in the first conversation.

Pilot
Fixed price, on one workflow, with no commitment beyond it.
Subscription
Annual, priced by the volume of work the agents handle, not by the number of users. It only starts if you decide to continue after the pilot.
What it covers
The platform, the agents running on it, and Mirage's engineers operating, monitoring and improving them.
What it does not include
Licences for your own systems, and hardware where a deployment needs cameras, probes or terminals; both are named in the quote.
Compared with per-seat tools
A per-user licence grows with the number of people who open the tool. A per-volume subscription grows with the work the agents do, which is what you are paying for; a workflow that ten people review costs the same as one that two people review.
The three stages of a Mirage engagement, what each costs and what you can decide at the end of it
StageWhenWhat you payYou can
Proof of conceptOne week after the first meetingNothing: it runs on a sample of your own documents or dataStop, or scope the pilot
PilotEngineers on site, one workflowA fixed price, from $10,000 to launchStop after it, with the output and the comparison in hand
ProductionFirst workflow live in 4 to 6 weeksAn annual subscription by volume, from $1,000 a monthAdd the next workflow on the same platform

What should you ask any AI agent vendor before signing?

Nine questions IT, procurement and operations leaders ask Mirage, with the page that answers each one. Put the same nine to every vendor you compare.

  1. Which of our systems does it write into, through which interface, and who enables the access?Named per workflow in the first meeting; where no documented interface exists, Mirage's engineers build the connector. See the integration section above.
  2. Where does it run, who holds the data and the keys?Your infrastructure, your cloud account or Mirage-hosted; in the first two, data and keys stay with you. See security and data handling.
  3. What does a person approve, and can we change that per workflow?Configurable autonomy per workflow, role-based access, human approval on the exceptions you define.
  4. What is logged, and can we export it?Every agent action is traceable to the input and the rule that produced it; audit logs stay under your organisation's control.
  5. What happens to a document the agent cannot settle?It is held with the reason and routed to a named person; nothing is dropped or guessed silently. At Biodéal, about 7% of orders are flagged for a person.
  6. Who runs it after go-live, and who changes it when our ERP is upgraded?Mirage operates, monitors and improves it in production, with the engineers who built it.
  7. What results can you show from a named deployment, with the definition behind each figure?Nine published case studies. Six state their figures with the definition behind each: Biodéal, OFRET Groupe, Transwin, John Cockerill, OCBM, Mass Céréales Al Maghreb. Rouandi describes its deployment without figures, and SGTM and G3C describe missions that are just starting.
  8. What does it cost, on what basis, and what can we stop?A fixed-price pilot you can stop after. From $10,000 to launch, then an annual subscription from $1,000 a month, priced by volume.
  9. What will you not do?Mirage does not sell self-serve software, does not check drawings against US building codes, and keeps no material catalogue or labour database: it feeds yours.

Questions from enterprise buyers

  • No. After a fixed-price pilot: from $10,000 to launch, then an annual subscription from $1,000 a month, priced by the volume of work, not by the number of users; the exact amount is quoted in the first conversation.

  • No. Mirage connects to the systems already in place, more than 200 so far, and writes back into them. Where no documented interface exists, our engineers build the connector during deployment.

  • Yes. It models your operation's own objects and rules, and each workflow has configurable autonomy, role-based access and human approval. A person on your side decides the exceptions.

  • Mirage operates, monitors and improves them in production, with the engineers who built them. Your team reviews what is routed to it.

  • Yes. The pilot is a fixed-price engagement with no commitment beyond it, and the subscription only starts if you decide to continue.

  • An assistant answers the person who asks. An agent deployed in a workflow picks up the work where it arrives (a mailbox, a portal, a plan room), checks it against your rules and master data, writes the result into your systems and routes the exceptions to a named person, with every step logged. Mirage builds and runs the second kind.

  • A reply within two business hours, a proof of concept on your own documents one week after the first meeting, and the first workflow in production in 4 to 6 weeks. Workflows spanning several systems can take longer and are scoped at the first meeting.

Bring us the operation you need to improve.

Mirage will map the workflow, identify what can be automated and define the fastest path to production.

Start with one workflow

Leave your work email, then pick a time for a 30-minute call on the workflow where your team loses the most time. You leave with a written plan to automate it. No commitment.

We use your email to reply to you and, now and then, to tell you about Mirage. You can opt out at any time. Privacy policy