Granny: Escape Together

CreepyToad · 2024 · $9.99 · Action · deal grade B

Measured on 2026-09-26 05:18 UTC, 10 days ago. The whole catalog is re-measured daily; a game that just launched can move fast between passes.

Estimated net residual revenue: $3.0k to $4.5k per month
Opportunity: $4.9k per month at x1.30 dormancy
Estimated lifetime owners: 67.0k
80% positive across 2015 reviews · 51.6 reviews/month

Why it's flagged

Developer active, last post 4 months ago
Store page localized in only 1 language(s)
Last discounted 0 months ago, 11 sales in the last 12 months
Proven demand elasticity: x1.5 review velocity during past deep sales

Analyst notes (AI-assisted)

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

Granny: Escape Together is a co-op horror survival game where players must escape a house while evading an AI-controlled grandmother, released by CreepyToad in 2024.

This title has found a solid niche in asymmetric co-op horror with respectable residual monthly earnings and an engaged community that skews young and multiplayer-focused. The core loop resonates (79% positive, strong replay in hard mode), but technical instability, procedural generation shortfalls, and uneven AI tuning are suppressing both retention and word-of-mouth. For a publisher or studio with live-service chops, the fundamentals warrant a technical overhaul pass and content cadence; the community is actively requesting a second map, suggesting appetite for expansion. Most realistic play: publishing.

Risk: Player reviews flag persistent bugs (AI pathfinding, item spawning, collision), performance hiccups, and balancing issues (Extreme mode perceived as RNG-heavy or exploit-prone) that erode long-term retention and recommendation intent.
Risk: Procedural generation described as shallow (five seed variants, limited randomization) limits replay variety; without a credible content roadmap, retention curves typically flatten in co-op horror titles after 30-50 hours.
Risk: Single-studio, single-title creator with modest post frequency (four per year, last developer post three months ago) suggests limited bandwidth for live updates; escalation or partner oversight will be necessary to sustain momentum.

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