Anthropic's Sonnet 5 frustrates non-technical business users

The user runs a small B2B company with two people and handles everything during the day. They adopted AI agents early, initially using Viktor, and became proficient enough to commit their marketing, copywriting, and strategy workflows to Cowork, an AI agent platform built on Claude. They were explicitly assured by peers in the AI community that they should not learn to code, because no-code platforms like Cowork would mature rapidly—improving "basically daily." Under that assumption, they invested in restructuring their workflows around Cowork and Sonnet 4.6, which handled business conversations solidly.

When Anthropic released Sonnet 5, the user found it unsuitable for their work. Sonnet 5 produces output that is longer and more generic, burns more tokens, and delivers the same or worse substance in business conversations. Where Sonnet 4.6 had been capable for strategic work, Sonnet 5 is not. The user has switched to Opus 4.7, the more expensive model, to maintain the quality they need—a cost increase they did not anticipate.

At the same time, Anthropic redesigned the Cowork interface, merging agents and conversations into a single view. Previously, they were cleanly separated. The user reports that this consolidation has destroyed their workflow organization, consuming 2–3 hours per week just to manage the new, merged view. The confluence of model downgrade (requiring a more expensive fallback), higher token burn, and interface friction that adds weekly overhead creates a compounding cost and usability burden. The user's original bet—that no-code platforms would mature steadily and remain cost-efficient—has not paid off; instead, they face higher costs, worse output quality in their use case, and eroded workflow efficiency.

The post highlights a widening gap between the promises made to non-technical business users and the reality of using no-code AI platforms. The user was explicitly told to avoid learning to code and to trust that no-code tools would mature at a pace that justified early adoption; that pitch persuaded them to commit resources and workflow redesign around Cowork. Instead, a model update (Sonnet 5) degraded the user experience—not because capability was removed, but because the new model's output became longer, less focused, and more token-hungry for the same business tasks.

This is not a case of the user misusing the tool or lacking technical skill; it is a case of the platform's economic and performance characteristics shifting against the user's needs. Forced to upgrade to Opus 4.7 to maintain output quality, the user incurs higher per-token costs. Simultaneously, the interface redesign—merging agents and conversations—has introduced friction that previous clean separation eliminated. Together, these changes undermine the two core promises: cost-efficiency and ease of use. For a 2-person company managing everything during the day, 2–3 hours lost per week to interface overhead is material. The tension suggests that for no-code platforms to sustain adoption among non-technical business users, model updates and interface changes must not increase cognitive or financial friction, even if they add raw capability elsewhere.

No comments yet. Be the first to share your thoughts!