Ruby Hoedown how conferences get made, and attended
pinned under “Sponsorship”

What sponsors get, and what is quietly worthless

Half of every benefit list is deliverables and half is hopes, and only one half keeps a sponsor.

Every sponsorship document lists benefits, and most of those lists mix two very different kinds of thing. Some entries are deliverables: an event either provided them or it did not, and both sides can check afterwards. The rest are hopes, phrased as exposure, visibility or brand alignment. The distinction is the whole subject of this page, because a list made only of the first kind is what keeps a sponsor for a second year.

Which listed benefits can be checked afterwards Of the entries on a typical sponsorship benefit list, a table, a named catering break, ticket allocations, the recording credit and funded scholarship places can all be verified after the event. Exposure, visibility, brand alignment and thought leadership cannot be verified by either side. The verifiable entries are drawn as solid blocks and the unverifiable ones as faint outlines. Verifiable on the left, unverifiable on the right A table, in a named position A catering break, named from the stage Three tickets A credit on every recording Two funded scholarship places Exposure to a targeted audience Increased brand visibility Alignment with the developer community Thought-leadership positioning Nobody can say afterwards whether these happened. Five things that either happened or did not.
The same list, sorted by whether anybody could check it in the week after the event. The dashed entries are the ones that make the solid ones look weaker.

The deliverables worth listing

A table, in a stated position. Position is the variable that matters and it is usually left vague. A table beside the catering is worth several times one at the far end of a corridor, because the value is conversations and conversations happen where people queue.

A named catering break. The largest line in most budgets and the one attendees notice, because somebody says the name from the stage while people are holding the coffee it paid for. It is the highest-value item most events have and it is routinely under-priced.

Tickets. Two or three at a supporter level. Sponsors send engineers, engineers talk to attendees, and that is the mechanism the whole arrangement runs on.

A credit on the recording. The only item with a life after the day. A recording that stays online for years carries the credit with it, which makes it the best value in most tier tables and the one sponsors most often overlook.

Funded places. Named scholarship places, covered on the scholarship funds page. It is the item that reads as support rather than as advertising, which for a developer audience is the point.

What is quietly worthless

A logo on a slide between talks, which is on screen while the room is empty. A logo on a lanyard, which is face-down for most of the day. A social media mention, which reaches an audience the sponsor already has. A “premium listing” on a website that has a few hundred visitors a month.

A logo is not nothing. It is just not what anybody is really paying for.

None of these are dishonest, and none should be removed from a list where they genuinely happen. The problem is when they are the list, because then the price is attached to items that cost the event nothing and deliver correspondingly little.

What a sponsor should ask for

Three questions settle most of it. Where exactly is the table, and what is next to it? How many people arrived last year, as distinct from how many registered? And what does the event send afterwards?

The third is the one that separates events. An organiser who volunteers an honest report, including the parts that went badly, is an organiser who intends the relationship to continue. One who goes quiet after the invoice is describing what next year will be like.

The report afterwards

A page is enough. Arrivals against the figure that was promised, what was delivered, what was not and why, the recording links, and one or two things the event would change. It costs an hour to write and it is the most under-used tool in the whole arrangement, because it is what a sponsor forwards internally when the next budget is set.

Where something was not delivered, saying so unprompted is worth more than the item was. An event that admits the recording failed keeps a sponsor; an event that hopes nobody noticed loses one without ever being told why.

The levels these deliverables sit at are on sponsorship tiers, the document they are listed in is on the prospectus, and whether an event should take a given company’s money at all is on community versus corporate. The pillar is conference sponsorship.

Questions

What do sponsors actually get at a small conference?

Things that can be checked afterwards: a table in a stated position, a named catering break, a few tickets, a credit on the recordings and funded scholarship places. Exposure and visibility are not deliverables, because nobody can say afterwards whether they happened.

Is a logo on a slide worth anything?

Very little on its own. It is usually on screen while the room is empty between talks. It is not dishonest to list it, but when a logo and a lanyard are the whole list, the price is attached to items that cost the event nothing.

Which item gives the best value?

Usually the credit on the recording, and it is the one most often overlooked. Every other item ends when the day does; a recording that stays online for years carries the credit with it the whole time.

What should a sponsor ask before committing?

Where the table is and what is beside it, how many people arrived last year as opposed to registered, and what the event sends afterwards. The third answer predicts the relationship better than the other two.

What should an event report after the day?

One page: arrivals against the promise, what was delivered, what was not and why, the recording links, and one or two things worth changing. Admitting a failure unprompted keeps sponsors; hoping it went unnoticed loses them silently.