Prospectus

The sponsor-facing document for an event. One page or one slide, built from five blocks in the order a reader’s questions arrive: what the event is and how long it has been running, who is in the room described in aggregate, proof that it works (past attendance, photos, brands who already backed you, a testimonial), the tiers with what each one includes and what it costs, and the contact plus the deadline to be included. Its test is simple. A brand should be able to read it and decide without emailing you a single question. It is written for the sponsor reader, credible and traction-led, which is exactly why none of its language belongs in copy your community reads.

Source: Eventbrite’s sponsorship prospectus guide defines it as “a comprehensive guide to your event and the sponsorship opportunities that exist around it” whose job is to “answer any questions a potential sponsor might have” (Eventbrite). The standard contents list (event concept and history, audience, community benefit framing, tiers with explicit benefits per bracket, contact and close) is consistent across Eventbrite and Social Tables. The DevOpsDays organizing guide treats the prospectus as the artifact you send sponsors instead of negotiating each deal, and puts it in the timeline at eight months out (devopsdays.org/organizing).

First used in: 1.5 · Sponsorship I: the package. Taken into the sales conversation in 2.4 · Sponsorship II: selling and activation.