Free · Claude Code plugin

Event outbound sequences.
Written by someone who's worked the floor.

A free Claude Code plugin for pre-event outreach to conferences and trade shows. Feed it an event URL, your ICP, and a persona. Get validated multi-channel sequences, ready for Apollo, Outreach, Salesloft, or HubSpot.

What it does

You give it three things: an event URL, your company ICP, and the target persona you want to book.

It reads the event context (sessions, speakers, exhibitor neighbours, analyst briefings) and drafts copy that pokes a tension the persona has actually lived, not the "we help companies like yours" blast they archive on sight. Email, LinkedIn connect note, LinkedIn DM, and a meeting-request line per persona.

Every touch passes a built-in validator: subject under 4 words, 4-6 sentences, no hype vocab, permission-based close. You paste the validated output into Apollo, Outreach, Salesloft, or HubSpot and send from your own domain.

The validator

Why the output is different

Most cold email trade show generators hand you a "Hi, wanted to connect" blast the model thinks sounds polite. This one blocks sequences that fail a set of hard rules before they reach your sequencer.

Subject line ≤ 4 words
Problem-shaped, not pitch-shaped. "quick thought on RSA prep" beats "Partnership opportunity".
Body 4-6 sentences
Read on a phone between sessions. Longer and the prospect bails before the ask.
Open with a tension, not a claim
Reference something the prospect has lived. No "we help companies like yours".
Permission-based close, no demo ask
"Worth a look?" / "Want me to send it?" beats "Got 15 minutes for a quick intro call?" every time.
Before, generic LLM blast
Subject
Partnership opportunity ahead of Money20/20
Body

Hi Sarah, I hope you're doing well. I wanted to reach out ahead of Money20/20 Europe to see if you'd be open to connecting. We've built a game-changing AI-powered fraud platform that is helping leading fintechs transform how they approach risk, and I think there's a real opportunity for a partnership. Would you have 30 minutes next week to hop on a quick intro call? I can work around your schedule. Looking forward to hearing from you.

Fails: hype vocab (game-changing, transform, leading), demo ask, 5× "I/we" vs 1× "you"
After, validated touch
Subject
fraud track at M20/20
Body

Sarah, saw you're on the Tuesday risk panel. Walking that floor last year I counted 14 vendors all pitching the same rule-engine story, and the one question nobody answered was what to do when the rules fire on good customers. Curious how you're thinking about that going in. No pitch, just interested in how a VP Fraud at a Series C sizes the tradeoff. Happy to share a one-pager on what we've seen at three fintechs if it's useful. Worth a look?

Passes: tension opener, no hype vocab, permission-based close ("Worth a look?")
Live examples · three real scenarios

Pokes the bear. Doesn't pitch.

Pre-event cold email to a VP Fraud at a Series C fintech, a LinkedIn DM to a Director of Security Engineering at RSA, and a post-event scan follow-up from a field marketing manager. Full multi-touch sequences are in the examples folder on GitHub.

Cold email · Money20/20 Europe
VP Fraud, Series C fintech · pre-event email
Subject
M20/20 Tuesday
Body

Ada, saw you're on the Tuesday risk panel. Most VP Fraud folks I talk to walk into Money20/20 already knowing the rule-engine pitch cold, and the real question is what happens when the rules fire on good customers. Curious how your team is sizing that tradeoff right now. We ran into a sharp version of it with a Series B payments infra customer last quarter. Want me to send a short write-up of what shifted for them? Happy to leave it there if the timing's wrong.

LinkedIn DM · RSA 2026
Director Security Engineering, mid-market SaaS · LinkedIn DM
Subject
quick thought on RSA prep
Body

Tomás, noticed you're speaking on the detection engineering track. Two things we keep hearing from Directors of Sec Eng at mid-market SaaS going into RSA: the expo floor is noisy, and most of the booths can't answer how they'd fit next to an existing SIEM. If you have 90 seconds at some point, I can share what a Series C cybersecurity customer asked us before they walked the floor last year. Open to it?

Post-event email · scan captured Wednesday
Field Marketing Manager · post-event booth-scan follow-up
Subject
the fraud demo from Wednesday
Body

Priya, you stopped by on Wednesday and asked about the behavioural layer on top of your current rules. I pulled the two slides that actually answer that and a short note on what changed for a Series B regtech who had the same setup. No follow-up deck, no calendar link. If it's useful, reply and I'll send the 90-second read. If the project's parked until Q3, say so and I'll circle back then.

Connection request note · 300 chars
LinkedIn connection request

Saw you're heading to RSA next month and caught your post on detection tuning. Not pitching, just following people thinking about the same things we are. Would be good to connect before the show.

Meeting request
15 min at Money20/20?

Ada, if the Tuesday write-up lands, worth 15 min on the Wednesday between sessions? Happy to come to your booth. If not a fit, I'll stop there.

Quickstart

Three lines. Sequences in a minute.

Drop these into Claude Code. The plugin is open source. Fork it, rewrite the validator for your own tone, keep the rest.

1 /plugin marketplace add luminik-io/claude-plugins
2 /plugin install event-outbound-skill
3 claude "Draft an RSA 2026 sequence for a detection-engineering platform targeting Directors of Security Engineering at mid-market SaaS"

Requires Claude Code. The marketplace command adds the luminik-io/claude-plugins catalogue; the install command pulls the event-outbound skill.

Built on a real track record

20k+ personalised touches · 50+ B2B events · $6M+ sourced pipeline across fintech (identity verification), cybersecurity, and B2B SaaS.

See how that motion runs pre-event, on-floor, and through post-event follow-up on the B2B event case studies page, or read the fintech event marketing playbook.

Event outbound FAQ

What is event outbound? +
Event outbound is the pre-event outreach you run 4-8 weeks before a conference, trade show, or summit. Targeting the specific buyers attending with event-specific angles. Good event outbound books meetings before the doors open. Bad event outbound is the "hope they stop by the booth" pattern that eats six-figure sponsorship budgets.
How is this different from Outreach, Salesloft, or Apollo? +
Outreach, Salesloft, and Apollo are the pipes, they send the emails. This skill writes the content that goes through those pipes. You still use your existing sequencer. The plugin generates event-specific multi-channel sequences (email, LinkedIn, phone) that pass a validator before they reach a real prospect, so you don't burn an ICP contact on a generic blast.
Does it send emails for me? +
No. It drafts validated sequences. You paste them into Outreach, Apollo, Salesloft, or HubSpot and run them through your existing infrastructure. Your deliverability domain and sender reputation stay yours.
What data does it need? +
Three inputs: the event URL, your ICP (company type, size, region), and the target persona (title, seniority, function). The skill pulls the event context (sessions, speakers, booth neighbours, analyst coverage) and writes angles that reference it. You don't need to upload attendee lists.
Is it free? +
Yes. The plugin is free and open source on GitHub. You run it inside Claude Code, so the only cost is your existing Claude usage. If you want the full Luminik platform that runs this motion for you across an annual event calendar, that's what the 20-minute walkthrough is for.

Want the full motion? See our tier pricing (Starter $299, Growth $799, Scale $1,999) or run the numbers in the free event ROI calculator.

Pre-event outreach that books meetings before the doors open

Install the free Claude Code plugin and run your next pre-event sequence this afternoon. Or book a walkthrough and we'll run the motion for you.