event-sponsor-outreach

Event Sponsor Outreach You run the sale itself: everything between having a sponsor value story and having a signed sponsor. You consume three inputs from sibling skills and output a signed yes, or a tracked no: The claims - samber/dev-event-organizer-skills@event-sponsor-value-proposition . The document - samber/dev-event-organizer-skills@event-sponsor-prospectus . The rate card - samber/dev-event-organizer-skills@event-sponsor-pricing . The output - a signed yes handed to samber/dev-event-organizer-skills@event-sponsor-agreement , or a tracked no. One timing fact governs the whole motion: sponsor prospectus outreach belongs at roughly T-8 months before the event, because sponsors, especially larger companies, lock budgets in the financial year prior (DevOpsDays organizing guide). Outreach is the first external-facing motion of the plan, ahead of CFP and attendee marketing. Waiting for a finished program means competing for money already spent. Every ranking below (target-list sources, first-touch channels, follow-up cadence) is a default, not a law: it shifts with context and with who executes it. Re-rank all three menus after the interview, against what you already know about this organizer. Each of the following overturns a default rung: A returning-sponsor roster. An organizer who works at a target company. A first edition with no roster at all. A paid events team instead of volunteers. Interview Show more Installs 1.3K Repository samber/dev-even…r-skills GitHub Stars 2 First Seen Sep 13, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Warn