Learn from the first batch before sending the next

Record what happened, not what you hope happened

Move a creator to Contacted only after you send the message. Record the date, contact channel, and the version of the pitch in your notes. Move to Replied when a person answers, even if the answer is no. Move to Covered only when you have a published link.

A copied draft is not a sent email. A sent key is not a redeemed key. A reply is not a sale. Keeping those distinctions makes a small campaign more useful than a larger spreadsheet full of assumptions.

Diagnose the stuck step

• No valid contact: revisit the channel's current contact preference and correct your list.
• Messages delivered but no replies: review fit, the opening, timing, and whether trying the build is easy. A small sample cannot identify one cause with confidence.
• Interest but no coverage: ask whether access or setup is blocking someone who has already engaged. Respect their schedule and editorial choice.
• Coverage but little store activity: inspect the link, the audience fit, and the store page before judging the creator.

Keep follow-ups useful

If the creator has not stated a different preference, consider one short follow-up after roughly a week. Treat that as a starting convention, not a guaranteed best time. Add a useful update or make access easier; repeating the entire pitch does not add value. Stop when they decline and respect any request not to be contacted.

PlayScout can remind signed-in users about unanswered outreach. Use a reminder as a prompt to review the conversation, not an instruction to send another message.

Change one thing and compare fairly

For the next small batch, choose one change: better comparison games, a clearer gameplay link, or simpler access. Keep a note of which changed. Compare batches over similar time windows and distinguish your own tests from outside interest.

If you use campaign links, Steamworks UTM Analytics can help inspect attributed visits and conversions, subject to its reporting limits. Movement in overall wishlists on a coverage day is a clue, not proof that one video caused it.

Steamworks: UTM Analytics ↗