RecoverPay (working name)
Idea status: Idea stage · Target: an MRR ladder ($1k → $50k by month 24) · Verdict: No as described. Go only as failed-payment recovery for Indian subscription businesses on Razorpay and UPI Autopay. · Last updated: 30 Sept 2026
Start here → WHAT-TO-DO-AND-AVOID.md: odds at each MRR level (with conditions, ~15 hrs/week / full-time: $1k ~50% / 65%, $5k ~22% / 34%, $10k ~11% / 20%, $20k ~4% / 9%), 12 do's, 14 avoids, checkpoints.
Where this idea came from: it was picked out in the 30 Sept 2026 micro-SaaS research as a bootstrappable B2B idea with a provable money outcome. "RecoverPay" is a working name. Check trademark and domain availability before using it publicly.
The idea in one line: dunning for subscription businesses. It runs smart retries, card-update emails and SMS, pre-dunning for expiring cards and cancel-flow saves, and it proves its value monthly with a "we recovered $X for you" report.
The wedge this review picked: Razorpay Subscriptions and UPI Autopay merchants in India. None of the big dunning tools integrate with Razorpay. Stripe doesn't retry India-issued cards. Paddle, Lemon Squeezy, Shopify subscription apps and plain Stripe accounts are already covered, some of them free. See analysis/02.
Research was run on 30 Sept 2026, with a confidence level on each claim. See research/10-verified-research.md.
Folder layout
recoverpay/
├── WHAT-TO-DO-AND-AVOID.md ← final analysis and decision (read first)
├── README.md ← this index
├── analysis/ ← the investor-style assessment
│ ├── 00-one-page-brief.md
│ ├── 01-verdict.md
│ ├── 02-market-reality-check.md
│ ├── 03-feature-scrutiny.md
│ ├── 04-expanded-feature-catalog.md
│ ├── 05-pre-mortem.md
│ ├── 06-fundability.md
│ ├── 07-gaps.md
│ └── 09-assumptions-and-open-inputs.md
├── plans/ ← execution plans
│ ├── 08-90-day-plan.md
│ └── 11-24-month-gated-roadmap.md
└── research/ ← cited evidence
└── 10-verified-research.md
File numbers match the other ideas in this portfolio, so cross-references like "doc 08" work the same way.
Documents
| # | Document | What it answers |
|---|---|---|
| — | WHAT-TO-DO-AND-AVOID.md | Final decision: MRR ladder odds, customer math, 12 do's, 14 avoids, checkpoints |
| 00 | analysis/00-one-page-brief.md | The whole assessment on one page |
| 01 | analysis/01-verdict.md | MRR ladder for 5 wedges and 2 time commitments, base rate, Tier A/B, fundable yes/no |
| 02 | analysis/02-market-reality-check.md | Buyer, pain score, native platform tools, competitors and their pricing, wedge comparison, market size |
| 03 | analysis/03-feature-scrutiny.md | Each stated feature sorted into Table stakes, Differentiator, Distraction or Liability |
| 04 | analysis/04-expanded-feature-catalog.md | About 35 features merchants ask for, classified and prioritised for the wedge |
| 05 | analysis/05-pre-mortem.md | Three most likely causes of death, warning signs, fixable or not |
| 06 | analysis/06-fundability.md | Would I invest, the skeptic's first 5 minutes, proof points, bootstrap vs raise |
| 07 | analysis/07-gaps.md | Gaps to pay, renew and refer, plus the compliance map (DPDP, TRAI DLT, WhatsApp, RBI, API keys) |
| 08 | plans/08-90-day-plan.md | First 90 days, week by week, sized for ~15 hrs/week |
| 09 | analysis/09-assumptions-and-open-inputs.md | Assumptions made, and the inputs that would change the verdict |
| 10 | research/10-verified-research.md | Cited research with confidence levels, and what's still unverified |
| 11 | plans/11-24-month-gated-roadmap.md | Month 0–24 phases, gates, revenue path, what $20k needs |
Caveat
Team, location, hours per week and payments experience were not provided. The assumptions are in analysis/09. The biggest unverified items are: how many Razorpay merchants bill ₹5 lakh or more a month in subscriptions, how many retries Razorpay runs and whether a third party can trigger them, and Indian involuntary churn rates. See research/10.