What we build
Software, hardware, and the way a team works around both. We start with what is broken in your week, and we make whatever that actually needs.
Four kinds of work
From one screen that saves a team an hour a day, to the system the whole operation runs on.
When the answer is not software. A sketch becomes a board, a board becomes a unit, a unit becomes a batch.
Software cannot fix a process that was never agreed. Sometimes the build is the process.
A product, the team that runs it, and the company around it. Started from nothing, more than once.
Intelligence, plumbed in
It sits on connectors, a semantic layer and a warehouse. We build those, and the hardware underneath when nothing is measuring the thing yet.
How we make AI survive real data
Connectors 
A semantic layer 
Evals you can check The part most suppliers get backwards
The usual deal is that you buy a platform and then change forty working habits to suit it. That is why rollouts fail, and why the person who understood the job best is often the first to leave.
A week on the floor, in the office, on the site. We learn the shortcuts nobody wrote down, because those shortcuts are usually the real process.
If the team writes on a whiteboard at 7am, the software fits around the whiteboard. We do not begin by telling forty people their habit was wrong.
The test we use: can somebody who was not in the meetings use it on their first shift, with nobody standing over them. If not, it is not finished.
The person who knew how the work really ran is the one a platform rollout usually drives out. We build so that knowledge gets easier to use, not replaced.
Hardware
Half the time the data you need is not in any system, because nothing is measuring it. Then the build starts with a board, not a screen.
01 What it must do, what it must survive, what it must cost. On paper, in days.
02 Schematic, layout, first boards on the bench. The code that runs on them is ours too.
03 Printed, then tooled if the numbers call for it. Sealed for dust, water, heat or a forklift.
04 In the plant, on the vehicle, on a wrist. Real conditions break assumptions that a bench never will.
05 Small-run build, test jig, serial numbers, spares. Enough to run an operation on.
However hard, whatever it is
Everything on this page is something we have made. The reason we can make it is the four steps below. We do not start building until we know what is actually causing the problem.
01 Days where the work happens, not a workshop in a meeting room. We watch the job get done and write down the shortcuts nobody wrote down.
02 Your data, your rules, your vendors and their documentation, and the published research on your sector. We report what is actually in there.
03 Not which tool fixes this. What is actually causing it, taken apart until we reach the piece that cannot be divided further.
04 Weeks, not quarters. By this point we are not guessing what to build, and guessing is the thing that makes projects long.
The hard edge
Some of this needs a partner, a licence or a test range. We tell you which on the first call, not after you have signed.
How both can be true
We have written a page on each sector we work in, with the figures and the sources. You can read it before you speak to us and judge whether we understand your week.
See the sectors we have studied
Engineering transfers. A queue behaves the same whether it holds insurance claims or castings. A sealed enclosure keeps water out of a sensor on a dairy farm and on a runway.
Tell us what you need madeStraight answers
A build company. Integration is usually the first project, because that is where the pain is, and it earns the right to the bigger work. Most of what we ship afterwards did not exist before.
Really hardware. Schematic, board layout, firmware, enclosure, test jig, small-run build. When an off-the-shelf unit does the job we will tell you to buy it, because that is cheaper for you.
Those are two different things. The industry knowledge is research, written down, and you can read it on this site. The building is engineering, and engineering transfers. A queue is a queue whether it holds claims or castings.
The engineering, yes, with the right partner for the parts that need a licence, a range or a cleared facility. We say which parts those are in the first call rather than after you have signed.
Whatever they do not have time or hardware skill for. Often we build the first version and hand it over, with the code, the boards and the documentation. Being kept is a choice, not a lock-in.
Because we spend the first week watching how they work instead of telling them. If the software needs a training programme to be used, we treat that as our mistake, not theirs.
The connector, the warehouse, the screen the team actually uses, and the sensor when nothing is measuring the thing you want to predict.
See everything we build Software Hardware Ways of working Whole ventures 
