Before choosing channels

Start with evidence, not volume

01Show the experience

Use real gameplay, mechanics, decisions, progress, and useful development context.

02Match the audience

Choose communities and creators because the game fits their interests, not because the audience is large.

03Measure the next step

Track qualified visits, demo plays, follows, wishlists, signups, or sales instead of raw posting volume.

Four-week planner

Set the real constraints

Plan readiness62%

Game and objective Game title Release stage Primary four-week goal Target audience Player-facing hookExplain the experience without awards, rankings, or vague superlatives.0 / 280

Capacity Marketing time each week: 4 hours Optional monthly test budget

$

The plan works at $0. A budget only adds a small validation experiment.

Strongest material available

Gameplay clips Playable demo Distinct artwork Developer story Technical insight Community moments

Channels you can maintain

Choose only channels you can update and answer consistently. Two well-maintained channels are better than six abandoned ones.

Website or devlog YouTube or video Short-form social Community or Discord Creators and press Relevant forums or events

Generated planChoose the strongest proof and channels

Four-week indie game marketing plan

Your game

Focus 4 hours per week on qualified store visits for a clearly defined player audience.

Primary message

Add the player-facing hook before publishing or pitching the plan.

Week 1Build the campaign foundation4 hours
- Write one audience statement for the players most likely to value the game.
- Use this message consistently: write one accurate player-facing hook.
- Choose qualified store visits as the only primary goal for this four-week cycle.
- Prepare the first proof asset around real gameplay clips and the developer story.
- Update the official game page with accurate screenshots, release status, requirements, developer identity, support, and one measurable call to action.
Week 2Publish useful proof4 hours
- Create one substantial source piece showing real gameplay clips and the developer story, then adapt it for each selected channel instead of reposting identical copy.
- Show the current build honestly. Explain the mechanic, decision, problem solved, or lesson behind what players see.
- Link every adaptation to the same appropriate next step and label campaign links consistently.
- Cut one or two short clips from the source piece, add readable context, and ask a specific question that can start a real conversation.
Week 3Start relevant conversations4 hours
- List ten creators, journalists, communities, events, or curators whose demonstrated interests genuinely match the game.
- Read submission rules and recent work before contacting anyone. Remove poor-fit targets.
- Write a short individualized introduction that explains why the game fits that person's audience and points to real gameplay clips and the developer story.
- Send a small batch of relevant pitches with the press kit, playable access when appropriate, clear disclosure, and one polite follow-up date.
Week 4Make the next action clear4 hours
- Publish a direct update for the current stage: playable demo, with one primary action tied to qualified store visits.
- Review which sources produced qualified visits and meaningful actions. Separate useful signals from raw impressions.
- Answer replies, thank people who contributed, correct outdated information, and record recurring player questions.
- Choose the strongest result from real gameplay clips and the developer story as the starting point for the next four-week cycle.
- Stop or redesign work that consumed time without reaching the intended audience.

Measure the goal

Track visits to the intended game page, source or campaign tags, meaningful next actions, and the messages that attract the right players rather than accidental clicks.

Quality guardrails

Use accurate footage and claims from the current build.
Participate in communities before sharing promotional links and follow each community's rules.
Do not buy reviews, fabricate engagement, mass-post identical messages, or imply coverage is guaranteed.
Record what earned qualified attention, stop low-value work, and reuse strong source material thoughtfully.

Build the supporting material

Turn the plan into useful public pages

Press kit builder

Package the pitch, release facts, media, developer background, and contact information.

Open builder → Editorial submission

Pitch a specific development story, technical lesson, demo, release, or unusual design decision.

Prepare a pitch → Release readiness

Check the build, ownership, media, delivery, support, identity, and payout requirements.

Run checklist →

Ready for a permanent storefront

Give every campaign a stable destination

Connect the plan to a searchable game page and developer profile rather than relying entirely on temporary social posts.

Start Developer Onboarding All Developer Tools