SOUTH+BRIDGE
Startups AI-translated

When a Wishlist Becomes a Graveyard

Korean indie developers launching without publishers in 2026 battle not against graphics, but against invisible accounting: refund timers and discount cycles. Break-even points are determined not by download counts, but by friction in design.

1UP · June 6, 2026 · 5 min read

AI Summary

Indie game profitability hinges less on sales figures than on design elements that prevent refunds within Steam's 2-hour window, convert wishlists into actual purchases, and sustain revenue through carefully planned 12-18 month discount cycles. For small Korean studios launching without publishers, survival depends not on producing more content, but on mastering the friction that keeps players engaged and treating sales strategy with the same seriousness as development.

When a Wishlist Becomes a Graveyard

Break-even points lie in design documents, not sales charts

Those who read indie game break-even points through sales graphs usually ask the wrong question. It's not about how much you need to earn to break even, but rather: what aspect of the game's design stops fingers from pressing the refund button? That's the real accounting.

Steam offers no-questions-asked refunds within 2 hours of play and 14 days of purchase. For players, it's a safety net; for developers, it's a timer. For shorter indie games, these 2 hours can represent half the total playtime. In other words, a game's break-even point is determined first by the density of design that holds players within the first 2 hours after launch, not by the price tag. Does increasing content reduce refunds? No. A stretched-out 2 hours actually invites the abandonment of "that's enough for me." What prevents refunds isn't quantity but friction—small resistances that make it impossible to stop, intentional scarcity that pulls the player into just one more round.

I've seen a game from a two- or three-person team in Busan that poured in a year of work. The content was sufficient. But the first 30 minutes were a tutorial. That game collapsed despite having decent wishlist numbers.

Wishlists are closer to liabilities than assets

Studios talk about wishlist numbers like bank account balances. The arithmetic goes: we've gathered 50,000, so we'll sell a few thousand copies at launch. There's a trap here. A wishlist is an intention, not a transaction. Between registration and purchase lie the launch day notification email, the price at that moment, first-day review scores, and the refund timer.

Conversion is heavily dependent on timing. Conversions concentrate on launch day and the first sale, and in the long plateau between them, wishlists slowly rot—people who only registered and forgot, people who gave their attention to other games, people waiting for a price drop. So 50,000 wishlists aren't 50,000 promised sales; they're closer to a liability that can instantly turn negative if you mishandle launch timing and first reviews. Once a single 'Mixed' review appears right after launch, algorithm visibility drops, and the accumulated wishlists die before they can even convert.

A counterargument is due here: doesn't having many wishlists mean Steam's algorithm will push you, making absolute numbers a strength? Half true. First-day exposure is clearly linked to wishlists and initial sales velocity. But the algorithm pushes 'games that sell well,' not 'games that are wishlisted a lot.' If conversion rate is low, exposure is quickly withdrawn. Numbers are just an admission ticket; the game is played by the first 2 hours of design.

The discount cycle is a game's second launch

This is where the real economics of Korean indie emerge. The full-price period is short, and a significant portion of revenue comes from discount windows—first sale, autumn, winter mega sales, bundles. A game doesn't sell once but gets 're-launched' multiple times.

But discounts aren't free. Discount too quickly or too deeply, and you betray early fans who paid full price and erode the game's perceived value yourself. Steam has rules preventing deep discounts for a certain period after launch, and there are minimum intervals between sales. So the break-even model becomes not 'sell X copies and you're done' but 'how do you design the discount curve over 12 to 18 months?' The structure is to recover development costs with first-year full-price sales, then create profit with a long tail of sales and bundles. Teams going without publishers must draw this curve themselves, but most don't know how. They spend a year making the game and a week on sales design.

All of this is visible in a single work. The indie roguelike deckbuilder 'Slay the Spire' rolled its wishlist with weekly patches throughout over a year of early access, and by launch, friction was built in from the moment you drew your first card. Before the 2 hours were up—before even the first run ended—the next run was already pulling you in. It didn't prevent refunds with content volume but with intentional resistance: different hands and insufficient resources every time. The reason this game sold again with every sale was the same—depth withstood the discount curve. On the opposite end are countless corpses that gathered wishlists with buzz and graphics only to collapse in the first 2 hours. There's no need to name them; hundreds emerge every year.

To small teams in Busan

Ultimately, the break-even point for launches without publishers is a design problem before it's a money problem. The friction in the first 2 hours that prevents refunds, the launch timing and first reviews that convert wishlists into purchases, the 18-month discount curve—none of these are solved by graphics, content volume, or buzz.

The path to survival for small teams, whether in Busan or anywhere, isn't making more. It's designing that one instance of friction that makes stopping impossible, and becoming as serious about creating the 18 months of selling it as the year spent making it. As long as you believe fun comes from content volume, break-even will forever lie beyond the next project.

This article was automatically translated from the Korean original by AI. For the authoritative version, read it in Korean.

한국어 원문 읽기 →