Skip to content

samber/dev-event-organizer-skills / skills/event-speaker-cold-outreach

event-speaker-cold-outreach

Verified

Write and sequence the cold invitation to a speaker a shortlist already picked - the message, not the search. Covers what a first invitation must disclose up front (event basics, honest budget and travel terms, the answer deadline, how you found them), personalization built from the shortlist's own "why", ranked first-touch channels, follow-up cadences that add a new angle instead of bumping, and the fee conversation where speakers have no rate card. Use whenever the user mentions writing a speaker invitation, pitching a keynote candidate, following up on an unanswered invitation, or a speaker who asks for a fee - even if they never say "outreach". Do NOT use to find or qualify candidates - use samber/dev-event-organizer-skills@event-speaker-sourcing instead.

references/cadence-and-fee-conversation.md

View on GitHub
# Cadence, angles, and the fee conversation

Contents: the three cadences · the angle table · the close-out message · the fee conversation · the concession list · confirmation shapes.

## Table of Contents

- [The three cadences, touch by touch](#the-three-cadences-touch-by-touch)
- [The angle table](#the-angle-table)
- [The close-out message](#the-close-out-message)
- [The fee conversation](#the-fee-conversation)
- [The concession list](#the-concession-list)
- [Confirmation shapes](#confirmation-shapes)

## The three cadences, touch by touch

### Single ask, then stop

One message. Silence is a no after the answer date. Use it when the slot has a viable next candidate ready, when the candidate is a courtesy ask you would not chase, or when a second message would cost more reputation than the slot is worth.

### Three-touch angle cadence (default)

The default cadence: Day 0, Day 3 only if you have new information, Day 7 with a fresh hook, then stop.

| Touch | Timing      | Condition to send                                                                                 |
| ----- | ----------- | ------------------------------------------------------------------------------------------------- |
| 1     | Day 0       | The full invitation.                                                                              |
| 2     | Day 3       | **Only if you have new information.** No new information means no touch - the gap is the message. |
| 3     | Day 7       | A genuinely fresh hook, plus the close-out below.                                                 |
| -     | after Day 7 | Stop. Re-approach only with something actually new, and never for the same slot.                  |

### Long-runway cadence (starved)

One to two weeks between touches, capped at three, tightening to three or four days as the answer date closes in. Use this when the candidate needs internal approval or is arranging international travel; it is the only cadence shaped for candidates who cannot decide in a week.

Its real cost is not the touches. It is the weeks the slot stays held open behind someone who may never answer.

## The angle table

Every touch after the first carries something the last one did not. "Never bump, always add an angle" is the operative rule; the bump is deleted from the menu rather than ranked in it, and its named forms are "bumping this up", "did you see my email", and the same pitch reformatted.

| Angle                  | What it actually is                                                                 | When it lands                                                         |
| ---------------------- | ----------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| A confirmed co-speaker | Someone else on the program the candidate would want to share a day with            | Strongest angle available; use it the moment a relevant name confirms |
| A program detail       | The track took shape, the format changed, the room got bigger                       | Any touch; safe and true                                              |
| An audience question   | A specific thing this room argues about that their work answers                     | Best for a candidate who is on the fence about relevance              |
| A constraint update    | Travel confirmed, the deadline moved, the slot length is flexible                   | Turns a soft no into a re-open                                        |
| A narrowed ask         | Same invitation, smaller commitment - a shorter slot, a panel seat, remote delivery | Last touch, when the size of the ask is the likely blocker            |

Two rules bound the table:

- An angle has to be true: a manufactured "we just heard from X" is a promise you cannot deliver, the pitch-killer that damages an event longest.
- An angle is not a discount: narrowing the ask is legitimate, inventing urgency is not.

## The close-out message

The last touch in a cadence. Name the silence without reproach, separate "no to this slot" from "no to this event" (recover the latter answer), and ask for information a decline should carry.

Shape:

> I'll stop here rather than keep filling your inbox - if the timing doesn't work, that's completely fine and I'd rather know than guess. If it's the format or the date rather than the event, tell me and I'll see what I can move. Either way, I'd genuinely like to have you in the room next year.

- **What it does:** names the silence without reproach, separates "no to this slot" from "no to this event" (which is the answer worth recovering), and asks for the one piece of information a decline should produce.
- **What it must not do:** guilt, deadline theatre, or a fourth touch disguised as a goodbye.

## The fee conversation

A sponsor negotiation runs against a rate card. A speaker invitation has no equivalent - no published price, no tier, no norm. What you have is the honest-budget line, fixed before the first message and stated in it.

**The hard rule: do not invent a market rate.** "I don't have a benchmark for this, here's our budget" is both the honest answer and the stronger one.

Direct payment to speakers can bring complex issues around taxes, visas, and conflict of interest or employment agreements. Route a real fee through whoever handles the event's money and contracts rather than routing it yourself.

Three shapes, by what the budget can actually do.

**No fee available, candidate asks for one.**

> We don't have a speaker-fee budget this year - I'd rather say that plainly than negotiate around it. What we do cover is travel and two nights' lodging, and I have some room on the date and the slot length if either of those helps. If a fee is the condition, I understand completely and I'd still like to keep talking for next edition.

**A fee is possible but not yours to agree.**

> I can't commit to that number myself - [name] approves speaker fees and I can have an answer by Friday. I don't want to leave you waiting without knowing why, so: Friday, and I'll come back either way.

Naming the decider and the date is the whole move. The cadence menu has no rung for "waiting on us", and an unexplained silence from the organizer's side cools a warm candidate faster than a no does.

**The candidate names a number you cannot benchmark.**

Do not counter with a figure you made up to look informed. Answer from your own budget, ask what the number is covering (some of it is often travel, prep time, or lost billable days rather than a fee as such), and see whether the concession list closes the gap instead.

## The concession list

Fix this list before the first message. These are ordinary concessions whose only test is that they cost you something real and are worth something real to them.

| Concession                      | What it costs you                   | When it works                                                                 |
| ------------------------------- | ----------------------------------- | ----------------------------------------------------------------------------- |
| Travel dates extended           | A night or two of lodging           | A candidate combining the trip with something personal                        |
| Shorter or longer slot          | Program rebalancing                 | A candidate short on prep time, or one with more to say than the slot holds   |
| Remote delivery                 | Production effort, some room energy | Travel, visa, or caring constraints - often the concession that saves the yes |
| Co-speaker seat                 | One ticket, a shared slot           | A candidate who wants to bring a colleague or a first-time speaker            |
| Companion ticket                | One ticket                          | Near-zero cost, disproportionate goodwill                                     |
| Recording and publication terms | Reach for the event                 | A candidate with an employer's approval process or an unpublished result      |
| Session time of day             | Schedule flexibility                | More often decisive than organizers expect                                    |
| An introduction                 | Your own social capital             | A candidate whose reason for coming is who else is in the room                |

Anything not on this list is not available, whatever the conversation does. That is the point of fixing it in advance.

## Confirmation shapes

**On a yes**, confirm in writing the same day. Missing any of these turns into a dispute later:

- slot, date, start time, length, format
- what the event pays and - explicitly - what it does not
- travel and lodging terms, with who books what
- recording and publication terms
- the deadline for title and abstract
- the review lane for the invited proposal, which `samber/dev-event-organizer-skills@event-speaker-sourcing` recorded in the packet and `samber/dev-event-organizer-skills@event-talk-selection` needs stated rather than guessed

**On a yes-with-conditions**, agree only from the concession list, then confirm exactly as above with the condition written into the same message. A condition agreed in a call and absent from the confirmation is a condition nobody agreed.

**On a no**, record the reason - timing, topic, budget, travel, format, or no reason given - and ask whether they would suggest someone else. A declining candidate is unusually well placed to refer, and a referral is the cheapest strong signal in the sourcing menu. Both the reason and the referral go back to `samber/dev-event-organizer-skills@event-speaker-sourcing`.

**On silence past the cap**, treat it as a no in your own records, release the slot, and move to the next candidate. Do not leave a slot open on hope; that is the most expensive habit in this workflow.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall