Run an event that produces pipeline, not badges scanned.
The right guest list, a real draw, an on-site conversation plan, and follow-up that converts.
Inside: The guest list, the draw, the on-site plan, and the follow-up.
Install it in one line, or paste it in.
~/.claude/skills/ and runs automatically when it is relevant.Connect your context. Set it to your motion.
it reads your open pipeline and target accounts automatically, so the guest list is built from real deals and real targets, not a generic invite blast.
tracks who actually replied, showed, and re-engaged, so the follow-up is aimed at real interest.
fills in titles and roles so the invite reaches the person who can actually move a deal.
This was built for a B2B SaaS org running field dinners and conference presence against open pipeline. Set these to your stack:
Your event motion is yours. The skill builds the list and the follow-up against the goal you set, not a generic attendance target.
| Set this | What it is | Default / Example |
|---|---|---|
| EVENT type | the format | dinnerboothroadshowhosted session |
| GUEST source | where the invite list comes from | open pipelinetarget accountscustomers |
| CAPACITY | seats you are filling | 14 for a dinnerre-tune per format |
| OWNER map | who owns each guest on-site | the rep who owns the account |
| FOLLOWUP window | days to first post-event touch | 2 (re-tunesooner is better) |
| GOAL | what the event is for | pipeline createddeals advancedretention |
Everything the skill does, in full.
Takes an event, a dinner, a conference booth, or a roadshow stop, and builds the plan that turns it into pipeline instead of a photo and an expense report. It picks the guest list worth the room, designs a draw people actually clear their calendar for, plans the on-site motion so the right conversations happen, and writes the follow-up that converts. Events do not create pipeline in the room; they create it in the two weeks after. This plans both halves.
- 1Build the guest list (the room is the strategy)
The single biggest lever on event pipeline is who is in the room. Build the list from real targets: open deals that need a push, target accounts you cannot get a meeting with any other way, customers who expand or advocate. For each seat, name why they are worth it and which rep owns them. A full room of the wrong people is a cost, not a pipeline event.
- 2Design the draw (worth clearing a calendar for)
People do not leave the office for a sales pitch. Give them a reason: a peer group they want to be in, a speaker or topic they cannot get elsewhere, a genuinely good experience. The draw is what fills the seats you chose. If the invite reads like a demo request, the accounts you most want will decline.
- 3Plan the on-site motion (conversations, not badge scans)
Decide before the doors open what a good on-site outcome is per guest, and who makes it happen. Assign each priority guest to the rep who owns them. Set the one conversation each guest should leave having had, and the specific next step to tee up in person. Scanning a badge is not a conversation; plan the conversation.
- 4Write the follow-up that converts (the pipeline is made here)
The event is the setup; the follow-up is the deal. Draft the post-event touch before the event, personalized to what each guest actually did and said, out within a couple of days while it is warm. Tie it to the next step you teed up on-site. A message can carry the account and persona context so the follow-up references the real conversation, not a form thank-you. Slow, generic follow-up is where event pipeline goes to die.
- 5Measure against the goal (pipeline, not attendance)
Judge the event by the goal you set, not the headcount. Count the meetings booked, the deals advanced, the pipeline created or influenced, tied back to the guests who were there. Attendance is an input; pipeline is the result. Report the result, and it tells you which events to run again.
- Every seat on the guest list has a named reason and an owning rep, never a generic invite blast.
- The draw is a reason the guest benefits, never a disguised sales pitch.
- Each priority guest has one intended conversation and a next step, planned before the doors open.
- The follow-up is drafted before the event and goes out inside the window, personalized to what the guest did.
- Results are counted as pipeline and meetings tied to real attendees, never as badge counts. Sample figures are illustrative only.
FIELD EVENT PLAN · Customer dinner, 14 seats (illustrative) Guest list (built from real pipeline) Guest / account Why the seat Owner Acme (VP) stuck deal, needs econ buyer Rep A Vertex (Dir) target acct, no meeting yet Rep B Blend (Champion) expansion candidate CSM ... ... ... Draw Peer roundtable on a shared problem + private dinner On-site motion Acme seat next to Rep A; tee up the CFO intro Vertex Rep B opens the first real discovery live Follow-up (drafted now, out within 2 days) Per guest, tied to the on-site next step, personalized Measure against goal: pipeline created + deals advanced Not badges scanned. Tie every result to a named attendee. Next moves: 1. Send invites to the 14 chosen seats; reps own their guests. 2. Pre-write the follow-up per guest before the night. 3. Book the teed-up next steps within 48 hours.
Where an operator takes this next.
The plan works from a pasted brief. Here is where the follow-up stops depending on someone remembering to write it the next morning.
The dinner ends. The plan for the next one starts building itself.
Have a rep type a one-line note per guest into a shared doc during the dinner, and a scheduled Claude task turns it into the personalized follow-up that same night.
Tag every guest in Salesforce so pipeline created or advanced in the following 60 days ties back to who was actually in the room.
Feed the meetings-booked outcome into Clay or your CRM so the next event's guest list is built from what actually converted, not a fresh guess.
One skill is the on-ramp.
A single skill does one job. Chained into a playbook, or run as a full build, it becomes a system. Here is where this one plugs in.