What problem does it solve? Event organizers struggle to articulate why a company should sponsor their conference or hackathon, often defaulting to vague exposure claims, invented ROI figures, or promises (lead lists, speaking slots) that community-run events structurally cannot deliver. This Skill produces honest, segment-specific value propositions before any prospectus or rate card exists. ## Core Features & Use Cases - Six-part JTBD template: Builds one statement per sponsor segment (Who / Why / What Before / How / What After / Alternatives) for product-feedback, recruiting, brand, and community-member buyers. - Honesty gating: Classifies the event as community-run or vendor-run, deletes undeliverable value categories like pipeline at community events, and writes a not-offered list before any benefit claim. - Proof-point instruments: Attaches evidence to every claim using returning-sponsor rate, registration demographics, program-content ratio, testimonials, or surveys, labeling each claim evidenced or aspirational. - Use Case: An organizer courting a bank's early-talent team for a 300-person community conference gets a recruiting-buyer statement that refuses a candidate database, cites the 60%-senior composition figure from registration data, and names conversation-based mechanisms like office hours. ## Quick Start Ask the assistant to draft the sponsor value proposition for your event, stating whether it is community-run or vendor-run and which sponsor segment to start with.
