Quick answer: Press outreach fails on fit, not volume: build a short list of writers who demonstrably cover games like yours, send a personal three-sentence email — why them, what the game is in one hook, what you're offering (key, embargo, assets) — with the trailer linked and everything one click away. Expect mostly silence, follow up once, and treat every reply as a relationship, not a transaction.
Press outreach fails on fit, not volume: build a short list of writers who demonstrably cover games like yours, send a personal three-sentence email — why them, what the game is in one hook, what you're offering (key, embargo, assets) — with the trailer linked and everything one click away. Expect mostly silence, follow up once, and treat every reply as a relationship, not a transaction. That's the short version — the sections below get into the how, the why, and the mistakes worth dodging.
The list is the work
A hundred targeted contacts beat ten thousand scraped ones. Build yours from evidence: who covered the games yours will be compared to (search outlet archives), who reviews your genre on YouTube and smaller sites, whose taste matches your game's vibe. Note their beat and the angle that fits them. Freelancers matter — they pitch outlets you can't reach.
Smaller outlets and genre-focused creators say yes far more often than the giants, and their audiences are denser with your buyers anyway. The IGN review is a lottery ticket; the beloved genre YouTuber is a plan.
The email that survives triage
Subject line: concrete and scannable ('[Game] — roguelike where the dungeon is alive, launches March 12, keys inside'). Body: one line of why-them ('you covered [comparable], this lives in that space'), two lines of what the game is (the hook, not the feature list), one line of the offer (key attached or on request, embargo if any, presskit link), trailer linked. Done. Under 150 words, every asset one click away.
Attach or instant-deliver the key when you can — each additional step (reply, form, wait) loses a percentage of busy writers. And send from a real address you check hourly during launch windows.
Timing, follow-ups, and the long game
Lead times: 2-4 weeks pre-launch for reviews (longer for bigger outlets), mornings midweek for opens. Follow up exactly once, a week later, brief and graceful — replies often come from the nudge, and more than one nudge burns the bridge. Track sends and responses in a sheet; outreach is a campaign, not an email.
Play it across releases: thank people who cover you, deliver on embargoes, stay findable, and don't spam the uninterested. The writer who passed this time knows your name next time — indie press coverage is mostly accumulated familiarity finally meeting the right game.
Marketing is a generosity game
The indie marketing that works rarely looks like advertising. It looks like sharing something genuinely interesting: a clip that makes people grin, a devlog that teaches something, a thread about a problem you solved. People share what makes them look good for sharing it.
So lead with the most interesting true thing about your game, not with the ask. 'Wishlist now' earns nothing by itself; a great 15-second clip earns the wishlist without asking twice.
Consistency compounds, virality doesn't
Every indie knows one game that blew up from a single tweet, and that story wrecks more marketing plans than it helps. Viral moments are lottery tickets. The reliable curve is slower: post regularly, get a little better each time, and let followers accumulate like interest.
Pick a cadence you can sustain on your worst week — one post, one clip, one devlog — and hold it for months. The audience you build that way actually shows up on launch day.
Plan for the bugs you won't see coming
Whatever else you take from this, build yourself a way to hear about problems. Once your game is on other people's machines, most failures happen out of sight: the crash on hardware you don't own, the save that corrupts once in fifty exits, the bug players mention in a review instead of a report.
A lightweight crash and bug reporting setup — even just Bugnet's free tier wired into your engine — turns that silence into a fixable list. The devs who look calm at launch aren't luckier; they just see their problems earlier.
Putting it to work
Don't try to act on all of this at once. Pick the one change that costs you the least and pays the most this week, do it, and see what actually happens before reaching for the next.
Most of this rewards steadiness over intensity. A small improvement made every week, checked against how real players respond, outruns any single burst of effort — in this corner of game development and every other one.
Show up where your players already are, lead with the interesting thing, and keep the cadence.