Skip to content
← Journal

Process 6 min read

From Brief to Frame: Inside Our Production Pipeline

How a one-line brief becomes a finished frame — and how we run the studio's content like software.

From Brief to Frame: Inside Our Production Pipeline

Great work isn’t an accident of talent; it’s a repeatable system that protects talent’s time. The romantic version of a studio is chaos and genius. The real version is a spine strong enough that the genius has room to happen. Here’s ours.

The spine: brief → treatment → board → shoot → grade → deliver

Every project, regardless of size, travels the same six stations:

  1. Brief. One page, ruthlessly short. The client’s outcome, the one feeling, the constraints. If we can’t write the brief in a page, we don’t understand it yet.
  2. Treatment. How we’ll get there — tone, references, the spine of the idea.
  3. Board. The visual plan, frame by frame, before a rupee is spent on production.
  4. Shoot. The most expensive station, so it’s the most planned. Surprises are for the edit, not the set.
  5. Grade. The last rewrite, in light. (We’ve written about why.)
  6. Deliver. Cut for every place it’ll live, because a film for the feed and a film for the cinema are different films.

Nothing skips a station. The discipline is what lets us be loose where it matters.

The file-based content engine

Here’s the part most studios don’t talk about: we run our own website like a piece of software.

New work doesn’t get “uploaded.” It gets dropped into an inbox — a folder with a short brief and the raw images. From there, a pipeline reads the brief, looks at every image, picks the strongest cover, chooses the page’s accent colour from the dominant hue in the work itself, optimises the assets, and composes the page — selecting layout blocks based on how many images there are and what shape they are.

Two landscapes become a diptych. A tall frame beside a wide one becomes an offset pair. A single hero shot becomes a full bleed. No two project pages come out identical, because the composition is driven by the work, not by a template.

Where automation ends and taste begins

The pipeline does the labour. It does not do the judgement.

It can resize a thousand images and never tire. It cannot decide that the third-best photograph is actually the cover because it’s the one that makes you feel the place. It can draft caption copy. It cannot decide what to leave unsaid. We let the machine handle more, and we keep enough for ourselves.

That line — between labour and judgement — is the whole reason the studio exists. Move it in the wrong direction and you get fast, forgettable work. Hold it in the right place and you get a studio that ships like software and feels like a hand-made object.

Why we built our own tools

We could have used an off-the-shelf site builder. We didn’t, because the tool you use shapes the work you make. A template nudges you toward the average. A system you built yourself nudges you toward your own standard.

So we built the standard into the tools: the RGB metaphor, the screen-black canvas, the block library, the pipeline that reads a brief and lays out a page. The website isn’t a brochure for the studio. It’s a working demonstration of how the studio thinks.

That’s the most honest portfolio piece we have.