138,000 Wishlists. 581 Sales. Now What?

Wednesday, 11pm, refreshing a page that isn't changing

Say it's 138,000 wishlists and 581 sales in launch week. Whatever your actual figures are, the ratio between them is the number you've now calculated four different ways hoping one of them comes out differently.

Four years. Wishlists were the metric everyone told you to chase — every marketing talk, every post, every Discord. You chased it. You hit it. The thing it was supposed to predict didn't happen.

Someone in your Discord has already said "just discount it." Someone else says patch the launch bugs first. Your partner asked, carefully, what the plan is. And you've booked a review with yourself for Monday because you can't keep making this decision at midnight.

Two questions are tangled together here, and mixing them is why you can't sleep. What broke is answerable with data you already have. Whether to keep going isn't a spreadsheet question at all, and treating it as one will hand you a wrong answer with a confident face on it.

Which link broke

A wishlist becomes a sale through a chain, and every link fails differently.

Wishlist to notification. Steam emails and notifies wishlisters when a game releases. That's the mechanism the whole strategy rests on. But a wishlist added twenty-two months ago by someone who saw a trailer once isn't the same asset as one added three weeks ago by someone who played your demo. The Steamworks wishlist report shows you when they were added, and shows deletions. Look at the age curve. If the bulk of your list came from one spike a long time back — a viral tweet, a festival, a bundle for a different game — the notification went out to people who no longer remember your game exists.

Region. Wishlist numbers by country live in the Regional sales report page, not in the wishlist report itself. A wishlist from a region where your price is a serious fraction of a day's earnings converts differently from one where it's a coffee. If a large share of your list sits in territories where you're priced high against local norms, the conversion was never going to look like the figures you've been reading.

Launch window. What else came out that week? Not whether there was competition, there always is, but specifically: did something enormous land in your genre within a few days either side, and did a big sale event overlap? Steam gives new releases launch visibility, and that visibility is a share of attention rather than a fixed allocation.

Store page. The link people skip, because it's the one that hurts. The traffic breakdown in Steamworks tells you how many people reached the page during launch week and what fraction of them bought. Lots of arrivals and few purchases points straight at the page. The usual cause is that the page promises a different game than the trailer does, or that the first two screenshots don't communicate what you actually do in the game inside about a second and a half. Ask five people who've never seen it to tell you what the game is, from the page alone, and write down what they say without correcting them.

The game itself. Read the review text. The score is an average of a few hundred strangers and tells you nothing about why. Refund rate matters more than the score, and you can see it — a game people buy and refund has a different problem from a game people don't buy.

These aren't mutually exclusive, and the store page is the one people skip, so check it even if you're certain it isn't that.

About the discount everyone's recommending: check your own dates in Steamworks before you plan around it. A discount generally can't run within 30 days of release, or within 30 days of a launch discount ending. Whenever your window does open, spending it on a problem you haven't diagnosed gets you a cheaper game and the same conversion.

And on the ratio you think you've failed — Valve's own wishlist documentation says there's no formula to accurately predict sales from wishlists, because people wishlist for different reasons. The conversion figures that circulate in Discords are self-reported, from developers with a reason to share, across wildly different genres and price points. Anecdotes, not a bar you missed.

Someone to read the breakdown with

What you want this week isn't encouragement. It's someone to go through the Steamworks numbers with you and say which link they'd bet on.

Indie Game Dev Maya is a TrueTalk persona: an indie developer and creative director character whose areas are indie game development, game design and the creative process. An AI, not somebody who has shipped a game. Free for the first conversation, a subscription after that. Worth an hour at 11pm when the Discord's gone quiet, if only to say the numbers out loud to something that will ask you what your first screenshot shows.

Six months, and what else you'd do with them

Start by getting the four years out of the decision. They're spent — spent if you patch on Tuesday, spent if you shelve it on Monday, and no choice available to you recovers them. What's actually on the table is the next stretch of your life. Call it six months.

So ask it that way. Is the next six months on this game the best available use of six months?

That's genuinely open, and the answer isn't automatically no. Continuing can be right if:

• The reviews from the people who did buy are good. A game 581 people liked has something in it. A game 581 people were lukewarm about is a different situation, and you already know which one you have.
• You've found a specific, cheap break in the chain. A store page that misrepresents the game qualifies — that's a weekend, not a year.
• There's a real second shot on the calendar: a festival-style event, a platform port, a sale window, a content update that gives you a legitimate reason to be visible again.

It can also be wrong even when the game is good, which is the part that stings. No runway. Six months that would come out of savings you actually need. The feeling that the work has quietly become a way to avoid admitting something. Those outweigh the merits of the build.

If this has gone past disappointment — if you're not sleeping, or the thought of Monday is bringing something heavier than dread — that's a GP or a therapist, and it comes before the store page does. Developers write openly about how hard the weeks after a launch can be. Treating that as a business problem to out-work is how people lose a year.

One more honest thing. Games do sometimes find their audience later: a sale, a streamer, a port, an update, a year of slow word of mouth. It happens. It also doesn't happen far more often, and the cases you've heard about are precisely the ones where it worked, which is why you heard about them. Don't plan on being one. Don't rule it out either. Nobody can tell you which you are.

What you can do is stop making the call on feel. Pick the two or three things you'd fix, give them a defined window — six weeks, not "until it works" — and write down tonight, while it still hurts enough to be honest, what number would count as movement. Then let Monday-you be bound by Wednesday-you's judgement, because Monday-you will have read the reviews again.