samber/dev-event-organizer-skills / skills/event-budget
event-budget
VerifiedBuild the budget and P&L for a technical event - every cost line split into fixed and per-head, the revenue mix against the funding model, a Good/Better/Best scope-tier ladder so break-even has three answers instead of one, a contingency sized as a stacked floor, pad and downgrade ladder whose cuts also price lost sponsor reach, a cross-edition reserve policy, annual funding decoupled from single events, and outflows scheduled against the dates sponsor and ticket money actually lands. Use whenever asked to build an event budget, model conference or hackathon costs, find break-even, size a contingency reserve, set a reserve or surplus policy across editions, fund a recurring meetup series annually, plan event cash flow, or decide what to cut when revenue falls short. Consumes prices and real vendor quotes, never sets them. Do NOT use to set ticket or sponsor prices - use samber/dev-event-organizer-skills@event-ticket-pricing or samber/dev-event-organizer-skills@event-sponsor-pricing.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 33.6 KB |
| evals/evals.json | config | 37.0 KB |
| references/budget-failure-case-studies.md | markdown | 6.4 KB |
| references/cash-flow-fiscal-hosting-and-tax.md | markdown | 11.8 KB |
| references/cost-taxonomies-and-sourced-benchmarks.md | markdown | 13.5 KB |
references/budget-failure-case-studies.md
View on GitHub# Budget failure case studies, read for their financial mechanism
Contents: how to use this set · five published cases · one anonymized case · what each one changes in the model · what this set does not prove.
## How to use this set
Each case below is read for the **financial mechanism** that ended or nearly ended the event, not for its headline cause. Two of them are usually told as demand stories and one as a burnout story; those tellings are accurate and are not the reason they are here. Cite the mechanism, and say which part of the cause it was.
None of these is a controlled comparison. They are five ways a budget has actually failed, useful for pressure-testing a model against known shapes of failure - not evidence about how often any of them happens.
## Comdex - cancelled 2004
Three large hardware vendors stopped leasing exhibit space, cutting off the organizer's revenue base. That forced the then-owner into bankruptcy, after a broader sector downturn had already reduced attendance and exhibitor counts.
**Mechanism: sponsor and exhibitor revenue withdrawal cascading into organizer insolvency** - not an attendance decline on its own. The revenue concentration is the point: a small number of large exhibitors were load-bearing, and their simultaneous exit was not absorbable.
**What it changes in the model:** revenue concentration is a budget risk, not only a sales risk. If the sponsorship target depends on a handful of names, the model should say what happens when the largest two do not renew - which is a question the tier ladder answers and a single budget does not.
## XOXO Festival - cancelled 2020
The small independent team knew that once money had been taken from sponsors and attendees, they could not financially recover if forced to cancel closer to the date. They cancelled early rather than carry that exposure.
**Mechanism: cash-flow risk from non-refundable pre-commitments, acted on pre-emptively.** This is a decision, not a realized deficit - no money was lost, which is exactly what makes it instructive.
**What it changes in the model:** the timing of irreversibility matters more than the size of the eventual deficit. This is the clearest illustration of why the outflow menu's compliance-cost axis is expressed as reversibility rather than as an amount.
## Vancouver Folk Music Festival - 2023
The organizing society stated that producing the 2023 event would require an extra 500,000 USD, which it judged "not realistic or sustainable" given cash flow. The cited driver was vendors now requiring up-front payment that the festival's cash-flow structure could not absorb.
**Mechanism: cost inflation arriving as a change in vendor payment terms, outrunning the organization's cash-flow model.** The total cost rose, but what actually broke was _when_ the money had to be available.
**What it changes in the model:** a supplier moving from net terms to payment up front changes nothing on the profit-and-loss line and everything at the lowest cash point. Re-read the trough whenever a payment term changes, not only when a price changes. (Not a technical conference - kept because the mechanism is format-independent and unusually clearly stated.)
## Strange Loop - final edition 2023
The stated reason for ending was organizer exhaustion rather than any lack of success, compounded by the financial risk of venues requiring bookings three years in advance.
**Mechanism: multi-year venue-booking financial exposure**, layered on top of burnout rather than replacing it. Cite the mechanism and name the compound cause honestly; presenting this as a pure budget failure misdescribes it.
**What it changes in the model:** the booking lead time for a large venue (9-18 months generally, and longer at the top end as here) means one edition's model routinely commits money on behalf of editions nobody has decided to run yet. Name that commitment as an obligation of the current edition, since that is where it will be paid from.
## OSCON - discontinued 2020
The publisher's president stated the company could not plan for or execute a business permanently changed by an unpredictable pandemic timeline.
**Mechanism: demand collapse resolved as a corporate portfolio decision**, not a single event's budget failure. Included as the honest counter-example: not every ended event ended for a budget reason, and a budget model should not claim credit for surviving a decision made at portfolio level.
## Anonymized case - scope cut, sponsors out
Event, organizer, place and figures withheld; read it as one reported shape, not a published case.
A large multi-day community event signed a big venue before ticket sales were known. Months before the date, sales sat well behind plan, so the organizers cut the budget drastically. Sponsors then withdrew, because the event they had bought into no longer reached the audience they had priced. Only digital visibility kept selling.
**Mechanism: a scope cut that also cut revenue.** The downgrade was modelled as a cost saving only, while sponsorship moved with reach, so the saving and the lost sponsorship partly cancelled.
**What it changes in the model:** price every downgrade rung net of the sponsor revenue it forfeits, and keep a staff-free digital visibility surface that survives a downgrade. It is also a second instance of the over-built venue shape below: the commitment was made before demand was proven.
## The over-built venue, as the recurring shape
Across these venue cases, the single largest financial risk named directly is over-building capacity relative to proven demand and then carrying deposit and attrition exposure on it. One organizer described the 1,500-capacity space he had committed to as "an amazing (but very expensive) venue" while the edition was still running.
That is the shape most of these cases share: the money was committed against a headcount that had not yet been proven, on a date chosen by the counterparty rather than the organizer.
## What this set does not prove
- It says nothing about **frequency**. Five published cases and one reported one are the ones that were written up or told, and events that quietly absorbed a shortfall published nothing.
- It contains **no counterfactual**. No case here shows an event that held a larger contingency and survived a comparable shock, so it cannot be used to argue for any particular reserve size.
- It is **not the only reading** of these events. Comdex and XOXO are just as correctly told as demand failures; the financial mechanism is one layer of the cause, never the whole of 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 |