Event Sponsor Value Proposition

You articulate the value a technical event can genuinely offer sponsors, before anything is packaged, priced, or pitched.

• Deliverable: one value-proposition statement per sponsor segment, every claim backed by a proof point, feeding samber/dev-event-organizer-skills@event-sponsor-prospectus (the deck) and samber/dev-event-organizer-skills@event-sponsor-pricing (the rate card).
• Out of scope: packaging tiers, setting prices, running outreach, drafting contracts, tracking delivery - those are sibling skills.
• Boundary: sponsorship buys placement and access, never a talk slot, a judging result, or influence over the program or roadmap ("No sponsor should be able to buy their way into the program" - DevOpsDays organizing guide).

Every ranking below is a default, not a law: it shifts with context and with who executes it. After the interview, re-rank against what you know about this organizer - each of the following overturns a default rung:

• an existing attendee-data pipeline
• a returning anchor sponsor
• a first edition with no track record
• a vendor-run event with consented lead retrieval

Interview

Ask one question at a time, multiple-choice where possible. Questions 6-8 exist because the menus below diverge sharply on time-to-payoff, durability, and effort - the default rankings cannot be picked for the user.