What is in the marketing plan template?

One row per task, in 7 phases from the hook to the first discount after launch. Each row has a goal, a channel, a task, an owner, one metric and a date. The 14 rows below are a start. Delete the rows that do not fit your game, and add your own.

The Task column holds the Steam rules that have fixed timing, such as the review time of a store page and the Next Fest deadlines. So when you put in your own dates, you can see at once which tasks are already late.

You can copy the table into a spreadsheet, or download the same rows as a CSV file. This page is the sheet. For the reasons behind each phase, read the full guide to marketing an indie game.

Marketing plan template for an indie game on Steam: one row per task. Replace "Your name" and "Your date" with your own.
PhaseGoalChannelTaskOwnerMetricDate
1. PositionOne hook and a list of comparable gamesResearchWrite the hook in one sentence. List 5 to 10 comparable games with price, tags and review count.Your nameHook and list agreedBefore the Steam page
2. Steam pageComing Soon page liveSteamSubmit the page for review at least 7 business days before the day you want it live.Your namePage live on the planned dayYour date
2. Steam pageFirst wishlistsTrailer and social postsPublish the announcement trailer with one tagged Steam link per channel.Your nameWishlists in the first week, by sourcePage launch day
3. WishlistsSteady wishlists each weekTwo or three channels you can keep upPost every week. Use one tagged link per channel and per beat.Your nameWishlists per week, by utm_sourceEvery week
3. WishlistsCreator coverageYouTube and TwitchSend the demo or a key to creators. Give each creator their own link.Your nameVisits and wishlists per creator linkYour date
4. DemoDemo liveSteamRelease the demo. Send the demo notification to wishlisters within 14 days.Your nameDemo players and wishlists per dayYour date
4. DemoA first session that holdsGame analyticsRead the first session funnel of the demo build and fix the largest drop.Your nameShare of demo players who reach the endOne week after the demo
5. Next FestDemo approved in timeSteamSubmit the demo for build review 3 weeks before the fest, or 5 weeks before for the Press Preview.Your nameDemo approved3 to 5 weeks before the fest
5. Next FestPress and creators play earlyEmailSend press and creators a tagged link before the Press Preview, which starts 11 days before the fest.Your nameVisits and wishlists by link2 weeks before the fest
5. Next FestWishlists in the fest weekSteam, streams and postsPost and stream each day. Log daily wishlists.Your nameWishlists in the week, over your normal weekFest week
6. LaunchA strong first weekSteamSet the release date and the launch discount before release. Steam notifies wishlisters at release.Your nameFirst-week sales per launch wishlistLaunch day
6. LaunchA stable buildGame analyticsWatch crash-free sessions and returned units each day of launch week.Your nameCrash-free sessions and refund rateLaunch week
7. After launchReturning playersSteamShip a major update and post an announcement for it.Your nameReturning players and sales in the next 7 daysYour date
7. After launchMore sales from wishlistsSteamRun the first discount of 20% or more, at least 30 days after release.Your nameUnits sold in the sale, over a normal weekYour date

Sources: Steamworks Coming Soon, Steam Next Fest, Wishlists and Discounting documentation.

How do I fill in each column?

Fill the columns from left to right, and keep each cell short. A row that needs two owners or two metrics is two tasks, so split it.

  • Phase: where the game is. Position, Steam page, wishlists, demo, Next Fest, launch or after launch.
  • Goal: the result you want, in a few words. "Coming Soon page live" is a goal. "Do marketing" is not.
  • Channel: the one place where the task happens, such as Steam, YouTube, email or your game analytics.
  • Task: one action that a person can finish. Start with a verb.
  • Owner: one name. On a solo project, write your own name on every row, so the load is visible.
  • Metric: one number that shows if the task worked, and where you read it.
  • Date: a day, or a rule such as "3 weeks before the fest". Change rules into days as soon as you know them.

Sources: none. These are template fields.

What should the plan say about the game and the audience?

The hook, five to ten comparable games, and where those players are. This is phase 1 of the sheet. These fields decide your tags, your price, the creators you contact and the festivals you enter, so fill them before any other row.

  • Hook: one sentence a player can repeat to a friend.
  • Comparable games: five to ten recent games at a similar scale.
  • Audience: where those players read, watch and talk.
  • Store pages: Steam app ID, itch.io page, your website.

Sources: none. These are template fields.

When should the Steam page go up?

As soon as you are ready to talk about the game in public. Valve requires the Coming Soon page at least two weeks before release, asks for review at least 7 business days before it goes live, and says players who wishlist two years ahead can be as likely to buy as those two weeks ahead.

Valve adds one warning: wait until you are fairly sure of the art direction and the core features. If the game changes a lot after the page goes up, players who wishlisted early may be confused. When you release, Steam sends a notification to every player who has the game on their wishlist.

Sources: Steamworks Coming Soon documentation.

Which beats go in the calendar?

The page launch, the demo, Next Fest, the release and the discounts after it. Put your dates in the When column. The Next Fest rows follow Valve's workback timeline; a game can join only one Next Fest. In 2027, Valve lists Next Fest from 22 February to 1 March and from 14 to 21 June.

Discounts have fixed rules, so plan them now. A launch discount runs for 7 to 14 days, and Valve suggests about 10% to 15%. After release, a product cannot be discounted for 30 days, apart from that launch discount. A discount of 20% or more sends a notification to players who have the game on their wishlist.

The beats of a Steam launch and the goal of each one, with the timing that Valve documents.
WhenBeatGoal
Your dateSteam page live, first trailerFirst wishlists
Your dateDemo releaseSteam can notify wishlisters once, within two weeks of the demo release
3 weeks before Next FestDemo submitted for build reviewStay in the festival
11 days before Next FestPress PreviewPress and creators play the demo
Next Fest weekFestival, streams, postsWishlists and demo players
Your dateLaunch, with a launch discount of 7 to 14 days if you want oneSteam notifies wishlisters at release
30 days or more after launchFirst discount of 20% or moreWishlist notifications and new buyers
After launchMajor updatesReturning players

Sources: Steamworks Steam Next Fest, Upcoming Steam Events, Wishlists and Discounting documentation.

What does a filled plan look like?

The table below is an example for a made-up game: Lantern Deep, a cave roguelike by a team of two, Ana and Ben. The game, the people and every target number are invented. Only the Steam rules and the 2027 Next Fest dates are real.

Read how the dates come from the rules. The team wants the page live on Monday 1 February 2027, so the review request goes in on 21 January, which is 7 business days before. They pick the June Next Fest, from 14 to 21 June 2027. So the demo goes to build review by 24 May, 3 weeks before, and the press emails go out before the Press Preview on 3 June.

The wishlist target for Next Fest is 800. The team took it from the median of 806 in the February 2026 survey by How To Market A Game, and treats it as a guide, not a promise. The launch is on 9 September 2027, so the first normal discount cannot start before 9 October.

Example plan for Lantern Deep, a made-up game. The owners and target numbers are invented for this example.
PhaseGoalChannelTaskOwnerMetricDate
1. PositionHook and comparable gamesResearchWrite the hook. List 8 cave and mining roguelikes.AnaList done11 January 2027
2. Steam pageComing Soon page liveSteamSubmit the page for review.BenPage live on 1 February21 January 2027
2. Steam pageFirst wishlistsTrailer, Reddit, BlueskyPublish the trailer with one tagged link per channel.Ana300 wishlists in week 1 (example)1 February 2027
3. WishlistsSteady wishlistsShort clips, RedditOne clip and one post each week.Ana60 wishlists per week (example)Every Thursday
4. DemoDemo liveSteamRelease the demo and send the demo notification.Ben1,500 demo players (example)17 May 2027
5. Next FestDemo approvedSteamSubmit the demo for build review.BenApproved24 May 2027
5. Next FestPress and creatorsEmailEmail 40 creators, each with their own link.Ana10 videos or streams (example)31 May 2027
5. Next FestWishlists in the festSteam, streamsPost and stream each day.Ana800 wishlists in the week (example)14 to 21 June 2027
6. LaunchA strong first weekSteamRelease with a 10% launch discount for 7 days.Ben700 copies in week 1 (example)9 September 2027
6. LaunchA stable buildGame analyticsCheck crash-free sessions each morning.BenNo drop against the demo build9 to 16 September 2027
7. After launchMore sales from wishlistsSteamRun the first 20% discount.AnaUnits over a normal weekAfter 9 October 2027

Sources: Steamworks Coming Soon, Steam Next Fest, Upcoming Steam Events and Discounting documentation; How To Market A Game (13 April 2026); example with made-up numbers.

What should I measure every week?

Wishlists by source, installs, retention and revenue. Each row names the place in the Manalens dashboard where the number comes from. Weeks start on Monday in the dashboard.

The weekly measurement table: each metric, where it comes from and the question it answers.
MetricWhere in ManalensQuestion it answers
Steam wishlists by source and campaignOverview source picker: Steam, after the UTM CSV importWhich posts and creators bring wishlists?
All wishlist adds and deletesSteam report, with the automatic Steam sync (Early access)Is the total growing?
Short link clicks by creatorLinksWhich creator sends traffic?
Website visitors by channelOverview, Acquisition cardWhich channels reach new people?
Installs by channel and campaignAttribution, Installs tabWhich channels bring players?
D1 and D7 retention, MAUDashboards: Game KPIs templateDo new players stay?
Crash-free sessionsDashboards: Game health templateDid a build hurt players?
itch.io views, downloads and paymentsOverview source picker: itch.ioIs the itch.io page selling?
Revenue by sourceAttribution, goal purchaseWhich channels sell the game?

Sources: Steamworks UTM Analytics documentation; Manalens product documentation.

How do I run the weekly review?

Fill the table every Monday for the last full week, and keep a beat log. Steam advises you to look back at wishlist data after a sale or an event to guide later choices.

Then open the plan sheet. Mark the rows that are done, move the dates that slipped, and check that every row for the next two weeks has an owner.

  1. Import the Steam UTM CSV for the last two weeks. Conversions are final 4 days after the visit, and the latest import replaces older rows.
  2. Fill each row of the weekly table.
  3. Compare each row with the week before.
  4. Read the beat log: the date, what you did and the link you used. Match each change in the table to a beat.
  5. Choose next week's beats and links.
  6. Update the plan sheet: done rows, new dates and owners.

Sources: Steamworks Wishlists documentation; Steamworks UTM Analytics documentation.

Which mistakes break a marketing plan?

Most broken plans fail on dates and on measurement, not on ideas.

  • A late store page. The page needs review time, and it must be up for at least two weeks before release.
  • A demo that misses build review. The deadline is 3 weeks before Next Fest, and a game gets only one Next Fest.
  • A discount inside a waiting period. No discount is possible for 30 days after release, after a price rise or after the last discount. Seasonal sales are exempt only from the last of the three.
  • One link for every channel. Then no row of the weekly table can name its source.
  • Rows without an owner or a metric. Nobody does them, and nobody can tell if they worked.

Sources: Steamworks Coming Soon, Steam Next Fest and Discounting documentation; our own advice.

How is the template different from the marketing guide?

The guide is the overview, and this page is the sheet. Our guide to marketing an indie game explains each step in order, with the data behind it: the hook, the store page, wishlists, festivals, creators, press, ads and the launch. It helps you decide what to do.

The template holds what you decided. It has no advice in it, only tasks, owners, metrics and dates. Read the guide once, then work in the sheet every week. If a row has no clear metric, go back to the guide section for that phase and pick one.

Sources: our own guides.

How do I fill the table automatically?

Manalens is the analytics and growth engine built for games. Connect Steam and itch.io and install the Unity, Godot or web SDK; the weekly table then fills from one project.

Sources: Manalens product documentation.

Frequently asked questions

When should I put up my Steam page?

As soon as you are ready to talk about the game in public. Valve requires the Coming Soon page at least two weeks before release, and asks for review at least 7 business days before it goes live. Valve also says players who wishlist two years ahead can be as likely to buy.

How many wishlists does Steam Next Fest bring?

In the February 2026 How To Market A Game survey, the median game earned 806 wishlists during the festival. The range was wide, so use the median only as a guide. Steam Next Fest runs three times a year, and a game can join only one Next Fest.

What should I measure every week?

Wishlists by source, installs, retention and revenue. Fill the table every Monday for the last full week, and compare each row with the week before. Keep a beat log with the date, what you did and the link you used, so you can match each change to a beat.

Can I download the marketing plan template?

Yes. The page has a CSV file with the same 14 rows as the table: phase, goal, channel, task, owner, metric and date. Open it in any spreadsheet tool, replace "Your name" and "Your date" with your own, delete the rows that do not fit your game and add new ones.

How is this template different from a marketing guide?

The template is the sheet you work in: one row per task, with an owner, a metric and a date. A guide explains why each phase matters and what works. Use our guide to marketing an indie game to choose your beats, then put each one in the sheet as a row.

Sources and implementation