Rebupl · launch desk · 02 Plan it
Launch Visibility Planner
7-day channel plan
A seven-day plan for the channels that fit your audience, with the effort counted and the order explained.
UnlockedIncluded for every maker
Compose
Launch datethe drop you are planning around
Hours per daythe plan will flag an overload
Goalthe one action the week is asking for
Audiencethis decides the channel order
Channelspick only what you can work
The planT-3 to T+3 · updates as you edit
01 · Xpublic build notes
02 · LinkedInthe longer story
- T-3Fri, Nov 6Set the table1h 20m
- Tighten the one-line pitch until a stranger can repeat it.
- Check the landing page on a phone; the first screen is the whole pitch.
- Post the launch on X with the outcome first; put the link in the first reply.
- T-2Sat, Nov 7Warm the room1h 25m
- Tell five people who already have the problem; ask what they expect.
- Write a build-in-public note for LinkedIn.
- Post the build note on LinkedIn; lead with the problem, not the feature list.
- T-1Sun, Nov 8Load the canon1h 15m
- Write and schedule the launch post. Do not leave it for the morning.
- Prepare a short reply you can adapt in every channel.
- Line up three people who will share it honestly — no fake votes.
- LaunchMon, Nov 9Launch2h 35m
- Publish the product and open the launch post.
- Post to X, LinkedIn; give each channel its own opening line.
- Reply to every comment for the first two hours.
- Ask for one small action: try it and reply with the first thing that breaks.
- T+1Tue, Nov 10Work the thread1h 30m
- Share the best question and your answer; it is the next post.
- Send five personal notes to people who showed interest.
- Ask ten visitors what was confusing; write the exact words down.
- T+2Wed, Nov 11Make the second wave1h 30m
- Post a build note: what changed between the idea and the launch.
- Go back to X with the best proof point.
- Turn the questions into an FAQ on the page.
- T+3Thu, Nov 12Collect the signal1h 5m
- Write a short recap: what you expected vs. what happened.
- Ask for one next action, not a vague “feedback welcome”.
- Put the next drop on the calendar while the week is still warm.
Over the week you have10h 40m of work · 7h available
Cut the lowest-leverage task or add hours. The replies on launch day are the last thing to drop.
Communities first: a useful native post beats a link on a timeline. Then X for the build note. The plan is ordered T-3 to T+3, not a calendar integration.
Run sheetbuilt from your inputs
- 01Pick the launch date first — every task is pegged to it.
- 02Choose only the channels you can actually work that week.
- 03If the load exceeds your hours, cut the lowest-leverage task rather than the replies.
