Cricket Management 26

Wilks Studios · 2026 · $13.99 · Indie · deal grade B

Measured on 2026-09-24 08:14 UTC, 12 days ago. The whole catalog is re-measured daily; a game that just launched can move fast between passes.

Estimated net residual revenue: $1.9k to $2.9k per month
Opportunity: $3.1k per month at x1.30 dormancy
Estimated lifetime owners: 1.3k
70% positive across 33 reviews · 20.4 reviews/month

Why it's flagged

Developer active, last post 0 months ago
Store page localized in only 1 language(s)

Analyst notes (AI-assisted)

Note written 2026-08-31; the live figures above take precedence over any numbers in it.

Cricket Management 26 is an early-access cricket team management simulator from an independent studio, positioned as a deeper alternative to aging incumbents like Cricket Captain.

This title occupies a genuine gap in cricket simulation: the genre lacks modern, feature-rich management depth. Review sentiment splits sharply between believers (who see FM-like potential and praise developer responsiveness) and frustrated early adopters (who cite UI failures, frequent crashes, and AI/logic bugs that block progression). The studio is newly operational, the build is weeks old, and monthly residuals remain modest, but the ceiling is high if core bugs are resolved and the team can sustain momentum through full launch. This is a publishing or revival play, not an acquisition. Most realistic play: publishing.

Risk: Early access release shows repeated crash, UI lockup, and game-blocking bugs (freezes at end of innings, scoreboard state mismatches, missing .exe on launch); one reviewer suspects AI-generated code contributes to patch churn rather than systematic fixes.
Risk: Cricket management is a micro-niche; the entire addressable market may be low-hundreds of thousands globally, and competition from Cricket Captain (20+ years of refinement) and big-studio console ports remains entrenched.
Risk: Solo developer or tiny team (one studio title, domain whois suggests individual ownership) raises sustainability risk if founder burnout sets in during the post-launch slog.

This case as Markdown · Estimates carry ±30-50% error per title.