event-ticket-pricing

Designs attendee ticket price ladders, access tiers, and refund policies for technical events.

1|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-ticket-pricing-samber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-ticket-pricing
Source: https://github.com/samber/dev-event-organizer-skills/tree/main/skills/event-ticket-pricing
Command: npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-ticket-pricing-samber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about event-ticket-pricing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set ticket prices for a tech conference?

Start from the budget's ticket revenue target, subtract committed comps from capacity, then pick a posture (free, nominal, community, or commercial) and build a persona ladder by payer type. Transpose ratios from comparable published ladders rather than copying absolute prices.

Should my community conference be free or charge a fee?

A nominal fee of roughly 10-20% of a commercial regional conference ticket converts unpaid RSVPs into committed headcount for catering and venue decisions. Charging anything pulls in accounting and tax obligations, so free-by-design remains a legitimate posture when sponsorship covers the budget.

How many ticket tiers should a conference have?

Keep public price points to at most two per persona on the time axis. A third phase works only as a late surcharge, never as a third discount step, since extra discount steps read as pressure tactics and train buyers to wait.

Can a group discount stack on an early-bird price?

No. Standard practice applies group discounts only to the standard tier, excluding early and late tiers, because stacking discounts the same seat twice. Publish the exclusion on the registration page before sales open.

Is there an industry standard refund policy for conferences?

No standard exists beyond a single dated cutoff, which all four sourced events share. The refund fee, hardship waiver, and transfer rules differ across every example, so the organizer must decide each term explicitly and publish it beside the price.

How do I offer free tickets to people who cannot afford them?

Use a need-gated application route reviewed by a named human rather than a public discount code or a cheap published tier. Write the reviewer, response time, window, and award before publishing the route, since an unanswered application is worse than no route.