How to find your first 10 playtesters (without a community or a budget)

Every playtesting guide assumes you already have an audience. Most indie studios do not. No Discord server, no mailing list, no wishlist page with traffic — just a build and the uncomfortable question of who is going to play it.

The good news: you do not need a crowd. Ten testers who actually play your genre will tell you more than a hundred random players ever could. This guide is about finding those ten, asking them the right way, and making sure they come back for the next round.

Why ten, and not a hundred

Playtesting does not scale the way marketing does. The fifth tester repeats most of what the first four found; the tenth adds a little; the fiftieth adds almost nothing new about the same question. What matters is not volume but fit: people who play games like yours, on the platform you are building for, who will tell you the truth.

Ten is also the number you can manage personally. You can read every answer, reply to every bug report, and thank every tester by name. That personal loop is your only real advantage over bigger studios — use it.

Before you ask anyone

Three things need to be ready before you send a single message.

A build that starts. It does not need to be finished, but it needs to launch, run for the length of the session you are asking for, and not corrupt anyone's day. If the build is fragile, say so and say exactly what to avoid.

A one-paragraph pitch. What the game is, what genre it is, what platform it runs on, and what you are testing this round. Two or three sentences. If you cannot write this, you are not ready to recruit.

A clear ask. How long the session takes, what you want them to do, and when you need it done. "Play for 30 minutes this week and answer a short form" gets answers. "Check out my game" gets silence.

Where the first ten actually come from

Start close, but do not stop there.

Friends and family — with a warning. They will play, but they will be kind, and kindness is the enemy of a playtest. Use them to verify the build runs and the form makes sense. Do not use their opinions to make design decisions.

Genre communities. Every genre has a home: a subreddit, a Discord server, a forum, a hashtag. Players there already understand the language of your game, which means their feedback starts at a level your friends cannot reach. Read the community rules before posting — most have a specific day or channel for feedback requests, and respecting that is the difference between a welcome and a ban.

Playtesting communities. Places that exist specifically to connect developers and players: subreddits like r/playmygame, playtesting Discords, and platforms built for this. The people there signed up to test games. They are the warmest audience you will find.

Local and online events. Game jams, meetups, and online showcases put your build in front of people who chose to look at new games. One evening at a local meetup can fill half your list.

Your own players, if you have any. A previous game, a jam entry, a demo — anyone who ever played something you made is a candidate. A short, honest message to twenty past players converts better than a post to two thousand strangers.

How to ask so people say yes

The difference between a request that gets ignored and one that gets ten volunteers is almost never the game. It is the ask.

Be specific. Name the genre, the platform, the time commitment and the deadline. Specificity reads as respect for the other person's time.

Say what is in it for them. Early access to something nobody else has played, a credit in the game, a key at launch, a small reward per session. It does not have to be money — it has to be something.

Make it easy to start. One link, one form, one session. Every extra step between "yes" and playing costs you testers.

Ask individuals, not crowds. A personal message to someone who posted about loving your genre beats a broadcast to a server of five thousand. Ten personal messages a day for a week is a full roster.

Filter for fit, not enthusiasm

The most dangerous tester is the enthusiastic one who never plays your genre. They will finish the session, give you detailed feedback, and every word of it will describe a game you are not making.

Two questions filter most of it: what do you usually play, and on what platform? If the answers do not overlap with your game, thank them and keep looking. A smaller panel of the right people beats a bigger panel of willing ones.

Keeping them for the next round

Finding ten testers is work. Keeping them is cheaper — and a tester who comes back already knows your game, so their second round of feedback is worth twice the first.

Close the loop. When the playtest ends, tell them what you learned and what you changed because of them. Nothing makes a tester come back faster than proof that their hour mattered.

Pay what you promised, when you promised it. Whatever the reward was — a key, a credit, a small amount — deliver it on time. The indie playtesting world is small and it talks.

Do not overuse them. A tester you ask every week burns out in a month. Rotate, and keep the asks short.

Mistakes that cost you your first ten

Recruiting before the build is ready. A broken first session does not get a second chance.

Asking everyone you know at once. If the first round reveals the form is broken, you have burned your whole list on a broken form. Recruit in small waves.

Treating testers as free marketing. A playtest is research. If the message smells like promotion, the feedback will be promotion-shaped.

Going silent after the session. Testers who never hear back do not test again — for you or for the next studio.

How Playtest Hub helps

Playtest Hub exists so the logistics of this guide stop being the hard part.

As a studio, you create a playtest for your game, set the testing period and the maximum number of testers — ten is a perfectly good number — and write the feedback form with the six question types. Testers apply, and you choose who joins based on their profile: the genres they play and the platforms they use, so filtering for fit takes minutes instead of guesswork. The build link is shown only to the testers you approved, and when the session ends, the Results page summarises that playtest on its own — participants, response rate, and a breakdown per question. You can reward participation with Credits, and the tester sees exactly what they earned.

Your first ten testers are out there, in the communities your genre already has. Prepare the build, write the honest ask, and go find them one message at a time.