# We build the technology other companies put their name on. > Nineteen years. Fifteen countries. Almost none of it with our name on it. A South African engineering house. Nineteen years of connected hardware, production AI agents, warehouse digital twins and respondent verification, shipped under our clients' names. ## The arrangement Our clients ship our work under their own name and keep the claim to it. We will not show you their logos or their results. What we will do is talk about the engineering in as much detail as you want. There is one below that we got wrong the first time, and in a conversation you will get the rest of them. ## What we build ### Hardware that talks when it was not designed to We design and build our own boards, ESP32 class, 24V, deployed inside commercial refrigeration. They report temperature, door events and power state over cellular links that drop for hours. Because the link is unreliable the device buffers locally and reconciles when it reconnects, and messages carry their own identity, so a replayed backlog cannot double-count a door opening. One equipment vendor would not release their protocol. We captured the bus traffic and reconstructed it, and those units are still reporting. Nobody has trouble with the sensor. The trouble is a network you cannot trust and hardware you cannot physically reach, so the firmware has to assume it is offline and be surprised when it is not. ### Agents that run unattended for years Production AI agents that hold real conversations with real customers, on WhatsApp and the web, with no human in the loop. Tens of thousands of messages handled, across years of continuous operation. We now run our own WhatsApp gateway. We used to rent one, and it went dark mid-service in a dispute we had no part in and no way to influence. That was our error to own: we had put a client's live channel on a dependency we could not restart. Conversation state is now persisted per turn, so a dropped reply is recoverable, and a retry returns the answer already paid for. Unattended does not mean unwatched. Every agent we run has a defined stop: a list of subjects it refuses and hands to a person, and a confidence floor below which it stops guessing and escalates. Failures are invisible to the customer and loud to the operator, which is the only version of that trade worth having. The hard part is the ten thousandth conversation, not the first: recovering its own state, and still running on a Sunday when nobody is watching. ### Warehouses that tell you what is wrong with them Digital twins of live distribution operations, built from movement data. We stopped building them from the warehouse's own plan because the plan and the floor diverge within months of go-live. On one 165,000 square metre site we ran evolutionary simulation against the real pick history and the model kept converging on a layout close to the inverse of the one in use. The fastest moving stock was in the furthest locations, and had been for years. Warehouse data almost never says anything is wrong. It reports what the operation did, not what it could have done, so the gap only appears once you model the second one. ### Systems that find the respondent farms inside your panel The fraud we find is rarely a bot. It is a paid human in a respondent farm, working through dozens of accounts on one handset, clearing state between sessions so each pass looks like a new person. They solve CAPTCHAs easily, because they are people. They pass attention checks, because they have seen thousands. They vary their answers just enough to survive straight-line detection. So we stopped trying to catch the answers and started catching the operation: state cleared between sessions, one device behind many identities, completion velocity, network overlap dense enough to separate a call centre from a family, and the fingerprints that survive an account switch. Five signals, weighted into a probability rather than a verdict, because the client sets the threshold. A brand tracker and a pharmaceutical study do not want the same one. We do not issue a pass or a fail. An honest respondent having a bad afternoon and a professional having a good one look similar on any single signal, and a system that hides that from you is lying about how hard the problem is. ## Who you would be working with **You will meet the engineers who build your system before you sign anything.** Nobody here will hand you over to a delivery team you have never met. ## How we got here We started in 2007, writing software for other people's businesses. Before long we were building the hardware as well. For example, in 2013 we rebuilt a category of live event and brand activation product around being portable. The incumbents arrived in trucks. Ours weighed forty kilograms, fitted in a car, and did more than the equipment it replaced. Banks put their name on it and ran it as marketing. What came after, roughly in order: enterprise platforms for warehousing, logistics and security. Facial recognition and computer vision. Robotics and hardware automation. Then our own boards, and AI that runs in production rather than in a demo, which is where most of the work sits now. Nineteen years of it. The names on the results belong to other people. ## How we engage We take the part nobody else wants: the thing that has to work, and that your existing supplier has said is not possible. Usually we own it end to end, from the board or the data model up. Sometimes we build one hard component and hand it to your team. Both are normal. Engagements start with a paid scoping piece, two to four weeks, ending in a specification and a fixed implementation price. If we do not think we are the right people, we say so then, and you keep the specification. Builds off that scope typically run three to six months. Afterwards you own the code outright, we warrant our own defects for twelve months, and you decide whether we keep running it or take it in house. Plenty of clients take it in house. ## Size **A mid-sized engineering house, based in South Africa, building for clients who mostly are not.** Small enough that whoever designs your system builds it. Large enough to have done it for nineteen years without missing a payroll. ## Close **Most of our work is invisible by agreement.** Bring your architect and ask us anything about how any of it was built. If we have built something like the thing you need, we will show you how it works. If we have not, we will say so. --- Contact: hello@beone.ai Source: https://beone.ai/ Generated: 2026-08-31 (auto-generated from index.html, do not hand-edit)