Software Development
Event Growth Strategy
Grow an established technical event edition over edition, or decide not to - the demand-headroom read, one discrete lever per edition (venue squeeze, track or day addition, venue step-up, price-led growth), the contract-risk gate on venue moves (deposits, attrition penalties, F&B minimums, long lead times), the pricing posture before scaling, and deliberate non-growth (caps, lotteries, shrinking back down) as a real strategy. Use whenever asked whether a conference or hackathon should grow, how to scale capacity, whether to add a track, a day or a venue, or how to stay small under excess demand. Do NOT use for a first launch - use samber/dev-event-organizer-skills@event-first-edition - or multi-event portfolios - use samber/dev-event-organizer-skills@event-portfolio-strategy.
- Publisher / source
- samber/dev-event-organizer-skills (found on skills.sh)
- Upstream record
- samber/dev-event-organizer-skills
- Version
- Version 3
- Published
- Publication review
- Approved for publication
- Content fingerprint
d97dff9e8902ccb4e3aa93bd738f7895ddc72825be226afc6cec4e7f7e9d69f0