Pricing

Prices start at $10,000 to launch and $1,000 a month. The exact amount is quoted in the first conversation, from your volume, the systems to connect and the workflows you want to run. There are no self-serve plans.

Book a call

How an engagement is priced

Every engagement follows the same four steps, and the price is set before the one you pay for.

  1. First meeting

    You walk Mirage through the workflow, the documents and the systems it touches. Nothing is billed.

  2. Proof of concept, one week later

    Mirage runs an agent on a sample of your own documents, to show it can do the job before you commit to anything. The exact price of the pilot and of the subscription is quoted in this first conversation.

  3. Fixed-price pilot

    Mirage's engineers come on site and deploy the agent on one workflow, at the fixed price quoted. You can stop after the pilot, with no further commitment.

  4. Annual subscription

    If you continue, the agent runs in production and Mirage operates it. The subscription is annual and priced by the volume of work the agents handle, not by the number of users.

The two published figures

From $10,000
To launch: the pilot that puts the first workflow in production, engineers on site included. Fixed price, agreed before it starts.
From $1,000 a month
The annual subscription that follows, billed for the platform, the agents and the engineers who run them. It only starts if you decide to continue after the pilot.
Quoted in the first conversation
Both figures are starting points. The amount for your operation depends on the three things below and is stated before the proof of concept.

What is included

One price covers the people, the integration and the running of the agents. There is no separate implementation fee, no per-user licence and no charge for building a connector.

Engineers deployed on site

Forward-deployed engineers spend time with the people who do the work today, map the workflow, its exceptions and its checks, and build the agent around them.

Integration with your systems

The agent reads from and writes into the ERP, TMS, WMS or other systems you already run, through their API, EDI or a file exchange. Where no interface exists, Mirage builds the connector as part of the deployment.

Running and monitoring

After go-live, Mirage operates the agents, monitors them and improves them on live data. Corrections your team makes become rules the agent applies from then on.

The platform

Mirage OS, deployed in the cloud, in your own cloud account or on-premise, with role-based access, human approval flows and a full audit trail.

What makes the price vary

Three things decide where your price sits above the starting figures.

Volume

The number of documents, orders, shipments or transactions the agents handle each month. The subscription is priced on it.

Number of systems

How many systems the agent has to read from and write into, and whether each one has a documented interface or needs a connector built.

Number of workflows

Each workflow is its own deployment, built around one document and one outcome. The second one reuses the integrations of the first, so it costs less to add than the first did to start.

The size of your company is not a factor. What matters is a real volume of operational work done by hand between documents and systems.

Pricing questions

  • There is a proof of concept on your own documents one week after the first meeting, before you commit to anything. The pilot that follows is a fixed-price engagement; there is no self-serve plan to try alone.

  • No. After the pilot, the subscription is annual and priced by the volume of work the agents handle, not by the number of people who use them.

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

  • 4 to 6 weeks for the first workflow, running on your own documents from day one. A workflow that spans several systems can take longer.

  • Yes. Connecting the agent to the systems you already run is part of the deployment, and where a system has no API, Mirage builds the connector. More than 200 systems have been connected so far, including SAP, Oracle, Microsoft Dynamics and Salesforce.

  • Because Mirage is not self-serve software. Each deployment is built and run by Mirage's engineers inside your systems, and its price depends on your volume, your systems and your workflows. The two published figures are the starting points; your exact amount is quoted in the first conversation.

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