Skip to content
Automation Club
  • MarkdownLaunch week plan: Acme PlannerExample output

    Launch week plan: Acme Planner


    Here's the plan. It runs from Tuesday 27 October to Thursday 5 November. The offer ends on Monday 9 November, which is after that window, so that day gets its own rows at the end of the table.

    The table uses two names for the cofounders. Product runs product and support. Marketing runs marketing and the community.

    Timing notes

    • All times are Pacific, on a 24-hour clock, as your clock shows them that day. US clocks go back an hour at 2:00 on Sunday 1 November.
    • The launch-day posts on X go out at 9:10, 12:30 and 15:00 Pacific. That's 12:10, 15:30 and 18:00 Eastern: lunchtime in the east and mid-morning in the west, then afternoon on both coasts, then the end of the East Coast working day. LinkedIn gets one launch post, and the replies under it do the rest.
    • Tuesday 3 November is also US election day. Results will fill feeds in the evening, so the last launch post goes out at 15:00 and the evening is for replies only.

    Questions the plan needs answered

    1. [ask: Does a team get half price by starting the free trial during launch week, or by paying during launch week? A trial started on 3 November ends on 17 November, after the offer closes.]
    2. [ask: At what time on Monday 9 November does the offer end, and in which time zone?]
    3. [ask: Is the half price applied automatically at checkout, or do teams enter a code?]
    4. [ask: What is the exact link for starting the free trial? And from 3 November, should acmeplanner.example.com/waitlist send people to the trial or do something else?]
    5. [ask: Product Hunt's day runs from 00:01 Pacific, and as far as I know, launches scheduled ahead go live at 00:01, not 9:00. Do you want the listing live at 00:01 with the site, email and posts at 9:00? Or do you want to post the listing by hand at 9:00, which gives it about 15 of the day's 24 hours?]
    6. [ask: Where do most of the people on your waitlist live? These times assume North America. 9:00 Pacific is 17:00 in London.]
    7. [ask: Do you have a short screen recording or a screenshot of a planned week? Teaser 2, the Product Hunt gallery and the launch thread all need one.]
    8. [ask: What is the regular price? People will ask what half price comes to, and the reply bank needs the answer.]

    The announcement pack, as the table names it

    PieceWhat it is
    Teasers 1 to 4Short posts before launch. 1: the problem in your users' words. 2: how it works, with a screenshot or clip. 3: Sunday evening, on X only. 4: "tomorrow at 9:00 Pacific."
    Reminder emailWaitlist email for 2 November
    PH listingProduct Hunt tagline, description, gallery and the makers' first comment
    Launch siteHome page with the trial button, offer banner, beta quote and beta numbers, plus a version without the offer for after 9 November
    Launch emailWaitlist email for 3 November
    Launch postsX thread (pinned), LinkedIn post and two short follow-up posts on X
    Beta DMNote to the 38 beta teams, sent before and on launch day
    Reply bankReady answers to the likeliest questions
    Thank-you postX and LinkedIn, 4 November
    Day-two postOne worked example, 5 November
    Last-day email and post9 November
    Link sheetEvery URL, where it's used and who checked it

    The plan

    Day and time (Pacific)ChannelWhat goes out or happensPack pieceWho
    Tue 27 Oct, 9:00Internal30-minute kickoff: agree this plan, split the pack between you, answer the questions aboveThis planBoth
    Tue 27 Oct, 10:00X, LinkedInTeaser 1: the problem in your users' words ("40 things on the list, 6 free hours"). Opening to everyone on Tuesday 3 NovemberTeaser 1Marketing
    Tue 27 Oct, 14:00Product HuntStart the listing as a draft: tagline, description, gallery, makers' first comment. Set the date to 3 November (ask 5)PH listingMarketing, with screenshots from Product
    Wed 28 Oct, 10:00WebsiteBuild the launch site on a preview link: trial button, offer banner with the end date, beta quote and numbersLaunch siteProduct
    Wed 28 Oct, 14:00EmailLoad drafts of the reminder, launch and last-day emails into the email tool. Send test copies to both of youReminder, launch and last-day emailsMarketing
    Thu 29 Oct, 8:30X, LinkedInTeaser 2: how it works. On Sunday evening it reads the calendar and the to-do list and puts the tasks into real time slots. Screenshot or clip (ask 7)Teaser 2Marketing
    Thu 29 Oct, 11:00Direct messagesNote to the 38 beta teams: the launch date and time, a thank-you, and a question: would they share an honest comment on Product Hunt on the day?Beta DMProduct
    Thu 29 Oct, 15:00InternalPack freeze: every piece final, and every URL in the link sheetAll pieces, link sheetBoth
    Fri 30 Oct, 10:00WebsiteDry run on the preview: create a new account on a phone and on a laptop, connect a calendar, get a first plan, reach checkout and see the offer applied (asks 1 and 3)Launch siteProduct
    Fri 30 Oct, 13:00InternalWrite the reply bank: the ten likeliest questions. Examples: what calendar access it needs, which calendars and to-do apps work, the price after three months, how the offer works, what happens when the trial endsReply bankBoth
    Fri 30 Oct, 15:00X, LinkedInSchedule Teaser 3 (Sunday, X only) and Teaser 4 (Monday)Teasers 3 and 4Marketing
    Sat 31 OctNoneDay off. Nothing goes outNoneBoth
    Sun 1 Nov, 17:00XTeaser 3: it's Sunday evening, when Acme Planner plans a team's week. Open to everyone from Tuesday 3 November. Scheduled on Friday, so check it still shows 17:00 after the clocks go backTeaser 3Marketing
    Mon 2 Nov, 8:00EmailReminder email to the waitlist (1,240 people): open to everyone tomorrow, Tuesday 3 November, at 9:00 Pacific. Includes the launch-week offer and its end date, and says one more email will come when it's live. No Product Hunt link yet, because it doesn't exist until launch dayReminder emailMarketing
    Mon 2 Nov, 8:30X, LinkedInTeaser 4: tomorrow at 9:00 PacificTeaser 4Marketing
    Mon 2 Nov, 10:00WebsiteLink check 1, on the preview: every URL in every piece, tracking tags and the unsubscribe link. Check that replies to the emails reach a personLink sheetBoth, each checking the other's pieces
    Mon 2 Nov, 11:00WebsiteGet ready for a rush: error alerts on, the support inbox set up with the reply bank as saved replies, calendar connections tested againReply bankProduct
    Mon 2 Nov, 13:00Product HuntFinal check of the listing: tagline, gallery order, first comment, site link, launch date and timePH listingMarketing
    Mon 2 Nov, 15:00InternalWalk through launch day hour by hour. Turn on notifications for Product Hunt, X, LinkedIn and the support inbox. Early nightThis planBoth
    Tue 3 Nov, 8:30WebsitePut the launch site live: trial button, offer banner, beta quote and numbers. Point /waitlist where ask 4 saysLaunch siteProduct
    Tue 3 Nov, 8:40WebsiteLink check 2, on the live site: every URL in the link sheet. Do one full trial signup on a phone and one on a laptop, with a calendar connected and the offer shown at checkoutLink sheetBoth
    Tue 3 Nov, 9:00Product HuntListing goes live, or has been live since 00:01 (ask 5). Post the makers' first comment straight away. Open the listing in a logged-out browser and add its URL to the link sheetPH listingProduct
    Tue 3 Nov, 9:05EmailLaunch email to the waitlist. The main button starts a free 14 day trial. Add the Product Hunt link as "we're answering questions there"Launch emailMarketing
    Tue 3 Nov, 9:10XLaunch thread, pinned: the problem, how it works (with the clip), the beta quote, the offer, the trial link. Product Hunt link in the last post of the threadLaunch postsMarketing
    Tue 3 Nov, 9:15LinkedInLaunch post: the same story in one post, with the trial linkLaunch postsMarketing
    Tue 3 Nov, 9:30Direct messagesPersonal note to each beta team and to contacts who asked to hear: it's live, thank you, and an honest comment on Product Hunt would help. Ask for comments, not upvotes, because Product Hunt discourages vote requestsBeta DMProduct (beta teams), Marketing (contacts)
    Tue 3 Nov, 9:30 to 12:30Product Hunt, X, LinkedInComment block 1: answer every comment within 30 minutesReply bankMarketing on all three. Product takes Product Hunt questions about how planning works, plus the support inbox
    Tue 3 Nov, 12:30XMidday post: the beta quote, and "38 teams in the private beta since June planned an average of 31 tasks a week each." Trial linkLaunch postsMarketing
    Tue 3 Nov, 12:30 to 13:30InternalLunch in turns, 30 minutes each. Whoever is on covers Product HuntNoneBoth
    Tue 3 Nov, 13:30 to 16:00Product Hunt, X, LinkedInComment block 2, with the same splitReply bankBoth
    Tue 3 Nov, 15:00XAfternoon post: the most-asked question so far, answered in two lines, with the trial link. Last post of the dayLaunch posts, reply bankMarketing
    Tue 3 Nov, 16:00WebsiteHealth check: trial signups, failed calendar connections, checkout errors. Fix what can be fixed today and note the rest for tomorrowNoneProduct
    Tue 3 Nov, 16:00 to 17:30Product Hunt, X, LinkedInComment block 3: clear everything unanswered, then stopReply bankMarketing
    Tue 3 Nov, 21:00Product Hunt20-minute check for comments from other time zones, then done for the nightReply bankProduct
    Wed 4 Nov, 8:00InternalPull yesterday's real numbers: trials started, Product Hunt finishing position, comments answered. Use only numbers you can showThank-you postProduct (app), Marketing (Product Hunt and social)
    Wed 4 Nov, 9:00X, LinkedInThank-you post: thank you, where we are (yesterday's numbers), one thing people asked for. The offer ends Monday 9 November. Trial linkThank-you postMarketing
    Wed 4 Nov, 9:00 to 11:00Product Hunt, X, LinkedInComment block: overnight comments and replies to the thank-you postReply bankMarketing
    Wed 4 Nov, 9:00 to 12:00EmailCheck in with every team that started a trial yesterday but hasn't connected a calendar or seen a first planReply bankProduct
    Wed 4 Nov, 14:00WebsiteAdd the three most-asked launch-day questions, with answers, to the siteReply bank, launch siteProduct
    Wed 4 Nov, 16:00Internal30-minute review: what broke, what worked, anything to change for Thursday and MondayThis planBoth
    Thu 5 Nov, 8:30X, LinkedInDay-two post with one worked example: a meeting lands on Wednesday afternoon, and that afternoon's tasks move to free slots without anyone dragging blocks. Reuse the clip. The offer ends Monday 9 NovemberDay-two postMarketing
    Thu 5 Nov, 10:00Direct messagesMarketing follows up with anyone whose question got a late or partial answer. Product thanks the beta teamsReply bank, beta DMBoth
    Thu 5 Nov, 13:00WebsitePrepare the end of the offer: the site version without the banner, and the discount set to stop at the end time (ask 2). Test on a previewLaunch siteProduct
    Thu 5 Nov, 14:00EmailLoad and test the last-day email. Send it to the waitlist, leaving out anyone who has started a trial. [ask: Can your email tool leave out waitlist people who have already started a trial?]Last-day emailMarketing
    Mon 9 Nov, 8:00EmailLast-day email: the offer ends today at the end time (ask 2). Trial linkLast-day emailMarketing
    Mon 9 Nov, 8:30X, LinkedInLast-day post, with the same messageLast-day postMarketing
    Mon 9 Nov, end time (ask 2)WebsiteOffer off: banner down, discount stopped, site showing standard pricingLaunch siteProduct
    Mon 9 Nov, right after the end timeWebsite, Product Hunt, XFinal link check: trial signup still works, and no page, Product Hunt listing or pinned post still offers half price. Unpin the X launch threadLink sheetBoth

    The busiest channel is X on launch day, with three posts. Every other channel stays at one post a day or fewer.

    Three things most likely to go wrong

    1. A link or the signup fails when people arrive. You can't fix an email once it's sent. And the one action you want, starting a trial, depends on signup and calendar connection working for strangers on their own devices. Check:

    • Keep every URL in the link sheet, with every place it appears.
    • Send each email to yourselves and click every link from the inbox on a phone, not from the editor.
    • In the Friday dry run and the 8:40 launch-day run, use brand-new accounts and go all the way from calendar connection to checkout.
    • At 16:00 on launch day, look for failed calendar connections.

    2. Something goes out at the wrong time. There are three ways this can happen this week:

    • Product Hunt's day starts at 00:01, not 9:00 (ask 5).
    • The clocks go back on Sunday 1 November. If a tool is set to UTC or a fixed offset instead of Pacific time, anything scheduled before the change goes out an hour early.
    • An email tool or scheduler set to another time zone sends at the wrong hour.

    Check on Monday 2 November:

    • Open every scheduled post and email, and make sure the time and time zone match the table.
    • Make sure the email tool's account time zone is Pacific.
    • Confirm the Product Hunt launch time on its scheduling screen.

    3. The offer confuses people or doesn't work. "Teams who join in launch week" can mean starting a trial or paying, and a trial started on 3 November doesn't end until the 17th (ask 1). If checkout doesn't apply the half price, the complaints show up in public Product Hunt comments during launch week. After 9 November, a leftover banner or pinned post can keep offering a deal that has ended. Check:

    • Write the rule as one sentence, with the end time and time zone. Use that sentence word for word in the emails, the site, the Product Hunt listing and the reply bank.
    • Test checkout in the Friday dry run.
    • When the offer ends, search the site, the Product Hunt listing and pinned posts for "half price".
    Made with Claude Code · Playbook

    Markdown · Document

    Step 3: the launch week plan. A real run for Acme Planner, a made-up app, from its launch brief. Every gap the brief left is an [ask] for the team.

  • MarkdownLaunch day repliesExample output

    Launch day replies


    Here are the eight, each with a draft reply under 60 words. Some replies say "we'll confirm" and have an [ask] under them. Once you've filled in the [ask], replace that sentence with the answer.

    1. Price

    "How much is it?"

    You can try it free for 14 days. Teams who join in launch week get the first three months at half price, until Monday 9 November. We'll confirm the regular price and reply here.

    [ask: What is the regular price? Is it per team or per person? Does starting the trial need a card?]

    2. The launch offer and the trial

    "If we start the trial this week but pay after it ends, do we still get half price?"

    Teams who join in launch week get the first three months at half price, and the offer ends Monday 9 November. A trial started this week runs past that date, so we'll confirm exactly what counts as joining and reply here.

    [ask: Does a team get half price by starting the trial by 9 November, or by paying by 9 November? At what time, and in which time zone, does the offer end?]

    3. How it compares with what they use now

    "How is this different from the calendar and to-do app we already use?"

    Acme Planner reads your calendar and to-do list on Sunday evening and plans your week into real time slots, around the meetings everyone already has. When a new meeting appears, it moves the tasks, so nobody drags blocks around. One beta team's operations lead called it "the first planner we didn't abandon after two weeks."

    If the comment names another product, post this reply as it is and don't mention that product.

    4. Privacy

    "What does it do with our calendar data? Who can see it?"

    Acme Planner reads your calendar and to-do list so it can plan your week. We'll confirm exactly what access it asks for, where the data is kept and who can see it, and reply here with the details.

    [ask: What access does it ask for: read only, or read and write? Where is the data stored? Who can see it? Is it used for anything besides planning? How does a team delete it?]

    5. Setup time

    "How long does setup take? Do we have to wait until Sunday for our first plan?"

    Acme Planner plans each week on Sunday evening. We'll confirm how long setup takes for a team, and whether a team that starts midweek gets a plan before its first Sunday, and reply here.

    [ask: How long does setup take for a team of 2 to 10, and what does each person have to do? Does a team that starts on a weekday get a plan before Sunday?]

    6. Who it's for

    "Does it work for one person, or for a team bigger than 10?"

    Acme Planner is built for small teams of 2 to 10 people who share a calendar and keep missing deadlines. In the private beta, 38 teams have used it since June. We'll confirm how it works for one person or a larger team and reply here.

    [ask: Can one person use it alone? Is there a team size limit, or a different plan above 10 people?]

    7. Which tools it connects to

    "Which calendars and to-do apps does it work with?"

    It reads your team's shared calendar and your to-do list. We'll confirm the calendars and to-do apps it connects to at launch and reply here with the list.

    [ask: Which calendar services and which to-do apps does it connect to on launch day? Or do tasks live inside Acme Planner?]

    8. How it decides

    "How does it decide which task goes where? Is this AI?"

    It reads your calendar and to-do list, then plans tasks into real time slots around the meetings your team already has, and moves them when a new meeting appears. We'll confirm how it chooses which task goes in which slot, and whether AI is part of that, and reply here.

    [ask: How does it choose which task goes in which slot: deadlines, priorities, time estimates? Does it use AI? If it does, the reply can say so plainly without using "AI-powered".]

    Made with Claude Code · Playbook

    Markdown · Document

    Step 4: launch day replies. Replies to the questions people were likely to ask, from the brief only.

  • MailExample output

    Thank you, and where we are after launch week

    Acme Planner

    to Your subscribers

    Hello,

    Thank you for following Acme Planner's launch week.

    From Tuesday 3 November to Monday 9 November, 412 teams started a free trial, and Acme Planner was number 4 product of the day on Product Hunt. Thank you to everyone who tried it, left a comment or sent us a question.

    The question we heard most was whether Acme Planner works with Outlook or only with Google Calendar. [ask: Does it work with Outlook calendars today? If not, what can we say about when? I'll write the answer here in one or two sentences.]

    The launch offer, the first three months at half price for teams who joined in launch week, ended on Monday 9 November.

    If your to-do list says 40 things and your calendar says you have 6 free hours, you can start a free 14 day trial here: [ask: the trial page link]

    The Acme Planner team

    Made with Claude Code · Playbook

    Mail · Email

    Step 5: the recap email. Written from made-up launch numbers. It shares only the numbers marked public and leaves a gap for the Outlook answer the brief did not have.

  • MarkdownLaunch note (private)Example output

    Launch note (private)


    Launch week, Tuesday 3 November to Monday 9 November 2026. This note includes paid numbers, so keep it internal.

    What worked

    • Trials: 412 teams started a free trial.
    • Paid: 61 teams moved to a paid plan with the launch offer by Monday 9 November.
    • Product Hunt: number 4 product of the day, with 286 upvotes and 74 comments.
    • Waitlist email: 48% of the 1,240 people on the waitlist opened the launch email and 9% clicked, even though the button was wrong for the first 40 minutes.
    • Comments: they gave us a clear list of what people need to know before they try it (see below).

    What went wrong, and why

    1. The launch email button pointed to the waitlist page for the first 40 minutes. Anyone who clicked in that window landed on the waitlist page, not the trial page, and we sent nothing to put it right.

    • Why: [ask: How did the waitlist link end up on the button?] The usual causes are a button copied from an earlier waitlist email, or a link check done in the email editor instead of by clicking a sent copy.

    2. Our launch pieces didn't answer the three questions people asked most:

    • Does it work with Outlook or only Google Calendar? (asked 23 times)
    • What is the price per user after the half price months? (asked 11 times)
    • What data does it read from our calendars? (asked 9 times)

    Why: none of the three answers was in the launch brief, so they weren't in the pieces we built from it. People had to ask in public, one at a time.

    Three changes for next launch

    1. Make a wrong link harmless, and catch it before the send.

    • Send the launch email to ourselves first and tap the button from the inbox on a phone.
    • From launch time, point the waitlist page to the trial page, so an old link still lands somewhere useful.
    • Have a two-line correction email ready in case a link breaks anyway.

    2. Answer the top questions before anyone asks. Put calendar support, price per user after the offer, and what data it reads on the home page, in the launch email and in the makers' first comment on Product Hunt.

    3. Make the offer fit the trial.

    • Write the offer as one sentence that says whether starting a trial or paying is what counts.
    • Set the end date so a team that starts its trial on launch day can finish the trial before the offer closes.

    This launch, a trial started on 3 November ran until 17 November, after the offer had ended. We don't yet know how many teams that affected.

    To fix this week

    Product

    • Outlook. 23 asks in one week is the clearest product signal from launch. If it doesn't work with Outlook today, say so on the home page and at signup, so Outlook teams don't start a trial that can't connect.
    • Launch week trial teams. Decide whether teams that pay after 9 November get half price. Tell them before the first launch week trials end on 17 November.

    Site

    • Pricing: one clear line on the price after the half price months, per user if that's how you charge.
    • Calendar data: a short, plain page on what Acme Planner reads from calendars and what it doesn't.
    • Waitlist page: confirm it now sends people to the trial page. If the waitlist form records signup times, find anyone who signed up in those first 40 minutes and send them the trial link with a one-line apology.
    • Old offer: check that no page, Product Hunt listing or pinned post still offers half price.
    • Recap email: before it goes to the list, tap its trial link from a sent copy.
    Made with Claude Code · Playbook

    Markdown · Document

    Step 5: the private launch note. What worked, what went wrong and why, and three changes for next launch.

Works with

  • Claude
  • Claude Code
  • ChatGPT
  • +28 more

Not affiliated with or endorsed by the companies shown.

Product launchPlaybookMembers

Run launch week from waitlist to recap

One brief becomes a day by day launch plan, ready replies for launch day and an honest recap afterwards.

Version 1.0Updated 12 Oct 2026

Needs access to
None
Permissions
None
Time to result (our estimate)
20 minutes to set up, 60 minutes a run

Example

Example session

  1. Step 3: Plan the week
  2. You

    Pasted the Acme Planner launch brief and the step 3 prompt: Pacific time, two cofounders, one on product and support, one on marketing.

  3. Your AI

    Tuesday 3 November is also US election day. Results will fill feeds in the evening, so the last launch post goes out at 15:00 and the evening is for replies only.

  4. Step 4: Prepare launch day replies
  5. You

    Pasted the step 4 prompt.

  6. Your AI

    Drafted replies to the eight likeliest questions, with an [ask] wherever the brief had no answer.

  7. Step 5: Write the recap
  8. You

    At the end of launch week, after the offer closed, pasted the step 5 prompt with our launch numbers.

  9. Your AI

    The offer has already ended. It closed on Monday 9 November, two days ago, so the email can't remind people that it's ending. Instead it says the offer ended.

What comes out
MailExample output

Thank you, and where we are after launch week

Acme Planner

to Your subscribers

Hello,

Thank you for following Acme Planner's launch week.

From Tuesday 3 November to Monday 9 November, 412 teams started a free trial, and Acme Planner was number 4 product of the day on Product Hunt. Thank you to everyone who tried it, left a comment or sent us a question.

The question we heard most was whether Acme Planner works with Outlook or only with Google Calendar. [ask: Does it work with Outlook calendars today? If not, what can we say about when? I'll write the answer here in one or two sentences.]

The launch offer, the first three months at half price for teams who joined in launch week, ended on Monday 9 November.

If your to-do list says 40 things and your calendar says you have 6 free hours, you can start a free 14 day trial here: [ask: the trial page link]

The Acme Planner team

Made with Claude Code · Playbook

Fit

About this item

Launch week goes wrong in small ways: a link that points to the wrong page, a number that differs between the email and the thread, a question nobody prepared for. This playbook runs the whole week from one launch brief, so the plan, the replies and the recap all say the same thing.

The example is a real run for Acme Planner, a made-up planning app, picking up from its announcement pack, with made-up launch numbers for the recap.

What you get

  • The announcement pack and an optional teaser, from their own items
  • A day by day plan from a week before launch to two days after, with times and owners
  • Replies for the eight questions you are most likely to get on launch day
  • A recap email for your list and a private note on what to change next time

Good fit

  • Founders and small teams launching a product or a big update
  • A first Product Hunt launch

Not for

  • Large launches with a PR agency and paid media

Who it is for

Skill level: Use AI weekly

How to use

The steps

  1. Step 1: Write the announcement pack

    Turns your launch brief into waitlist copy, the launch email, an X thread, a LinkedIn post and a Product Hunt listing.

    Runs in Claude

    Launch announcement pack from one briefTemplateMembers
  2. Step 2: Make the teaserOptional

    Plans an eight second vertical teaser and writes the image and motion prompts for it.

    Runs in Claude

    Make an eight-second launch teaserPromptMembers
  3. Step 3: Plan the week

    Lays out every email, post and check from seven days before launch to two days after, with times and owners.

    Runs in Claude

  4. Step 4: Prepare launch day replies

    Drafts short replies to the eight questions people are most likely to ask, from the brief only.

    Runs in Claude

  5. Step 5: Write the recap

    Turns your launch numbers into a recap email for your list and a private note on what to change next time.

    Runs in Claude

How to use it

Download the playbook and open README.md. Each step says which tool it runs in.

Trust

What's inside

  • 03-launch-week-plan.md1.1 KB
  • 04-launch-day-replies.md677 B
  • 05-recap.md911 B
  • README.md2.2 KB

File names and sizes only. The files come with membership.

Permissions required

None

Requirements

You bring

  • A filled-in launch brief, from the announcement pack
  • Your launch date, time zone and who on the team does what
  • Your launch numbers, when launch week is over, for the recap

Tested on

VerifiedTested in the last 90 days
  • Claude Code · Claude Opus 5.512 Oct 2026 · Steps 3 to 5 for a made-up app, with made-up launch numbers for the recap. Steps 1 and 2 have their own examples.

Known limitations

  • It plans and drafts. Scheduling, posting and sending are done by you or your tools.
  • The recap only knows the numbers you give it.

More

Questions

Do I need the announcement pack first?
Yes. Every step reads the same launch brief, which comes from the announcement pack template. That keeps the dates, numbers and offer the same everywhere.
Is the teaser required?
No. It is optional, and it needs an image and video tool with credits. The plan works without it.
Does it post anything for me?
No. It writes the plan, the replies and the recap. You or your scheduling tool post them.