Use case · Steam launch
Four weeks before launch,
what belongs in each week?
Store-page work, demos, Next Fest, and launch content can all collide. Plan the order early so you are not filling gaps at the last minute.
Week one: prepare assets and selling points
Do not rush into daily posting. Select GIFs that explain the core gameplay, visual highlights, screenshots of characters and the world, and one sentence that helps players understand the game immediately.
Prepare this week
- 3 core-gameplay assets
- 2 visual-highlight assets
- 1 one-sentence game description
- 1 player FAQ
Weeks two and three: prepare platform versions from the same assets
Create platform-specific versions around the same theme and add them to the promotion plan. Professional prompt recipes reduce repeated writing, while the promotion coach points out the kinds of content the project still lacks.
Change the expression, not the selling point
Keep the core theme consistent, but adapt the opening, length, tags, and action prompt to each platform's reading habits.
Week four: collect feedback and prepare launch reminders
Collect recurring player questions, creator feedback, and store-page information. By now, you can begin to see which descriptions are easiest to understand and which assets create discussion.
Final pre-launch check
Confirm that priority assets, each platform's prepared publishing package, the store link, and creator Keys are ready. Keep the strongest content for the first post-launch update cycle.
Next step
Put the four pre-launch weeks on one calendar.
Schedule the core content first, then add the rest as the project progresses.