Sponsors Don't Read Your Prospectus

Every NOG organizer I've talked to has, at some point, spent a weekend making a sponsorship prospectus prettier: better logo placement rules, a shinier tier chart with the usual silver, gold, and platinum bands. I did roughly the same thing when I started sketching the sponsor-support module for NOGnet. My first instinct was to build a document generator: pick a template, drop in event stats, export a PDF that looks like it came from a real events company instead of a handful of volunteers and a shared spreadsheet.

Then I sat with how sponsorship actually gets decided at these events, and the document turned out to be the least important part of the whole process.

The bottleneck isn't the pitch

NOG events run on volunteer labor and a rotating cast of organizers. Someone chairs the event one year, hands it off the next, and whatever relationship existed with a sponsor's marketing contact usually leaves with them. Knowledge of who actually says yes at a given company and when their budget gets allocated tends to live in somebody's inbox, not in a document. Whether that contact even still works there is usually anyone's guess by the time a new organizer goes looking.

So the prospectus PDF, however sharp, tends to arrive at the wrong moment. It lands in a general inbox after that year's sponsorship budget is already spoken for, or goes to a contact who left the company a while back. The organizer put in the work on the pitch and the layout, and none of it mattered because the timing and the addressee were off.

Once that pattern was obvious I stopped trying to make the output prettier and started asking a duller question: what would help an organizer here? Fewer wrong doors would do more than a nicer-looking document.

What the module does instead

What I ended up building is closer to a contact-and-timing tracker than a pitch-deck tool. It keeps a record of who sponsored past events and who the actual human contact was, plus a line or two of notes on how that relationship went last time. When a new organizer takes over, that history is sitting there instead of buried in someone's old email thread.

The other half is more speculative and I'm still not confident I've got it right: surfacing likely sponsors an organizer hasn't approached yet, based on who sponsors similar events, and nudging on timing rather than content. Knowing that a company's next budget cycle is about to open is worth more to an organizer than a template with better kerning.

I'm building this alone, without a room full of sponsorship managers to interview, so take the confidence level with a grain of salt. Most of what shaped the module came from being an organizer myself and from a handful of conversations with other NOG people who seemed relieved someone was finally asking about the boring parts, who to call and when, instead of offering to redesign their tier chart for the fifth time.

There's a version of this feature I almost shipped that would have looked more impressive in a screenshot, with live PDF preview and drag-and-drop logo placement. Probably more fun to build, too. It wouldn't have solved a problem anyone running these events has. The prospectus was never what stood between an organizer and a sponsor saying yes. A stale contact and a missed budget window usually was.

None of this is finished. The contact-history piece works well enough that I use it for NOGnet's own sponsor conversations. The timing nudges are still rough, mostly because "when does a mid-size networking vendor plan its conference budget" turns out to be a hard question to answer generically across companies. I'll probably get that part wrong a few more times before it's useful.