What clients think they need

Clients usually come to a studio with a specific request. A rebrand. A website redesign. A packaging refresh. Those requests are almost never wrong, but they are almost never the whole problem either. They are the surface symptom of something bigger sitting underneath.

A rebrand often means the positioning drifted before the visual identity did. A website redesign often means the naming stopped working before the site did. A packaging refresh often signals a distribution shift the founder has not yet articulated. The request is the tip of the iceberg. The real project is below.

What we listen for

The first thirty minutes of a discovery call are the most valuable minutes in the whole engagement. We are listening for what the client is not saying as much as what they are. Where do they stumble in describing the business? What competitor do they mention twice? What do they get defensive about? What have they already tried?

Those tells tell us what the brief actually needs to solve, which is often not what the client wrote in their intro email.

How we redefine the scope

By the end of the call, we usually reframe the project. Not to talk the client into a bigger engagement. To make sure the engagement we agree on is aimed at the right problem. Sometimes that means we shrink the scope. Sometimes it means we push it wider. Almost always, it means we shift what the deliverables are actually for.

Why this is not scope creep

Scope creep happens when the definition of the project changes after work has started. What we are describing is the opposite: doing the definition properly before work starts, so no one is surprised later. That work is unglamorous. It happens on a Zoom call, not in Figma. It is also the single biggest predictor of whether a project ships well.

The brief that comes in the email is a symptom. The brief we agree on the call is the actual project. That is the whole difference.