✓ Survived Rank 2 of 19 proposedIndie B2B SaaS Oct 31, 2026

Fixed-price dead-stack migration service with AI tooling

A productized service that ports abandoned legacy systems (ColdFusion, FoxPro, retired-maintainer embedded code) to modern stacks in weeks at a fixed price.

Open the discussion ↗

A ready-to-paste brief for Claude Code, Cursor or any coding agent.

I want to build a small, bootstrappable product. Help me plan and start the MVP.

Product: Fixed-price dead-stack migration service with AI tooling
What it is: A productized service that ports abandoned legacy systems (ColdFusion, FoxPro, retired-maintainer embedded code) to modern stacks in weeks at a fixed price.
Who pays: CTOs/ops directors at SMBs and mid-market firms whose legacy maintainers retired or who have deferred migration for a decade; $15k–$80k fixed-price projects against budget already earmarked or newly freed by the 10x cost drop.
Closest alternatives: Traditional consultancies (Thoughtworks et al., slow and expensive), TSRI / Heirloom (automated transpilation, mainframe-focused, enterprise-priced), In-house Claude Code experiments
The gap: Transpiler vendors target mainframe/enterprise at high prices and produce unreadable output; consultancies quote 12-18 months. Nobody sells a fixed-price, weeks-long, AI-driven migration aimed at SMB dead stacks with equivalence testing included.
Why now: Commenters show the cost of these migrations dropped ~100x in the last 12-18 months, but most SMBs lack an engineer who knows how to run the workflow — that expertise gap is the sellable product right now.
Moat to build toward: Repeatable per-stack playbooks plus proprietary verification tooling compound across projects; reputation/referrals in niche legacy communities.
Biggest risk: The workflow becomes common knowledge and every in-house dev does it themselves with a $200 Claude plan, collapsing service margins.

First three steps:
1. Pick one stack pair (ColdFusion->Spring or FoxPro->modern web) and productize the record/test/rewrite/verify pipeline.
2. Run 2-3 discounted pilot migrations sourced from HN/legacy forums to build case studies and timings.
3. Package pricing tiers with a migration-readiness assessment as the paid entry product.

Start by asking me up to five questions about constraints (stack, budget, timeline), then propose the smallest version a paying customer would use, and scaffold it.

Overall6.6/10

Pain7

Willingness to pay7

Timing8

Gap6

Moat4

Feasibility7

For

Who pays

CTOs/ops directors at SMBs and mid-market firms whose legacy maintainers retired or who have deferred migration for a decade; $15k–$80k fixed-price projects against budget already earmarked or newly freed by the 10x cost drop.

What people said · 4

Modernized a 20-year-old embedded codebase in ~3 months for about $20k in tokens plus half a mid-level dev, after both original maintainers retired. Read the comment ↗
A migration discussed for 12 years and estimated at 12-18 engineer-months was done in under two weeks with a $200/mo AI plan. Read the comment ↗
Reverse-engineered an old FoxPro program with Claude in a week at 99% fidelity. Read the comment ↗
Two people rewrote a production Ionic/Spring app to React-Native/Next in two weeks without paying users noticing. Read the comment ↗

Paraphrased from the discussion. Follow the links for the original comments.

Competitors and gap

Traditional consultancies (Thoughtworks et al., slow and expensive)TSRI / Heirloom (automated transpilation, mainframe-focused, enterprise-priced)In-house Claude Code experiments

Transpiler vendors target mainframe/enterprise at high prices and produce unreadable output; consultancies quote 12-18 months. Nobody sells a fixed-price, weeks-long, AI-driven migration aimed at SMB dead stacks with equivalence testing included.

Why now

Commenters show the cost of these migrations dropped ~100x in the last 12-18 months, but most SMBs lack an engineer who knows how to run the workflow — that expertise gap is the sellable product right now.

Moat · 4/10

Repeatable per-stack playbooks plus proprietary verification tooling compound across projects; reputation/referrals in niche legacy communities.

Against

Red team: Fixed-price AI-driven migration of dead SMB stacks rides a real 100x cost drop with clear evidence of paid engagements, and as a productized service it fits the indie track despite thin moat.
What would kill it: The workflow becomes common knowledge and every in-house dev does it themselves with a $200 Claude plan, collapsing service margins.

Start

First three steps: Pick one stack pair (ColdFusion->Spring or FoxPro->modern web) and productize the record/test/rewrite/verify pipeline.
Run 2-3 discounted pilot migrations sourced from HN/legacy forums to build case studies and timings.
Package pricing tiers with a migration-readiness assessment as the paid entry product.
Source discussion: Cisco gives engineer unlimited AI tokens to rewrite legacy code ↗ 294 points358 commentsFrom the commentsLinked article

#	Score	Idea	Track	Category	Pain	Pay	Time	Gap	Moat	Build
1	6.6	Abuse detection and instant kill for AI API keysMonitors LLM provider usage/billing telemetry for your API keys, flags anomalous spend within minutes and auto-revokes compromised keys.	Indie	Security	7	6	8	7	4	8
2	6.5	Continuous exposure scanner for Azure API connectionsContinuously audits Azure Logic Apps API connections for over-privileged tokens and known cross-tenant attack paths before someone else finds them.	Indie	Security	7	6	8	6	6	6

For

Against

Start

More from this issue