samber/dev-event-organizer-skills / skills/event-growth-strategy
event-growth-strategy
VerifiedGrow 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 21.6 KB |
| evals/evals.json | config | 27.5 KB |
| references/growth-case-studies.md | markdown | 10.1 KB |
| references/venue-and-money-mechanics.md | markdown | 5.3 KB |
references/growth-case-studies.md
View on GitHub# Growth case studies
The case record behind the skill's levers, caps, and failure modes. Every figure below comes from organizer statements, event sites, or contemporary press unless flagged otherwise. Three figures are contested between credible sources - report those as ranges, never pick one silently (see the last section).
## GopherCon - venue step-up triggered by visible over-demand, then a track and a day
- 2014 debut (Denver, Marriott): the team "had to change our room layout twice and negotiate with the Marriott twice to get bigger space because we had more demand for tickets than we had space for people" (Gopher Academy blog, 2016). The step-up trigger arrived as real-time, in-event overflow, not a projection.
- 2015: moved to the Colorado Convention Center, "effectively doubling our capacity" - one discrete step, not incremental growth.
- 2016: added two parallel afternoon tutorial tracks, pre-empting the fragmentation critique in the CFP announcement itself: "Everything will be recorded and available after the conference, so while it's impossible to be in three places at once, you won't miss out." This was the named mitigation for hallway-track dilution.
- 2019 (San Diego, 1,800+): deliberately chose a single venue "offering both rooming and programming under one roof" specifically "to maintain the tight sense of community" - a counter-example to "bigger requires a sprawling campus." Also added a fourth day (Community Day).
- 2024 (Chicago): "over 800 attendees" - a material drop from the ~1,800 peak. Flag: the figure comes from a sponsor recap, not an organizer post-mortem. Treat it as indicative, and read it against the market-wide post-pandemic contraction, not as a growth mistake.
- Pricing ladder: Early / Standard / Late tiers, group discounts (5% for 5-9, 10% for 10+) on standard tickets only.
## Rails World - capacity doubling plus track addition in one edition, then the squeeze
- 2023 (Amsterdam): single-stream, sold out "in less than 45 minutes" (DHH). Attendance is a contested figure - see the last section.
- 2024 (Toronto): "more than 1,000 Rails developers from 57 countries," two days, two tracks. DHH: "we are going to nearly double the capacity for attendance." Venue, sponsorships, and CFP were announced ~9 months ahead, the practical lead-time floor in action - compressing GopherCon's two-edition pattern (venue move, then tracks) into one edition.
- 2025: rather than sign a third, larger venue, returned to the Amsterdam venue. DHH: "The venue we returned to was already at capacity the first time around, but Amanda managed to fit a third more attendees by literally using slimmer chairs!" - the clearest documented venue-squeeze case, and the skill's default rung.
## RailsConf - a governance ending, not a growth failure
- Grew to six tracks over three days by 2014-15 ("Three days and six tracks, that was huge!" - Evil Martians recap). It ran a premium "Supporter Ticket" tier explicitly funding its Scholars and Guides accessibility programs.
- The 2022 rupture (DHH's "No RailsConf" post after losing the standing opening keynote) and the 2025 final edition were governance and politics, in the organizers' own accounts. The Rails Foundation launched Rails World as successor, and DHH framed it as "the baton has been passed."
- Flag: never cite RailsConf's ending as a grew-too-big case. It is the skill's canonical example of a governance ending misread as a growth failure.
## FOSDEM - track-based free scaling, the third posture
- Free, no registration, all-volunteer (LWN.net 2025: "None of the organizers are paid"). Visitors grew from ~4,000 (2011) to 8,000+ (since 2017). The 2025 edition ran "over 1,100 events and 79 tracks."
- Scales almost entirely by adding devrooms/tracks - never by capping attendance. Room-level control instead: "If there is risk of overcrowding, place somebody at the door and use the full signs" (Devroom Managers Manual).
- The documented cost: recurring attendee reports of queues and "overcrowded rooms often impossible to enter." No free-entry model escapes overcrowding. It relocates the capacity problem from the gate to each room.
- Portability warning: this lever ordering only works because there is no ticket revenue and no per-head financial risk - it does not transfer to a ticketed conference where the venue contract and per-head math are load-bearing.
## PyCon US - the accessible-pricing scaling commitment
- Organizers' own words (2016): "we have kept our Individual and Corporate prices stable as the conference has moved into larger and more expensive venues, but we have slashed our Student ticket prices by more than 40% over five years!"
- Mechanism:
- Sponsorship cross-subsidizes registration.
- A needs-based financial aid program (average grant ~$700 in 2017).
- Early-bird gated by volume ("the first 800 tickets"), not date.
- Scaled to ~2,400-3,000 total attendees across a dozen venue moves with a foundation staff of 8 - the strongest documented counter-example to "scaling forces price increases," and the reason a public community-price commitment is this skill's recommended default posture.
## XOXO - grew, tried double, deliberately shrank
- Passes sold, year over year:
- 2012: 400 passes, sold out in ~50 hours.
- 2013: ~700, with an application process filtering commercial intent.
- 2015: capped ~1,000.
- 2018: ~2,300, the deliberately large "experiment" ("double the size" - organizer Andy Baio).
- 2019: reversed. Organizer McMillan named three reasons (Fast Company):
- The giant venue "felt isolated."
- "2,300 people is too many for a festival billing itself as a place for creatives to forge meaningful relationships."
- Administering it felt "actively unpleasant."
They accepted "roughly a 50% reduction in our production budget" as the price. Baio on the smaller edition: "It was the most relaxed and most fun I've had in seven years running the event."
- Allocation: application + lottery, explicitly "to counter" the bias where "a first-come, first-serve system typically favors those with time and money," prioritizing underrepresented attendees.
- The 2024 finale: cap at 1,000, pass price cut from $500 to $250 by shortening the program, after the sponsorship that had funded ~20% free passes receded - "The tech companies... stopped spending money on independent events like XOXO" (OPB). Sponsor concentration ended the event while attendee signals stayed warm.
## Monktoberfest - cap for damage control, kept for quality
- First edition (2011) capped at 100 "as damage control… a small disaster would be preferable to a large one" (organizer Stephen O'Grady). Today ~150: he "could sell twice as many tickets as he does" but keeps it small for intimacy - the same cap, reframed from risk hedge to quality choice.
- Group-purchase ban as allocation: "It made it much less likely that large groups of attendees… would form cliques."
- A category of constraint worth naming: some signature elements are physically unscalable (the brewery "just don't brew enough" of the event's signature beer for 300-400) - an argument for a cap independent of venue, money, or bandwidth.
## Brooklyn Beta - the single-edition leap, the deleted option
- Attendee counts by edition:
- 2010: ~150-200.
- 2011-12: ~300, sold out.
- 2013: the usual 300-person conference _plus_ a one-day ~1,300-person event in "an amazing (but very expensive) venue" (founder Chris Shiflett, flagging cost and strain in real time: "we had more hiccups than in previous years").
- Community verdict, documented: "I'm just not sure it scales well from 300 to 1300" and "the acoustics in the hangar-like space battled against the speakers" (Jeremy Keith) - a venue-fit failure at the leapt-to scale.
- The loop, in an organizer's words: "Being small is a big part of what made the conference so intimate and amazing, and being so intimate and amazing was what made the conference so popular… in 2013 they made the decision to break it wide open."
- Flag: the 2014 ending was a deliberate wind-down (the founding "fight" framed as won, plus organizer life changes) - nothing indicates insolvency or sponsor pullback. Cite this case for the format-leap-breaks-intimacy failure mode only, never as a financial collapse.
## GigaOm - the cash-flow cautionary tale, not an event-growth case
- A company-level insolvency (March 2015) with events as a major revenue line: it "didn't even have enough money to pay vendors helping to put on its Structure Data conference," cancelled nine days before doors.
- Flag: this is corporate overextension, not one event outgrowing itself. Use it only to illustrate that venue and vendor commitments turn a cash-flow failure into a nine-days-out cancellation - nothing else transfers.
## Web Summit - the outlier upper bound
- Dublin years under one founding team:
- 2010: ~400.
- 2012: 4,200.
- 2014: 22,000, the year of the notorious Wi-Fi failures.
- 2015: ~42,000, then relocation to Lisbon after exceeding any Irish venue, a compound trigger of national venue ceiling, infrastructure strain, and government-support disputes.
- Founder Paddy Cosgrave: "We tried with a small team in 2010 but had no idea we would have had 42,000 attendees come to Dublin in 2015."
- Flag: this ~100x-in-five-years rate rode a broad general-tech topic, and it is the record's upper bound, not a benchmark. The documented normal for niche developer conferences is roughly doubling per discrete step. The base year itself is contested - see below.
## Contested figures - always report the range
Three conflicts exist where credible sources disagree, with no reconciliation available. Never collapse them into one number.
- **XOXO 2019 size**: "capped at 750" (Wikipedia) vs. ~1,200 (Fast Company) for the same year. Cite as "roughly 750-1,200, sources disagree."
- **Rails World 2023 attendance**: "700+ Rails developers" (rubyonrails.org) vs. DHH's "700 tickets in less than 40 minutes" and, elsewhere, "the lucky 650 attendees." Possibly tickets-sold vs. show-ups, but unreconciled. Cite as "roughly 650-700+."
- **Web Summit's first year**: 2010 (~400 attendees) is the usual starting point, but some sources cite a ~150-person 2009 precursor. Any growth multiple ("~100x") shifts with the disputed base year - say so when citing it.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |