Launch week is chaos. You know this intellectually. But nothing prepares you for the actual experience of juggling bug reports, community management, press requests, social media, and basic human needs like sleep and food all at once.
The developers who navigate launch week successfully aren't calmer or more talented. They're more prepared. They front-loaded the decisions and preparation so launch week itself becomes execution, not improvisation.
Here are 47 specific actions across the week before, day of, and week after launch.
One Week Before Launch (Days -7 to -2)
Steam Store Finalization
-
Final store page review. Read every word of your description out loud. Check all screenshots display correctly. Verify your trailer plays without issues.
-
Capsule art at all sizes. View your Small Capsule (462x174) in context with competitor games. If it doesn't pop, you have one week to fix it.
-
Tags audit. Are your top 5 tags the most specific sub-genres that describe your game? Push generic tags to lower positions.
-
Release date and time. Pick a specific time, not just a date. Tuesday-Thursday tends to work best. Avoid major AAA launch days.
-
Pricing double-check. Confirm regional pricing. Decide on launch discount (10-15% is common for visibility).
Press Kit Polish
-
Update screenshots to final build. Remove any that show outdated art or cut features.
-
Launch trailer live and downloadable. YouTube embed plus direct MP4 download link.
-
Review quotes if available. Add any positive coverage from preview builds or early access.
-
Verify all download links work. Test the ZIP file. Test individual asset downloads.
-
Contact information prominent. Your press email should appear at least twice on the page.
Communication Prep
-
Draft launch day announcement. Write the Steam announcement, social media posts, and newsletter email now. Not at 3 AM on launch day.
-
Prepare social media assets. Launch key art formatted for Twitter, Discord, Reddit. Don't scramble for images during the chaos.
-
Newsletter ready to send. If you have a mailing list, the launch email should be drafted and scheduled.
-
Discord announcement drafted. Your community deserves a proper launch message, not a hasty one-liner.
Technical Preparation
-
Final build uploaded and tested. Play through the first 30 minutes on a clean install. Verify achievements trigger. Check save systems work.
-
Verify Steam achievements, trading cards, cloud saves. Each of these can fail independently. Test them.
-
Emergency patch process documented. Know exactly how to deploy a hotfix if something critical breaks at launch.
-
Backup everything. Source code, build files, marketing assets. Paranoia is appropriate.
Community and Support
-
Steam Discussion forums set up. Create pinned topics: Bug Reports, General Discussion, Tips & Tricks.
-
Support email monitored. Someone needs to be checking this throughout launch week.
-
Known issues documented. If there are minor bugs you're aware of, list them publicly. Players appreciate transparency.
Two Days Before (Days -2 to -1)
Final Checks
-
Third-party play test. Have someone who hasn't touched the game play through the opening. Fresh eyes catch what you've become blind to.
-
Time zone math. Confirm when your game goes live in your key markets. Coordinate any announcements accordingly.
-
Creator embargo reminder. If you gave early access to content creators with an embargo, remind them when the embargo lifts.
-
Personal preparation. Clear your schedule. Tell family/roommates you'll be unavailable. Stock up on easy meals.
Press and Creators
-
Final press reminder email. A brief "launching in 48 hours, here's the press kit link" to your priority contacts.
-
Creator check-in. Confirm any coordinated coverage is still planned.
-
Verify key distribution. Everyone who received a review key should have redeemed it successfully.
Launch Day (Day 0)
The Morning
-
Verify the game is actually purchasable. Open an incognito browser, search for your game, confirm you can add to cart.
-
Steam announcement published. Your launch announcement should be one of the first things that happens.
-
Social media posts live. Hit publish on all platforms. Your drafted posts are ready. Just click.
-
Newsletter sent. Your subscribers should hear about launch from you, not accidentally.
-
Discord pinged. Let your community know it's real.
Active Monitoring
-
Watch Steam reviews. The first few reviews set the tone. Respond thoughtfully to constructive criticism. Don't respond to trolls.
-
Monitor social mentions. Search your game name on Twitter, check YouTube for videos dropping, watch for Reddit posts.
-
Community questions answered. Be present in your Discord and Steam forums. Engagement signals matter.
-
Bug triage. Not every bug needs an immediate patch, but you need to know what's breaking for players.
If Things Go Wrong
-
Critical bug discovered: assess scope. How many players are affected? Is the game unplayable or just annoying?
-
Communication over silence. If something is broken, say so publicly. "We're aware of X and working on a fix" buys enormous goodwill.
-
Emergency patch if necessary. Deploy if the issue is severe. Valve's review is typically fast for emergency fixes.
