In development

Robots know where people are. Not who they are.

Concept · November 2026 · seeking pilot partners

A safety scanner sees a human as an obstacle forty centimetres wide. That is enough to hit nobody, and too little to work together. Which is why robots rarely fail on technology — and often on the floor: people do not trust them, and after three months the machine stands still.

Crew — a robot interaction module
The concept

Crew is a bolt-on kit for robots that already exist: a compute module with a badge reader and cameras, mounted on the robot. The kit gives the robot a colleague layer: it knows who is standing next to it — from the badge people already wear, never from faces — and remembers what they did together.

That changes what you can say to a robot. ‘Come to Krish’ instead of to a coordinate. ‘Continue from yesterday’ instead of setting up again. And the robot adapts its behaviour to how the people on this floor react: two robots on two sites behave differently after a year.

We build the identity and session layer, the behaviour model, the link to the robot, and the privacy architecture a works council can approve: badge off means anonymous, no performance reports, data stays on the robot. The robot's own safety stays in charge — the module gives goals, never motor commands.

Why it matters
25–35%
of a construction worker's day is skilled work; the rest is walking, waiting and searching (Aalto iCONS)
3.6 M
extra construction workers the EU needs by 2030 (European Construction Observatory, 2026)
1 kit
badge reader, cameras and a compute module, on the robot you already have

On your robot

No new chassis, no new arm: the pilot runs on the platform you already sell or use.

No re-certification

The module gives goals and speed limits; the existing safety chain stays untouched.

Past the works council

No face recognition, no performance data, badge off is anonymous. Built to be approved.

Robots that keep running

Acceptance on the floor is where field robots fail. This is the layer that changes that.

Who we're looking for

This is why this page exists. If you fit one of these rows, we want to talk to you.

Who
What we ask
What you get
WhoMobile-robot and cobot builders
What we askOne robot, one site, three months: the kit on your platform, in a co-funded pilot.
What you getWe do the integration; you get the pilot data, a working demo and first right to the OEM licence.
WhoIntegrators
What we askA customer where people and robots get in each other's way, and an hour with your engineer.
What you getPartner terms on the kit and support at the first installation.
WhoConstruction, logistics and lab companies
What we askA robot nobody trusts, and the works council's go-ahead to try.
What you getA pilot with no face recognition, no performance reports, and data that stays on the robot.
WhoRobot builders with scars
What we askTwenty minutes on what killed your last field robot.
What you getOur write-up of all the interviews, anonymised, and a seat at the first demo.
WhoDevelopment partners and funders
What we askCo-funding of the first kit and the first three pilots.
What you getThe full concept including the cart, the pilot results first, and a conversation about terms.
Get in touch

How we work

01

Feasibility first

Every stage starts with whether it works and what it costs — an honest go/no-go before money goes into building.

02

Proven parts, our own core

What already exists we buy off the shelf. We only build what is not there yet: the software, the integration and the design around them.

03

Developed in the open

The status is on this page, estimates are called estimates, and partners get a quarterly update — also when things go badly.

Can you supply, pilot, advise or fund?

Send two sentences. You'll get the full proposal under NDA, and a call within a week with the engineer working on it.

Get in touch
All projects