Almost every project we take on begins with a request for a specific thing.
We need a two-minute explainer. We need a showreel for the conference. We need something for the funding round.
And almost every one of those requests turns out to be a symptom rather than a diagnosis. The two-minute explainer is requested because a founder is exhausted from explaining the same thing in every meeting. The conference showreel is requested because last year’s booth was ignored. The funding-round film is requested because a deck isn’t landing and nobody is quite sure why.
The stated deliverable is a guess at a solution. The job of discovery is to check whether it’s the right one.
What client discovery actually looks for
We’re trying to answer three questions the brief usually doesn’t contain.
What is the actual mechanism? Not the positioning: the machinery. Where does revenue come from, what has to be true for the model to work, and which part is genuinely hard? In telecoms and Web3 especially, the interesting bit of a business is almost always the bit that never makes it into the marketing copy, because it’s difficult to say quickly.
What does the audience currently believe? Every film enters an existing conversation. If your audience already thinks your category is a scam, a slick brand film reinforces the suspicion rather than answering it. If they’ve never heard of the category at all, you’re building from zero and cannot assume a single shared reference.
What is the film competing against? Not competitors’ films: attention. A LinkedIn feed. A conference floor at 4pm. A partner watching on mute in a meeting they’re only half in. The context of viewing changes the film more than most briefs allow for.
You cannot get to any of this from a brief document. You get to it from conversations, and from asking questions that are slightly uncomfortable.
The questions that do the most work
Some of these look blunt on paper. Asked properly, in a room where trust already exists, they’re the fastest route to a good film.
“Explain it to me like I’m smart but I’ve never heard of your industry.” The gap between how a founder explains their business to a peer and how they explain it to an outsider is the entire territory the film has to cover. Listening to someone struggle across that gap tells us exactly where the difficulty lives.
“What do people consistently get wrong about you?” Misconceptions are gold. They’re a pre-identified list of the things the film needs to correct, and they come from real conversations rather than from a positioning workshop.
“What have you tried that didn’t work?” This saves months. It also tells us whether the problem is the content, the format, the distribution or the underlying proposition. Those are four very different diagnoses with four very different films attached.
“Who in your organisation disagrees with this project?” There is almost always someone. Finding them in week one is a gift. Finding them at the final approval stage is a disaster.
“What would make this a waste of money?” Clients answer this one honestly and specifically, in a way they never answer “what does success look like?” The failure condition is more informative than the success condition.
Understanding beats requirements-gathering
There’s a version of discovery that’s really just form-filling: budget, deadline, deliverables, references, done. It’s efficient and it produces exactly what was asked for, which is the problem.
We’d rather do the slower thing. On a complex project that means sitting in on internal calls, reading the whitepaper properly, asking an engineer to walk us through the architecture, spending time with the product rather than the pitch. It means being willing to be the least knowledgeable person in the room for a while.
This is uncomfortable, and it’s the point. If we never reach the stage of asking a genuinely naive question, we haven’t gone deep enough to find where the audience will get lost, because we’ll have skated over the same hard part they will.
The moment discovery has worked
There’s a specific signal we look for, and it’s reliable.
It’s when we explain the client’s business back to them, and they say “yes, and actually the bit you should lead with is…”
That sentence means two things. First, that our understanding is close enough to be useful. Second, that the client has stopped briefing us and started thinking with us. Everything after that point is collaboration rather than instruction, and collaborative projects are consistently better than instructed ones.
Until that sentence happens, we’re still guessing well. After it, we’re building.
When discovery changes the deliverable
Sometimes the honest outcome of discovery is that the requested thing is wrong.
We’ve had projects where a single explainer film was the ask and the real need was a short series, because one film could not carry three distinct audiences without becoming vague. We’ve had the reverse too: a proposed series that would have been better as one properly-made piece and a set of stills, because the budget wouldn’t stretch to three good films and three mediocre ones help nobody.
Saying this costs money in the short term. It’s also the difference between a studio that sells production and a studio that solves problems. The first gets a project. The second gets the next four.
Why understanding is the deliverable
Everything we make is downstream of this stage. The script, the visual language, the pacing, the choice of what to leave out. All of it is just understanding, expressed in a medium.
Which means a studio’s real capability isn’t its camera package or its render farm. It’s how quickly and how honestly it can come to understand something it didn’t understand a month ago. That’s the skill. The rest is craft in service of it.
Clarity isn’t a style. It’s a by-product of somebody having genuinely done the work of understanding, and audiences can tell the difference immediately, even when they couldn’t tell you why.