For machine and plant builders · worldwide installed base
Service portal. From the regional manager's inbox to the machine file.
Every machine gets its own file, tracked by serial number: build revision, service visits, maintenance reports. Your customer sees only their own machines and can request spare parts straight from the file. We build it and run it for you. Your ERP stays exactly where it is.
What a day with Kumiko looks like.
Same reality, told the other way around.
| Situation | Today | With Kumiko |
|---|---|---|
| Breakdown | Customer reports a breakdown, inside sales hunts for the serial number and history across the ERP, the service folder, and the regional manager's inbox. | Enter the serial number, done. Build revision, last visit, and open cases are right there, even when the regional manager is on vacation and nobody knows his inbox. |
| Documentation | Machine documentation sits with the customer in a folder that eventually disappears. | Every machine has its own file, tracked by serial number. Build revision, service visits, parts replaced, documentation revisions. None of it can go missing in a filing cabinet. |
| Spare parts | Spare-parts request comes in by email, the customer doesn't know their part number, inside sales translates it by hand into a quote. | The customer submits the request straight from their machine file. The part number is correct automatically, because the system already knows the build revision. |
| Service visit | Technician drives out without a visit history, the service report exists as a carbon copy on paper and turns up weeks later as a scanned PDF on the shared drive. | The technician sees the history on a tablet and writes the service report on site. The customer signs off right there, and it lands in the file straight after. Both sides get their proof: you get proof the contract was fulfilled, your customer gets the record for their own auditor. |
| Access | End customer, field technician, inside sales, and regional management all work with different, loosely defined access. | Every end customer is its own tenant and sees only their own machines. The separation sits in the database, not in a filter a bug could bypass. Technician, inside sales, and regional management get their own roles. |
| Contracts | Maintenance contracts sit in contract documents, nobody can see at a glance which deadline is currently running out. | Contracts and deadlines live as data in the system. Before one runs out, the portal lets you know. |
How you get there.
First call, first version in 2 to 4 weeks, then ongoing operation.
The starting point is one product line or one service area, not the entire fleet. We build machine files, roles for end customer, technician, inside sales and regional management, plus the API connection to your ERP.