Scheduling Social Posts and Email Around Launch Day
Promotion · 8 min read ·
A launch is a sequence of messages. Plan which post or email goes out when, how to schedule safely, and which messages should never be automated.
Launch communication has a rhythm. A few messages before, one big message on the day, a few after. Most founders either send too many, too early, or leave everything to the morning and send it badly. A short schedule, written in advance, fixes both problems.
This guide covers what to send, when to send it and how to schedule without embarrassing mistakes.
Principles
Fewer, better messages. Each one should have a clear purpose and a single action.
Match the audience. Your email list, your social followers and your community contacts are different groups with different expectations.
Put humans in the loop. Schedule the routine, not the relational.
Respect rules. Product Hunt's launch guide says you cannot ask people directly to upvote and should ask them to visit and comment. Hacker News's guidelines tell users not to solicit upvotes, comments or submissions. Write your messages to fit.
The message map
Plan each message as a row in a table: channel, audience, time, purpose, action. A typical small-launch map looks like this.
Three weeks before: the heads-up. To your list and close contacts. "I am launching on [date, time zone]. I would love your eyes on it. Here is what it is." Purpose: awareness. Action: put the date in their diary.
One week before: the reminder. Short. Date, time, one-line description. Purpose: keep it fresh.
One day before: the nudge. Even shorter. "Tomorrow at 09:00 UK time. Link will follow."
Launch day, opening: the announcement. The big one. The link, one sentence, one ask: visit and tell me what you think.
Launch day, midday: a different angle. A short follow-up on social with a new image or story, not a repeat.
Launch day, evening: a thank-you. Naming what happened and inviting people who missed it.
Day after: the debrief. A short note to your list thanking them and saying what you learned.
One week after: the update. What you fixed because of their feedback.
That is eight messages across four weeks. Many launches need fewer.
Email reaches people who asked to hear from you, so treat it with care.
Subject lines: plain and specific. "We launch Thursday at 09:00 UK time" beats anything clever.
Length: short. A few sentences and a link.
One call to action. Not three.
Plain text or light design. A personal feel works better than a newsletter template for most small launches.
Send times: check your own open data if you have it; otherwise choose a time when your audience is likely to be at a desk or a phone.
Sender name: a real person.
Unsubscribe link: always present.
Only email people who have agreed to hear from you, and say what they signed up for. If you did not collect agreement, do not use the list.
Social posts
Social platforms have their own conventions, but a few general rules apply.
- Write for the platform, not a copy of the email.
- Lead with the point. The first line is what shows in a feed.
- Include one image, well chosen, with alternative text where the platform supports it.
- Make the link obvious, and tag it so you can see where visitors come from.
- Avoid hashtag clutter. One or two relevant tags at most.
- Reply to every response.
Google's image guidance recommends meaningful alt text and descriptive file names for images, and the same habits help social images be accessible.
Scheduling without disasters
Scheduling tools are convenient and dangerous in equal measure. Follow these steps.
- Write the schedule in one place, with times in ISO 8601 form including the offset, for example 2026-10-02T09:00+01:00. Wikipedia describes the standard as an unambiguous way to represent dates and times, which is exactly what you need when three tools each have their own time zone setting.
- Check each tool's time zone setting. Many default to the account's zone, not the one you assume.
- Send yourself a test of each scheduled message.
- Review links in every message after scheduling. Tools sometimes alter them.
- Keep a master list of what is scheduled and where, so you can cancel or edit quickly.
- Have a kill switch. If something goes wrong on the day, you must be able to pause every scheduled message in minutes.
What not to automate
Some messages need a person.
- Replies to comments and questions.
- Apologies when something goes wrong.
- Responses to criticism.
- Thanks to individuals.
- Anything that depends on live events, such as "we are now live" if the launch slips.
Scheduled replies look robotic and can be tone-deaf if they arrive in the middle of a problem.
Handling changes
If the launch time changes, your scheduled messages are suddenly wrong. Know where they all are, pause them, correct them and re-schedule. Mention the change plainly: "Because of a delay, we are now launching at 11:00 UK time." When you update, keep a note of what changed and why.
Avoid pressure tactics
It is tempting to send an urgent message every hour on launch day. Resist. People tire quickly. Instead:
- Send one announcement.
- Add one new angle later in the day.
- Send one thank-you.
- Reply to people who respond.
The rest of your effort should go into the conversation, not the broadcast.
Measure what you send
Tag links in each message so your analytics can tell channels apart. Afterwards, compare:
- Which message drove the most visits?
- Which led to the most sign-ups?
- Which got replies?
- Which was ignored?
Write the answers in your launch notes. Next time you will send fewer messages and better ones.
A sample day map
Local time is UK. 07:00 final checks. 08:30 email to list scheduled for 09:00. 09:00 launch opens, first comment posted. 09:05 social post. 09:30 personal messages to helpers. 12:30 second social post with a different image. 16:00 reply sweep. 18:00 thank-you post. 20:00 final replies. All times in the plan carry the zone, and each scheduled message has a test copy in your inbox.
On this site
Our launch calendar and its coming-soon list show booked launches by launch week (weeks begin on Monday in UTC), which makes it easy to line your messages up with your week. A paid launch picks its week on the submit page; a free listing is placed in the free queue, 1-2 weeks out. A launch entry is currently $5, and a free listing can be upgraded to one at that price. The about-founders page says who runs What Is Launching.
Writing the messages
The structure of a good launch message is almost always the same: one line on who you are or why they are hearing from this person, one line on what you made, one line on what you would like them to do, and the link. Everything else can go.
An example announcement for an imaginary product: "Hi, it is Maya. Today I am launching Quillbox, a simple way for freelance writers to track which pitches are out and who owes them a reply. It is free to try without an account. I would love to know whether the first screen makes sense. Here is the link: [link]. Thank you for reading."
That is five sentences. It names the person, the product and the audience, offers a low-friction way to try it and asks one question. It does not ask for votes, and it does not use hype.
Message hygiene
Before any message goes out, run a short check. Is the link correct and tagged? Does the subject line say what is inside? Is the time stated with its zone? Would you be comfortable if this appeared on a screen behind you? Is there a way for the reader to opt out? If all five answers are yes, schedule it. If any is no, fix it first. These five questions, asked every time, prevent most of the embarrassing errors that scheduling tools make possible.
When things go wrong
If a wrong message goes out, correct it plainly and quickly. A short follow-up such as "Correction: the time in my earlier message was wrong; it is 09:00 UK time" is better than silence. People appreciate a clear fix, and the reputation cost of a visible, honest correction is far smaller than the cost of a confusing launch.
A short word on frequency
If you are unsure whether to send one more message, do not. Every extra reminder costs a little goodwill, and the people most likely to act on your launch will already have done so after the first. Spend that energy on replies instead. A thoughtful answer to one person is worth more than a fourth reminder to a hundred.
Archiving the schedule
When the launch is over, save a copy of your message map with what actually went out and when. Add a column noting the result of each message, such as visits or replies. Over several launches this archive becomes your own evidence base about what works for your audience.
The takeaway
Plan a short sequence, write times in one unambiguous format, test every scheduled message, keep replies human and keep a way to pause everything. A few well-timed, honest messages beat a barrage.
Questions and answers
- Which messages can I schedule?
- Reminders, announcements and thank-you notes. Keep replies, apologies and anything sensitive live and personal.
- How many emails should I send around a launch?
- Fewer than you think. A reminder before, an announcement on the day and a thank-you or update afterwards is enough for most small launches.
- How do I avoid time zone mistakes in scheduled messages?
- Check the zone setting of each tool, write times in ISO 8601 form with an offset in your plan, and send yourself a test.
- Can I ask my followers to vote for my launch?
- Not directly on several major platforms. Product Hunt says to ask people to visit and comment instead of asking for upvotes.