What we learned from the project we almost turned down

The brief seemed fine. The budget was fair. Something felt off and we couldn't name it until halfway through the discovery session.

What the brief said

A product studio — two founders, three years in, genuinely interesting work in a sector we don't usually touch. They wanted a brand identity and a positioning refresh. They had a clear timeline, a reasonable budget, and a strong sense of what they liked visually. On paper, an ideal project.

The thing that made us hesitate was harder to articulate. Something in the initial call about the way they described their previous branding work — the way they explained why it hadn't felt right, and what they thought had gone wrong. It was too certain. Too resolved. When someone has a precise theory about why the last thing failed, it sometimes means they know what they want and need someone to execute it. That's a different project than the one they're describing.

We took it anyway. We should have asked one more question first.

The discovery session

Halfway through, it became clear that the two founders had different intuitions about what the brand was actually for. Not incompatible ones — they'd built a successful company together, they were clearly aligned on the work itself — but the brand positioning question surfaced a difference in how each of them thought about their audience and their ambition that neither had fully named.

This isn't unusual. In fact, it's common enough that we now expect it on any project with two or more founders. The brand strategy process has a way of surfacing assumptions that were working perfectly well until someone asked about them directly.

What was unusual was how far along both founders were in their respective theories about what the solution should look like. They'd each arrived with a position that was slightly different, and both positions were strong enough that the discovery work couldn't simply dissolve them. We had to spend the first two weeks on work that should have been done before we were engaged.

What we'd do differently

The question we should have asked in the initial call: Have the two of you talked about this together yet, or are we going to be the first conversation where this comes up?

It's a slightly uncomfortable question. It implies that the founders might not be aligned. Most clients would hear that as a mild accusation. But it's a much smaller discomfort than two weeks of discovery work that covers ground the clients thought was already behind them.

We ask it now. Not as a gotcha — as a genuine inquiry about where the project is starting from. The answer tells us more about the real scope of the work than anything in the brief.

What we learned

Two things, neither of them new, both of them worth relearning:

The brief tells you what the client thinks the project is. The discovery session tells you what the project actually is. These are almost never the same thing, and the gap between them is where the real work happens. A studio that only works to the brief is a studio that produces technically correct answers to the wrong question.

And: the hesitation you feel at the start of a project — the thing you can't quite name, the question you don't quite ask — is almost always worth naming and asking. Not because it will change whether you take the project, but because it will change how you go into it. We were right that something was off. We just didn't listen to ourselves in time to prepare for it.

The project turned out well. The work was strong and the clients were genuinely good to work with. But the path to the outcome was longer than it needed to be, and the length was our fault — not because we didn't know what we were doing, but because we didn't ask what we already suspected.