THE METHOD
Six Stages, One Direction.
The same pipeline runs on every project, whether it is a single film or a campaign that has to ship in more than one language and format. It is written out here so you can see where your decisions land before you commit to anything.
01
Brief
We start with what the piece has to do: the audience, the message, where it runs and in which formats and languages. Scope and shot count come out of that conversation, and so does a realistic timeline.
You describe the project. Nothing is committed and nothing is quoted at this stage.
02
Treatment
The creative approach is agreed before any shot design begins: the story, the look, the camera language, and the continuity rules the piece will hold to from first frame to last.
You agree the direction, or send it back. This is the cheapest point in the whole process to change your mind.
03
Shot design
Every sequence is broken into directed shot sheets before a single frame is generated. Blocking, lensing and lighting are decided here, in writing, shot by shot.
You see the shot sheets. What is on them is what gets built.
04
Production
Each shot is built from structured prompts rather than prose, using JSON-driven prompt control. Characters are held steady across the production with reference sheets, and dialogue is matched to picture with frame-accurate lip-sync.
Nothing is needed from you while this runs, unless something in the brief changes.
05
Review and versioning
Versions are produced and compared side by side rather than committed to on the day. A change of location, product colour, time of day or language is another pass through the pipeline, not a new shoot.
You review versions against each other and say which one goes forward.
06
Finish and delivery
Colour grading, logo lock-ups and master delivery in the formats and aspect ratios the campaign actually needs, mastered from one concept rather than re-edited per placement.
You receive the masters. Format and aspect-ratio requirements are set back at the brief, not discovered here.
Tools in the stack
No single platform is good at everything, and the good ones change every few months. These are the tools currently in use. The list is expected to change, and a project is never designed around one of them.
Signature methods
These do not change with the tooling. They are the reason output stays consistent across a production rather than shot by shot.
- Character-consistency sheets
- Frame-accurate lip-sync
- JSON prompt engineering
- A/B versioning and iteration
- Cross-platform porting