PyMunich

shown, and actual

Where the Money Comes From

Costs are committed months ahead. Revenue is not, and the difference between the two timelines is where community conferences fail. For a commercial example of related workforce measurement, see how Microsoft Teams tracks activity from Monitask.

One community's experience at roughly 300 attendees. Numbers vary enormously by scale, country and venue arrangement. For broader conference and speaking context, MPI is another useful reference.

The three lines

Tickets. The largest line for most community events, and the most predictable in size — you can model it from last year. Badly timed: sales are weighted heavily toward the final weeks, and the early-bird period exists partly to move some of that money earlier.

Sponsorship. The line that decides whether the event is comfortable or desperate. Predictable in nothing: commitment timing, payment timing and amount all vary, and a sponsor who confirmed in January may pay in November.

Grants and community funds. Language foundations, local government, university support. Smaller, slower, and frequently earmarked for specific purposes such as travel grants or accessibility.

And in-kind support, which is not revenue and behaves like it: a free venue, donated AV, a sponsor covering catering directly. The most valuable form of support and the one that never appears in a budget, which means its loss is invisible until it happens.

The timing problem, concretely

Venue deposit: six to nine months ahead.

AV contract: signed months ahead, payable near the event.

Catering minimum: committed weeks ahead on an attendance estimate.

Ticket revenue: mostly the final six weeks.

Sponsorship payment: on the sponsor's terms, frequently thirty to sixty days after invoice, and the invoice frequently goes out after the event.

So there is a window — roughly from the venue deposit to the ticket surge — where the organisation has committed most of its costs and holds a fraction of its revenue. For a volunteer group with no reserves, that window is the actual risk, and it does not appear in a budget that shows annual totals.

What reduces the exposure

Early-bird pricing with a real deadline. Moves ticket revenue earlier, which is its main purpose. The discount is the price of the timing.

Sponsorship invoiced on signature, not after the event. Ask. Many companies pay on receipt and simply were not invoiced early.

Deposits negotiated down, or split. Venues that want the booking will sometimes restructure.

A reserve carried between years. The single most effective measure and the hardest to build, because a volunteer organisation with money in the bank is under constant pressure to spend it on the current event.

And in-kind support secured early, because it is the cheapest cost reduction available and it takes the longest to arrange.

The question to answer before committing

On the worst day, how much has been spent and how much has arrived?

One number, plotted across the year. Not a budget — a cash timeline. Most organising teams have never drawn it, and drawing it takes an hour.

If the worst day is negative and nobody has agreed to cover it, that is the finding. It is also, in our case, what 2020 exposed: the costs were committed, the tickets were sold, and refunding was correct and expensive.

Who is liable

The part to settle before signing anything.

An informal group is frequently not a legal entity, which in many jurisdictions means individual organisers are personally liable for contracts.

A registered association changes that and costs paperwork.

Either is fine as a decision. What is not fine is discovering the answer after a cancellation, which is when it becomes an urgent question about somebody's personal finances.

The short version