What Actually Happens When You Send Us a Brief

Most clients send a brief and then wait. What they don't see is what happens in the 48 hours after that email lands.

We read it twice. The first time for what you're asking. The second time for what you actually need which is sometimes a different thing. A brief that says "we need product renders for our new launch" is asking for images. What it actually needs might be a campaign toolkit, a set of assets optimised for different channels, or a single hero image that everything else extends from. The distinction shapes the entire scope.

The diagnostic question

After the second read, there's a question we ask internally before anything else: is this a rendering job, a design problem, or a communication problem? A rendering job is defined. The product exists, the look is understood, the outputs are clear. We model, light, render, deliver. A design problem means the look isn't resolved yet. The client has a product but isn't sure how it should be presented  what environment, what mood, what camera direction. That's a creative conversation before it's a production one.

A communication problem means the brief is trying to solve something upstream. The images need to land with a specific audience in a specific context, and the brief hasn't quite articulated what that means for the visual approach. Getting this diagnosis right determines everything that follows. A rendering job that's actually a design problem will run into avoidable conflict in the revision stage. A communication problem that's treated as a rendering job produces technically correct images that don't do their job.

The first call

Then comes the first call. Not a sales call a diagnostic conversation. Twenty to thirty minutes. Most of the questions are simple: what is this for, when does it need to be done, what exists already, what's the budget range you're working with. That last question makes some clients uncomfortable. It shouldn't. Budget doesn't limit ambition it shapes it. Knowing what's available means we can tell you exactly what we can deliver within that range, instead of building a proposal that overshoots and surprises everyone at the invoice stage. We'd rather have an honest conversation early than an uncomfortable one later. A 10-minute conversation at the start can save three rounds of expensive revisions. That's not an argument for more process it's an argument for the right conversation at the right moment.

From first call to scope document

After the call, we write a scope document. Not a quote a scope. The scope describes what we understood the project to be, what we'll produce, what we'll need from you, how revisions work, and what happens outside the agreed scope. The scope is the agreement before the agreement. It's the moment where both parties confirm they're looking at the same project. Misalignments caught here cost nothing. Misalignments caught in week three cost time, money, and goodwill. The work starts when both sides sign off on what "done" looks like. That alignment isn't bureaucracy. It's half the project.