The video tool buying committee starts with the second person you meet
Quick answer:A video tool buying committee is the set of people who have to agree before video software gets bought: the person who makes the videos, the person who owns the budget, and whoever holds legal, IT and procurement. A strong first demo reaches one of them. The meeting should end by naming the next one.
A marketing buyer at a mid size B2B employee recognition SaaS company, the one overseeing a two person video team, sent this after a demo that went well:
things just ramped up. I need to put a pause on these meeting for now.
Their quarter changed shape. The evaluation was sitting in one calendar, and that calendar filled. I now treat a first meeting as unfinished until a second name is on the record.
Who sits on a video tool buying committee?
The entry point is almost never the whole list. In our calls it has been an internal video program strategist, a video and production decision maker at a health system, a marketing manager with a two person team under them, and once a seller side individual contributor who found Capsule on their own and wanted their manager to see it.
Behind that person sits the budget owner, who readswhat Capsule costsand decides whether it fits a line item, plus legal, IT and procurement in whatever order that company runs them. Any one of them can pause a process without ever saying no.
Why does a video tool buying committee go quiet after a good first demo?
Four things have stalled our own evaluations: a reorg, a workload spike, an incumbent contract, and a gatekeeper who wants the vendor conversation to stop at their desk. Product doubt has never been one of them. Nobody has gone quiet on us because they looked at the software and disliked it.
The incumbent contract version is the easiest to hear. The video and production decision maker at a large multi state nonprofit health system said it early:
I just signed on with a new vendor. So I won't be looking for another two years.
That gives me a date, which is more than most first calls produce. Two year commitments are also one reasonvideo tools pile up inside one company.
The gatekeeper version is quieter. A seller side individual contributor who was the entry point at a B2B revenue intelligence software company wrote back after checking upward:
he asked that I not meet this week. He said he would explore Capsule and reach-out if its something he would like to explore further
The manager now owns the evaluation and has never seen the product with a person in the room.
| What we heard | Who said it | What paused the evaluation | Second person worth naming |
|---|---|---|---|
| things just ramped up | Marketing buyer overseeing a two person video team, mid size B2B employee recognition SaaS company | Workload | The team member who would run the first project |
| I just signed on with a new vendor | Video and production decision maker, large multi state nonprofit health system | Incumbent contract | Whoever owns the renewal date |
| he asked that I not meet this week | Seller side individual contributor, B2B revenue intelligence software company | Gatekeeper | The manager, while the first call is still happening |
| I am going to get in touch with my creative team | Marketing side buyer, product analytics software company | Handoff with no date | The named creative lead |
What does a handoff inside a video tool buying committee sound like?
Usually like good news. A marketing side buyer at a product analytics software company wrote this:
I am going to get in touch with my creative team internally to see if they are interested in trying something.
There is no name in that sentence and no date. The whole sequence depends on a busy person remembering to introduce us to people who missed the demo and have no reason to prioritize it. Ask which person on the creative team, then offer a short recording they can forward. Evaluations thatstall after a strong first meetingtend to stall exactly here.
How do you end a first meeting by naming the second person on the video tool buying committee?
I ask three questions before the last five minutes. Who else touches this once it becomes real. What would that person need to see. Whether we can get twenty minutes with them inside two weeks. Then I write the name into the recap email so it exists somewhere outside the call recording.
When the answer to the third question is no, I ask what has to happen first. That question surfaces the contract date, the reorg or the budget cycle, and it turnshow long video software approval actually takesinto something I can put on a calendar.
What does one video tool buying committee look like from both sides?
At that mid size B2B employee recognition SaaS company we heard from two people. The internal video program strategist described their own position on a call:
I'm the person who would spearhead this sort of thing. Like he's just like what video do you want
So we had the person who runs the work, reporting to someone who asks for outputs. Weeks later the marketing buyer above them wrote the email at the top of this post. Both voices were accurate, both were useful, and we met them in separate conversations instead of one.
A better version of that first meeting ends with the strategist naming their manager on the call, the manager watching twenty minutes of a real project, and both of them looking at the same three numbers we publish: 93% lower cost per video, 10x more videos, 8x faster production.
FAQ
What is a video tool buying committee?
It is the group whose agreement a video software purchase requires. Typically the producer or creative lead who would use the tool, the marketing owner who holds budget, and the approval functions: legal, IT, procurement.
Who approves video software purchases inside a large company?
It varies by company. In our own calls the first conversation is usually with the person closest to production, while the approval itself passes through a budget owner and one or more review functions.
Why do video software evaluations go quiet after a good demo?
In our call corpus the causes are reorgs, workload spikes, incumbent contracts and gatekeepers. Product doubt has not been one of them.
How do I get a second person into a video tool evaluation?
Ask for the name and the role before the first meeting ends, ask what that person would need to see, and put the name in the written recap so the introduction does not depend on memory.