Verified against Claude · 2026-08-05
Write the three-post sequence that actually fills a webinar, not just the announcement
Plan the announce, reminder, and last-call posts for a webinar or event as three distinct posts with three different jobs and three different hooks, instead of the same announcement copy-pasted three times with a new date.
The prompt
Ready to copy — highlighted parts are example details you can swap.
EVENT OR WEBINAR TOPIC AND FORMAT
45-minute live webinar walking through a real usage-based pricing rollout, with Q&A
DATE, TIME, AND REGISTRATION METHOD
Thursday Aug 20, 11am ET, register at example.com/webinar
WHO SHOULD ATTEND, SPECIFICALLY
RevOps and pricing leads at B2B SaaS companies considering a pricing model change
THE SPECIFIC THING A REGISTRANT WALKS AWAY ABLE TO DO
Walk away with a checklist for the 5 things to test before rolling out usage-based pricing company-wide
WHO'S SPEAKING OR HOSTING, AND WHY THEY'RE CREDIBLE ON THIS
Hosted by someone who has run 3 real usage-based pricing rollouts, including one that had to be reversed
WHY ONE ANNOUNCEMENT RARELY FILLS A ROOM
Most registrations for an event come from people who see it more than once, in a different framing each time, not from the first impression alone. Posting the identical copy three times with only the date changed reads as repetitive to anyone following closely and wastes two of the three touches that could have done a different job.
WRITE THREE DISTINCT POSTS
1. ANNOUNCE (1-2 weeks' notice) — leads with Walk away with a checklist for the 5 things to test before rolling out usage-based pricing company-wide as the hook, not the event's existence ("I'm hosting a webinar" is not the interesting part; what someone walks away able to do is). Includes Hosted by someone who has run 3 real usage-based pricing rollouts, including one that had to be reversed as a specific reason to trust the content, not just a bio line. Ends with the registration action clearly.
2. REMINDER (1-2 days before) — assumes some readers already registered and some are seeing this cold; leads with a specific detail that will actually happen in the session (a real example that will be walked through, a specific question that will get answered) that wasn't in the announce post, giving anyone who saw the first post a new reason to care rather than just repeating it. States the exact time again, including timezone.
3. LAST CALL (same day, a few hours before or "starting now/soon") — short, urgency-driven, but urgency grounded in something real (seats capped, a specific thing happening at the start that latecomers will miss) rather than manufactured scarcity language ("only a few spots left!") that isn't true.
STRUCTURAL VARIATION CONSTRAINT
No two of the three posts may share their opening line or hook mechanism — if the announce post leads with a number, the reminder should lead with something else (a scene, a question, a named detail), so a reader following your feed doesn't recognize the same structure being reused with new dates plugged in.
OUTPUT
The three posts, clearly labeled with their intended send timing relative to the event, plus one line on what specific new information each later post adds beyond "this is still happening," since a reminder that adds nothing new is functionally just a repost.Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Event registration data across platforms consistently shows most registrants convert after seeing a promotion more than once, in different framings — not from a single high-quality announcement. This is the direct reason a three-post sequence with three distinct jobs (introduce the value, add a new specific detail, create real urgency) outperforms one good post reposted with a new date: each post is targeting a reader who didn't convert on the previous one, for a different reason each time.
Requiring the reminder post to include a detail that wasn't in the announcement — a specific example, a specific question that gets answered — directly addresses why reminders usually underperform: a reader who already saw and passed on the announcement has no new information to update on if the reminder just restates the same pitch, so nothing changes their earlier decision not to register.
Grounding last-call urgency in something real — a capped seat count, something specific happening at start — instead of manufactured scarcity language matters because LinkedIn audiences have become measurably numb to fake urgency phrasing, and a false scarcity claim a reader can see through (there clearly are more than "a few spots left" on a webinar with no attendance cap) costs more credibility with that reader for future promotions than the marginal urgency was worth.
The structural-variation constraint — no shared opening line or hook mechanism across the three posts — targets what actually gives a copy-pasted sequence away even when the date has been updated each time: a follower scrolling past all three in the same week recognizes the skeleton before they register the new content, and that recognition itself reads as low-effort regardless of how good any individual post's writing is.
Verified against
Claude Sonnet 5 · 2026-08-05
ChatGPT GPT-5.1 · 2026-08-05
Changelog
- 2026-08-05 — Initial publish for the rewritten linkedin category, verified against Claude (Sonnet 5) and ChatGPT (GPT-5.1).
Need this built into your business?
If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.
EXPLORE GOOGLE ADS MANAGEMENT
