AI POCs Are the New Briefs

A client recently sent over a brief ahead of our introductory call. It was well-written, covered the basics, gave us enough to prepare. During the call, I asked my usual discovery questions. And somewhere in that conversation, it came out: they'd been playing around with the concept in Claude. They'd actually built something.

They never thought to show it to us. It hadn't occurred to them that it might be useful. To them, it was just tinkering.

To me, it was the real brief.

What they'd built in an afternoon told me more about what they actually wanted than anything in the document they'd spent hours writing. And it made me realize: this is going to happen more and more.

The Shift That's Already Happening

For decades, the design process started the same way: client describes what they want, designer interprets, designer builds. The brief was the bridge between their world and ours.

That bridge is changing. Clients can now generate a working prototype in an afternoon — without a designer, without a developer, without a technical background. AI tools handle the execution. The client just directs.

This will become the norm. Clients will increasingly arrive at the first meeting with something already built. And the question for designers is: what do you do with that?

Why a POC Tells You More Than a Brief

A written brief is a translation. The client has something in their head — a feeling, a need, a vision — and they translate it into words. Words that are imprecise, incomplete, and filtered through what they think a designer needs to hear.

A POC is something different. It's a series of decisions. Every choice the client made — what to include, what to leave out, which direction to take when the AI offered options, when to stop — reflects how they actually think. It's their thinking made visible.

AI tools build on best practices by default. They generate what's commonly done, what works in most cases. But the client plays with it. They iterate. They nudge it in directions that feel right to them. By the time they stop, the POC carries two layers: the AI's baseline, and the client's personal fingerprint on top.

That fingerprint is what you're actually looking for. It's the brief underneath the brief.

The First Question You Should Ask

When a client shows you their POC, resist the instinct to evaluate it. Don't say what's good, what's wrong, what you'd change. Not yet.

Ask instead: "When did you feel this was ready? What made you stop here?"

That question unlocks something a design critique never would. It takes you into their decision-making process — how many iterations they went through, what they were optimizing for, what "good enough" looked like to them. And in that answer, you'll find the principles they were reaching for, even if they couldn't name them.

How many iterations did they take? That tells you how deeply they engaged. What made them stop? That tells you what they value most. What did they consciously change from the AI's first output? That tells you where their instincts diverge from best practice — and that divergence is exactly where real personalization lives.

You are not reviewing a deliverable. You are reading a map of how they think.

What AI Misses — and Where You Come In

AI tools are good at best practices. What they can't do is understand how a specific person, in a specific organization, with a specific context, will actually perceive and use what's been built. AI optimizes for the general. Design, at its best, optimizes for the specific.

The client's POC is already partway there. They've taken the generic AI output and pushed it toward something that feels right to them. Your job is to take that further — to understand what they were reaching for, amplify the choices that reflect genuine insight, correct the ones that reflect habit or limitation, and bring the UX and UI knowledge that makes the difference between something that looks right and something that actually works.

Not polishing but translating — from their instinct to something intentional.

Communication Becomes the Design Work

This shift changes what design actually is. When the client arrives with a POC, the work is no longer primarily about execution. It's about understanding. About conversation. About knowing how to ask the right questions, listen to the answers, and translate what you hear into decisions about what stays, what changes, and why.

You can't withdraw behind your monitor and influence this process from a distance. The work happens in the conversation — in real time, with the client, on the fly. The designer who can navigate that — who can read a POC, ask the right question, understand the thinking behind it, and shape the next step together with the client — is doing something AI cannot replicate.

And because AI is handling more of the execution, there is more time for exactly this. More time to understand. More time to personalize. More time to make the work genuinely reflect the client — not just the industry standard.

The Brief Didn't Disappear. It Evolved.

Written briefs will still exist for a while. But the most valuable brief you'll receive is increasingly going to be something the client built — not something they wrote. A POC that carries their fingerprint, their instincts, their unconscious decisions about what matters.

The designers who recognize this — who know how to read a POC, ask the right questions, and build on what the client has already started — will work faster, produce more relevant outcomes, and build stronger relationships.

Your client built your brief in Claude. They just don't know it yet. Your job is to know it for them.