Tips for Outreach (Part 2): Stop Making People Guess What Build You’re Offering

Name the build clearly — or people will just move on

If your email says “demo” but what you’re actually sending is a Steam Playtest invite, an Early Access key, a closed beta build, or a time-limited trial, you’re making the receiver do detective work. Press and creators won’t. They’ll just skip — because confusion reads like risk.

If you missed Part 1 (deliverability + credibility foundations), start here first:
Tips for Outreach – Part 1: Make Sure Your Emails Actually Arrive

Playtest gameplay video (example)

Video credit: Fix Gaming Channel.

---

This gets even messier for solo devs, because you’re juggling store terms that sound similar but behave very differently. The fix is simple: name the access model clearly, then add two or three clarifier details so nobody misunderstands the status of the game.

1) The quick rule: label the build, then add 3 clarifiers

Pick one label (Demo / Trial / Beta / Playtest / Early Access / Prologue), then add these three clarifiers right under it:

• Cost + access: free / subscription / key / request access / preorder / invite-only
• Time limit: none / weekend / X hours / limited event dates
• Content scope: vertical slice / full game / opening chapter / multiplayer test / technical test

That’s enough to remove most confusion — without you writing a wall of text.

2) Demo vs Trial vs Beta vs Playtest vs Early Access (plain-English definitions)

Here’s the clean version people actually understand:

What you call it	What it usually means	Where people get confused
Demo	A limited slice meant to show the game. Usually free. Usually no time limit.	People assume “demo = free,” so “free demo” can sound redundant unless you’re contrasting it with a trial.
Trial	The full game, but time-limited (hours/days/weekend). Often tied to a subscription or promo.	Lots of people call this a “demo” even though it’s the full game with a timer.
Beta	Pre-release access for testing (or marketing). Can be open, closed, timed, or invite-only.	“Beta” can mean anything from real testing to a hype event. You must clarify access + dates.
Playtest	A controlled test build, often invite-based, often focused on feedback/QA.	Some devs say “demo key” when it’s actually “request access” or limited invites.
Early Access	A paid, in-development release. It’s the product (not a preview), and updates over time.	Creators may treat it like a finished launch unless you state “in development” clearly.
Prologue	A standalone “opening chapter” style release that can function like a permanent on-ramp.	People confuse it with a demo — but it often behaves more like its own release.

If you’re solo: don’t overthink this. The goal is not perfect terminology — it’s removing doubt for the person receiving your email.

3) Why people say “Free Demo” (and when it’s actually useful)

You’re not wrong to feel that “Free Demo” sounds off. Traditionally, demos were assumed free. The reason the wording spread is simple: the word “demo” got muddy.

• Some “demos” are actually full-game trials with a timer (often subscription-linked).
• Some “demos” are actually betas (timed events), or playtests (invite access).
• Some “demos” now have their own store presence on PC storefronts, so people started adding “free” as a fast signal: “no timer, no subscription, no key.”

My recommendation for dev outreach:

• Use “Demo” by itself if it’s the normal thing: free, no timer, publicly available.
• Only add “free” when you need to contrast it with a trial or subscription: “Demo (no time limit)” vs “10-hour trial (subscription).”
• Never call a playtest invite a demo. That’s the fastest way to trigger confusion.

4) Copy-paste blocks you can use in your outreach emails

Drop one of these near the top of your email (right after your one-line pitch). It makes the game’s status instantly clear.

Option A — Demo (public)

Build status: Demo (public) — free, no time limit.
Scope: [e.g., first 30–60 minutes / one level / a vertical slice].
Access: [Steam demo button / Itch page / direct link].

Option B — Trial (full game, time-limited)

Build status: Full game trial (time-limited).
Time limit: [e.g., 10 hours / weekend / ends on DATE].
Access: [subscription / promo / platform program].

Option C — Beta (event testing or preview)

Build status: Beta (pre-release testing).
Dates: [START DATE] to [END DATE].
Access: [open / closed / key / preorder / invite].
What we’re testing: [servers / balance / onboarding / performance].

Option D — Playtest (invite-based feedback)

Build status: Playtest (invite-based).
Access: [Steam “Request Access” / keys / whitelisted emails].
Focus: [bug reports / balance / stress test / onboarding].
Notes: [NDA? embargo? streaming allowed?].

Demo videos (examples)

Video credit: Fix Gaming Channel.

Video credit: Fix Gaming Channel.

Subject line templates that reduce confusion

• [GAME NAME] — Demo now live (public, no time limit) — coverage if interested
• [GAME NAME] — Steam Playtest invite (closed test) — feedback welcome
• [GAME NAME] — Beta test dates inside — streaming allowed / not allowed
• [GAME NAME] — Early Access review key — in-development build

Common outreach mistakes that create instant doubt

• Saying “demo key” (demos usually don’t need keys). If it needs a key, call it a beta build, preview build, or playtest access.
• Not stating whether streaming is allowed. If you don’t say it, many creators assume it’s risky.
• Not stating time limits. If it ends in 48 hours, say so clearly.
• Calling something a “demo” when it’s actually the full game on a timer (that’s a trial).

Related reading (Fix Gaming Channel)

• Tips for Outreach – Part 1: Make Sure Your Emails Actually Arrive
• Indie Dev Playtest Guide (Part 2): From First Keys to Useful Feedback
• Fix Access — Developer Services (if you want help running outreach + assets properly)

---