π° Budget & break-even
Plan what the event costs, watch real revenue land against it, and see how many tickets you need.
π° Budget plans what the event costs, and then keeps itself honest β real ticket and sponsorship revenue lands in it automatically, so the same page answers "what did we think?" and "where are we actually?"
π The tiles
| Revenue (actual) | Real money in β from paid orders and paid sponsor invoices. |
|---|---|
| Expenses est / committed / actual | Your three expense columns side by side, so you can see how much of the plan is still a guess. |
| Projected expenses | The number to plan against: each line's actual where it's been billed, else what you've committed to, else your estimate β added up line by line. So entering one real invoice doesn't change your total cost picture, it just makes one line of it certain. |
| Net P&L | Revenue minus projected expenses. Green when positive, red when not. |
| Cost per attendee | Projected expenses divided by valid tickets. |
| Break-even | 340 tickets (212 sold) β how many you need, and where you are, with a β once you're past it. |
π§Ύ Categories and lines
The budget is grouped into categories (Venue, AV, Catering, Marketing, Speakers, Revenue) and each category holds lines. Adding a line takes a Category (the placeholder suggests Venue, AVβ¦), an Item, a Vendor, a quantity and a $ unit cost β naming a category that doesn't exist yet creates it.
Each line carries three money columns, and the distinction is the whole point:
| Column | Meaning |
|---|---|
| Estimated | What you think it will cost. Fill this in while planning. |
| Committed | What you're contractually on the hook for β a signed venue contract, a confirmed catering order. Your real exposure, even before an invoice arrives. |
| Actual | What you've genuinely been billed or paid. |
Lines show a variance once an actual exists, so overruns surface as you enter invoices rather than at the end.
For every total the page derives β projected expenses, Net P&L, cost per attendee and break-even β each line contributes its actual if it has one, otherwise its committed, otherwise its estimate. A line never counts twice, and a line you haven't been billed for yet never counts as zero.
βοΈ Fixed versus variable
Every line is fixed by default, or variable if you mark it so. Fixed costs don't move with headcount (venue hire, AV, a speaker fee); variable ones are per-person (lunch, badges, tote bags).
β¨ The AI budget drafter
Rather than typing thirty lines, describe the event β "250 in-person, hotel venue, 2 tracks, catered lunchesβ¦" β and let it draft a budget. Each proposed line comes with a quantity, a unit cost, a fixed/variable classification and a short rationale for why it's there.
- Describe the event's shape: headcount, venue type, format, what's included.
- Read the draft β particularly the fixed/variable flags and anything that looks like a placeholder price. It knows event budgets in general, not your venue's quote.
- Apply it, then correct the numbers as real quotes come in.
π Automatic system lines
Some lines are maintained by the platform and marked with a π β they aren't editable by hand, because they mirror what actually happened:
| Line | Kept in step with |
|---|---|
| Ticket sales (auto) | Revenue category. Actual = the total of all paid orders. Updates as tickets sell. ποΈ Ticketing β |
| Sponsorships (auto) | Revenue category. Actual = paid sponsor invoices, so it moves when you mark an invoice paid. π’ Exhibitors β |
| Speaker fees | Speakers category. Estimated and committed = every fee entered; actual = the fees you've marked paid. πΈ Mark paid on a fee is what moves it from committed to actual, the same as on a travel claim. |
| Speaker travel | Speakers category. Committed = approved plus paid claims; actual = paid claims. So πΈ Mark paid on a claim is what moves it from committed to actual. π€ Speakers β |
β©οΈ What refunds do to the budget
Refunded orders leave paid status, so the Ticket sales (auto) line falls the next time it's recalculated. Break-even and cost-per-attendee shift with it, since both count valid tickets.
π― Using break-even well
- Get it right before you set prices. Enter fixed and variable costs, read the break-even number, and sanity-check it against the audience you can realistically reach. If break-even needs more people than the room holds, the price is wrong.
- Watch it as early-bird pricing rolls over. Break-even uses the average ticket actually sold, so the number moves as your mix changes.
- Use it to decide on extras. "We're 40 tickets past break-even" is a much better basis for approving the reception than a feeling.
- Reconcile afterwards. Enter the final invoices as actuals, then keep the event as the reference for next year's draft.