What problem does it solve? Setting ticket prices for a conference or hackathon involves interlocking decisions - free versus paid, persona tiers, early-bird gates, scholarships, group discounts, and refund terms - and getting any one wrong costs revenue, attendance, or credibility. This Skill turns those decisions into a structured, defensible ticket structure grounded in real published conference ladders. ## Core Features & Use Cases - Posture and ladder design: Decide between free, nominal, community, or commercial pricing, then build a persona ladder (corporate, individual, student) using transposed ratios from sourced events like PyCon US and EuroPython rather than copied amounts. - Access and bulk mechanics: Configure date- or volume-gated early-bird steps, need-gated scholarship routes with application mechanics, group discounts with stacking exclusions, and pay-by-invoice rails for corporate buyers. - Refund and transfer policy: Write a publishable refund, transfer, and hardship policy before tickets go on sale, using four real conference policies as worked examples plus a decision checklist. - Use Case: A 300-person community DevOps conference moving from free to paid gets a nominal-fee recommendation, paid capacity computed after subtracting sponsor and speaker comps, and a complete publishable price structure validated section by section. ## Quick Start Ask the assistant to design the ticket price ladder for your technical conference, including tiers, early-bird gates, and a refund policy.