ResidualPlaybeta Open the radar

Never Second in Rome

Alessandro Roberti · 2026 · $12.99 · Indie · deal grade B

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

  • Estimated net residual revenue: $2.5k to $3.8k per month
  • Opportunity: $4.1k per month at x1.30 dormancy
  • Estimated lifetime owners: 25.5k
  • 81% positive across 644 reviews · 28.7 reviews/month

Why it's flagged

  • Developer active, last post 1 months ago
  • Studio active elsewhere (2 titles tracked), so this one may welcome a partner
  • Store page localized in only 1 language(s)
  • Last discounted 3 months ago, 2 sales in the last 12 months

Analyst notes (AI-assisted)

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

Never Second in Rome is a historical tactical RPG sequel where you manage a Roman soldier's career and legion through complex century-level combat and administrative systems.

This is a quiet indie sequel with a devoted but narrow audience: Roman history enthusiasts and systems-heavy tabletop players who prize mechanical depth over accessibility. The title has generated solid residual revenue on minimal promotional spend and maintains a loyal 30% returning player base. For a small publisher or studio seeking a completed, profitable catalog asset with zero discount activity and room for localization (particularly German, which has a 9% language gap), this represents low-risk acquisition territory; revival potential exists through targeted marketing to wargaming and historical strategy communities, though the UI and onboarding friction are well-documented pain points. Most realistic play: acquisition.

  • Risk: Ultra-niche appeal and high complexity create a ceiling on player acquisition; reviews show distinct love-it-or-hate-it split driven by expectations set by the simpler predecessor.
  • Risk: Multiple player complaints about UI clarity and combat opacity suggest the game's onboarding and tutorial systems may require redesign to expand the audience.
  • Risk: Heavy reliance on a solo developer (Alessandro Roberti); no updates logged in recent months despite operating studio status, raising questions about continued support capacity.

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