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.
Installierte Basis · weltweit
Maschinen
Sound familiar?
Your machines run at customer sites all over the world, many of them for fifteen years already. The overview of all that lives in the regional manager's head. Six typical symptoms:
Friday afternoon, right before quitting time, a customer reports a breakdown. Now inside sales starts searching: serial number in the ERP, build revision in the service folder, last visit in the regional manager's inbox.
The regional manager keeps half the customer history in his own Outlook. If he's on vacation, the search stalls.
"I need the part that got replaced last time." That's usually all the customer knows, and they shouldn't need to know more. But which part number matches their exact build revision is often something inside sales doesn't know either. The quote still gets typed up by hand.
The machine at the customer site looks different from the engineering drawing. Someone rebuilt the drive unit eight years ago.
The machine documentation sits with the customer in a folder. Sooner or later the folder disappears. Then someone on your side has to dig up the right revision on the shared drive.
The technician drives out without knowing what a colleague already replaced on the last visit. He fills out the service report on paper, with a carbon copy. One copy stays with the customer, the original is supposed to go back to the plant. Sometimes it arrives. When a warranty dispute comes up later, the one thing missing is proof that the machine was serviced at all.
And on a Friday afternoon he's standing in front of the machine without the right spare part, because nobody knew it was already running low after the last visit.
What you committed to in the maintenance contract lives in the maintenance contract. In other words, a PDF. Nobody can see at a glance which machines are under contract or which deadline runs out next week.
And the simplest question of all goes unanswered: which machine stands where, at what build revision, at which customer?
What a day with Kumiko looks like.
The portal doesn't replace the ERP, it sits next to it. Master data and order creation stay exactly where they are. The connection runs over the API.
„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.
„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 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.
„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.
„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.
„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.
Installierte Basis · weltweit
Maschinen
Techniker Novakhat den Servicebericht vor Ort erfasst: Hydraulikventil getauscht, Ersatzteil direkt aus der Maschinenakte bestellt. Ausführungsstand und Dokumentation sind aktualisiert.
How you get there.
Pilot program: 3 months free, setup and hosting included, in exchange we get to turn it into a case study. Just ask whether a place is currently open. After that, fixed pricing: setup one time, hosting monthly, billed separately.
1 / 3
We talk through your service reality: how many machines are out there, how you handle spare-parts requests and service visits today. Clear answer at the end: fits or doesn't.
2 / 3
The starting point is one product line or one service area, not the entire fleet at once. We build machine files, roles for end customer, technician, inside sales, and regional management, plus the API connection to your ERP. Free for pilot customers, otherwise a fixed price in the four-figure range depending on scope.
3 / 3
Hosting in Germany (Hetzner) or on-prem on your own server. Updates, backups, monitoring, a direct Slack channel to the maintainer. Monthly fixed price based on number of machines, not on your number of end customers.
Setup sprint and ongoing hosting are separate line items. Setup once, hosting monthly. The pilot program covers both for 3 months. And if we go out of business as a vendor: the generated code lives in your own repo, the data in your own Postgres database, running in Docker. The portal keeps running on your own server, even without us. (The self-host path, around €50 a month on Hetzner, is the separate option for your own devs, not the service price here.)
Tech-Substanz für IT-Leitung
Tenant isolation for every end customer →
Every customer sees only their own machines. The isolation sits in the database query itself, tenant-scoped from the ground up. It holds up even for a portal with hundreds of end customers on one platform.
Machine file via event-sourcing →
Every service visit, every part swap, every documentation revision is an event. A complete machine history across a 15 to 20 year lifespan, not just the last few years.
Four roles, four views →
End customer, field technician, inside sales, and regional management see exactly what their role allows. Permissions are tied to actions, not to one shared interface.
Hosting in Germany or on-prem →
Hetzner in Germany, your own Kubernetes or bare metal, air-gapped possible. Customer data from anywhere in the world stays under your control.
Pilot program open to machine and plant builders in the DACH region. Direct contact with the maintainer, no sales funnel.