For organizers inviting a speaker their shortlist already picked
Speaker AskThe first invitation to a speaker, honest and short, and the follow-ups that add something.
Enter the slot, the candidate your shortlist picked and why, the honest budget line and the date you need an answer. Free in your browser, in the order the skill sets: the packet checked first (a name without its why goes back to sourcing), the travel gate against the four-to-six-week floor, the channel, the depth and the cadence re-ranked for this candidate, and the disclosure list every first invitation must state - the budget and the answer date up front, under 150 words, no banned vocabulary, no links. A run writes the invitation, or the follow-ups that each add a new angle and the reply to a yes-but. This writes the message, not the search: the shortlist arrives from upstream. Run the result past a humanizer pass before sending (the skill's step 6). The page never invents a fee, a market rate or a fact about the candidate, labels every number of its own self-set, and tags what the references call judged or reported.
1 The event and the interview free
2 The sourcing packet and the candidate free
Workflow step 1: the packet arrives from sourcing - this page writes the message, not the search. Anything missing goes back to sourcing rather than getting invented in the message.
3 A draft, the reply, and what is new since free
Every follow-up carries something the last one did not. Only what is true goes here - a manufactured "we just heard from X" is a promise you cannot deliver.
4 The ask, worked out free
What the page flags
The sourcing packet (Q1) - what it carries
The pole (Q2) - what the invitation can honestly offer
The travel gate (step 2)
Channel, depth and cadence - re-ranked for this candidate, deleted rungs struck
What the first invitation must state (step 5) - and the pasted draft against it
The follow-up schedule - a new angle every touch, stopping at the answer date
The reply (step 9) - each condition against the negotiable list
Closing the loop (step 10)
What the references label judged, reported or self-set
5 The files free
The invitation checklist, the follow-up schedule as a spreadsheet and a calendar, and everything the page worked out.
6 The invitation metered
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
Channel and depth
The invitation
Caveats
Caveats
The page's check of this reply
7 Saved asks
How it works - and what is sourced
The order is the skill's: the packet from sourcing is checked first, and a name without its why, its evidence or a published contact route goes back to sourcing rather than getting invented in the message; the pole decides what the invitation can honestly offer; the travel gate is checked before anything is written; the first-touch channel, the personalization depth and the follow-up cadence are re-ranked for this candidate from the interview, every move named and every ruled-out rung deleted, not demoted (a guessed or scraped address, the candidate's community space, the merge-field blast, the bump); the invitation is written against the disclosure list and the five-part structure, then cut to length; it goes past a humanizer pass before sending; the follow-ups each carry a new, true angle and stop at the answer date; a yes-but is answered only from the negotiable list fixed before the first message; and the loop closes with a written confirmation or a recorded no and a referral ask.
Sourced from the skill's references: the disclosure checklist, the five-part structure, the cap of roughly 150 words (the page reads it as 150), the banned vocabulary, the subject under 50 characters, the four-to-six-week travel floor, Day 0, Day 3 only with new information and Day 7 then stop, one to two weeks between long-runway touches, the angle table, the close-out shape, the fee scripts and the concession list. Self-set, and said so wherever used: a hard answer date at 14 days or fewer, a low effort ceiling under 2 hours per invitation, a 20-minute call, the follow-up word cap and the long-runway touch placement. The page reads a reply by keywords - read it yourself when it says unclear. There is no rate card for speakers: two community events publish flat honoraria (!!Con's USD 256, ffconf's GBP 500), and those are calibration for what a small honorarium looks like, never a rate to counter-offer with. Trading conditions for money uses ordinary concessions, not a convention of event practice; the email-over-DM ordering is judged, not measured; every vendor-pole adjustment is judged.