What Aristo taught me about the gap between shipping and mattering
Building a working product is no longer the expensive part. I know this because
I built one. Aristo started as ChamberOne, a business communication platform that
answers customer questions from a company's own material, and it runs today as a
widget on a client's live production site. The build was fast. Everything after
the build was not.
That gap is the whole story, and almost nobody writes about it honestly, because
the build is the part that photographs well.
The measurement that changed how I work
When we took over a client's digital operation last year, I ran an inventory
before touching anything. The site had no analytics, no tag manager, no search
console verification, no pixel of any kind. Three plugins were installed and two
of them were inactive. The company had been publishing for months into a channel
nobody was reading, and nobody had noticed, because there was nothing in place
that could notice.
At the same time, our own publishing queue held 37 pieces of content. Thirty one
were waiting for review. Five had revisions requested. One was approved. Approval
existed. Publication did not. We had built the approval step and skipped the step
that makes approval mean something.
Neither of those problems was a software problem. Both were expensive.
What the sector looks like when you measure it
I wanted to know whether this was one bad case or a pattern, so we measured it.
We pulled the full web presence of 1,912 companies in one US business sector:
domain age, sitemaps, publishing history, mail infrastructure.
- 1,680 of them have no sitemap at all
- 76 have a blog
- 205 show any content publication date, ever
- 1,293 run corporate email, so these are operating businesses with staff and invoices, not shells
An entire sector of functioning companies publishes nothing. The tooling to fix
that has been cheap and available for two years. The tooling was never the
constraint.
Speed is a product decision, not a rendering decision
The same pattern shows up inside the engineering. We had a 3D product
configurator that looked correct and took about ninety seconds to produce a
result. Ninety seconds is not slow in rendering terms. It is fatal in product
terms, because nobody waits.
The fix was not a faster renderer. We moved the lighting out of the runtime and
baked it, then treated each option as an albedo swap. The same visual result now
arrives in about three seconds. Nothing about the model improved. We stopped
asking the machine to compute something at the worst possible moment.
Where the difficulty actually moved
Building Aristo took weeks. Getting a business to route its customers through it,
maintain the material behind it and trust the answers it gives is still in
progress, and that work has no shortcut. The technical barrier fell. The
behavioural barrier did not move at all.
This is why I am sceptical of AI product claims that lead with capability. A
capability demo tells you what the model can do in a controlled request. It tells
you nothing about what happens when a real company puts its name behind the
output, and that is the only question that decides whether the product survives.
The next generation of technology companies will not win on model access.
Everyone has model access. They will win on understanding why an organisation
with a working tool still does not use it.
Top comments (0)