Video production for consulting firms
A consultancy film has to prove competence without naming a single client. That contradiction is the entire planning problem.
What this is about
Almost everything a consultancy does on an engagement sits under an NDA, so the film has to say something while naming nobody. That one constraint shapes casting, locations and script at once: partners speak in anonymised patterns, case studies lose their sector detail, and client offices are usually out of reach entirely. What remains is your own space — meeting rooms, project rooms, travel — plus people whose calendars are sold in blocks. A partner released for half a day has been taken off billable work, which is why interview slots run short, shift late and are rarely rehearsed. Whiteboards, laptop screens and printed decks in frame carry live client material and get screened before release.
Sector routine beats general experience: knowing the field's approval paths and constraints produces more realistic plans than more shoot days without that context.
What runs differently here
Where this differs from the general case:
- Client names, logos and even recognisable sector details fall under the engagement NDA — the shot list has to work with anonymised examples from the start
- Partner and principal availability is billable time: interviews get half-day releases at best, and a live project escalation outranks your call sheet
- Whiteboards, sticky-note walls and open laptops in the background carry real engagement data and have to be dressed with cleared placeholder content
- Client premises are almost never filmable; the office you get is your own, which forces variety out of lighting and framing rather than locations
- Independence and conflict-of-interest rules can bar a consultant from appearing next to a competitor of their current client, even as a background extra
What the plan has to deliver
A production plan is useful to this role when it provides the following:
- An anonymisation pass on the script before casting: which stories may be told, at what level of detail, cleared by legal
- Interview blocks booked against partner calendars with a named alternate for each speaker who might get pulled
- A set-dressing list of cleared placeholder documents, slides and whiteboard content for every desk in frame
Common pitfalls
What most often goes wrong in practice:
- Building the story around a flagship project that legal will never let you describe recognisably
- Booking one senior speaker with no substitute and losing the shoot day to a client escalation
- Shooting an authentic-looking war room and finding real client names legible on the wall in review
With TillyGen
TillyGen turns the briefing into scenes that each carry their clearance level and their speaker, so an anonymisation note or a cancelled partner changes the schedule instead of the shoot day.
Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.
Frequently asked
May we show a real client project on camera?
Only with that client's written permission, and it is rarely given. Plan for anonymised composites instead: the pattern, the method and the outcome shape, with names, sectors and figures removed before the script is locked.
How long will partners actually be available?
Assume short, late-confirmed windows. Book interviews in tight blocks, prepare questions that work in twenty minutes, and name a backup speaker for every slot so a client escalation does not empty the day.
What has to be cleared besides the script?
Everything readable in frame — slides, whiteboards, laptop screens, printed reports — plus the office itself if client material is stored there. Treat set dressing as a compliance item, not a design detail.
How long does it take to get started with TillyGen?
A first project takes under an hour to set up. There is no configuration phase in which templates and fields have to be defined before the tool produces anything.
Can the results be exported?
Yes — as PDF for the crew, CSV for downstream systems and through the API for anything automated. The plan stays the source; the exports are views of it.