Remote monitoring lets a maker of espresso machines, commercial laundry, dishwashers, combi ovens, ice machines or floor scrubbers bill the output its machines already count: cups poured, loads washed, cycles run, and protect that revenue with service that lands before the machine disappoints a customer at 7 AM. In the example on the Commercial Appliances solutions page, a cafe’s espresso machine pours 12,600 cups in a month, gets its boiler descaled before opening after a 5-second drift in recovery time, and closes with a $1,512.00 invoice at $0.12 per cup.
Key points
- Appliances are the machine category closest to the customer’s own revenue, so output billing is a relief to buy, not a novelty: per cup, per load, per cycle.
- The controller already counts the output; the business model begins the day that counter reports instead of dying in the machine.
- Appliance failures are predictable and boring, which is exactly what makes uptime sellable: scale slows a boiler, a worn bearing loads a drum motor, a blocked condenser melts an ice bin.
- Connectivity is undramatic: Modbus for laundry rooms, LoRaWAN for scrubbers, cellular or site networks for kitchens, satellite for the remotest dispensers.
The walkthrough: a descale before the morning rush
The page’s simulated case follows Espresso 21 at a harbor-street cafe. Every shot pours at temperature while the boiler keeps up, recovering between shots at its descaled reference. One week, with the same shot pattern, recovery runs 5 seconds slower than that reference and crosses the descale limit: scale is building in the boiler. The platform books a descale and a water filter change for the next visit, before opening hours, and tells the cafe. Recovery returns to normal, no morning queue ever notices, and the month closes with 12,600 cups poured, the uptime guarantee kept, and the $1,512.00 invoice issued.
The daily texture is part of the sale: the dashboard shows 148 cups poured since 7 AM, hour by hour (38, 56, 41, 13), because a cafe owner reads cups the way a plant reads kilowatts. Month to date, the machine stands at 4,318 cups billed at $0.12 per cup ($518.16, up 9% on October), and the four-machine fleet shows $1,653 ready to bill across all four sites, each line itemized in cups.
The fleet is the business
Single connected appliances are a feature; the fleet is the moat. Ten thousand machines reporting output and health close a loop that one-time sales never do:
The page’s smaller cards show the loop on other equipment: a laundry drum loaded 15% over its rating, because sites put 46 kg into a 40 kg machine (an overloading pattern only fleet data reveals, $160 a month), and a floor scrubber picking up 84% of its water, flagging a squeegee change ($95 a month). Fleet baselines also answer the question every appliance maker gets from finance: what does a service contract actually cost us per model, per water hardness zone, per customer type. With the data, the price is arithmetic.
Which measurements carry the business?
| Measurement | What it tells you | What it sells |
|---|---|---|
| Output counters (cups, cycles, vends) | Revenue happening | Billing per unit of output |
| Boiler recovery and extraction time | Scale building | Descale by condition |
| Drum motor load | Overloading, bearing wear | Service and training |
| Water filter capacity | Consumable state | Filters on subscription |
| Oven cavity temperature | Food safety and quality | Compliance plans |
| Ice bin level | Stock about to run out | Refill routes by demand |
| Scrubber battery | Fleet readiness | Uptime contracts |
How do appliances connect?
Over whatever the site already has, which is the point: washers, dryers and ironers report over Modbus in the laundry room; floor scrubbers and sweepers over LoRaWAN; combi ovens, dishwashers and ice machines over cellular, MQTT or HTTP; coffee, vending and dispensers over satellite where nothing else reaches. Installed machines retrofit with add-on sensors for temperature, current, water flow or energy, with no change to the appliance, a payload parser absorbs proprietary controller formats, and more than 500 integrated devices decode out of the box.
Each customer, the cafe chain, the hotel, the laundromat operator, signs in to a TagoRUN portal and sees only their own machines, consumption and invoices, under your domain with the Custom Domain & Whitelabel add-on and in your own app on the App Store and Google Play with the Custom Mobile App add-on. For an output-billed product, the brand on that screen is the brand on the invoice, which is exactly how it should read.
The business models, priced
| Model | What the customer pays for | Basis |
|---|---|---|
| Uptime plan | Machines ready at opening time | $ per appliance, monthly |
| Output billing | Cups, loads, cycles, vends | $ per unit of output |
| Consumables subscription | Filters, chemicals, descales by condition | $ per appliance, monthly |
| Fleet benchmarks | Usage, faults and water hardness across sites | $ per chain subscription |
The climb between the rows is the one we mapped in Climbing the Fusion Ladder, and in appliances it is the shortest climb of all, because the output counter, the hard part everywhere else, ships in the machine already.
Where does TagoAI fit?
TagoAI builds the fleet screens so your team stays on the machines. Describe the view in the TagoAI panel, for example “an espresso fleet board per chain, quiet while boiler recovery sits at the descaled reference, flagging any machine drifting slow”, and TagoAI creates the widget and its code against live devices; in the page’s sample it flags the machine recovering 6 seconds over clean. Verify what it builds against device data before a customer sees it. Underneath, the trained models in TagoIO Analytics learn each machine’s normal, so a busy Saturday does not read as a fault and a slow boiler never hides inside an average.
Frequently asked questions
Can appliances already at customer sites be connected? Yes. Add-on sensors for temperature, current, water flow or energy retrofit over LoRaWAN, cellular, satellite or other supported networks. New machines send from the controller over MQTT or HTTP.
Our controller has its own data format. Is that a problem? No. A payload parser converts it into named variables as each message arrives.
Can each chain see only its own machines? Yes. Access Management policies isolate every customer in their branded portal.
How is per-cup billing computed? An Analysis totals cups, wash cycles or run hours per customer per month and posts the figures to your billing system over HTTP.
Is the platform dependable enough to invoice on? TagoIO runs on AWS in the US or the EU with a 99.9% uptime SLA for eligible accounts, ISO 27001 certified and GDPR compliant. Details at tago.io/trust.
Start with one machine at one counter
Connect a single espresso machine or washer at a cooperative customer, let a month of cups or cycles accumulate, and price the uptime plan from what the data shows. The Commercial Appliances solutions page walks the full sequence, and the free QSR efficiency ebook covers the kitchen side of the same story. The box you ship was always a subscription; the counter inside it only needed somewhere to report.