Turn Every Installed Unit into Recurring Service Revenue
Plant sees value on the energy / downtime bill. You own brand, customer, and attach. We are the on-prem engine.
Subscription attach on installed base — not a project
White-label; IoTGPT is the engine
You keep renewal and parts pull-through
Why this is an OEM P&L play
- •Break-fix + parts alone under-monetizes the installed fleet. A monitoring subscription turns each shipped unit into annual attach.
- •Plant buys savings / avoided downtime (four machine proof pages). You buy fewer emergency rolls, stickier renewals, and attach without building digital alone.
- •Your levers: ARPU per unit, attach rate, service cost per contract, parts pull-through. Proof at the plant; margin with you.
Why through us — not alone, not another platform alone
vs build in-house: reliable alerts + next steps on closed networks take years. Skip R&D; sell under your brand in weeks for a packaged line.
vs PTC / Siemens / telemetry: they move data and dashboards. We add priced, explained alerts from ordinary control readings — on-prem, no new sensors — as a sellable service.
vs bare software: plants buy a named drift with a cost tag — what field and service orgs close — not model scores.
Where money shows up (OEM side)
ARPU / annual attach per unit · Attach rate on new + installed · Emergency call ↓ vs planned visit · Retention & parts pull-through
ARPU, list price, and revenue share are partner-negotiated — not published here.
What it takes from you
Package
one machine line + proof one-pager for your engineers.
Brand & sell
white-label; your sales/service sells the subscription.
Support
you own first-line; we backstop product/models under partner SLA.
Own the account
you bill and renew. We do not farm end customers.
Commercial principles
Honest scopeCommercial brief, not a price list. ARPU / attach % / share depend on region, machine, and support model. Machine pages: "does it work?"; this page: "why you earn." Use both in OEM meetings.