Every engineer arrives knowing what the last three visits found
For lift, climate, door and building services companies that maintain installations under contract. We help you work the AI-first way, with agents that prepare each visit and follow up inspections, and Hivemind, our flagship, holding every installation's history for engineers, planners and AI tools.
Built for lifts, climate systems, doors, technical maintenance
Read by Claude, ChatGPT, Copilot and your agents · within your permissions
Sound familiar
The fix lives in one engineer's head
Your senior engineer knows the unit at the hospital trips when the door sensor gets damp. When he is on holiday, the on-call colleague drives out twice and the client calls the account manager.
Inspection remarks slip between visits
The inspector leaves a list of remarks with a deadline. It sits in a PDF in someone's inbox, and the next maintenance visit goes ahead without anyone knowing it is there.
Every contract promises something different
One client has a four-hour response on breakdowns, another pays for office hours only. The on-call desk looks it up in contracts nobody can find at night.
Everyone works from the same company
What changes once Hivemind, our flagship, is the knowledge under every AI tool and agent your team uses.
First visit, right visit
The engineer reads the installation's history, the last fault and the parts used before getting in the van. Fewer return visits for the same fault.
Remarks get closed
Every inspection remark has an owner and a date. Planners see what has to happen on the next visit, and the client sees it handled before the reinspection.
New engineers up to speed
A new engineer asks their AI about a make, a site or a procedure and gets your company's answer, with the senior engineers' notes behind it.
Agents that do the work
Agents like these we build with you. Each has a toolbox: what it may read, what it may change, and what waits for a person.
Visit prep
Every weekday at 16:00 · for tomorrow's work orders
Visit prep, every weekday at 16:00 · for tomorrow's work orders: Reads tomorrow's work orders and posts a short brief per engineer in Slack: last faults, open remarks, parts, access and the contact on site.
3 allowed · 1 waits for a person
Inspection follow-up
Every weekday at 08:00 · for new inspection reports
Inspection follow-up, every weekday at 08:00 · for new inspection reports: Reads new inspection reports from the shared mailbox, adds each remark to the installation with its deadline, and drafts the reply to the client for a planner to approve.
2 allowed · 1 waits for a person · 1 does not exist for this agent
Connects today
- Knowledge base
- Slack
- Gmail
Next to what you already use
- Service and work order software such as Simpro or Syntess
- Maintenance and asset planning such as Ultimo or Planon
- Accounting such as Exact or AFAS
- Manufacturer portals and service manuals per make
A system without a connector yet gets one: we build it as part of Build.
We set it up with you
Implement
We interview your planners and senior engineers and write down installations, known faults and contract terms.
Automate
Visit briefs, inspection follow-up and the monthly service report per contract.
Build
A connector to your planning system, or a fault lookup by make and error code for engineers on site.
Learn
Training for planners and engineers: asking good questions on site, checking the answer, writing back what they found.
Questions
Our engineers are on the road all day. Will they use this?
They use it in the AI app on their phone, the one many already have. They ask in plain words, by voice if they like: what failed here last time, what this error code means on this make. There is no new app to learn and no form to fill in.
Can one client see another client's installations?
No. The knowledge base belongs to your company and only your team can reach it. Clients only see what you send them, and agents never send a mail to a client without a person approving it first.
Do we have to type up years of service reports first?
No. We start with interviews of your planners and two or three senior engineers, plus the documents you already have. Old reports on Drive or SharePoint can be read when someone asks. The knowledge base grows from there with every visit.