A 30-person company can pick a video vendor with a checklist and a gut feeling. A 500-person company cannot. Once procurement, legal, brand, and three department heads all have a say, “we liked their reel” stops being a defensible decision. You need a process that produces a paper trail, survives an audit, and still lands you a vendor who is actually good at making videos.
We have sat on the vendor side of dozens of these selections, and the difference between the smooth ones and the painful ones is always structure. Here is the sequence that works: requirements document, shortlist, a sane RFP, a scoring matrix, a paid pilot, and then the MSA.
Start With a Requirements Document
Before you contact a single vendor, write two pages: the business goals video needs to support, the formats you expect to produce over twelve months (training, testimonials, event coverage, executive comms), estimated annual volume, technical deliverables and specs, brand and accessibility requirements, security or compliance constraints, a budget band, and who signs off. If you cannot fill in those blanks internally, you are not ready to evaluate anyone.
This document does double duty. Internally, it forces marketing, HR, and leadership to agree on what they are actually buying before vendors start pitching them different dreams. Externally, it makes every quote comparable, because all bidders are pricing the same scope instead of guessing. Most selection disasters trace back to skipping this step.
Build the Shortlist Before the RFP
Do not blast an RFP to fifteen companies you found on Google. Research first: pull six to eight candidates from referrals, industry work you have admired, and local market searches. Check that each one has portfolio work in your formats, the capacity to handle your annual volume, and clients of roughly your size. Cut to three to five before any formal document goes out.
Then book a 20-minute capabilities call with each finalist. You are not negotiating yet. You are checking team size, how much they subcontract, who would run your account, and how fast they respond to a simple scheduling email. That last one is data. A vendor who takes four days to book an intro call will take four days to answer questions during your shoot week. Take notes in a shared doc during these calls, because the small impressions, who asked smart questions, who talked only about gear, who actually listened, become tiebreakers later when the proposals all look polished.
Write an RFP Good Vendors Will Answer
Here is an uncomfortable truth: the best production companies decline bad RFPs because they have enough work already. Thirty pages of legal boilerplate, forty generic questions, no budget range, and a demand for free spec creative will filter out exactly the vendors you want. Keep yours under ten pages: company context, your requirements document, eight to twelve questions that actually differentiate vendors, your evaluation criteria, and a real timeline.
Always include the budget band. Hiding it does not create leverage; it creates quotes scattered from $8k to $80k that you cannot compare. And instead of spec work, ask each vendor to walk through one past project similar to yours: the brief, the process, the budget, the result. That answer shows you how they think without asking them to work for free.
Score With a Matrix, Not a Meeting
Define weighted criteria before responses arrive, not after. A typical split: portfolio relevance 25%, process and project management 20%, price 20%, capacity and scalability 15%, references 10%, working chemistry 10%. Adjust the weights to your situation, but lock them first. Deciding the criteria after you have read the proposals is just rationalizing a favorite. Put the weights in the RFP itself, too: vendors write sharper, more honest responses when they know exactly what is being measured.
Have each stakeholder score independently, then meet to discuss only the gaps: anywhere two scorers differ by more than two points. This keeps the loudest person in the room from picking the vendor, surfaces concerns early, and produces exactly the documentation procurement wants when someone asks why the cheapest bid did not win.
Pilot Project First, Then the MSA
Do not award an annual contract off paper. Give your top scorer one real, paid project: a single video on a normal timeline, typically in the $3k to $10k range. Watch how they handle kickoff, communication cadence, the shoot day, and especially revisions. Proposals are marketing. A pilot is evidence. Most vendors look identical on paper and completely different in week three of a project.
If the pilot lands, negotiate the master services agreement: rate card, turnaround SLAs, revision terms, IP and raw footage ownership, insurance requirements, and termination language. With the MSA in place, every future video is a one-page statement of work instead of a fresh procurement cycle. That speed is the entire payoff of doing selection properly once.
Vendor Selection FAQ
How long should the whole process take?
Six to ten weeks from requirements document to signed MSA, including a pilot. Two weeks for requirements and shortlisting, two to three for the RFP cycle, three to four for the pilot, one for contracting. Longer than that and your best candidates start deprioritizing you.
Who should own the process, procurement or marketing?
Split it. Marketing owns requirements, evaluation, and the creative judgment, because they have to live with the work. Procurement owns the commercial terms, compliance checks, and the MSA. Selections run entirely by procurement tend to optimize for price and produce videos nobody watches.
How many vendors should receive the RFP?
Three to five. Fewer gives you no real comparison; more wastes everyone’s time, including yours, since reviewing a serious proposal properly takes two to three hours. Quality vendors also check how wide an RFP went, and a cattle call signals the win probability is not worth their effort.
What if the pilot project goes badly?
Then it did its job. You spent a few thousand dollars to avoid a year locked to the wrong partner. Debrief honestly, decide whether the issues were fixable communication problems or fundamental capability gaps, and run a pilot with your second-place scorer. That is exactly why you ranked more than one.
The bottom line: requirements before vendors, shortlist before RFP, matrix before opinions, pilot before contract. Each step exists to keep the decision honest, and together they take less time than untangling one bad annual agreement.
If you are building a vendor process right now and want a sample requirements doc or a look at how we respond to RFPs, email Mason Carter, our Client Solutions Manager, at mason@blueboxdigital.com. He will send real examples, no pitch attached.
Put us in your RFP.
Requirements doc, scoring matrix, pilot project: run your full process on us. We answer fast, quote in line items, and enjoy a fair fight.