The launch week playbook: what to do Monday through Sunday before launch day, plus the exact six-paragraph launch post template that actually converts.
The week before your launch is more important than launch day itself. Launch day is a few hours of publishing and responding. The pre-launch week is where you build the runway that day uses: the audience announcement, the launch post, the tested assets, the personal outreach, and the weekend soft launch. Here is the full seven-day playbook, plus the exact launch post template.
Launch is a window, not an event
Here is what happens to founders who treat launch as a single-day event. They publish. They get a spike of traffic from Product Hunt or LinkedIn. The spike lasts forty-eight hours, they convert maybe four to twelve customers in that window, and then they are back in the kitchen on Friday afternoon staring at analytics dropping toward zero — fourteen customers, no obvious path to a hundred.
The founders who succeed treat launch as the start of a window — typically a two-week window — during which they are unusually visible, unusually energetic, and unusually focused on getting the right things to happen. The launch isn't the finish line of the build. It's the starting line of the business. And that window opens a full week before you publish anything.
The pre-launch week, day by day
| Day | The job |
|---|---|
| Monday | Tell your audience the launch is coming — date, why, who it's for |
| Tuesday | Write your launch post (two hours), edit it the next morning |
| Wednesday | Prepare and test every asset: landing page, pricing, signup, checkout |
| Thursday | Personal notes to ten people who could support the launch |
| Friday | Rest — no tinkering |
| Weekend | Soft launch to your presell customers; fix the top issue Sunday |
Monday — tell your audience. Your newsletter list, your LinkedIn followers, your community contacts. Don't pitch. "On [date], I'm launching [product]. Here's why I built it. Here's who it's for. If you want early access, here's where to find me on launch day." The energy is anticipation, not promotion.
Tuesday — write your launch post. Spend two hours on it. It's the most important paragraph of writing you'll produce in your first year. Six paragraphs maximum, under five hundred words. Read it the next morning and edit. The full template is below.
Wednesday — prepare your assets. The landing page is polished. The pricing is clear. The signup flow has been tested by you and one other person. The welcome email triggers correctly. The Stripe checkout works. The product has been used by beta customers for at least a week and the obvious bugs are fixed. If any of these are not ready, push the launch by a week — a launch with broken signup destroys more trust than a slightly delayed launch ever could.
Thursday — do the outreach. Send personal notes to ten people you'd like to support the launch. Not promotional asks. "I'm launching on [date]. You've been part of the journey. If you have a moment that day to take a look, I'd appreciate it." Most will respond. Some will share. A few will become your first customers. Personal notes convert in a way mass announcements never do.
Friday — rest. Seriously. The launch is set. Tinkering at this stage introduces bugs and burns the energy you need for the launch days. Close the laptop.
The weekend — soft launch. Send the product to your five to ten presell customers (the ones you won before you built — the same people covered in getting your first 10 customers). Let them use it over the weekend. By Sunday night you'll have heard from at least three of them about something small to fix before the public launch. Fix it Sunday evening. Ship the fix. Go to bed.
The launch post template (steal the structure)
The structure: hook (one sentence that names the problem your audience feels), context (two to three sentences on why it matters), what you built (two to three sentences, no buzzwords), proof (one sentence of validation), call to action (one sentence with a link). Here's a working example for a software product — adapt the specifics, keep the structure:
If you're a solo consultant running three to ten retainer clients, you spend hours every Monday in a fragmented mess of Notion docs, Google Sheets, and Slack threads just trying to figure out what each client needs this week.
I've been running a consulting practice for eight years. Every productivity tool I tried was built for agencies with project managers or for solo freelancers with one client at a time. Nothing fit the middle — the consultant with a small portfolio of long-term retainers.
So I built one.
It's called [Product Name]. One workspace per client, with everything you need in one view: their KPIs, recurring deliverables, weekly status, and the next three things you owe them. AI-generated weekly status emails you can review in two minutes instead of writing in twenty.
Twelve consultants tested it over the last eight weeks. Eleven are paying for the first month already.
If you want to try it, here's the link: [URL]
Comments and questions welcome — I'll be here all day responding.
That's under four hundred words, and it works because it does five specific things in order: names the audience by their actual problem, establishes you understand the problem from inside it, describes what you built without selling, drops one specific proof point, and makes the next step trivially easy. No marketing fluff. No "introducing." No "we're excited to announce."
Launch day: publish, then be present
Get up at least an hour before launch. Publish. The email to your list goes out; the post drops. Then respond to every comment, reply, and question — the first hour of engagement is the most important, because it signals to the platform's algorithm that the post is getting traction, and that signal drives the next wave of distribution.
Don't multitask. Today is one thing. Use a vacation day. No meetings, no day-job email, no fixing product bugs. The launch is a four-to-eight-hour window of high-engagement work, and your job is to be present for every conversation. The comment thread is what most readers actually read — it's the social proof that turns a casual visitor into a customer. Stay engaged for an hour or two after dinner to catch the other time zones, then close the laptop. Tomorrow is day two.
The one mistake that invalidates all of it
Launching before the audience exists. The launch is to an audience — if the audience is twelve LinkedIn connections, the launch has nowhere to land. The thresholds: fewer than two hundred engaged newsletter subscribers, fewer than five hundred LinkedIn followers in your target market, fewer than fifty engaged community members. Below those, delay the launch by four to six weeks and build the audience aggressively — building in public is exactly how. A delayed launch into a real audience is infinitely better than an on-time launch into silence.
Frequently asked questions
How long before launch should I start preparing?
The structured playbook takes one week: announce Monday, write the post Tuesday, test assets Wednesday, outreach Thursday, rest Friday, soft launch over the weekend. But the audience takes longer — if you haven't been posting consistently for two to three months, build that first.
What should a launch post include?
Five elements in order: a hook naming the problem, context on why it matters, what you built without buzzwords, one sentence of proof, and one clear call to action. Six paragraphs maximum, under five hundred words. "Check it out" is not a call to action — "click here to try it free" is.
What do I actually do on launch day?
Publish early, then be present. Respond to every comment within the first hour — that's when the algorithm decides whether to amplify. No meetings, no multitasking, no bug-fixing. The launch is four to eight hours of high-engagement conversation, plus an evening session for other time zones.
How many customers should a launch produce?
A single-event launch typically converts four to twelve customers in its forty-eight-hour spike. Run the full two-week window — pre-launch week, launch day, post-launch week — and the realistic range is five to a hundred paying customers, depending on your product and audience size.