Plan of ActionBalatro
Steam AppID 2379780 - Generated 6/20/2026
WillitWishlist Score
4.72
Exceptional wishlist presentation
Balatro already has exceptional Steam-page alignment. This plan focuses on protecting its simple core hook while segmenting future campaigns and monitoring the few recurring sources of player friction.
AI summary export is currently in alpha testing. Review recommendations before using them in production planning.
Executive priority
- Protect the “poker roguelike” opening sentence across every major campaign.
- Show one understandable decision before extreme combo spectacle.
- Keep campaign variations recognisably Balatro through cards, Jokers, CRT texture, and the established palette.
What is already working
- The store pitch creates an immediate mental model.
- Every major asset reinforces the same player fantasy.
- Public feedback repeats the same synergy, replayability, and flow-state benefits.
- The capsule owns a distinctive visual shorthand at small sizes.
30-day action plan
- Week 1: audit all active assets against the one-line core promise.
- Week 2: create three trailer openings for strategy, poker-curious, and broad indie audiences.
- Week 3: test whether each opening explains the decision before showing the payoff.
- Week 4: compare click-through, trailer retention, and repeated public language by audience segment.
Community feedback actions
- Turn repeated synergy-discovery language into update headlines and creator briefs.
- Explain that deep poker knowledge is not required in FAQ and onboarding-facing content.
- Track high-stakes frustration separately from general difficulty feedback.
- Preserve the positive one-more-run language without making unqualified behavioural claims.
Price and player-count monitoring
- Use player-count peaks as public attention markers, not sales totals.
- Record verified price and discount snapshots before interpreting future changes.
- Compare update, sale, and major announcement dates against the same monthly player series.
- Do not attribute a player-count change to price without a corresponding verified event.
Final launch-marketing checklist
- One clear hook above the fold.
- Gameplay shown before accolades.
- Screenshots ordered from simple decision to build payoff.
- High-intent mechanical tags first.
- Audience-specific campaigns retain the same core sentence.
- All public metrics labelled with their limits and source dates.
Benchmark note
Benchmark context is directional and should be compared against games at the same launch or visibility milestone. Public concurrent-player and review data are interest signals, not private sales figures.
View benchmark source