event-growth-strategy

Decides whether an established technical event grows, holds, or shrinks through one discrete lever per edition.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Organizers of established conferences and hackathons face recurring pressure to grow without knowing whether demand truly supports it, which lever to pull, or how much venue-contract risk to accept. This Skill turns that decision into a gated, evidence-based process instead of a guess driven by one viral sellout or an anchor sponsor's check. ## Core Features & Use Cases - Demand-headroom gate: Requires repeated sub-hour sellouts, a 30-50% waitlist, and unsolicited sponsor inbound across editions before any growth lever is chosen, and checks sellout speed for batch-release manufacturing. - One-lever growth menu: Ranks venue squeeze, price-led growth, track addition, day addition, and venue step-up by effort, value, efficiency, and compliance cost, with the single-edition multi-rung leap deleted outright. - Deliberate non-growth menu: Treats caps, group-purchase bans, application-plus-lottery allocation, and deliberate shrink as real strategies, including burnout as a named reversal benchmark. - Financial risk gate: Surfaces deposits of 25-50%, attrition and F&B minimum penalties, and 9-18 month venue lead times before any venue-touching commitment. - Use Case: A 400-person conference sells out in 25 minutes with a 170-person waitlist and is offered a 900-seat hall at 40% deposit. The Skill rejects the jump because the fast sellout has not repeated across editions, recommends a venue squeeze instead, and installs a four-signal warning watch. ## Quick Start Ask the Skill whether your established conference should grow next edition, for example: our 300-person event sold out in 20 minutes with a 200-person waitlist, should we sign the 600-seat venue?

Frequently Asked Questions about event-growth-strategy

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

FAQPage Schema
How do I decide if my conference should grow next year?

Check whether demand signals repeat across editions: sellouts well under an hour, a waitlist around 30-50% of capacity, and unsolicited sponsor inbound. One fast sellout is not enough evidence, and the Skill routes you to exactly one growth lever rather than several at once.

Should my conference add a second track or move to a bigger venue?

Start with the cheapest rung: squeeze more capacity from the current venue via layout changes, bounded by fire-code limits. Track addition comes next with the hallway-track dilution trade-off, and a venue step-up only after cheaper rungs are exhausted and demand has repeated.

What are the financial risks of signing a bigger venue?

Venue contracts typically require 25-50% deposits at signing, plus attrition and food-and-beverage minimum penalties owed even if attendance falls short. Events of 300+ attendees book 9-18 months ahead, so you commit long before that edition's demand is visible.

Can staying small be a real strategy for a sold-out event?

Yes. Deliberate non-growth is a documented strategy with allocation mechanisms: hold the cap with a waitlist, ban group purchases, run an application plus lottery, or deliberately shrink. Documented events capped on purpose to protect intimacy and room composition.

When should an event shrink instead of grow?

Shrink when a reversal benchmark fires: sellout speed slowing year over year, rising no-show rates, a single sponsor exceeding your declared revenue-share threshold, or organizers reporting the work has become actively unpleasant. Burnout is treated as a leading indicator, not a mood to push through.

Does this Skill work for a first-time conference launch?

No. It explicitly excludes first launches and routes them to the event-first-edition skill, since its growth gate requires demand evidence repeated across at least two editions. Multi-event portfolio questions route to event-portfolio-strategy instead.