Skip to content

samber/dev-event-organizer-skills / skills/event-growth-strategy

event-growth-strategy

Verified

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.

FileKindSize
SKILL.mdskill md21.6 KB
evals/evals.jsonconfig27.5 KB
references/growth-case-studies.mdmarkdown10.1 KB
references/venue-and-money-mechanics.mdmarkdown5.3 KB

references/venue-and-money-mechanics.md

View on GitHub
# Venue and money mechanics

The financial risk layer under every growth decision, the demand-headroom heuristic and the cases behind it, the three pricing-evolution mechanisms, and the two warning patterns that fire before the money does.

## Venue contract risk mechanics

- Deposits typically run 25-50% at signing, balance due 14-30 days out.
- Hotel room-block **attrition penalties** and **food-and-beverage minimums** are the core exposure: the organizer owes the shortfall even when attendance lands below the committed block or minimum. An over-built edition can lose money at an attendance number that looks respectable.
- Lead time: conferences of 300+ attendees are typically booked 9-18 months ahead. A venue step-up decision therefore has to be made a year or more before the bigger edition runs - long before that edition's own demand is visible.
- Post-pandemic tightening: venues have become "frequently unwilling" to renegotiate minimums - the older case studies operated in a more forgiving contract environment than today's.
- Downside caps to negotiate when a step-up is promoted:
  - The smallest deposit and shortest attrition/minimum commitments available.
  - Venues run by nonprofits or with flexible room blocks.
  - Capacity sized to the proven number plus a modest buffer, never the aspirational one.

## The demand-headroom heuristic

Across every documented step-up case, organizers did not grow into projected demand. They waited for demand to visibly exceed supply, then took one discrete step. The observed signals:

- Sellout speed (sub-hour sellouts).
- Real-time in-event overflow (twice-renegotiated room layouts).
- Waitlists.
- Unsolicited sponsor inbound.

The skill's gate applies a composite threshold, a starting heuristic and not a published industry standard. It requires all of the following, repeated across editions:

- Sellout well under an hour.
- A waitlist around 30-50% of capacity.
- Unsolicited sponsor interest.

No "sell out in X weeks or don't grow" rule exists in the literature. The event's own history (via `samber/dev-event-organizer-skills@event-market-fit`'s pace instruments) beats it as soon as two editions of data exist.

The repetition requirement is the load-bearing part: one viral year misleads, and sellout speed itself is manufacturable through batch releases - check for batching before believing it.

## Pricing evolution across editions - three complementary mechanisms

Decide the posture before scaling, publicly, so growth doesn't quietly price out the base that built the event. The three mechanisms combine, and the strongest cases run at least two:

1. **Early-bird laddering** - dated tiers (Early / Standard / Late) or volume-gated tiers ("the first 800 tickets"), with group discounts confined to the standard tier. It manages the sales curve, but does not by itself protect accessibility.
2. **Supporter tier cross-subsidy** - a premium tier "priced at a premium to help fund" scholarships and accessibility programs. Distinct from a VIP upsell: the surplus is spent on other attendees, and saying so is part of the tier's value.
3. **Public community-price commitment** - the recommended default: hold individual prices flat (or cut student prices) across venue step-ups, funded by sponsorship cross-subsidy. One event held prices stable through five years of larger, costlier venues while cutting student tickets 40%. Note the dependency this creates: the commitment is only as durable as the sponsor base funding it, exactly why the sponsor-concentration watch below matters more once this posture is public.

Pricing can also move deliberately _down_ when shrinking: a case where organizers halved the pass price by shortening the program, framed as "a fair compromise." Shrinking is a pricing event too - plan it, don't let the old price ride on a smaller product.

## Warning patterns that fire before the money does

**Sponsor concentration** - sponsorship is usually the revenue majority for independent developer events, and tickets are "almost always priced at less than the actual cost." Sponsors budget a year ahead, so a single sponsor's withdrawal hits a growth budget with no time to replace the revenue before the edition runs. One event lost the sponsorship that had funded a fifth of its passes while attendee enthusiasm stayed high.

The threshold ("no single sponsor above X% of revenue") is self-set: declare it before the growth push. Treat crossing it as a reversal benchmark even mid-success.

**Organizer burnout as a leading indicator** - in two independent cases, the organizing team's own stress preceded any financial or operational trigger. One shrank a doubled event after administering it felt "actively unpleasant," and one wound down after organizer life changes.

A small team hits its human ceiling before its financial one. Treat a bandwidth or "no longer fun" report as a legitimate, named input to the hold/shrink decision, not a soft complaint to override with green demand numbers.

**Market-wide contraction context** - as of a 2023 industry write-up, the average independent in-person event still ran 30-40% below pre-pandemic attendance (virtual down a similar amount from its peaks). Read a single event's plateau against this baseline before diagnosing a demand ceiling: market context is not a per-event failure signal, and growth-rate expectations calibrated on pre-2020 cases need tempering.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 323kUpdated Claude CodeCodexVerifiedInstall