For event organizers, before tickets go on sale
Ticket LadderPrice your tickets from the budget - not from last year's guess.
Enter the budget, the sponsorship, the room, the comps and who pays. Free in your browser: what tickets must raise, paid seats after comps, whether to charge at all, a corporate / individual / student ladder at the ratios PyCon US and EuroPython publish, the early-bird or late-price gate, group and scholarship rules that never discount a seat twice, and whether the whole ladder reaches the target at a full house. A run writes the ticket plan, or your refund and transfer policy in words you can publish.
1 Your event free
The event and the budget
The room
Who pays (% of tickets)
The gate
Groups, invoices and access
Refunds and transfers - decide before the first ticket sells
2 The ladder, worked out free
What the page flags
The ladder
3 Plan or policy metered
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
Target and capacity
Posture
The ladder
The gate
Access
Groups and invoicing
Record
Caveats
The page's check of this reply
4 Saved ladders
How it works
The target comes from the budget: total expenses minus sponsorship and other income is what tickets must raise. Committed comps - sponsor allotments, speakers, organizers, volunteers - come off the room before anything is priced; there is no percentage rule for comps, so count them. Then the posture: free by design deletes the ladder; a nominal fee (10-20% of a commercial ticket nearby) spreads risk rather than funding; a community price covers what sponsorship does not; a commercial price belongs to a vendor-run event.
Prices split by who pays. Leave them blank and the page proposes a ladder at the published ratios - EuroPython 2026 for community pricing (about 1.7:1 business to personal, 2.2:1 personal to education), PyCon US 2026 for commercial (about 1.9:1 and 3.4:1) - sized to break even at 85% of seats sold, a self-set margin. Published top-to-floor ratios run about 1.7:1 to 6.5:1: transpose ratios, never amounts. The refund checklist is the nine decisions the four sourced policies (PyCon US, EuroPython, RustConf, KubeCon) answer differently; the only thing they share is a single dated cutoff.