Event & Scale OS

An open-source operating system for executing B2B events, built as Claude Code skills.

Run the whole thing from the command line: decide which events are worth doing, negotiate what you buy, build the room, fill it with the right people, run the day without surprises, and follow through fast enough that the pipeline is real. Executive dinners, conference sponsorships, your own flagship event, stages, and everything that has to happen at 7am on load-in day.

No app to host. No account. No database. Twenty-four skills plus plain text in a workspace/ folder on your machine.

---

Why this exists

Event content splits into two useless halves. One half is inspiration: photos of a beautiful dinner, a post about how "events are back." The other half is event-planner logistics with no commercial thinking in it at all. Neither one tells a B2B marketer whether to sign the sponsorship, what to ask before signing it, how many meetings to target, or what to do when the venue wants a certificate of insurance naming seven additional insureds two weeks out.

This repo is the operating detail in between. It comes from running enterprise dinners, a five-figure conference sponsorship, an owned event with a founder on stage, and the retrospectives afterward that said what went wrong.

Three beliefs run through every skill:

• The investment is in the machine that fills the room, not in the event. A well-run event with the wrong people in it is an expensive party. The audience machine gets more pages here than the event does.
• The pipeline is booked before anyone gets on a plane. Pre-booked meetings are the metric. Everything else at an event is list building, and it should be budgeted as list building.
• The follow-up is written before the event, not after. Every team that plans to write follow-up afterward sends it five days late, and five days late is the difference between a meeting and a polite reply.

---

The 24 skills

Program and selection

• event-program-setup – the portfolio charter: objective, budget split across formats, annual calendar, capacity
• event-selection – which events are worth doing, scored, with the arithmetic that says no
• sponsorship-negotiation – what to buy, what to refuse, and the questions to ask before you sign
• event-budget – full cost accounting, per-head math, stacked service charges, cost per qualified meeting

Filling the room

• audience-machine – the founder-independent target list, tiered and owned, built before invites go out
• invite-motion – waves, copy, channels, over-invite ratios, RSVP management, no-show mitigation
• meeting-engine – pre-booking the 1:1s, matchmaking platforms, calendar operations, staff capacity

Formats

• executive-dinner – 8 to 15 covers, venue to seating chart to the anchor voice, and the no-pitch doctrine
• roundtable-and-salon – practitioner roundtables, moderation, and the rules that make people talk
• conference-activation – sponsored conferences: booth against suite, stage, transferable seats, the hallway
• owned-event – your own flagship: co-hosts, venue, program design, and what it really costs
• virtual-events – webinars and virtual roundtables as the scalable tier, without the registration vanity

Stage and content

• speaking-and-stage – abstract submission, slot negotiation, speaker prep, and production constraints that kill decks
• event-content – the content machine built before the event: recap, social, photography brief, distribution

Operations

• venue-selection – criteria, all-in per-head comparison, private-room requirements, negotiation
• event-logistics – insurance certificates, shipping and receiving windows, load-in, AV, food and beverage minimums
• run-of-show – the hour-by-hour for every day of the event, with owners on every line
• staffing-and-briefing – who is responsible for which guests, the VIP track, and the night-before huddle

Follow-through

• event-followup – tiered follow-up, written before the event, sent inside 24 hours
• event-measurement – the scorecard, cost per qualified meeting, and reporting at 30, 60, and 90 days
• event-retrospective – the debrief that turns one event into a repeatable play

Quality

• writing-quality – the anti-slop gate every writing skill runs before output
• artifact-eval – scores invites, abstracts, and follow-ups against a rubric and revises to a pass

Operate

• event-and-scale-os – the front door: portfolio status, what is due this week, next best action

Full countdown map: docs/lifecycle.md.

---

Quickstart

1. Install the skills (see INSTALL.md).
2. Set up the portfolio. Run event-program-setup. It interviews you on objective, budget, formats, team, and capacity, then writes workspace/program/.
3. Decide before you commit. Run event-selection on any event you are considering. It produces the arithmetic and a go or no-go, and it is willing to say no.
4. Fill the room first. Run audience-machine before invite-motion. Building the list after the invite copy is how rooms end up full of the wrong people.
5. Then run the loop. event-and-scale-os reads the portfolio and tells you what is due, by event, by week.

---

The principles baked into every skill

• Say no early. Most of the money lost on events is lost at signature, not on the day. Several skills exist mainly to talk you out of something.
• The primary metric is qualified meetings. Not badge scans, not registrations, not impressions. Every format defines what qualified means before the event.
• Everything has an owner and a date. An unowned line in a run of show becomes a problem at 7am on load-in day.
• Ask before you sign. Matchmaking platform open dates, literal booth dimensions, deck merge rules, insurance requirements, expected attendance and title mix. All five of those change the plan and none of them are in the sales deck.
• No fabrication. Nothing invents an attendance number, a benchmark, a quote, or a guest. Unknowns stay marked as unknowns.
• Human in the loop. Nothing sends an invite, signs a contract, or books a venue. The skills draft, price, and recommend.
• Local and private. Invite lists, contracts, and guest notes live in workspace/ on your machine, gitignored by default.

---

The reference stack

Written against a specific stack so it runs on day one, with substitutions documented:

Layer	Reference	Common swaps
Invite and RSVP	Partiful or Splash	Luma, Eventbrite, RSVPify, a plain form
Target list building	Clay	Apollo, ZoomInfo, Sales Navigator, a spreadsheet
CRM	HubSpot or Salesforce	Pipedrive, Attio, a tracked sheet
Outreach	Salesloft or Outreach	Apollo, HubSpot Sequences, personal email for dinners
Meeting booking	The organizer's matchmaking app (Brella, Grip, Swapcard)	Chili Piper, Calendly, a shared calendar
Event tracker	A spreadsheet, per event	Notion, Airtable, Monday
Webinars	Zoom Webinars or Goldcast	Livestorm, Hopin, StreamYard
Badge and lead capture	The organizer's scanner	Popl, Vivenu, manual capture

Full detail, including the no-budget path for each layer: docs/stack.md.

---

Contributing

Issues and PRs welcome. Good first contributions: a venue comparison for a city that is not covered, a format not in docs/formats.md, region-specific insurance or shipping notes, or an artifact-eval spec for an artifact type. House rules: no invented numbers, human in the loop, and every recommendation survives the question "does this book a meeting?"

License

MIT. Fork it, adapt it, run your events on it.