BLOG

Process breakdowns

A series on building a CGI tutorial system for a U.S. automotive-tech client — from the first briefing to the system partners use today.

PART 1

We Were Hired to Make Videos

How a motion-design job posting turned into an 18-month project: why AVT's partner network needed shooting tutorials that anyone could follow with zero training.

READ →
PART 2

The Cost of One Mistake

When an untrained partner shoots a vehicle tour wrong, the mistake repeats at scale. Why we ruled out live-action video and built AVT's tutorials in CGI.

READ →
PART 3

112 Videos, or 38

Nine shooting levels times every vehicle configuration added up to 112 tutorial videos for one body type. Here's how we got it down to 38.

READ →
PART 4

The Visual Language That Became the Client's Property

Why AVT chose proprietary vehicle designs over stock 3D models, and how a custom visual language became an asset the client owns outright.

READ →
PART 5

Why Quality Shouldn't Depend on One Person

Over 200 tutorial videos by different artists still look like one product. How frame-level standards and test tasks keep quality independent of any one person.

READ →
PART 6

The Client Always Knew Where We Stood

Weekly reports, approval in small pieces and cheap blocking passes: how we kept an 18-month CGI project free of surprises for the client.

READ →
PART 7

The Mistakes We Made

Three mistakes from 18 months of building CGI tutorials, one of which reached the client, and why client approval is no substitute for quality control.

READ →
ARTICLE COVER
PART 8

This Isn't the End of the Project

Over 200 tutorials, five vehicle types finished and a system behind them: where the AVT project stands after a year and a half, and why it is not the end.

READ →

Let's map your process

We'll look at where people make mistakes, what it costs, and whether a visual system makes sense for you.