After the Talk: How to Promote a Conference Talk on Social Media Without Spending the Weekend on It

TL;DR: To promote a conference talk on social media, post in three waves: a slides link with the event hashtag the moment you step off stage, a recording post when the video lands, and one or two “lesson” posts a week later. Write the source facts once, let an AI agent reshape them per platform, and keep the thank-you notes human.

You gave a 30-minute talk on Thursday. People came up afterwards, three of them asked for the slides, and you said “I’ll post them tonight.” It’s now Sunday. The slides are still on your laptop, the conference hashtag has gone quiet, and the recording will drop in two weeks, when nobody’s looking.

That gap is where most of a talk’s reach is lost. The talk itself reached the room. Everything after it reaches everyone else, and that part is mostly admin: links, tags, a few posts timed against a schedule you don’t control. This guide is for speakers who’d rather spend that admin time on the next talk.

The three waves of post-talk posts

Speakers who write about this agree on the first move: put the slides link out right away. Gleb Bahmutov’s checklist of what he does after a conference starts with making the deck public before the event, posting the link immediately afterwards, thanking the audience, and tagging the conference so attendees can find it. I’d stretch that into three waves, because each one has a different trigger and a different job.

Wave 2 is the one people forget, because its date is set by the organizer. Wave 3 is the one that gets you invited back, since it shows what you actually know instead of what you presented.

Wave 1: the slides post (same day)

Keep it boring and complete. It needs five things:

1. A one-line description of the talk, not the title alone.
2. The slides link, as a public URL that works without login.
3. The event hashtag, so the post lands in the stream attendees are already watching.
4. A tag for the organizer account.
5. Your handle on the slides themselves (and, if you have them, your Bluesky or Mastodon handles too).

Where the hashtag lives matters. The same post can’t be copy-pasted across networks. A rough split that works:

• X and Bluesky: short, hashtag-driven, one image (the title slide or your best diagram). Attendees live-posting the event are there.
• Mastodon: hashtags are the main way anyone finds your post, so include the event tag and one or two topic tags in CamelCase for screen readers. Put a description on the image.
• LinkedIn: a few more sentences. Who the talk was for, one takeaway, then the link. Slides as a document upload often get read here, because people scroll them like a carousel.

Have the first post written before you fly. “Thanks to everyone at X, slides are here” needs no inspiration, just a link you can paste.

Wave 2: the recording post

Most recordings arrive days or weeks later, on a date nobody tells you. Two habits help:

• Put the talk’s year and event name in the video description so a stranger can tell whether it’s current. Bahmutov recommends something like “Presented at ReactConf Finland 2021” for this reason.
• Link slides and video to each other, and to the blog post if the talk started as one.

The post itself should lead with a single moment rather than “my talk is now online.” Pick one 60-second segment, name the timestamp, and say what a viewer will get from it. “Minute 14: why we dropped the queue and went back to cron” will get clicked more often than a title card.

Wave 3: lessons from the talk

A week later, the slides post is old. This is where you give the talk a second life by pulling out single ideas. Sources like Stephanie Morillo’s piece on repurposing talks as blog posts make the same point for long-form: a slide deck without the speaker’s words is mostly empty, and a narrative version of the talk is more useful to people who weren’t there. The social version is smaller. Three examples that tend to work:

• The thing you cut: a slide that didn’t fit the time limit, with the one-paragraph explanation.
• The audience question: the best question from Q&A and your short answer. This one also tags a person if they’re happy to be named.
• The mistake: the one failure from your own project that the talk was built on.

These are also what you’d want on Dev.to or your own blog. If you do publish the long version, crossposting it to Dev.to automatically means the canonical link points to your own site.

Letting an AI agent handle the reshaping

Here’s where the work really adds up: the same four facts (title, link, hashtag, takeaway) need to become a thread-sized post, a LinkedIn paragraph, a Mastodon post with tags and alt text, and a Bluesky post, across three waves. That’s a dozen small drafts.

I’d split the job like this. You write one talk.md file: title, event name and hashtag, slides URL, video URL (blank until it exists), and your three lesson ideas with a sentence each. The model’s job is formatting and scheduling. Yours is deciding what’s true and worth saying.

PublishPort works like this: you sign in to your own accounts once in the desktop client, and your AI agent calls list_capabilities and local_bash through the relay, reads each tool’s --help, and posts from your logged-in sessions. Give it talk.md and ask for wave 1 drafts per platform, review them on the plane, then queue wave 2 and 3 for later. The pricing page lists what each plan covers. For the broader picture of one agent running several networks, see publishing to multiple platforms at once, and the same idea applied to a single event is covered in Product Hunt launch day posts.

Limits worth knowing

• The desktop client has to be running and logged in when a post is due. Conference travel plus a closed laptop equals a missed wave 1 post, so send that one live, from your phone if you have to.
• Image handling differs by network. Do a dry run with the title slide before the event.
• Models make up details. Check every name, handle and timestamp against your notes. A wrong organizer tag is worse than none.
• Don’t blast the same text at several hashtags or tag dozens of attendees. It reads as spam and it is.
• Thank-you notes to organizers and fellow speakers should be written by you.

If you haven’t tried posting from an agent before, test it with a throwaway post first.

A post-talk checklist

• Slides on a public URL, linked on slide one and the last slide
• Event hashtag and organizer handle saved in talk.md
• Wave 1 drafts per platform written before travel
• Wave 2 reminder set for when the recording is expected
• Three lesson ideas, one sentence each
• Video description includes event name and year
• Thank-you messages written by hand

FAQ

When should I post my slides after a conference talk?

As soon as you finish, or even as your talk wraps up. That’s when attendees are still looking at the conference hashtag. Posting a week later still helps, but you’ve lost the live audience.

Which hashtag should I use for a conference talk post?

The event’s official hashtag first. It puts your post in front of the people following the event and in any archive the organizers compile. A talk-specific tag on your slides is a bonus, not a replacement.

Should I tag the conference and other speakers?

Tag the organizer account, yes. Tag other speakers only when you’re referring to something specific they said. Blanket tagging reads as spam.

Is it worth posting on Bluesky and Mastodon as well as X and LinkedIn?

If your audience is on them, yes. Conference communities now split across Bluesky, Mastodon and X, and following the event tag on each is how remote attendees join in. Mastodon needs hashtags to be found at all.

What if the recording isn’t published for weeks?

Do wave 1 and wave 3 without it and schedule wave 2 for when it appears. Don’t hold the slides back waiting for the video.

Can AI write my talk promotion posts?

It can draft them well from a notes file. It can’t know which moment of your talk landed, so the choices stay yours.