Pricing

Three ways to work with us.

Infrastructure first. AI second. Most plants start with the $500 Assessment — it's the easiest yes you'll make this quarter.

2. Pilot
$2–5K /mo · 3-mo min
We structure one line: nameplates, manuals, PLC tags, PMs, fault history. MIRA goes live on that scope.
  • Hands-on namespace structuring
  • OEM manual indexing
  • PLC tag ↔ asset reconciliation
  • MIRA deployed on the pilot line
  • Before/after namespace report
  • Direct line to Mike + the team
Talk to Mike →

Scoped to one line / one cell during pilot

3. Operating Layer
$499 /mo per plant
MIRA in production on a structured namespace. Telegram + web + CMMS write-back. Quarterly namespace audits.
  • Unlimited MIRA queries, whole team
  • Cited OEM answers + fault history
  • CMMS write-back (MaintainX, Limble, UpKeep, Atlas)
  • Continuous structuring as assets come online
  • Quarterly namespace quality audit
  • 14-day money-back guarantee
Subscribe →

Recommended after a Pilot, or for plants already well-structured

Why this stack, not seat-licensed SaaS

Pure consultancies leave you with a binder. Pure SaaS leaves you hallucinating. We do both — the structuring and the execution layer that runs on top.

What you get
Generic AI / Per-seat CMMS
FactoryLM
Asset hierarchy & nameplates structured
You do it
We do it
OEM manuals indexed & bound to assets
You do it
We do it
PLC tag ↔ asset reconciliation
You do it (or never)
We do it
AI answers grounded in your namespace
Hallucinations
Cited every time

We integrate with MaintainX, Limble, UpKeep, Atlas — we don't replace them. The structuring is the wedge.

Questions

Why start with a $500 Assessment?
Because most plants don't know which of their problems are structural and which are tooling. The Assessment shows you the gap in writing — assets, documents, PLC context, CMMS hygiene — so the Pilot scope is informed, not guessed. It's also a low-friction first step. No contract, no commitment beyond the visit.
What's actually delivered in a Pilot?
A working, structured namespace on one bounded scope — typically one line or one cell. That means scanned nameplates, indexed manuals bound to assets, PLC tags reconciled, PM schedules extracted, fault history captured, and MIRA deployed against that scope. You get a before/after namespace report at the end of month 3 so you can see the lift in writing.
Do you replace my CMMS?
No. We integrate with MaintainX, Limble, UpKeep, and our own Atlas. Your CMMS is where work orders live. The Operating Layer writes work orders into it automatically when MIRA confirms a fault. Your techs never leave the tools they know.
Why not a self-serve SaaS sign-up?
Because the work that makes AI actually useful — structuring your assets, manuals, PLC tags, and history — can't be done by a wizard. It takes hands on the floor. We tried the self-serve route. AI hallucinated because there was no namespace to ground it on. The Assessment exists precisely because the work is real.
Can I skip straight to the Operating Layer?
If your plant is already well-structured — clean asset hierarchy, manuals digitized, PLC tags consistent — yes. Most plants aren't, which is why we start with an Assessment. The scorecard at /assess will tell you honestly where you stand.
Multi-plant pricing?
Enterprise — talk to Mike. 5+ plants get a dedicated transformation lead, on-prem option, SSO/SAML, and SLA.