Software turnaround foundry

Good software deserves a second operator.

We take neglected software off a founder's plate, repair what stalled, and run it for revenue. No funeral. No rewrite theater.

PricingOnboardingCheckoutRetentionSupportGrowth

01 / THE DEAL

We operate. You keep ownership.

Reclaimware takes responsibility for the product, support, releases, and growth under a written 12-month operating agreement.

01

No upfront sale

The founder grants operating rights. The code and company stay theirs while we prove the turnaround.

02

Revenue splits 70/30

Reclaimware receives 70% of net collected revenue for doing the work. The founder receives 30%.

03

Rights can revert

If we fail to ship or stop operating, the agreement defines a clean handback. No product limbo.

02 / THE FILTER

We buy evidence, not potential.

A product needs a working surface and one credible demand signal. We score every candidate out of 100 and only advance products at 80 or above.

Automatic no: unclear ownership, sensitive-data dependence, regulated financial activity, medical decisions, gambling, adult content, crypto custody, or unresolved security problems.
30

Demand

Users, installs, traffic, reviews, or revenue we can verify.

20

Distribution

A reachable audience that does not begin at zero.

20

Fixability

A meaningful improvement can ship inside seven days.

15

Economics

Low operating costs and a credible path to healthy margin.

15

Rights

Clear ownership, licenses, and transferable access.

Advance threshold80 / 100

03 / CASH ENGINE

Five-day Revenue Rescue

For founders who want the product repaired without handing over operations. We diagnose the revenue leak, implement one high-leverage fix, instrument it, and leave a 30-day plan.

First two sprints$2,500Then $5,000See the full sprint

FIELD NOTE 001

The pre-launch graveyard is not our market.

A polished codebase with zero users is not neglected software. It is unfinished market research.

Our first public marketplace scan surfaced products advertised as "production ready" but marked pre-launch. Those fail the distribution test immediately. The better turnaround target is smaller and less glamorous: a working product with a few hundred users, visible support debt, and an owner who has stopped releasing.

First repair sequence: stabilize the current promise, talk to existing users, remove checkout friction, reactivate the dormant audience, then add features only when behavior earns them.

VerdictDistribution before renovation.
Read a scored public revival memo →

04 / INTAKE

Built something useful, then ran out of road?

Give us the evidence and the ugly truth. We review every submission against the same scorecard.