The Impressive and the Billable Are Not the Same Thing

I've been asking people in the industry a question. Not abstract, concrete. Have you deployed this to a client?

Not demonstrated. Not run a workshop. Delivered, invoiced, and owned the accountability for it working in another organisation's daily operations.

OpenClaw

OpenClaw takes a disproportionately large share of industry discussion right now. Podcasts, LinkedIn feeds, conference stages. Gateway-first architecture, self-organising workflows, a curator that learns what's used and what can be archived. It's genuinely impressive to watch.

One of the more technically advanced people in the field, active in AI training, building for months, described it as "self-doing in a completely different way."

Same person, on whether it's been deployed to a paying client: "I haven't done that. Haven't productised it. Haven't seen that done. Just for my own world."

What It Is

OpenClaw is a personal tool. It's designed for its owner, not for handover. What makes it powerful is the deep integration with the owner's processes, context and workflows. Moving it to a client's organisation is not deployment. It's a new build in a new context with new data.

It also requires a level of technical maturity to deploy and maintain that most organisations neither have nor should need to have.

"Just for my own world" is not a failure. It's a precise description of what the tool is.

The Only Business Case

The commercial context around this category of tools is, with exceptions, FOMO consulting. Workshops and conversations that sell on the feeling that people should understand, should keep up, should be part of the movement. No one in the room says they don't understand. No one asks whether it can actually be delivered to a client.

That creates a tool that fills media channels in proportion to its visibility, not to what it's actually been delivered for.

The honest answer is rare. It costs something to say.

What's Missing

What does the client buy? Who owns the system when the delivery is done? Who calls when something doesn't work?

None of those questions get solved by the next version update.

If you can't answer who owns the system on Monday morning, you haven't built a product. You've put on a performance.

See also: Trust Comes Before the Technology (series 27) and They Don't Want to Understand -- They Want to Check It Off (series 17)