Skip to contentIn memory of Adam Robinson.Watch the film
SaaS Yacht Club

Why building software UI for humans is a risky bet in the AI era

Adam Robinson · Jul 2026 · 1 min read

Last week Clay released an API after all of the smartest Clay pundits in the world told me they’d absolutely never ever do it. What does THAT tell you about the state of the world?

My Take: You’re an idiot if you’re building UI for people.

The argument, made to me by INCREDIBLY smart people, was that a public API would hurt Clay's business by making it less sticky. Clay was sticky BECAUSE workflows lived in the UI. Let people build on an API, and those workflows go elsewhere. It also devalues Clay's vendor relationships, because you no longer have to log into Clay to access that data. Which was their other "moat."

Now, it's possible that 100% of the revenue Clay actually cares about is Enterprise, and that revenue will be VERY slow to move onto an API/CLI. If that's the case, Clay may have done this to get UGC going again. UGC comes from the SMB segment, and you can't kill stickiness that's already dead there. If that's the play, tip of the hat to Kareem and the Clay team. Wise move.

But even so: Clay just did something that, if you asked Claude whether they should do it, Claude would say "no, that kills your moats and your stickiness."

That's a HUGE statement about the state of the world today.

#1: I love that at least ONE other CEO isn't blindly taking direction from Claude.

#2: This way of doing things is in such high demand that a $5B darling unicorn is willing to satisfy it, even though it's very not good for the stickiness of their business.

What am I getting at?

If I were starting a new business today (and I am)...

I would service this use case and do nothing else (which I am).

UI for humans is dead.

Long live APIs. 🏴‍☠️

Written by Adam Robinson and shared publicly; kept here in full, in his memory.