Dating 4 Girls

RainbowGame · 2026 · $9.99 · Adventure · deal grade B

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

Estimated net residual revenue: $848 to $1.3k per month
Opportunity: $1.6k per month at x1.50 dormancy
Estimated lifetime owners: 61.6k
96% positive across 1581 reviews · 12.7 reviews/month

Why it's flagged

Developer active, last post 5 months ago
Studio active elsewhere (3 titles tracked), so this one may welcome a partner
No Steam discount in 4.0 years (deepest tracked: -0%)

Analyst notes (AI-assisted)

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

A full-motion-video dating sim with four character routes, AI-driven dialogue, and puzzle elements that has quietly accumulated strong residual interest since 2026.

Dating 4 Girls sits in the top percentile for its genre on Steam, with 97% recent sentiment and a durable monthly revenue stream despite zero promotional activity in the past four years. The AI chat integration and multi-route narrative structure suggest technical sophistication beyond typical FMV titles. This is a candidate for catalog acquisition by a publisher seeking profitable, low-maintenance IP in the visual-novel / FMV space, or for a developer exploring AI-character licensing opportunities. The tiny current player base (1 active, 9 peak last month) and complete promotion silence suggest either deliberate dormancy or post-launch neglect by the original publisher. Most realistic play: acquisition.

Risk: FMV and dating-sim genres have narrow, volatile audiences; revival requires targeted marketing to a niche demographic unlikely to yield mainstream adoption.
Risk: The AI dialogue system is a core differentiator but may depend on third-party infrastructure, licensing, or deprecated APIs that need audit before acquisition.
Risk: Zero discounting in 48 months and minimal developer posts (3.6 months ago) suggest the title may be in royalty-collection mode rather than actively maintained; legacy code or asset dependencies could surface during integration.

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