Deck & Conn

Funtime Electrics · 2026 · $14.99 · Simulation · deal grade A

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

• Estimated net residual revenue: $11.2k to $16.8k per month
• Opportunity: $18.2k per month at x1.30 dormancy
• Estimated lifetime owners: 4.6k
• 76% positive across 120 reviews · 111.1 reviews/month

Why it's flagged

• Developer active, last post 0 months ago
• Studio active elsewhere (2 titles tracked), so this one may welcome a partner
• Last build shipped 0 months ago
• Store page localized in only 1 language(s)

Analyst notes (AI-assisted)

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

A retro-styled turn-based space-ship command simulation where you manage tactical systems and crew decisions across procedural patrol missions.

Deck & Conn occupies a rare niche in tactical space sims with strong artistic direction and mechanical depth, but ships with critical quality-of-life gaps (no mid-mission saves, repetitive mission structure, unfinished systems balance) that suppress word-of-mouth and player retention. The title is currently a quiet earner with solid residual traffic and a vocal minority of enthusiasts, but represents either a post-launch polish opportunity for a patient publisher, or a licensing play if MicroProse intends to fold it into a larger IP strategy. The developer remains active and responsive; the upside lies in addressing a short list of completion items rather than fundamental redesign. Most realistic play: publishing.

• Risk: Developer history: prior title Objects in Space was left incomplete; players cite this when assessing commitment risk to ongoing support for Deck & Conn.
• Risk: Mission repetition and shallow content depth are cited repeatedly as dealbreakers; current player base is self-selected for tolerance, limiting growth without content expansion.
• Risk: Save-system absence mid-patrol is the single most-cited blocker in reviews; softlocks and procedural mission sameness also noted; these are solvable but require active engineering bandwidth.

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