Owned Event

Your name on the door. The highest ceiling and the highest risk, because a thin room at your own event is a public failure rather than a private one.

When to use

• A customer base worth convening
• A partner whose venue and brand lend credibility you have not earned yet
• A launch that deserves a room
• Anything from fifty people in a partner's office to a multi-day conference

Inputs

• Reads: workspace/program/charter.md, workspace/audience/target-list.csv
• Needs from user: the objective, the target size, the budget, whether a co-host exists, and honest team capacity

Workflow

1. Find a co-host before you find a venue

A co-host changes the economics and the credibility more than any other decision.

What a good co-host provides: a venue at no cost, their own audience, a brand association worth more than yours, preferred vendors already vetted, and a reason for the event to exist that is not "we wanted to do an event."

Who they are: an investor, a large partner, a customer with an impressive office, a complementary vendor selling to the same buyer, or an industry body.

What to agree in writing, early: who owns the invite list and whether it is shared, whose brand leads, who pays for what, who speaks, who owns follow-up on shared attendees, and what happens to the relationship afterward. Co-hosted events go wrong on list ownership more than on anything else.

Ask for the next one while the goodwill is fresh. The best moment to lock a repeat is the week after a clean run, not six months later.

2. Set the room composition target before anything else

The number that decides whether this worked:

Target accounts as a share of attendees. For an owned event, 40% is the floor and higher is the goal.

Write it in the plan, measure it at every RSVP milestone, and treat it as the primary success metric alongside meetings. Registration volume is not a metric. A room of 111 people that is thin on buyers is worse than a room of 60 that is not.

3. Design the program around conversation, not broadcast

Use the confirmed speaker lineup as the invitation hook. Lock speakers before the invite waves go out, because "X, Y and Z will be there" is the line that fills the room.

4. Run the speaker pipeline as a pipeline

Speaker wrangling breaks in three predictable places: the initial commitment cycle drags, someone drops late, and preparation is reactive. Fix all three by design:

• Lock speakers 10 to 12 weeks out, with backup names already vetted. Assume one of three will drop
• The confirmation gate is a signed one-pager plus an accepted calendar invite, not a verbal yes
• Preparation on a calendar at 6, 4, and 2 weeks out, not when someone remembers

5. Build the VIP track

The most common miss at an owned event is treating all attendees identically when five to ten of them are the reason you did it. A VIP track costs almost nothing:

• Reserved seating near the front
• A named handshake at the door, by someone briefed on who they are
• A founder-anchored side conversation in a corner of the reception
• One team member who owns each VIP for the night
• A separate follow-up tier

6. Assign named attendees to your own team

Before the event, every person from your company gets three to five named attendees they are responsible for talking to. Written down, confirmed in the huddle. Pipeline conversations left to chance during a happy hour do not happen.

7. Budget honestly

An owned event is where scope creeps hardest. Model it with event-budget, and get these lines in:

• Venue, or zero if a co-host provides it, plus what the co-host expects in return
• Catering and beverage, all-in
• AV and production
• Speaker travel, if you are covering it
• Photography and video
• Staff days across planning and delivery, which is by far the largest hidden line for an owned event
• Follow-up and content production

A co-hosted evening at a partner's headquarters can genuinely run at a few thousand out of pocket. A real user conference is a program with a dedicated team. Do not let anyone conflate the two in planning.

8. Build the content machine before the day

An owned event that produces no content wasted the room. Written in advance: the recap in skeleton, social posts in each voice, the photographer's shot list, and the thank-you and no-show sequences. See event-content.

Output

• Writes: workspace/events/<event>/owned-event-plan.md with the co-host agreement points, composition target, program, speaker pipeline with backups, VIP track, and staffing assignments
• Prints: the composition target against current RSVPs, the speaker status with backups, the VIP list, and unowned lines

Rules & quality bar

• Co-host before venue. It changes everything downstream
• List ownership agreed in writing with any co-host
• Room composition target set first and measured at every milestone
• Speakers locked 10 to 12 weeks out with vetted backups
• A signed one-pager plus an accepted calendar invite is the confirmation gate
• The VIP track exists
• Named attendees assigned to every team member
• Staff days are in the budget
• Registration volume is never reported as success

Related skills

• Reads: audience-machine, invite-motion, event-budget
• Pairs with: venue-selection, speaking-and-stage, event-content, staffing-and-briefing
• See also: docs/field-notes.md notes 1 and 10