# Ticket Ladder

> Set attendee ticket prices for a technical event from its budget, then write the refund and transfer policy before
> the first ticket sells. Enter total expenses, sponsorship, other income, the room's capacity, committed comps and who
> pays for a ticket (an employer, the attendee, an institution). The page works out the target, paid seats, the
> posture, a persona ladder, the gate, the access rungs, the group and invoice rules and a full-house projection.
> A metered run writes the ticket plan or the refund policy in publishable words. Built on the SkillSafe skill
> @samber/event-ticket-pricing (samber/dev-event-organizer-skills, MIT). Not legal or tax advice.

https://ticket-ladder.skillsafe.ai/

## What is free
- The target: total expenses minus sponsorship and other income; paid capacity: the room minus counted comps (sponsor allotments, speakers, organizers, volunteers) - no percentage rule for comps.
- The posture: free by design (deletes the ladder), nominal fee (10-20% of a commercial ticket nearby), community price, or commercial price for a vendor-run event.
- The persona ladder split by who pays - Corporate, Individual, Student - with prices you enter or proposed at the published ratios (EuroPython 2026 for community pricing, PyCon US 2026 for commercial), sized to break even at 85% sold (self-set); the top-to-floor ratio against the published 1.7:1 to 6.5:1 range.
- The gate: an early price until a date, a late surcharge after a date, or the first N tickets; a group discount kept off early and late prices; the invoice rail at full price, deleted when no entity can invoice; scholarship, student and supporter rungs.
- A projection of what the ladder raises at a full house against the target, the break-even share, and the nine refund and transfer decisions with what is still open.
- Ladder CSV, Markdown and JSON exports, plus a ticket-types CSV (one row per ticket type with price, quantity and sale window, comps and scholarships as hidden types) to set up your ticketing platform.
- "Save as a new copy" keeps last edition's saved ladder unchanged when you plan the next one.

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (plan or policy), `event`, `ladder` (the page's arithmetic) and `facts` (the page's picks, the refund checklist and every finding).
- `plan` replies with `summary`, `target`, `capacity`, `posture`, `ladder`, `gate`, `access`, `bulk`, `projection`, `metrics` and `caveats`; the page holds the posture, target, paid seats, every price and gate price and the gate to its own, and refuses an invoice rail called a discount or a number not in the input.
- `policy` replies with `policy` (publishable text), `decisions` (the nine items in order), `open` and `note`; the page refuses filled-in undecided items, relative windows, a fee other than the one decided and an invented credit.

## Links
- API tutorial: https://ticket-ladder.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/event-ticket-pricing