You make the case for video automation with your own numbers, a small pilot and an honest list of risks. Measure what one version of your video costs you today, show how often the work repeats, and ask for a short trial on one real project instead of a big purchase. A boss can say yes to a measured, low-risk test far more easily than to a promise.
Most pitches for automation fail for the same reason. They lead with what the software can do, and the person signing off has no way to check any of it. This article is about the other approach. It covers what to measure before you say a word, how to put it on one page, which risks to raise yourself before anyone else does, and where our own product, Templater, fits into that conversation and where it does not.
One note before you start. This page assumes you already suspect automation is right for your work. If you are still deciding that, read when it is worth automating your After Effects templates first. That piece answers whether. This one answers how to get a yes.
Measure what the work costs you now
Your boss does not need to believe in automation. Your boss needs to see a problem that is real, costed and getting worse. The only evidence that does that is a record of your own work, gathered before you make the request, because a number you measured on your own desk is harder to argue with than any figure from a vendor. We will not give you an industry average to paste in, and you should be suspicious of anyone who does. Your stopwatch is the evidence.
Keep a simple log for two or three weeks. A spreadsheet with one row per finished version is plenty. Record five things for each one.
Hands-on time per version. Start a timer when you open the project and stop it when the file is delivered. Count everything, the swapping of text, the hunting for the right photo, the fixing of a line that no longer fits, the export, the renaming and the upload. People tend to time only the edit and forget the fiddly work around it, and the fiddly work is often most of the job. If you work in a team, ask each editor to log their own versions, because the slowest and fastest people on a team can differ a lot and an average hides that.
Turnaround. Write down when the request arrived and when the finished file went out. This is a different number from hands-on time. A version might take a short while to make and still sit in a queue for two days because the editor was on another job. Turnaround is what the people waiting on you actually feel, so it is often the number that lands hardest with a manager.
Errors and redos. Every time a version goes back for a fix, log what was wrong and how it got there. A misspelled name, an old price that survived from last week, a clip cut short so the end card was clipped. Each one looks like a one-off slip. A column of them shows a pattern, and the pattern is the cost of asking a tired person to retype the same kind of information over and over.
Who was waiting. Note who asked for each version and what they could not do until it arrived. A sales team that cannot send a follow-up, a social team that misses a posting window, a client who chases you twice. This turns your hours into someone else’s problem, and your boss probably cares about that someone else.
Where the changing information came from. For each version, write down where the new name, number or photo lived before you typed it in. A shared sheet, an email, a form, a database export. This matters more than it looks, because automation is cheapest when the changing information already sits in a table. If it arrives scattered across emails, part of your pitch has to be turning that habit into a sheet, and you should know that before you walk in.
At the end of the log you will have something most automation pitches lack. You will have a real number for hands-on time per version, a real picture of turnaround, a count of fixes and a list of the people who were kept waiting. Multiply the time per version by the number of versions you expect over the next quarter, and you have the size of the problem in your own units. For a wider view of the signals that show a team has outgrown hand editing, our piece on the volume where personalized video becomes operationally necessary goes deeper than we will here.
There is one more thing to measure, and it is the one people skip. Write down which parts of each version actually needed your judgment. Choosing the right shot for a story. Deciding the tone of a headline. Picking music. Those parts do not belong in the automation case, and saying so up front makes the rest of your numbers more believable. A pitch that claims everything can be automated is a pitch your boss will poke holes in. A pitch that says the repetitive half goes to the machine and the creative half stays with people is one they can picture.
Put it on one page and ask for a small test
The pitch itself should fit on one page. A manager reads the first few lines carefully and skims the rest, so the order matters more than the polish. Here is a structure that works, with a short note on why each part is there.
Open with the problem in the reader’s terms, not yours. “We make a new version of the regional promo every time an offer changes, and the sales team waits two days for each one” lands better than “editing is tedious”. Use the turnaround and the list of who was waiting, because those are the costs your boss already hears complaints about.
Then give the measured numbers, briefly. Time per version, the expected volume for the next quarter, the count of fixes from your log. Label them as what they are, a few weeks of your own measurement. Do not round them up to sound bigger. If your boss asks how you got the figure and you can show the log, you have won more credibility than any chart could buy.
Next, describe the change in plain words. The designer builds the video once as a template. The changing information, the names, numbers, photos and clips, comes from a spreadsheet, one row per version. Software reads the rows and makes the versions. People still check the results before they go out. That is four sentences, and it is enough. Avoid product jargon in this paragraph. Your boss needs to understand the shape of the change, not the features.
Then ask for a test, not a purchase. This is the most important choice in the whole document. A request to buy software for the department is a big decision with a budget line attached. A request to spend a few weeks rigging one real project, timing it and reporting back is a small decision with an obvious exit. Say what project you will use, how long the test will run, what you will measure and what result would count as success. Something like “if the template cuts our turnaround on the regional promo and the error count drops, we come back and ask for licenses, and if not, we stop”.
Close with the ask, stated plainly. Time for you or a designer to build the test, and approval to try the software. If there will eventually be a cost, say where the price lives rather than guessing at a figure. If the conversation reaches money, point to the vendor’s own pricing page.
A worked example
Picture an in-house video producer at a company that runs a large annual conference. Every year, the marketing team wants a short promo clip for each speaker, with the speaker’s name, title, session name, time slot and headshot over the event’s branded motion design. Speakers confirm in waves, details change, and sessions move between time slots. The producer builds every clip by hand from last year’s project.
She keeps a log for three weeks during the early wave of confirmations. It shows her hands-on time per clip, including the time spent fixing clips after a session moved. It shows that most requests sat for a day or more because she was also cutting the keynote video. It shows a handful of redos, each one a session time that changed after the clip went out, and one speaker whose title was out of date. And it shows that every piece of changing information already lived in the event team’s speaker sheet. She was copying from that sheet into After Effects by hand.
Her one-page case says exactly that. The problem is turnaround and stale details on speaker promos. The numbers are her own. The change is a speaker template driven by the speaker sheet the event team already maintains. The ask is to rig one template during a free trial, run the next wave of confirmations through it, compare the time and the error count against her log and report back before the event. Her boss does not have to believe anything. He only has to agree to a test with a clear finish line, and the test produces the evidence for the real decision.
Notice what the producer did not do. She did not promise that the template would make every clip perfect, and she did not claim it would free up a fixed number of hours. She kept the keynote and the opening titles out of the pitch entirely, because they are one-off creative work. That restraint is what made the rest believable.
Say the risks out loud before anyone else does
The fastest way to lose a yes is to have your boss discover a risk you left out. The fastest way to earn one is to list the risks yourself, with what you will do about each. These are the ones we would put on the page if we were in your seat. Some come from our own product documentation, and we have said so where they do.
The setup costs time before it saves any. Building and rigging a template is real work, and it happens up front. A simple template with one headline and one image is quicker than one with many dynamic layers, footage of different lengths and several languages. We do not publish a figure for how long rigging takes, because it depends on the template, so do not promise one. The honest version is that the test exists to find out.
Someone has to know After Effects. Templater is a plugin that runs inside After Effects. A designer builds the template and rigs it. After that, the people who supply the data only need the spreadsheet, which is part of the appeal. In the DraftKings story on our blog, the design team built templates in After Effects and linked them to Google Sheets, and members of the customer experience team filled in the sheet to produce graphics, with no design experience needed. But if nobody on your team can do that first step, the pitch has to include hiring for it or getting help, and you should say so.
The data has to be clean. A template reads what is in the cell, exactly as it is typed. If the source sheet is messy, someone has to tidy it, and someone has to own it afterward. A template moves errors from the edit to the data, where they are easier to check, but it does not invent correct information. Name the person who will own the sheet in your pitch.
The design will not change itself. A template is one design with many versions. If each video needs its own hand-built animation, there is no single template to rig. Rules can resize text and fit footage of different lengths, but they cannot make a creative choice. Keep work like that out of the test.
Rendering needs machines and licenses. Templater needs After Effects installed and running on any machine that renders, including a server or a cloud machine. The After Effects license for each of those machines is a separate matter from Templater, so flag it to whoever handles software licensing. Render time depends on the length of your videos, the resolution, your hardware and how the template is built, so tell your boss the test will measure it rather than quoting a number.
People still review the output. Automation does not remove the final watch before a video goes out. A study we wrote about in automated news video is better with a human touch found that partly automated news videos that humans edited were liked about as much as human-made ones, while highly automated ones were liked significantly less. That was news video, so do not stretch it, but it supports building review into your plan rather than promising to remove it. Our guide to preview modes and spot checks shows how to make that review fast.
Your security team may have questions. If your videos carry customer or employee details, someone will ask where that data goes. Templater runs on machines you control, which often makes that conversation simpler, but you should still bring your security or IT contact in early instead of after the pilot.
When you list risks like this, your pitch changes character. It stops being an enthusiast asking for a toy and becomes a professional proposing a controlled experiment. That is the version that gets approved.
Where Templater fits in the pitch, and where it does not
We make Templater, so weigh this section with that in mind. Its structure happens to suit the small-test approach above, which is why we mention it.
Templater links an After Effects composition to a data source. You can customize text, images, branding, graphic elements, colors and embedded footage, on one layer or every layer, so one template becomes many videos. It reads Google Sheets, tab-separated files exported from a spreadsheet app, JSON files and feeds, and Que, our cloud job queue. Layout rules adjust dynamic layers relative to their composition and to each other, so a long name does not spill off the screen. Time Sculpting, our patented set of time-based rules, crops, trims, shifts and stretches layers so footage of different lengths still fits the design.
For a pitch, the useful part is that it comes in three editions that work as steps. Rig is for the person who sets up a project, maps the data and previews the results. It cannot batch render. Pro adds batch rendering and replicating from the data source, started by a person. Bot adds automation, watching the data source and rendering new rows with nobody pressing a button. You can propose starting at the lowest step that solves the problem and moving up only when the test proves you need to. Our Templater licensing guide explains the editions in detail, and the pricing page has the costs.
The trial suits the test structure too. We offer a 30-day free trial of Templater Bot, so you can rig your real project before anyone spends money. The trial has two limits worth naming in your pitch: the dynamic layers carry a watermark, and replication inside the project file is turned off (replicates can still go to Adobe Media Encoder). If you buy and then find Templater is not right for you, you can contact us for a refund within 30 days of purchase. Put both facts in your pitch. They lower the risk of saying yes, and that is the whole point of the document.
If your boss wants proof that teams like yours use this, there are two stories we can point to without overstating them. DraftKings, which streams live for twelve hours a day, built templates for its stream graphics and has them generated from a spreadsheet in minutes instead of hours, according to our DraftKings case story. The National Academy of Television Arts and Sciences uses Templater to automate graphics for the hundreds of award categories and winners in an Emmy season. Use these as evidence that the approach works in production. Do not use them as a forecast of your own savings. Your log is your forecast.
Where does Templater not fit? If your work does not repeat, it is the wrong purchase, and you should not pitch it. If nobody can build in After Effects and you cannot get help, the plan stalls at step one. If you want a hosted web editor where non-designers build videos in a browser, that is a different kind of tool from a plugin that runs on your own machines, and we would rather you know that before your pilot than after. We also offer custom development and implementation help, quoted individually, for teams that want the setup done with them.
The bottom line is simple. Do not ask your boss to believe in automation. Show what the work costs today, in your own measured units, and ask for a small, time-boxed test on one real project with a clear definition of success. List the risks yourself, keep the creative work out of the claim, and let the test produce the evidence for the bigger decision. A measured experiment is much easier to approve than a promise.
People building this kind of case tend to ask us the same few things. Here are straight answers.
Frequently Asked Questions
What should I measure before pitching video automation to my manager?
Log every finished version for two or three weeks. Record hands-on time from opening the project to delivering the file, the turnaround from request to delivery, every redo and its cause, who was waiting on the version, and where the changing information came from. Hands-on time times expected volume gives you the size of the problem in your own units. Turnaround and the list of people waiting show the cost your manager already hears about. Your own measured log is stronger evidence than any industry figure.
Should I ask my boss to buy the software or to approve a trial?
Ask for a trial first. A purchase is a budget decision. A time-boxed test on one real project is a small decision with a clear exit. Name the project, the length of the test, what you will measure and what result counts as success. Templater has a 30-day free trial that includes every feature of every edition, with a watermark on the dynamic layers, which is enough to rig and run one real project. If the results hold up, you return with evidence and ask for licenses.
Can I promise my boss a specific number of hours saved?
No, and you should not try. We do not publish a figure for how long rigging takes or how much time a template saves, because both depend on your template, your data and your volume. Promise a measurement instead. Compare the time per version and the error count during the trial against the log you kept before it. That comparison is a number your boss can trust because you produced it.
Who on the team needs to know After Effects for this to work?
One person who can build and rig the template. Templater runs inside After Effects, so a designer creates the video, marks which layers take data and maps each one to a column. After that, the people who supply information only need the spreadsheet. If nobody on your team can do the first step, include hiring or outside help in the pitch. We also offer custom development and implementation help, quoted individually.
What risks should I include in the proposal?
Include the up-front setup time, the need for someone who knows After Effects, the need for clean data with a named owner, the fact that a template is one design and cannot invent new animation per version, the machines and After Effects licenses needed for rendering, and the review step that stays in place. If your videos carry customer or employee details, add a note that your security contact has been consulted. Raising these yourself makes the rest of the case more believable.
Which Templater edition should I put in the proposal?
Propose the edition your test shows you need, and say which step that is. Rig sets up the project and previews data but cannot batch render. Pro batch renders or replicates when a person starts the run. Bot watches the data source and renders new rows with nobody pressing a button. Propose the lowest step that solves your problem and move up only when the test shows you need to.
Is there proof that other teams use this in production?
Yes, though use it as evidence of the approach, not as a forecast. DraftKings links After Effects templates to a spreadsheet so its customer experience team can produce stream graphics in minutes instead of hours. The National Academy of Television Arts and Sciences automates graphics for hundreds of Emmy award categories and winners. Your own trial results are what should drive the decision about your team.
