2.4 · Sponsorship II: selling and activation
The big idea: sponsorship gets sold off a list, not off a hope, and what you are actually selling is something the sponsor gets to do in the room, designed by you.
The analogy
Section titled “The analogy”You already know what happens after the deck exists. The producer takes it out. And what separates the producers who close from the ones who don’t is almost never a better pitch. It’s a longer list. They keep every financier, fund, and executive they have ever spoken to in one place, with where that conversation stands and what has to happen next, and they keep adding names to it while the earlier ones go quiet.
Two habits live inside that list. The first is that a good producer asks what kind of film this person is looking to back before pitching the one in their bag. The second shows up later, once money arrives with a brand attached to it. The good ones write that brand into the scene so it belongs there, instead of taping a logo across the frame. A can of soda sitting on the counter in a diner scene is invisible in the best possible way. A character stopping mid-conversation to tell you how refreshing it is, is where the film dies.
Selling sponsorship is those two habits, and nothing else in this lesson is more complicated than that.
Segment: 18:16–33:29, identifying prospects, pitching without being salesy, and upgrading tierswatch full video
How it works
Section titled “How it works”In 1.5 you built the package. What makes somebody say yes to it is a list. A sponsor pipeline is one tab on your master sheet where every brand you might approach gets a row, and every row sits in one of six named stages: prospect, contacted, call, proposal, closed, fulfilled. The row holds the company, the actual human’s name, when you last spoke, and the single next thing that has to happen. That is the whole tool, and at your scale it lives in a spreadsheet. Not a downgrade from real software, just what the practice looks like until you are carrying dozens of partners at once.
The arithmetic of that list is the uncomfortable part, and also the freeing part. Most rows die. Brands go quiet, budgets were committed months ago, your contact changes jobs. So the number worth watching early is not how many closed, it is how many named prospects are in there at all. Three conversations that all end in no does not mean sponsorship doesn’t work for a filmmaker community. It means three is not a pipeline. And a no is not a dead row, it is a row you contact again next time, which is exactly what Tom on the panel describes: relationships that took a year or two to turn into anything.
Filling the top of that list starts with fit, not with size. The brands worth your first ten rows are the ones whose goal points the same direction yours does. They want filmmakers to touch their gear, or to be seen backing the people coming up. Start with the brands who already showed up for you, because a past supporter is the warmest row you will ever have. Then work outward through the categories around a filmmaker’s life. Gear and rental houses, post and colour, coffee and food, film schools, festivals.
Then comes the stage almost every beginner skips. A discovery call is a short conversation where you ask what the sponsor is trying to achieve, before you show them a price list. Fifteen minutes, no deck. Shaina’s line on the panel is the reason it exists: the data you put in front of a sponsor is only valuable if it happens to be the value they were looking for. A brand chasing awareness and one chasing product trials want different things from the same booth, and you cannot tell which from their website. Her other rule belongs here too. Don’t be salesy. You are not persuading a stranger, you are finding out whether there is a fit, and saying so honestly when there isn’t.
What you write down after that call is a ROO, a return on objectives. It is the sponsor’s own stated goal, rewritten as something you can observe and report back. Not sales, because their sales happen somewhere you cannot see. More like fifty filmmakers getting hands on the gimbal, or the brand named from the stage as the reason the room got fed, or photographs of real people using the product that they are free to post. Write it into the row while the call is fresh. It becomes the spine of the proposal, and later of the report.
The proposal is then easy, because it is your published prospectus with their name on it, the tier you honestly think fits, and the activation you designed around their ROO. Hold your published prices, because every custom deal is a negotiation you repeat with the next brand. When you do want to move a sponsor up a level, use the levers the panel names, because they cost nothing out of budget: bundle the next event in at the higher tier, or offer exclusivity in their category.
The last stage is the one people forget is a stage at all. Fulfillment means every promised benefit actually delivered, with proof captured while the event is happening rather than reconstructed from memory a week later. Logo placement, booth position, the mention from the stage, the tickets, the photos. Each one marked delivered, changed, over-delivered, or missed, honestly, including the missed ones. You build the whole report in 3.6. For now it is enough to know the sixth stage exists, and that renewals come from it, not from next year’s prospectus.
Which leaves activation, the half that turns all of this from a sales problem into a design problem. The sponsor does something in the room rather than appearing on a banner, and you design the slot. There is a single question to ask of every idea: does this add something to the room, or does it interrupt it? A table where people can pick up a gimbal and shoot with it adds. A brand covering the food, named warmly from the stage, adds. A sales pitch dropped into the middle of the program interrupts, and your integrity rule already ruled it out. That is precisely why the rule earns its place. It stops being something you enforce and becomes the constraint that makes you invent something better.
One last thing, the same seam as always. The pipeline, the ROO, the proposal, the report are all written for the sponsor reader, concrete and traction-led. None of that language goes near the copy your community reads. In a community post, a sponsor’s activation appears as a thing people get to try, never as a partner we are pleased to announce.
The receipts (evidence, if you want it)
- The six-stage spreadsheet pipeline (prospect → contacted → call → proposal → closed → fulfilled) is standard practice at community scale; dedicated sponsor-management platforms only appear at property and agency scale (SponsorCX). This course’s industry map §4 records it as the community-scale default.
- DevOpsDays on owning the pipeline: “From experience, we found that it helps to have a dedicated local organizer or two act as the contact with the sponsors to track prospects, payment, and giving them discount codes.” The same section lists what sponsors will ask before you ever get on a call, including what they get at each level, so the prospectus should be ready to send (devopsdays.org/organizing).
- On timing, their runway puts the prospectus out at eight months before the event, and says why: “Sponsors, especially larger companies, lock in budgets the financial year prior. It is best to get on their radar now instead of after your program has gone live” (devopsdays.org/organizing).
- On holding your published prices: “you may want to refrain from deviations from whatever standard package you publish in your sponsor prospectus. Exceptions take extra CPU cycles for your busy organizing team.” And on breadth over size: “the more companies that sponsor, the better: it amplifies the ideas and shows that many companies subscribe to the devops idea” (devopsdays.org/organizing).
- The integrity rule carried through from 1.5, verbatim: “No sponsor should be able to buy their way into the program. The schedule should be decided by your local organizers,” alongside “we do NOT ever give out or sell lists with contact details of attendees.” The same guide strongly discourages scannable attendee badges, because the common implementation hands sponsors a contact list by another route (devopsdays.org/organizing). Worth reading before a sponsor asks you for lead scanning.
- TEDx runs a nine-step sponsorship process that maps almost cleanly onto the pipeline: brainstorm prospects, check them against the prohibited list, reach out with a letter and a presentation, finalise with an agreement, “collaborate on activation,” invite them to your event, send a thank-you with photos and a recap afterwards, and keep in touch if you want them next year (TEDx Organizer Guide, About partnerships).
- Their described outreach is a staged sequence, not a single email: “a letter, followed by a one-page project brief, followed by a phone call, followed by an in-person presentation of slides or a portfolio, ending with follow up phone calls and detailed discussions” (TEDx, Approaching sponsors).
- TEDx’s own activation menu, from their relationship-management chapter: a “sponsored meal” announced as provided by the sponsor, a gift from the sponsor to all attendees, “a short demonstration, given by the sponsor, to exhibit a new technology outside the main venue space,” an engagement area in your social space, and logo placement. Same chapter: assign one or more people from your team to check in with the sponsor a few times during the event day (TEDx, Relationship management).
- TEDx draws the same line DevOpsDays does, from a different direction: sponsors “have no editorial control or veto power over your program,” cannot be speakers at the event they sponsor, and “don’t have the right to dictate who appears on your stage or who attends your event” (TEDx Organizer Guide, sponsors and finances).
- Activation, as the wider industry defines it: interactive booths, product demos, branded photo experiences, gamified stations such as a hoop-shot booth that converts baskets into charity donations, and walkthrough experiences (Skift Meetings, experiential marketing examples; Events.com, brand activation ideas).
- From the video segment, the lines worth keeping. Shaina at 27:43: “I have a number one rule, don’t be salesy. It’s really about building that relationship, getting to know them.” Shaina again just before it, on why the discovery call comes first: “you really have to find out what their goal is for being at your event,” because “the data that you put in front of them is only going to be valuable if it’s the value they’re looking for.” Kiera at around 30:11 on upgrades: bundle two events into one higher-level purchase, and look for anything you can add “that does not take any money out of your budget.” Tom at around 32:22 on category exclusivity as the other upgrade lever (Whova, Event Planning Tips 26).
- On the fulfillment stage, previewed here and taught in 3.6: build the tracker before the event, one row per promise with the proof to capture, an owner, and a status (HeySummit, sponsor report template). Itemise every asset, benefit, and activation truthfully, including explanations where an objective was not met (The Sponsorship Collective, fulfillment report template). On timing, “delivering a visual, data-rich recap within 10 business days demonstrates professionalism” (Bridged, sponsorship ROI).
- Flag on the anchor prices. The DevOpsDays tier figures quoted back in 1.5 are that guide’s approximate examples, currency-mixed across EUR and USD, and they vary by city. This course treats them as structural anchors only, never as price guidance for the Philippine market (industry map §8, item 5).
- Honest gap, restated. Sponsorship as a full sales system, meaning prospect research at volume, objection handling, renewal cadence, is publicly owned by The Sponsorship Collective, whose free material this lesson synthesises alongside DevOpsDays practice. What you get here is a pipeline a volunteer organiser can actually run. It is not their methodology.
Your one move
Section titled “Your one move”Open the Pipeline tab on your master sheet and put ten named prospects in it. Six columns: company, the human you would actually contact, stage, date of last contact, the one next step, and the date that next step happens. Start with the brands who have already supported the community, then fill the rest from the categories that sit around a filmmaker’s life. Everyone starts at Prospect, except the ones you have already spoken to, who start where they really are. Thirty minutes, done when there are ten rows and every row either names a person or says out loud that finding that person is the next step.
A worked example: seeding the August pipeline
The brands who have already supported Filmmakers Connect are your warmest rows, and they belong at the top of the sheet before you go looking for anyone new: Cafe Shylo, Luntra, Rotary Filmfest, APFI, Hollyland, Skyrocket, TTRacing. Every one of them has said yes to something once already, which makes the ask a continuation rather than an introduction.
The rest of the ten come from categories, not from trying to brainstorm brand names in the abstract:
| Category | Why they fit the room | Likely tier |
|---|---|---|
| Gear and rental houses | The room is full of people deciding what to shoot on next | Cash tier plus a hands-on activation |
| Coffee, food, venue | Feeding a room of a hundred people is a visible, warm contribution | Host tier, in kind |
| Film schools and workshops | Their students are already in the room, and they want to be seen backing the scene | Small cash tier, or Community tier |
| Festivals and other communities | No cash changes hands, they cross-promote you and you promote them | Community tier |
| Post, colour, and audio houses | Rarely approached by community events, which is exactly why they answer | Cash tier plus a demo slot |
Now one activation, designed rather than accepted. Say a gear brand’s ROO from the discovery call is “get the new gimbal into the hands of people who will actually buy one this year.” The lazy version is a table with a poster on it. The designed version is a station in the connect-time window with two units, a volunteer whose only job is keeping it busy, a short line for people to try a move they have never pulled off before, and the community photographer briefed to shoot it. The sponsor gets hands on gear, a queue that reads as demand, and a folder of photographs of real filmmakers using their product. The room gets to play with a gimbal for free. Nobody sat through anything.
Notice which reader each half of this is written for. The table above and the ROO are sponsor-facing, and none of that phrasing belongs in a community post. What the community hears is simply that there is a gimbal to try.
Want to go further?
Take the three warmest rows on your sheet and book the discovery call before you send any tier sheet at all. Fifteen minutes each, one question to open it: what would make this worth it for you. Then write their answer into the ROO column in their words, not yours. Three calls will teach you more about what your room is worth than any amount of redrafting the prospectus.
The needle: an event is won before doors open, and a sponsor conversation is won on a list you were adding names to weeks before you needed the money, and in a call where you listened first.
Terms introduced
Section titled “Terms introduced”Check yourself
A gear brand replies to your prospectus email within the hour: "Interested, send us the packages." What is the step most first-time organizers skip right here?
You have approached three brands about August. All three said no. What does that actually tell you?
A camera brand comes in at your top tier and wants their new gimbal in front of people. They propose a ten-minute demo from the stage, in the middle of the live podcast recording. What do you design instead?
You can move on when you can… name the six pipeline stages in order, say what a discovery call is for and what you write down after it, and look at any sponsor idea and tell whether it adds to the room or interrupts it.
Go deeper
Section titled “Go deeper”- Next up: 2.5 · Program design: the show people remember, where the room’s energy gets shaped on purpose and the live podcast becomes a peak with a rehearsal of its own.
- The full Whova panel runs just over an hour. Outside the segment above it drifts into poll readouts, host-platform features, and war stories from very specific industries, so the fifteen minutes you watched is the usable part of it.
- The DevOpsDays organizing guide, Finding and Handling Sponsors, read alongside its sponsorship packages section. It is the closest published account of running sponsors as a volunteer team, right down to invoicing and chasing logos.
- The TEDx Organizer Guide, sponsors and partnerships, for the nine-step process, the sample outreach letter, and the relationship-management chapter on what to do with a sponsor once they have said yes.
- The Sponsorship Collective, the honest gap named again. Their blog is free, and it is the deepest public material anywhere on sponsorship as a sales system.