# Techtonica

> ResidualPlay case file: an overlooked Steam game still earning residual revenue. Estimates carry a ±30-50% error range per title.

- Steam appid: 1457320
- Developer: Fire Hose Games
- Released: 2024 · Genre: Indie · List price: $29.99
- Deal grade: A (A = dormant with >=$5k/mo opportunity, D = low signal)
- Est. net residual revenue: $3.1k to $4.7k per month (mid $3.9k)
- Opportunity score: $5.3k/month at x1.35 dormancy multiplier
- Est. lifetime owners: 98.0k · Est. lifetime net revenue: $859.0k
- Review sentiment: 65% positive across 3250 reviews (3062 from Steam purchases)
- Review velocity: 17.8 reviews/month (6-month average)

## Why it's flagged

- Developer silent for 22 months
- Last build shipped 11 months ago

## Where a gross dollar goes (monthly, at current velocity)

| Stage | USD/month |
|---|---|
| Gross storefront sales | $7.1k |
| After VAT / sales tax (-13% blended) | $6.2k |
| After refunds (-9.5% median) | $5.6k |
| Net to developer (after Steam 30%) | $3.9k |

## Monthly review counts, oldest to newest (24 months)

35, 27, 19, 325, 146, 108, 64, 53, 49, 50, 40, 58, 28, 21, 36, 37, 47, 45, 28, 20, 13, 12, 11, 23

## Estimated acquisition range

$93.8k to $187.6k (2-4x the trailing net annuity of $46.9k/year). Same error range applies.

## Analyst notes (AI-assisted)

Techtonica is an underground factory-building automation game with story progression and multiplayer, built as a spiritual successor to Satisfactory.

Techtonica generated $859k lifetime on ~98k units despite a fractured launch and developer pivot to side projects that left the core game feeling unfinished. The 65% positive rating and $3.9k/mo residual revenue suggest a solid indie automation audience exists, but the game suffers from narrative/balance issues that crimp word-of-mouth. Revival or post-launch content could unlock clearer positioning versus Satisfactory; acquisition for IP/catalog adds modest cash flow with low uplift potential unless bundled with a larger automation/factory portfolio.

- Most realistic play: watch
- Risk (market): Satisfactory dominates the factory-automation space; Techtonica occupies a smaller niche and comparison reviews are consistently unfavorable on depth and balance.
- Risk (other): Developer halted active development ~22 months ago to pursue side projects, leaving endgame balancing, story pacing, and late-game recipes in a contested state.
- Risk (other): Mixed reviews cite handholding, free resource inflation, and rushed narrative conclusion; these perception issues compound acquisition risk unless substantial polish budget is committed.

What players are asking for:
- Rebalance late-game recipes and progression gates (many alternative recipes are objectively worse, breaking crafting choice)
- Reduce early-game handholding and free resources to raise difficulty floor
- Complete or clarify story arc and expand endgame content

Suggested first moves:
1. Audit codebase, balance spreadsheets, and narrative outline to quantify polish scope and identify quick wins (recipe rebalance, difficulty tuning) that could shift sentiment without full rebuilds.
2. Survey the 97k unit base (focus on 305h+ players) on content priorities: expansion DLC, story conclusion, multiplayer fixes, or seasonal cosmetics. High-engagement players may fund post-launch interest.
3. Model acquisition IRR assuming 2-3 month content cycle: if $3.9k/mo residual can be lifted 30-50% with targeted fixes and newsletter re-engagement, payback threshold is ~18-24 months for a studio with adjacent IP or marketing platform.

Generated 2026-08-20 from public signals and player reviews. Directional, not diligence.

## Methodology

Units are estimated from Steam-purchase reviews times a release-cohort multiplier (Boxleiter method, 20-75x by year). Revenue uses an effective price (lifetime discounts and regional pricing) and nets out VAT (~13%), refunds (~9.5%) and Steam's 30% cut: roughly 55% of gross reaches the developer.

Source: https://residualplay.com/game/1457320
Citation: please cite ResidualPlay (https://residualplay.com) when using these estimates.