Theo says he won't use a product with a dashboard
Arvid Kahl says his customers are asking for the same thing, and the fix is making UI, MCP and API fully interchangeable.
Theo posted that if he has to go to a dashboard to use your product, he is not going to use your product. The second line is the one that should worry anyone selling software. He said he is more likely to tell Claude to rebuild it.
If I have to go to a dashboard to use your product, I'm not going to use your product.
Arvid Kahl replied that he is hearing the same thing from his own customers, sometimes directly and sometimes as requests for feature parity in the API and MCP (the protocol agents use to call a product's tools). His conclusion is broader than Theo's. He says products have to present all affordances equally to humans, agents and machines, and that UI, MCP and API have to be fully interchangeable.
Where they actually differ
This is not a disagreement about direction. Both are saying agents are now a real class of user and that a product only reachable through a web interface is a product some people will route around. The split is scope.
Theo's version is a verdict on the dashboard itself. If the primary way in is a screen he has to log into and click through, he churns before he starts, and the replacement is a prompt rather than a competitor. Kahl's version keeps the dashboard and adds obligations. Three surfaces, same capabilities, no feature that exists in one and not the others.
That difference costs money. Building one agent-shaped interface and skipping the UI is a smaller job than maintaining three paths to every feature forever, with the parity testing that implies. Kahl is describing ongoing work, not a launch.
The business read
What makes this more than a preference is the rebuild threat. Theo is saying the floor for "I'll just make my own" has dropped far enough that a thin product behind an annoying interface is now competing with a weekend of Claude. Kahl's framing is the defensive one, which is that parity across surfaces is what keeps a customer from asking whether they need you at all.
Two people, two posts. Nobody has put numbers on how many customers are actually asking for this yet.
UI, MCP, and API have to be fully interchangeable.
Steal the numbers, not the vibes
One email a day. Under three minutes. Real MRR, real pricing, real launches from founders building with AI.