Indie Game Backlog Tracker: A Wishlist-to-Play Plan for Steam and itch.io
backlog managementwishlistbuying guideSteamitch.iogame dealsindie game bundlestemplates

Indie Game Backlog Tracker: A Wishlist-to-Play Plan for Steam and itch.io

IIndie Games Shop Editorial
2026-11-05
7 min read

Build a practical Steam and itch.io backlog tracker with price targets, play priorities, bundle checks, and a monthly review routine.

An indie game backlog tracker turns a scattered Steam or itch.io wishlist into a practical play plan. This guide provides a repeatable framework for recording prices, discounts, bundles, demos, playtime, co-op needs, and personal priorities so you can decide what to buy now, what to wait for, and what to play next without letting every sale expand your backlog.

Overview

A wishlist is useful for collecting possibilities, but it does not answer the questions that matter at checkout: Will you play this soon? Is the current price appropriate? Does it work with your available hardware? Is it a solo game when you need co-op, or a long commitment when you only have short sessions?

A backlog tracker adds that decision layer. It can be a spreadsheet, notes document, database, or paper list. The tool matters less than the fields and the review habit. The goal is not to measure your gaming life perfectly. It is to make buying decisions consistent enough that discounts do not override your actual time, interests, or budget.

Use one list for games you may buy and another for games you already own. Keeping those lists separate prevents a common problem: treating an unplayed purchase as progress simply because it has been added to a library. For broader buying context, compare storefront features in Where to Buy Indie Games: Steam, itch.io, Humble, and Key Stores Compared.

How to estimate

Start with a simple score rather than trying to predict whether a game is objectively good. Your tracker should estimate fit for you. A useful decision score can combine four factors:

  • Interest: How strongly you want to play the game, scored from 1 to 5.
  • Timing: How likely you are to start it within the next few weeks, scored from 1 to 5.
  • Value: How well the current price fits your target, scored from 1 to 5.
  • Friction: Hardware, online, launcher, controller, or session-length concerns, scored from 1 to 5, with a higher score meaning fewer obstacles.

One repeatable formula is priority score = interest + timing + value + friction. A game scoring highly is a stronger candidate for an immediate purchase or install. A low score does not mean the game is bad; it means the timing or buying conditions may be wrong.

You can also estimate the cost of a planned batch. Add the current prices of the games you would genuinely start soon, then subtract discounts or bundle savings only after checking which titles you actually want. The result is your planned spend. Keep optional games outside that total. This prevents a large bundle discount from disguising a larger purchase than you intended.

For a more useful value comparison, calculate cost per planned hour = purchase price divided by estimated hours you expect to play. Use a range rather than false precision. For example, if an illustrative game costs $12 and you expect to play it for 6 to 10 hours, the planned cost per hour is approximately $1.20 to $2.00. This is not a quality rating. It simply shows whether the purchase fits your own use case.

Inputs and assumptions

Create one row per game and record the information at the time of review. The following fields are enough for a useful indie game wishlist and backlog tracker:

  • Game title and storefront: Record Steam, itch.io, Humble, or another legitimate store separately. A game may have different formats, launchers, or purchase options across storefronts.
  • Current price and currency: Enter the displayed price and the date checked. Do not assume an old sale price will return on a predictable schedule.
  • Target price: Set the price at which you would feel comfortable buying. You can also use a target discount, but a fixed personal budget is easier to apply.
  • Ownership status: Choose one label such as wishlist, demo played, owned unplayed, playing, completed, paused, or abandoned.
  • Estimated playtime: Use a broad range and note whether it reflects the main path, a typical session, or optional content.
  • Priority and start window: Record both how much you want the game and when you expect to play it. A highly anticipated game with no available start window should not automatically be an urgent purchase.
  • Co-op and multiplayer needs: Note whether the game is solo, local co-op, online co-op, or dependent on a specific group of friends. Verify the current store description before buying.
  • Technical fit: Add platform, controller, operating system, Steam Deck or other handheld notes, and any requirements that matter to you.
  • Source and refund comfort: Record the storefront and format you prefer. For key sites, consider seller transparency and redemption details before treating a lower price as equivalent.
  • Reason to buy: Use a short note such as “short horror game for October,” “co-op weekend,” or “pixel art exploration.” This keeps the purchase connected to a real plan.

For itch.io games, demos, browser projects, downloadable files, and bundles may require different tracking notes from a conventional Steam purchase. Record whether you have tested the game, downloaded it, or merely saved the page. For bundles, mark the individual games you want and the number you would realistically play. The bundle is only part of the calculation; unused items still add to discovery and storage clutter.

If bundles are a regular source of backlog growth, read Indie Game Bundles Explained: How to Find Good Bundles Without Buying Filler. For wishlist design, How to Build an Indie Game Wishlist You Will Actually Play offers a complementary approach.

Worked examples

Example one: choosing between two sale candidates. Imagine Game A is an illustrative $8 purchase with a 3-to-5-hour estimate, strong interest, and a clear plan to play this weekend. Game B is an illustrative $15 purchase with a 10-to-15-hour estimate, moderate interest, and no planned start date. Game B may look stronger on hours per dollar, but Game A has better timing and a lower immediate commitment. Your tracker should allow Game A to win if the purpose of the purchase is near-term play rather than maximum theoretical value.

Example two: evaluating a bundle. Suppose a bundle contains eight games. You identify three that interest you, but only one has a realistic start window. Enter the bundle price as the cost of acquisition, then mark the other games as potential rather than guaranteed value. If you would buy the one planned game alone at a similar price, the bundle may be convenient. If the bundle costs substantially more than your target for that game and the other titles are unlikely to be played, waiting may be the better decision.

Example three: planning a monthly cap. Assume your personal monthly indie game budget is an illustrative $30. Your tracker contains two planned games totaling $22 and three optional games totaling $24. Buy only from the planned total unless an optional game replaces, rather than adds to, one of those purchases. This substitution rule is simple: every new purchase must either fit under the cap or remove an existing purchase from the plan.

These examples use invented figures to demonstrate the method, not to suggest current market prices. Replace them with the prices, discounts, and time estimates shown when you review your own list.

When to recalculate

Review the tracker once a month and briefly before major seasonal sales, publisher promotions, or bundle events. Recheck the current price, target price, storefront, bundle contents, and your available playtime. Pricing inputs change, but your personal inputs change too: a new release, a move, a hardware change, or a busy month can make a previously sensible purchase less suitable.

Recalculate sooner when a game leaves early access, receives a substantial update, adds or changes co-op features, appears in a bundle, or becomes available on a platform you use. Avoid treating a price alert as an instruction to buy. Treat it as a prompt to reopen the row and ask whether the game still fits.

At each monthly review, take five actions:

  1. Move games you no longer want to a low-priority or archived list.
  2. Promote games with a clear start date and a price that meets your target.
  3. Remove owned games from the buying list and assign them a play status.
  4. Choose one to three next games rather than a long queue.
  5. Record why you skipped the rest: price, time, hardware, co-op availability, or reduced interest.

Use that final note to improve future decisions. If most purchases remain unplayed, raise the required timing score. If you repeatedly miss games because you wait for a specific discount, consider a broader target-price range. If your tracker fills with cheap games, compare it with Best Indie Games Under $10, but keep the same start-window rule.

A backlog tracker works when it reduces decisions, not when it becomes another collection to maintain. Keep the fields that change your choices, review them when prices or plans change, and let the next purchase earn its place through a clear reason to play.

Related Topics

#backlog management#wishlist#buying guide#Steam#itch.io#game deals#indie game bundles#templates
I

Indie Games Shop Editorial

Editorial Team

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.