A little over a year ago, we delivered a basic tokenised design system for a client’s retail operation. Last week, he rang me up and showed me a fully functioning website he had built himself, guided by little more than a few prompts and Claude's assistance. Far from expressing dissatisfaction or seeking to terminate his agreement, he was eager to demonstrate his newfound competence and the progress he had made, anticipating recognition rather than reproach. This encounter ought to give every product or design system designer pause, for it is by no means isolated.
The longstanding premise behind most agency retainers has been that clients pay for strategy, brand and technical expertise because building and maintaining a relationship is beyond their reach. Yet that premise is rapidly losing force. The instinctive reaction as this reality shifts is often defensiveness: a reflexive insistence that 'you still need a CMS of some sort, you still need me for this.'
Such responses frame the client’s growing capability as a threat to be minimised, rather than a development to be understood. In truth, that posture serves no one and, more often than not, undermines the very relationships it is intended to safeguard. This client, by his own admission, is not technically inclined.
He experimented with Claude intermittently, but returned in earnest with the advent of Opus 4.5, upgrading to a paid plan and using it for tasks ranging from file organisation to research and data synthesis. By his own reckoning, he is now 'doing the work of the entire design team' without needing consolidation or consultation. He proceeded to build part of the website: DNS configured, HTML file prepared, Supernova style integrated, and a connection to the internal server established.
Notably, throughout our discussion, he never once mentioned “UI”, “System” or “CMS”. For him, the tools simply disappeared. It is early days—less than a month in, and far too soon for any meaningful return-on-investment calculations—but the capability itself is no longer in doubt.
The “Team of One” principle, defined by Design at Scale™ in early 2020, is particularly pertinent here: the constructive approach is not to defend one’s patch but to recast the relationship as a genuine partnership—business owner to business owner, rather than vendor to client. In practical terms, this means exchanging gatekeeping for translation. Be candid about where a do-it-yourself build will encounter genuine obstacles: spam-laden forms, hosting, DNS, terms and policies.
This is the essence of “One Language”: reduce technical risk to a minimum by delivering a fully integrated design system layer in terms that a non-technical proprietor can meaningfully address. Guide clients toward tools that suit their current capabilities, and make explicit what remains your responsibility and what is now theirs.
It also touched on “One Location”: where all the experiments live in one space so that each iteration and change can enable the next. These ways of experimenting with design data layers are no longer just experiments but production-ready MVPs—Minimal Vibe-coded Products. The translation to real code, like React or PHP, is almost instant.
Two objections surface fast. Some sceptics suggest their DIY site won't be as good as a professional build—probably true today, but beside the point; this was never an argument about quality, it's about the direction of travel. And 'it's one anecdote, not a trend'—fair, but early signals are exactly what you act on before they become obvious to everyone else. The real risk isn't the client's new confidence. It's the provider's complacency in assuming that this will remain rare.
GIVE™ and Design at Scale™ focus not on discoverability or new opportunities, but on delivering proven, verified, and well-tested code that can go live and serve your customers. It is about the provider's maturity in empowering the client to experiment, so that build and deployment reach DoR—Definition of Ready—sooner, with a well-defined MVP based on the actual company brand foundation rather than the Claude default model for rendering simple HTML pages.
AI-driven client self-service isn't erasing the need for our expertise — it's expanding our reach and narrowing our integration with the client, thereby increasing value on both ends. Clients now have agency; by enabling their exploration, we bring experience to the table before deployment and drive profitability and retention. And that is where the honest partner matters more than ever.
If you're rethinking how your team delivers value once clients can self-serve the easy parts, or facing the challenge of defining where that value lies and how to calculate it, that's exactly the conversation we have at Design at Scale™.
