« Unveiled », « launched », « deployed », « available »... Robotics marketing loves words that sound like immediate availability. The problem: they describe very different realities, and confusing them is costly.
At Bybotix, we read these terms as statuses, not interchangeable promises. Here's the decoder.
Three words, three realities
Most announcements fall into one of these three statuses — and only the third really concerns you as a buyer.
- Announced. A video, a name, a promise. It proves an intention, sometimes a vision. Not that a product exists.
- Demonstrated. The robot does something, on stage or on video — often in controlled conditions, sometimes via teleoperation. It proves a capability, not availability.
- Commercialized. There's a price, specifications, sales terms. Only then are we talking about a product — and even then, not necessarily reachable from Europe.
The same robot can be « commercialized » in the United States and only « announced » for Europe. Both statuses coexist without contradiction.
The classic trap: the demonstration
A demonstration is built to convince, not to inform. Teleoperation, editing, dozens of takes, a calibrated set: nothing illegal, but it isn't proof of autonomy. In front of an impressive video, one useful question: is it repeatable, without a human pilot, outside the set?
How to read an announcement without being fooled
Three simple reflexes:
- Look for price and specs. No public price or datasheet = we're, at best, at the « demonstrated » stage.
- Separate the market. « Available » where? US or Chinese availability is not European availability (importer, conformity, support to verify).
- Date the promise. « Soon », « this year », « eventually »: a vague date is information in itself.
This decoder complements our 5 maturity levels grid, which goes further — all the way to local support.
The Bybotix takeaway
Using these words as statuses saves you disappointment and bad budget decisions. And when information is missing, saying so is also a service: a serious observatory resists vagueness rather than relaying it.
To find out which status a robot you're interested in is really at, ask us.