What problem does it solve? Deciding which developer conferences, meetups, and hackathons to sponsor is hard: tier names mean nothing across events, prospectuses hide the clauses that matter, and badge-scan counts make bad sponsorships look successful. This Skill turns event sponsorship into a decision process with a single objective, a qualified portfolio, a negotiated package, and a pre-set threshold that proves whether the money worked. ## Core Features & Use Cases - Portfolio and tier selection: Scores candidate events against one primary objective, compares portfolio shapes (ecosystem-anchored, flagship-led, farm-team, regional spread), and reads package line items instead of tier names. - Negotiation and activation design: Sequences negotiation asks by efficiency, refuses ethics failures like buying attendee lists or stage slots, and designs on-site activations (help-desk booth, workshop, prize track, side event) matched to staffing capacity. - ROI measurement and renewal verdicts: Builds a fully loaded cost model including staff time, sets a target cost per qualified conversation before signing, and produces renew, renegotiate, or drop verdicts after each event. - Use Case: A DevRel lead with €90,000 and three travelling engineers receives two or three candidate year portfolios with allocation splits and staffing costs, one recommended with the losers explained, plus per-event thresholds before any contract is signed. ## Quick Start Ask the skill to build a sponsorship plan for your developer event budget, naming your objective, budget, and staffing ceiling.
