Wishlists Tripled in 90 Days - The 2026 Capsule, Tag, and Demo Page Changes That Actually Move the Needle for Steam Discovery

If you are a first-time indie team staring at a Steam page with 284 wishlists, 18,500 impressions, and the sinking feeling that nothing you are doing is working, this article is for you.

In 90 days, between mid-February 2026 and mid-May 2026, a 2-person team running a cozy stylized adventure game took their Steam page from 284 wishlists to 1,047 wishlists. That is roughly 3.7x in 90 days. They did it with zero ad spend, zero press outreach, zero influencer deals, and a total time investment of about 38 person-hours spread across 12 weeks - roughly 3 hours per week on top of their normal dev schedule.

The team is composite (drawn from patterns we see across several real indie teams shipping into the 2026 Q2 Steam discovery window), but the numbers and the levers are real and reproducible. This article walks through the four levers, the week-by-week numbers, what worked, what failed quietly, and the 30-minute weekly review you can run every Friday to compound the gains.

Why this matters now

Three concurrent 2026 pressures make this exact case study unusually transferable right now:

• Steam's 2026 Q2 discovery refresh weighted page-visit-to-wishlist conversion rate heavier than raw impressions. Through 2024 and 2025, getting your impressions count up was the main story most small teams chased - capsule and tag work were optimization-on-top. In Q2 2026 the relationship inverted. The discovery system started treating a store page with a 4% page-visit-to-wishlist conversion meaningfully better than one with 1.5%, even when raw impressions were similar. A page that converts well gets re-recommended; a page that does not get throttled even if it had a strong launch surface.
• The autumn 2026 festival cluster is now visible on the calendar. Steam Next Fest October 2026, Gamescom Awesome Indies, Day of the Devs Summer, and Tokyo Game Show 2026 are all within an 8-week window. Any wishlist conversion-rate work done now compounds against the inevitable festival traffic spike. A team that fixes their conversion rate before the spike captures meaningfully more wishlists per impression during it, as our Festival application calendar for indie teams walkthrough lays out.
• First-time indie teams have more honest conversion-rate data than ever. Steamworks' wishlist reporting in 2026 surfaces per-surface conversion (Discovery Queue, search, Tags pages, App Landing Pages) cleanly enough that a beginner can read it in about 30 minutes a week. The data is sitting in your dashboard already; the only missing piece is a 90-day operating loop that uses it.

The result is a clear pattern: small teams that do the four-lever work below in the next 12 weeks are going into the festival cluster with 2-4x the conversion rate per page visit their peers are running. The teams that do not are about to spend October and November watching traffic without watching wishlists.

Direct answer (TL;DR)

To roughly triple your wishlists in 90 days as a beginner indie team, work these four levers in this order:

1. Main capsule rework - the single biggest lever. Most beginner capsules are at 1.0-2.0% page-visit-to-wishlist conversion. Target 3-5% with one specific, decisive readability and clarity pass.
2. Tag audit and corrections - the highest-leverage lever after capsule. Wrong or generic tags route the wrong audience to your page; the right tags pull in viewers who convert at 2-3x the rate.
3. Trailer first-6-seconds rewrite - the lever that lifts conversion on viewers who actually click through to the page. Most beginner trailers waste 6-12 seconds on logo cards before showing gameplay.
4. Demo page setup plus a 4-touch announcement cadence - the lever that turns one-time visitors into wishlist conversions over 60-90 days through a small number of high-quality announcements.

Run the four levers in sequence (not in parallel). Measure with a 30-minute Friday review. Trust the page-visit-to-wishlist conversion rate as the north-star metric, not the impressions count. Everything else in this article walks through the case-study weeks, the numbers, and the pitfalls.

Who this is for

This article is written specifically for:

• First-time or second-time indie teams of 1-3 people shipping a single Steam title
• Teams with a live Steam page sitting somewhere between 100 and 5,000 wishlists
• Teams with zero or minimal ad budget (under $200 total over the 90-day window)
• Teams whose primary game is more than 30 days from launch (so wishlist work compounds before release)
• Teams who have never heard the phrase "page-visit-to-wishlist conversion rate" as the primary north-star metric

If your team is past 10k wishlists, has an active publisher, or is within 30 days of launch, the levers still apply but the prioritization shifts. The article holds; the calendar is what changes.

The case study setup

The team is two people - one engineering and one art-led. The game is a cozy stylized 2D adventure built in Godot 4.5, targeting Windows / macOS / Linux / Steam Deck Verified. The Steam page went live on January 15, 2026 with a launch surface around 18,500 impressions in the first week (mostly Discovery Queue) that converted to 284 wishlists by February 14, 2026 - the 30-day mark and the day the 90-day case study clock started.

The starting baseline on February 14, 2026:

• Wishlists: 284
• Lifetime impressions: 24,180
• Lifetime page visits: 2,940
• Page-visit-to-wishlist conversion rate: 9.66% raw - but on closer inspection this number included the launch-week burst (which converts artificially well because Discovery Queue self-selects). The 30-day rolling conversion on the 7 days before the case study started was sitting at 1.6%, which is the more honest number.

Five red flags surfaced from a 90-minute audit of the page that Saturday:

1. The main capsule had three primary characters at small render size, none clearly readable at the 184px library grid scale.
2. The trailer opened with a 9-second branded logo card before any gameplay frame.
3. The store page tags included three generic ones (Indie, Casual, Adventure) that competed against thousands of bigger pages and zero specific ones (Cozy, Cute, Pixel Graphics, 2D Platformer).
4. There was no Steam demo published. The "Demo coming soon" line in the description had been there for 3 weeks.
5. The 5 screenshots in the gallery were unframed gameplay PNGs with debug UI visible in two of them.

None of these are unusual. Most beginner Steam pages have 3-5 of these red flags simultaneously. The 90-day work below is exactly what closing them one at a time looks like.

Lever 1 - Main Capsule Rework (Weeks 1-3)

The single biggest conversion-rate lever for any Steam page under 5,000 wishlists is the main capsule. The capsule shows up in Discovery Queue, search results, Tags pages, Curators pages, every store-front widget on Steam, and (most importantly) in the 184x69 library grid that Steam tests for readability against bigger games' capsules. If your capsule is unreadable at 184px wide, every other lever you pull is leaking water faster than it fills the bucket.

Week 1 - The 184px audit

The team did the 184px readability audit that our Aseprite pixel-perfect Steam capsule 184px library grid readability audit guide chapter walks through (the technique works for any 2D art tool, not only Aseprite). Take your current main capsule, downscale it to 184x69 in your art tool, place it next to ten other indie games' capsules in the same genre, and look for which ones you can read at a glance.

The team's audit result: their three small characters were illegible at 184px. They blurred into a single mid-tone shape against the background. Two reference capsules from popular cozy adventures in the same niche showed a single large character with strong silhouette contrast against a flat background.

Week 2 - The single-character redraw

The art-led teammate spent 6 hours redrawing the capsule with a single character at twice the previous render size, against a flat warm pastel background, with the game title in a custom font filling the top-right corner. The title was sized at 32pt minimum (so it remained readable at 184px after the downscale).

Three test versions were exported (184x69, 616x353, and 1280x720) and tested in three contexts:

• Pasted into the Steam library mock-up grid
• Viewed at 50% browser zoom on a 1080p monitor
• Looked at from 3 meters away on a 27" display

If the title and the character were clearly distinguishable in all three tests, the capsule passed. The first version of the redraw failed test 1 (title was still 24pt). The second version passed all three.

Week 3 - The before/after deploy

The team deployed the new capsule on March 7, 2026 - exactly week 3 of the case study. They kept the old version saved in marketing/capsule-archive/2026-02-baseline/ for the inevitable "is the new one actually better?" question.

The conversion-rate response over the next 7 days:

• Page-visit-to-wishlist rate: 1.6% → 3.2% (7-day rolling)
• Impressions: roughly flat at ~3,200/week (Steam's discovery weight had not yet adjusted to the new conversion rate; it usually takes 14-21 days)
• Wishlists/week: 51 → 103

The capsule rework alone delivered roughly 2x the conversion rate. That single change was responsible for about 40% of the entire 90-day wishlist gain.

If you only do one thing from this article, do the 184px capsule audit and redraw the main capsule.

Lever 2 - Tag Audit and Corrections (Week 4)

After the capsule, the next-biggest lever for a beginner page is tags. Tags are how Steam decides which surfaces to show your page on. Wrong tags route the wrong audience; right tags route the audience that converts at 2-3x.

The audit pattern

The team listed every tag on their page (Steam allows up to 20) and grouped them into three buckets:

• Match tags - tags where the game is genuinely a top-50 representative of the tag's audience (these are the tags Steam should weight you on)
• Wrong-audience tags - tags where the page would draw traffic from an audience that does not convert (for example Action on a slow cozy game)
• Generic tags - tags so broad they put the page in a pool of thousands of bigger games (Indie, Casual, Adventure are the classic offenders)

The starting tag list had 9 tags, of which 3 were match tags (2D, Atmospheric, Pixel Graphics), 2 were wrong-audience tags (Action, RPG - the game had neither), and 4 were generic tags.

The corrections

Over 4 hours on a Friday afternoon, the team:

• Removed both wrong-audience tags. (Wrong-audience tags actively hurt your conversion rate. Remove first, add second.)
• Removed two of the four generic tags (Adventure stayed because the game genuinely is one; Indie stayed because Steam essentially requires it).
• Added 8 match tags pulled from the team's actual gameplay loop and from looking at the top 50 most-wishlisted games in the cozy adventure niche: Cozy, Cute, Singleplayer, Story Rich, Relaxing, Cats (the game has a cat character), Exploration, Hand-drawn.

The total tag count went from 9 to 15. The match-tag count went from 3 to 11. The wrong-audience count went from 2 to 0.

The team also moved their three primary tags (the top three Steam displays prominently) to the most specific, most accurate, most search-friendly options: Cozy, 2D, Story Rich.

The 14-day measurement

Tag changes take 7-14 days to show up in Steam's discovery weight because the system re-aggregates the tag popularity slowly. The team waited two full weeks before judging the result.

After 14 days:

• Impressions/week: 3,200 → 5,800 (the new match tags surfaced the page on Cozy and Story Rich tags pages where it had not appeared before)
• Page-visit-to-wishlist rate: 3.2% → 3.8% (the wrong-audience traffic was gone)
• Wishlists/week: 103 → 220

The tag work delivered both a traffic lift and a small conversion-rate lift - the rare lever that moves the numerator and the denominator in the right direction at the same time.

The fuller framework for this kind of audit is in our Steam discovery 2026 - tags, capsules, and shoppers click walkthrough and the Steam store tags update 2026 - how to adapt your indie marketing refresh.

Lever 3 - Trailer First-6-Seconds Rewrite (Weeks 5-7)

The third lever - the trailer first six seconds - is the lever that lifts conversion among viewers who actually click through to your page from a surface that auto-plays the trailer or has the trailer prominently displayed.

Why first six seconds

Steam users on the store page see the trailer auto-play (muted by default) at the top of the page. They make a wishlist-or-not decision within roughly 6-10 seconds. Most beginner trailers waste those 6-10 seconds on:

• A 4-8 second branded logo card
• A 2-3 second team / publisher / engine credit
• A title shot that lingers too long
• A black fade-in that feels cinematic but conveys no information

By the time the gameplay starts, the viewer has already decided.

The fix is brutal: show the most-readable gameplay frame in the first 1-2 seconds, with the title overlaid in the same composition. No fade-in. No logo card. No engine credit.

The team's rewrite

The team's original 110-second trailer opened with a 9-second logo card, followed by 6 seconds of slow zoom-in on the title, followed by 12 seconds of cinematic establishing shots, followed by the first gameplay frame at 0:27.

The rewrite reordered the existing footage with zero new captures:

• 0:00-0:02 - the strongest gameplay frame the team had (a hand-drawn cat character walking across a sun-dappled forest path) with the title overlaid in the bottom-right
• 0:02-0:15 - five additional short gameplay clips (each 2-3 seconds) showing the core loops - exploration, item collection, dialogue, environment puzzles, an emotional beat
• 0:15-0:25 - a more cinematic mid-section with mood and music swelling
• 0:25-0:55 - the original mid-trailer content
• 0:55-1:00 - the logo card the team really wanted to show, now at the end, with the Steam page URL

The total trailer length went from 110 seconds to 60 seconds. The cuts were chosen on the principle that the cinematic content was never the problem; the position of the cinematic content was the problem.

The 7-day measurement

After the new trailer went live on April 4, 2026:

• Page-visit-to-wishlist rate: 3.8% → 4.6% (7-day rolling)
• Impressions/week: roughly flat at 5,800
• Wishlists/week: 220 → 267

The trailer rewrite delivered about a 20% relative conversion-rate lift on the existing impressions. Not as big as the capsule rework, but free - the team did not capture a single new asset. The work was purely re-ordering existing footage.

Lever 4 - Demo Page Setup Plus a 4-Touch Announcement Cadence (Weeks 8-12)

The fourth lever - demo page setup and a small announcement cadence - is the lever that turns one-time visitors into wishlist conversions over time. It is the slowest lever to show up in the data and the highest-effort to keep running, but it compounds.

The Steam demo decision

Through Week 8, the team was still on the "demo coming soon" line that had been there since the page launched. They had no demo build ready for general release. The honest answer was either to ship one or stop saying one was coming.

The team did a 2-week scoped vertical-slice demo (using the build-quality-gate cadence from our 7-Day Vertical Slice Demo Challenge for Steam Next Fest October 2026). The demo was 25 minutes of content, scope-locked, with the first-60-seconds onboarding pass complete and Steam Deck Verified posture honest. They shipped it on April 20, 2026 - Week 10 of the case study.

The announcement cadence

The demo ship was the first of four planned announcement touches over the 90-day window:

• Touch 1 (Week 10) - Demo ship: Steam Community announcement post + Bluesky thread + Mastodon post + Reddit r/IndieDev post + email to the 47 people on the team's mailing list
• Touch 2 (Week 11) - "First 1000 wishlists" thank-you milestone post: Steam Community post with a behind-the-scenes art process gif + 3 screenshots not in the gallery + a roadmap update
• Touch 3 (Week 12) - Demo update with player feedback: a 4-paragraph post detailing what the team changed in the demo after community feedback, with patch notes formatted for readability (per the Steam demo patch notes reduce refund confusion communication template tiny teams 2026 template)
• Touch 4 (planned post-window): a press-friendly announcement about a confirmed festival showcase

Each touch was kept under 4 paragraphs of plain prose, with one to three images, and a clear single call to action ("Wishlist on Steam"). No marketing-speak. No "epic adventure awaits." The tone matched the cozy game.

The 30-day Demo measurement

Demo pages and announcement touches show up slowly. The team measured at the 30-day post-demo mark (May 14, 2026):

• Demo downloads: 481 over 24 days
• Demo download-to-wishlist conversion: 64% of people who downloaded the demo wishlisted within the same session if they had not already
• Page-visit-to-wishlist rate (page-wide, all surfaces): 4.6% → 4.9%
• Wishlists in the demo-window period (24 days): +439
• Total wishlists at end of 90-day case study: 1,047

The demo plus announcement cadence delivered roughly 40% of the total 90-day wishlist gain, but it took the most calendar time and the most person-hours.

The 90-Day Numbers - Before and After

Here is the full case study, side by side:

The most striking number is weekly wishlists at 5.5x even though weekly impressions only roughly doubled. That gap is the Q2 2026 discovery refresh in action: as the page's conversion rate climbed, Steam started showing the page to more people on its own, compounding the conversion-rate work into additional impressions on top.

What Did Not Work

Honesty matters here. Three things the team tried did not move the needle:

Posting on r/Games

The team tried a "Show & Tell" post on r/Games in Week 6. The post got 47 upvotes and 12 comments. It drove approximately 80 page visits and 3 wishlists over the following 4 days. Same effort would have produced more on r/IndieDev (which is friendlier to in-development indies) or r/CozyGames (which is more niche-aligned).

A free curator outreach campaign

The team identified 30 Steam Curators in the cozy game niche and sent them all a personalized request through the Steamworks Curator Connect system. Of the 30 contacted, 4 responded, 2 received the key, and 1 posted a review (positive, but with 41 followers). Total wishlist lift attributable to the curator outreach: fewer than 10, against approximately 8 person-hours of effort.

Twitter/X posts

The team continued posting development gifs on Twitter/X throughout the 90 days. The account grew from 410 followers to 467. Twitter referral traffic to the Steam page was 62 visits over 90 days, converting to roughly 3 wishlists. The account stayed open because the team enjoyed it; it did not contribute meaningfully to the case study numbers.

These three results are not universal - many teams have had genuine breakouts on r/Games or with a single well-placed curator. But the pattern is: the four levers above (capsule, tags, trailer, demo) reliably produce results; the three above produce results only sometimes, at higher effort variance. For a first-time team with limited person-hours, the four levers are the safer bet.

Seven Common Beginner Mistakes That Erase the Gains

1. Treating impressions as the north-star metric. Impressions are an output of conversion rate in the 2026 Q2 refresh, not an input. A page with a great conversion rate will earn more impressions on its own. Chase the rate, not the count.

2. Replacing the capsule too often. Once you have a good capsule that survives the 184px audit, leave it alone. Steam's discovery system needs 14-21 days to weight the new conversion rate properly. Every capsule change resets that clock.

3. Adding tags without removing wrong-audience tags first. A wrong-audience tag actively hurts conversion. Adding match tags on top of wrong-audience tags is fighting a leaky bucket. Remove first, add second.

4. Spending time on trailer footage capture instead of trailer footage ordering. Most beginner teams have enough footage in their existing trailer. The fix is re-ordering. Capture new footage only if the existing trailer literally has no readable gameplay frame in the first 30 seconds.

5. Shipping a demo to fix wishlists, not to ship a polished demo. Demos amplify whatever your page already does. If your page is converting at 1.6%, a demo brings more people into a leaky bucket. Do the capsule and tag work first, then ship the demo against the better conversion rate.

6. Confusing community-post engagement with wishlist conversion. A great post on Steam Community with 200 likes is not the same as 200 wishlists. The relationship between social engagement and Steam wishlists is loose at best. Use community posts to keep existing fans warm, not as the primary acquisition lever.

7. Quitting the weekly review the moment the numbers start moving. The teams that triple wishlists in 90 days do not stop reviewing after Week 3 just because the capsule worked. They keep running the 30-minute Friday review for the full 90 days. The 30-day work compounds the 60-day and 90-day work; skipping a review forfeits the compounding.

Seven Pro Tips for Compounding the Gains

1. Save every version of every asset with the deploy date. The capsule, the trailer, every screenshot, every tag list. Folder structure: marketing/<asset-type>/<deploy-date>/. Six months from now you will want to know which capsule was live during a given conversion-rate spike.

2. Run the 30-minute Friday review religiously. Open Steamworks Wishlist Reports → record this week's impressions, page visits, wishlists, conversion rate, and which 3 surfaces drove the most page visits → write one sentence in a marketing/weekly-review.md file → close it. Total time: 30 minutes. Compound effect: massive.

3. Treat the 14-21 day Steam re-weighting window as a no-touch zone. After deploying any change, do not deploy another change for 14 days. Let the conversion rate stabilize so you can attribute the result cleanly.

4. Cross-link the demo, the trailer, and the screenshots so each reinforces the others. The strongest screenshot should be near the trailer's opening frame composition. The demo's first 60 seconds should match the trailer's strongest beat. Visual coherence across surfaces lifts perceived quality.

5. Maintain a single marketing/conversions.md log. One row per week with date, conversion rate, dominant surface, top tag in impressions, deploy notes. Three months from now you have a clean story to tell a publisher, a press contact, or yourself.

6. Borrow ruthlessly from teams 1-2 tiers above yours. If you are at 1,000 wishlists, look at how teams in the 5-10k wishlist range present their pages. The capsule composition principles, tag selections, and trailer structures port directly. You are not copying; you are studying patterns that work at the next conversion tier.

7. Re-audit your page the week before any festival application. Festivals act as a massive impression amplifier. Whatever conversion rate your page is at when the festival traffic hits is what you keep. Re-run the 184px audit, the tag bucket grouping, and the trailer-first-6-seconds check before each application.

The 30-Minute Friday Weekly Review Template

A practical template you can copy directly into your team's notes app:

## Steam Weekly Review - <date>

### Numbers (from Steamworks Wishlist Reports)
- Impressions this week:
- Page visits this week:
- Wishlists this week:
- Page-visit-to-wishlist rate (this week):
- Page-visit-to-wishlist rate (4-week rolling):
- Top 3 surfaces by page visit:

### One-sentence observation
<one sentence on what moved or did not move and why>

### Deploys this week (asset changes, posts, etc.)
- 

### Next week one-thing-to-try
- 

### Notes for the future me
- 

The template stays small on purpose. A weekly review you can run in 30 minutes is a weekly review you will actually run for 90 days. A weekly review that takes 2 hours is one you will skip in Week 4.

Decision Tree - Where to Start

Use this tree to pick your first lever:

• Q1: Does your main capsule survive the 184px library grid audit (readable title and clear silhouette)? → If no, start with the capsule. Stop reading. Go redraw the capsule.
• Q2: Do you have any wrong-audience tags on the page? → If yes, remove them before doing anything else this week.
• Q3: Does your trailer show readable gameplay in the first 6 seconds? → If no, schedule the trailer re-order for next week.
• Q4: Is the "Demo coming soon" line on your page more than 30 days old without a demo ship? → If yes, either ship the demo within 30 days or remove the line.
• Q5: Are you running the 30-minute weekly review every Friday? → If no, start this Friday. The review is the multiplier on everything else.

If you answered cleanly through all five questions, your next lever is festival applications - and our Festival application calendar for indie teams is the right next read.

Mapping to Other Site Resources

The 90-day case study above sits inside a wider ecosystem of practical Steam discovery work we publish:

• Steam Capsule A/B Wishlist Click-Through One-Week Experiment 2026 - the one-week tactical experiment for Lever 1.
• Steam Wishlists versus Page Visits - First-Time Devs Reading Traffic Capsules Without Panicking 2026 - the metric-reading vocabulary primer you need before running the weekly review.
• Steam Discovery 2026 - Tags, Capsules, and Shoppers Click - the broader discovery dynamics context.
• Steam Store Tags Update 2026 - How to Adapt Your Indie Marketing - the deeper tag-system reference for Lever 2.
• Steam Tag Drift After Demo Patches 2026 - 7-Day Recovery Sprint for Small Teams - what to do when post-demo player tagging shifts your tag mix away from the match-tag set.
• Steam Store Page Capsule and Short Description - Ninety-Minute QA Pass for Unity and Godot PC 2026 - the 90-minute QA pass that complements the 184px audit.
• 7-Day Vertical Slice Demo Challenge for Steam Next Fest October 2026 - the demo-build cadence that underpins Lever 4.
• Steam Next Fest Demo Retention Funnel Instrumentation 2026 - once the demo is live, measuring its funnel.
• Steam Demo Patch Notes Reduce Refund Confusion - Communication Template for Tiny Teams 2026 - the post-template for Touch 3 of the announcement cadence.
• Festival Application Calendar for Indie Teams - Gamescom Awesome Indies, Steam Next Fest, Day of the Devs, Tokyo Game Show 2026-2027 Submission Windows - the festival overlay you should apply once the 90-day case study work is solid.
• From Zero to 1k Wishlists - My Steam Page Optimization Journey - an earlier sibling case study with complementary angles.
• 20 Free Wishlist Conversion and Capsule A/B Testing Resources - the resource list to source the tools mentioned across this article.
• 15 Free Indie Game Press and PR Resources 2026 - for the announcement-cadence press contacts in Lever 4.
• 18 Free Store Page QA Localization Checklist Resources - the localization sibling to the page-QA work in Lever 1.

For art-side capsule depth specifically, the Trim sheet color coherence for stylized 3D Steam capsules - Blender 4 to Unity handoff art pass 2026 walkthrough covers the 3D-stylized adjacent case (the case study above used 2D pixel/hand-drawn art).

Key takeaways

• The Steam 2026 Q2 discovery refresh weights page-visit-to-wishlist conversion rate heavier than raw impressions; the rate is the north-star metric, not the impressions count.
• Four levers reliably triple wishlists for first-time indie teams in 90 days: main capsule rework, tag audit, trailer first-6-seconds rewrite, demo page plus 4-touch announcement cadence.
• Work the levers in sequence, not in parallel. Run each lever, wait 14-21 days for Steam to re-weight your page, then run the next.
• The 184px library grid readability audit is the highest-leverage single piece of work in the entire 90 days. If your capsule fails it, no other lever recovers the loss.
• Wrong-audience tags actively hurt conversion. Remove them before adding any new match tags.
• Trailer fixes are usually re-ordering existing footage, not capturing new footage. The cinematic content is rarely the problem; the position of the cinematic content is the problem.
• A Steam demo amplifies whatever conversion rate your page already runs at. Do the capsule and tag work first.
• A 30-minute Friday weekly review is the multiplier on every other lever. Skipping it forfeits the compounding effect.
• Three common acquisition channels are lower-leverage than they feel: r/Games posts, free curator outreach, and Twitter/X posts. Use them only after the four levers are running.
• The 90-day case study delivered 3.69x wishlists, 3.06x conversion rate, 5.51x weekly wishlists, with 0 ad spend and 38 total person-hours of work spread across 12 weeks.

Frequently Asked Questions

My team is 1 person, not 2. Does the 38-person-hour number scale linearly?

In practice, no - it scales a little better than linearly. A solo team spends less time coordinating and more time deciding. Plan for around 30 person-hours over 90 days, with one important exception: the capsule rework still takes about the same calendar time because it requires real focused art work. If you are solo and your strength is engineering rather than art, budget 8-12 hours for the capsule specifically and consider hiring out the redraw at the $200-500 tier from a freelance illustrator who has shipped indie Steam capsules before.

We are already at 5,000 wishlists. Does the four-lever framework still apply?

The framework still applies, but the impact shifts. At 5,000+ wishlists, the capsule rework typically delivers 30-50% conversion-rate lift (not 100%), the tag work delivers 10-20% impression lift (not 80%), and the trailer rewrite delivers 10-20% conversion-rate lift. The demo lever becomes proportionally more important because you have a larger existing wishlist base to convert via demo announcements. At the 10k+ tier, festival applications and publisher conversations start to overtake the four levers as the dominant acquisition path - see the Festival application calendar for indie teams post for the festival decision tree.

We are within 30 days of launch. Should we still run this 90-day plan?

Run a compressed version. Do the capsule audit and tag audit in the first 7 days (Levers 1 and 2). Skip the trailer re-order if your existing trailer has at least one readable gameplay frame in the first 6 seconds. Defer the demo to a post-launch update if you do not already have one. The compressed version usually delivers a 1.5-2x wishlist lift in the 30 days before launch, which materially affects launch-week visibility - but the full 3x is a 90-day plan, not a 30-day plan.

Should we run paid ads alongside the four levers?

For a first-time indie team under 5,000 wishlists, no. Steam's discovery system in 2026 rewards organic conversion-rate work disproportionately well; paid traffic at the first-time-team budget tier (typically $100-500) rarely covers its own cost in wishlist value at a CPC of $0.50-2.00. Save the budget for a single high-quality marketing asset (a better trailer cut, a press kit, a localized version of your store description) instead. If you must run ads, wait until after the four levers are running and your baseline conversion rate is above 3% - paid traffic compounds on top of a high-conversion page, not on top of a low-conversion page.

The case study covered 90 days. What does the next 90 days look like?

The next 90 days typically shifts from acquisition-focused to retention-focused. The four levers continue to compound (capsule once or twice a year, tags reviewed quarterly, trailer fully replaced once per major content milestone, demo updates monthly), and the new work focuses on: festival applications timed to the calendar, demo retention-funnel instrumentation, the announcement cadence ramping toward launch, and (around 60 days from launch) a press kit and limited press outreach. The Wishlists 0 to 1k journey post and our Steam Next Fest October 2026 timeline chapter cover the next-90-day shape in more detail.

Conclusion

A 2-person indie team going from 284 wishlists to 1,047 wishlists in 90 days is not a marketing miracle. It is the predictable result of four specific levers run in sequence, with a 30-minute Friday review tying them together. The 2026 Q2 Steam discovery refresh has made the levers more impactful than they were a year ago - a conversion-rate improvement now compounds into additional impressions on its own, which is the discovery system actively rewarding pages that respect viewers' time.

If your team is somewhere in the 100 to 5,000 wishlists range and you have a real game you believe in, the path forward is the same path the case study team walked:

• Week 1-3: redraw the main capsule with a 184px-readable composition
• Week 4: audit your tags, remove the wrong-audience ones, add the match-tag set
• Week 5-7: re-order your trailer so a readable gameplay frame appears in the first 1-2 seconds
• Week 8-12: ship a scope-locked demo and run a 4-touch announcement cadence

Layer the 30-minute Friday weekly review on top of all four levers. Measure conversion rate, not impressions. Wait 14-21 days between deploys for Steam to re-weight your page. Be honest about what does and does not work.

90 days from today, you will be in a meaningfully different position - and the position you choose is downstream of the work you do this week.