Case Study 2: Balatro — How LocalThunk Marketed a Card Game into GOTY Contention

Balatro is a poker-themed deckbuilding roguelike built by a single developer working under the name LocalThunk. It was released on February 20, 2024, on PC (Steam, Epic, GOG), Mac, and shortly after on every major console. In its first week it sold over two hundred fifty thousand copies. By the end of 2024 it had sold approximately five million copies and was nominated for Game of the Year at multiple major award shows, including The Game Awards, where it won several categories and was nominated for GOTY itself. In less than a year, a solo developer had made one of the most successful indie games of the decade.

Unlike Among Us, Balatro was not a lucky timing event that a team failed to cause. Its success was engineered — through specific, deliberate marketing choices made by a solo developer over roughly eighteen months of pre-launch work. Because of this, it is the more useful case study for the kind of developer this book addresses: someone who does not have millions to spend on PR and cannot count on a pandemic to deliver their audience.

Here is what LocalThunk did.

The Design That Made the Marketing Possible

First, the design. Balatro is a single-player deckbuilding roguelike where the player builds poker hands to score points, purchases Jokers that modify scoring in increasingly ridiculous ways, and attempts to beat escalating score thresholds across a run that typically lasts thirty to sixty minutes. The mechanic is deep (hundreds of Jokers, countless combinations, emergent synergies) but the core loop is instantly legible (everyone knows poker hands; everyone understands "score more points than the target"). Runs end in either victory or defeat, and each run tells a small story.

The visual aesthetic is lo-fi. The cards are pixel-art representations of standard playing cards. The UI is deliberately retro, evoking early Windows dialog boxes and casino video games of the nineties. The color palette is warm, neon-saturated, and immediately recognizable.

All of these choices turned out to be marketing choices as much as design choices. The deep-but-legible mechanic produced shareable moments — a Joker combo that scored a million points in a hand reads immediately on screen, even to a viewer who has no idea how the game works. The lo-fi aesthetic reads well at small resolutions (TikTok, thumbnails, retweets). The thirty-to-sixty-minute runs meant streamers could play an entire run in one segment. The game was, by the accident of its design, perfectly shaped for the 2024 content-creator landscape.

Whether this was deliberate or intuitive, it matters less than the fact that it was true. LocalThunk had made a game that could be marketed effectively with the tools available to a solo developer.

The Slow Build: Demos and Next Fest

LocalThunk did not launch Balatro in 2024 with a viral splash. He built toward it for roughly eighteen months.

The first public demo appeared in mid-2022. It was posted on itch.io as a free prototype. It contained a small subset of the Jokers and mechanics, ran well in a browser, and was shared in deckbuilder-fan communities on Reddit (/r/slaythespire, /r/roguelikes), Discord servers, and Twitter. Early adopters discovered it, played it, and began sharing clips.

The Steam store page went live in late 2022 or early 2023, with a trailer, screenshots, and a "Coming Soon" status. Wishlists began accumulating — at first slowly, then faster as the demo generated word of mouth.

LocalThunk participated in Steam Next Fest — at least one, arguably multiple Next Fests in the year leading up to launch. The Next Fest demo was polished, offered several full runs, and was built to leave players wanting more. It was covered in Next Fest "best demos" articles by indie-focused content creators. Wishlists spiked during each Next Fest and continued to grow between them.

By the time the game launched in February 2024, Balatro had accumulated a large wishlist base — estimates place it well above a hundred thousand, with some sources suggesting significantly more. This base was not the result of a single marketing moment; it was the compound accumulation of eighteen months of steady, demo-driven, Next-Fest-anchored visibility.

The lesson for a solo developer: wishlists are not earned in a week. They are accumulated over a year or more of deliberate, patient work, punctuated by a handful of specific high-leverage moments (a demo drop, a Next Fest participation, a showcase appearance).

The TikTok Factor

If the slow build was the foundation, TikTok was the accelerator.

TikTok as a platform rewards specific kinds of content: short vertical videos (thirty to sixty seconds), bold visuals that read at a glance, meme-able audio, and narrative hooks. Balatro clips fit this pattern almost perfectly. A typical viral Balatro TikTok might show: a player builds a ridiculous Joker combination, takes a deep breath, plays a single poker hand, and watches as the score explodes by a factor of a hundred. The visual is the numbers going up impossibly fast. The audio is often a dramatic or meme-worthy music cue. The entire clip is fifteen to thirty seconds. It is shareable, rewatchable, comment-bait ("how did this combo work?"), and genre-portable — even viewers who do not play deckbuilders understand "big number good."

LocalThunk did not have a massive TikTok presence himself. What he did was make a game whose moments translated naturally to the format. TikTok users — streamers, gaming content creators, and ordinary players — created the content. The algorithm did the rest.

This is an important distinction. Not every indie developer needs to personally become a TikTok influencer. What they need to do is make a game whose best moments are portable, clippable, and genre-legible. Balatro is, in retrospect, maximally portable to short-form video.

Developers who want to learn from this should ask a specific question about their own game: what thirty-second clip of my game, if posted on TikTok with the right audio, would make a stranger scrolling past want to wishlist it? If you cannot answer this question — if your game's best moments are slow, require context, or only land after hours of setup — you have a marketing challenge that is worth solving before launch, not after.

The Solo-Dev Persona

LocalThunk maintained a deliberate public persona throughout development and launch. He was active on Twitter and Reddit but not prolific. He wrote occasional developer blog posts. He appeared on podcasts and interview pieces. He was known for a friendly, slightly self-deprecating voice, for being obviously passionate about the game, and for being a solo developer in a genre often dominated by small teams.

This persona mattered. Indie audiences respond to solo developer stories — Eric Barone for Stardew Valley, ConcernedApe (the same developer), Toby Fox for Undertale, Lucas Pope for Papers, Please and Return of the Obra Dinn. The "one person made this" story is inherently compelling. It is also credible: a solo developer's games have a coherence that team-made games sometimes lack.

LocalThunk leaned into this without overplaying it. He was not constantly talking about being solo. He was not making it his brand. He was simply making the game, sharing progress, and being authentically present in the communities where his players were. When interview opportunities came, he took them. When they did not come, he did not chase them.

The broader lesson: a solo developer has a specific marketing asset — their own authorship — that larger teams do not. This asset is most valuable when it is used sparingly and genuinely, not performatively.

The Publishing Partner: Playstack

Balatro was published by Playstack, a London-based indie publisher. This fact is often obscured in the "solo developer succeeds" narrative, because it complicates the pure-solo story. It is worth addressing directly.

Playstack's role was significant in specific areas: platform ports (console launches on PlayStation, Xbox, Switch, mobile), localization (over twenty languages at launch), QA, marketing coordination, and PR. LocalThunk remained the sole developer, the sole creative voice, and the owner of the IP. But the scale of the launch — simultaneous PC and console, twenty-plus languages, coordinated press — would not have been possible for a true solo operation.

This is important because it reveals the limits of the "solo dev does everything" narrative. Balatro's success depended on the developer's craft and on a publisher handling the operational scale. Had LocalThunk self-published PC-only with no localization, the game would still have been excellent — but it would likely have sold a fraction of five million copies.

The lesson for a solo developer reading this book: the choice between self-publish and publisher is not a moral choice but a pragmatic one. Balatro makes sense as a case study because the developer chose to partner with a publisher to achieve the scale the game deserved. A smaller solo developer with a smaller-scope game might correctly choose self-publishing. A developer with a game that has larger ambitions — multi-platform, multi-language, console-era scale — should seriously consider a publisher, and Balatro is the model of what that partnership can look like when it works.

Post-Launch Update Cadence

After the February 2024 launch, LocalThunk continued to work on the game. Updates came at a measured pace — not hourly patches, not weekly drops, but substantive additions every few months. The 1.0 release was followed by patch 1.0.1, then balance updates, then the Friends of Jimbo collaboration series (which added crossover Jokers featuring characters from other indie games — Dave the Diver, Slay the Spire, Vampire Survivors, The Witness, Cyberpunk 2077, and more).

The Friends of Jimbo updates deserve specific note. Each collaboration was a free addition to the game. Each was a marketing moment in itself — a press story, a partnership, a cross-community promotional opportunity. Each brought the Balatro audience into adjacent games' awareness and vice versa. And each was a small content update that returned the game to the front page of news cycles.

The post-launch marketing lesson: a successful game's updates are themselves marketing. Each content patch, each collaboration, each balance pass is a reason for the press to write, for streamers to revisit, for dormant wishlisters to convert, and for owners to re-engage. Post-launch work is not "what you do after marketing" — it is marketing.

What You Can Take From This

Most readers of this book are not going to build Balatro. It is a specific game with a specific appeal, and replicating its success is not a template. But the marketing practices LocalThunk demonstrated are replicable. Here is what a solo developer or small team can take:

Start your demo strategy early, iterate on it, and run it through at least one Steam Next Fest. This is the single biggest takeaway. LocalThunk did not market Balatro by posting a trailer on Twitter two weeks before launch. He seeded a demo for eighteen months and used Next Fest as his amplifier. Your plan should include a demo and should include a specific Next Fest date to target.

Design for clippability. If your game's best moments do not survive compression to a thirty-second TikTok, your game is fighting the 2020s discovery environment. You can either redesign moments to be more portable, or accept that your marketing will depend more on long-form content (YouTube Let's Plays, reviews) and less on short-form viral spread. Both are valid — but you should choose deliberately, not by accident.

Cultivate a solo-dev persona if that is what you are. Not performatively. Authentically. If you are a solo developer, let people see the work. Post occasional devlogs. Appear in community Discords. Be the human behind the game. This asset compounds.

Partner with a publisher for scale if the game deserves scale. Balatro with Playstack sold multiples of what Balatro self-published PC-only would have. The same logic applies to your game: if the ambition is multi-platform and multi-language from day one, a publisher partner is usually the right call. If the ambition is smaller, self-publishing may serve.

Plan post-launch content as marketing, not maintenance. LocalThunk's Friends of Jimbo collaborations were as much a marketing strategy as a content strategy. Your post-launch roadmap should be shaped partly by what will generate press, partnerships, and re-engagement — not just by what bugs need fixing.

Be patient. Eighteen months of pre-launch work, polished and sustained, produced a launch with enough wishlist fuel to burn for months. A six-week marketing sprint does not. If your launch is eight weeks away and you have not started, the honest advice is to delay the launch.

Balatro is not a miracle. It is what happens when a developer with taste, patience, and discipline executes a coherent marketing plan for eighteen months, against a well-designed game whose moments happen to be perfectly legible on the platforms where 2024's audiences live. Most of the elements of that plan are available to any solo developer with the time and intention to do the work.

The uncomfortable truth is that marketing is a craft, like level design or combat tuning, and like those crafts it rewards sustained attention over months and years. LocalThunk did not "get lucky." He did the work. The work paid off. That is the only lesson that matters.