# Sponsor Why

> An honest value story for one sponsor segment, with proof under every claim. Pick one sponsor segment, enter what
> that prospect told you it needs, the audience evidence and track record you hold and what the event will not offer,
> and get the honesty gate written first, the lead value category, every claimed category checked against an activity
> in the program, the six-part jobs-to-be-done statement with a proof point under every claim - then the value story
> for the prospectus and the discovery questions for the next call. Built on the SkillSafe skill
> @samber/event-sponsor-value-proposition, from samber/dev-event-organizer-skills (MIT), by Samuel Berthe.
> One segment at a time; the honesty gate before the offer; pipeline only at vendor-run events. It never invents an
> audience number, a return rate, a sponsor quote, a lead count or an outcome, flags a first edition and uses the
> skill's substitutes, and labels its own numbers self-set. Packaging and prices belong to the prospectus and pricing.

https://sponsor-why.skillsafe.ai/

## What is free
- The pole's consequences: at a community-run event no attendee contact list, no purchasable slot, lead capture only when an attendee volunteers it, and pipeline deleted, not demoted; at a vendor-run event pipeline and consented lead retrieval, bounded by consent.
- One segment fixed (product-feedback, recruiting, brand, community-member, or the page's pipeline buyer at the vendor pole), with a blended Who flagged.
- Discovery: the prospect's need recorded in its own words and mapped onto a category; a guess from job ads is flagged as not discovery.
- The honesty gate: what the event will not offer, written before any claim, and every claim that contradicts it or the pole flagged.
- The value-category lead menu re-ranked for the interview (revenue deadline, one-off or compounding, hiring pressure), every move named and every deleted rung struck, with the co-lead picked by discovery.
- Offer-activity coherence: an activity in the program for every claimed category.
- The six-part JTBD statement (Who, Why, What Before, How, What After, Alternatives) checked part by part; a proof point under every How claim, labelled evidenced or aspirational, with first-edition substitutes; the post-draft value-equation check; buying-influence diligence.
- A verdict: run discovery first, write the honesty gate first, fix first, ready for the prospectus.
- Exports: the six-part statement (.md), the proof-point inventory (.csv), the coherence table (.csv), everything (.json).

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (case or story), `event`, `evidence`, `program`, `notes` (may be empty) and `facts`.
- `case` replies with `summary`, `verdict`, `segment`, `will_not_offer`, `lead`, `coherence`, `jtbd`, `value_check`, `gaps` and `caveats`; the page holds every gate item, category, claim and proof to its own.
- `story` replies with the prospectus copy for the one segment - `headline`, `opener`, `what_you_get`, `what_we_do_not_offer`, `audience`, `track_record`, `next_step` - plus `discovery_questions` for the next call and a `note`.

## Links
- API tutorial: https://sponsor-why.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/event-sponsor-value-proposition
- Pricing the tiers: https://sponsor-ladder.skillsafe.ai/