RecoverPay
As described:StopNarrowed:NarrowNo as described. Go only for Razorpay and UPI Autopay merchants in India.
subscription businesses · ₹6,800 a month (~$77) · last reviewed (next review by 29 Dec 2026) · 35 cited sources
Start this week
- Tell me your hours per week available, where you're based, and whether you've built payment integrations before.
- Do the Razorpay API spike on a test account: subscription failure webhooks, mandate status, failure reasons, payment-link creation. Read the Razorpay partner and OAuth terms.
- List 40 Indian subscription businesses on Razorpay (check their checkout pages) and book 10 calls. Ask: "How many renewals failed last month, and what did you do about it?"
- Build the leakage-audit spreadsheet: export 90 days of failed and recovered payments, and turn it into a one-page ₹ report.
Checkpoints and kill gates
Decide in advance what counts as on track. Missing a checkpoint means changing the buyer or the offer, not adding features.
Day 14
~15 hrs/week
Razorpay API spike done: you can read failures and mandate status, and create payment links for a test merchant. Partner or OAuth route known.
Full-time
Razorpay API spike done: you can read failures and mandate status, and create payment links for a test merchant. Partner or OAuth route known.
If you miss it
If you can't read failures reliably, stop. The wedge doesn't exist.
Day 30
~15 hrs/week
20 merchant calls. 5 paid leakage audits or pilots (₹5,000–10,000 each).
Full-time
20 merchant calls. 5 paid leakage audits or pilots (₹5,000–10,000 each).
If you miss it
Change segment once (edtech ↔ SaaS ↔ D2C refills). Two misses: stop.
Day 90
~15 hrs/week
10 paying merchants. Median verified lift ≥3× fee versus holdout.
Full-time
10 paying merchants. Median verified lift ≥3× fee versus holdout.
If you miss it
Cut to WhatsApp recovery only, and re-run the audit offer to a new segment.
Month 6
~15 hrs/week
$1k MRR (~15 merchants). Month-3 retention ≥75%.
Full-time
$1k MRR (~15 merchants). Month-3 retention ≥75%.
If you miss it
Pivot A: mandate-health monitor only (a cheaper, narrower tool). Pivot B: sell through a billing platform (white-label to a Razorpay partner agency).
Month 12
~15 hrs/week
$3.5k MRR (~45 merchants). Churn ≤3%/month. Razorpay partner listing live.
Full-time
$3.5k MRR (~45 merchants). Churn ≤3%/month. Razorpay partner listing live.
If you miss it
Stop adding features. Fix onboarding and the report. A profitable $2–4k is a valid outcome.
Month 18
~15 hrs/week
$6.5k MRR (~85 merchants). Second rail live (only if month 12 was hit).
Full-time
$6.5k MRR (~85 merchants). Second rail live (only if month 12 was hit).
If you miss it
Put everything into the single best channel. Drop the second rail if it hasn't sold 5 accounts.
Month 24
~15 hrs/week
$10k MRR full-time (~130 merchants), or $5k at ~15 hrs/week
Full-time
$10k MRR full-time (~130 merchants), or $5k at ~15 hrs/week
If you miss it
Above target: hire one sales and onboarding person to chase $20k. Between $2k and target: run it profitably. Below $1k: stop, or sell the code and customers.
Do
1.Pick one wedge: Razorpay Subscriptions and UPI Autopay merchants in India. Drop Paddle, Lemon Squeezy, Shopify and general Stripe.
Target: 100% of year-1 revenue from Razorpay merchants
Why: Verified: Paddle Retain is free on Paddle Billing. Churn Buster and FlyCode own Shopify subscriptions. Stripe has 10+ tools. No major dunning tool lists Razorpay.
2.Recover through WhatsApp first, then SMS and email. Every message carries a one-tap UPI "pay now" link and a "switch to UPI Autopay" link.
Target: ≥60% of recoveries come from WhatsApp messages
Why: Indian customers read WhatsApp. Global tools are built around email. This is your one real product edge.
3.Prove the lift with a holdout group. Keep 10% of failed payments on Razorpay's default flow, and report recovery against that baseline.
Target: Every monthly report shows incremental ₹ recovered versus the holdout
Why: Razorpay already retries. If you can't prove your lift, the report is marketing, and merchants will work that out by month 3.
4.Lead with a free leakage audit. Read-only access produces a one-page "you lost ₹X to failed renewals in the last 90 days" report.
Target: 30% of audits convert to paid
Why: The pain is silent. Most merchants don't know the number until they see it.
5.Watch mandate health, not just failures. Flag mandates that are expiring, cancelled by the customer in their UPI app, or blocked by the ₹15,000 extra-authentication limit. Message the customer before the debit fails.
Target: 30% of saves come from pre-failure outreach by month 9
Why: This is the Indian version of "pre-dunning for expiring cards", and RBI rules create failure types that global tools don't model.
6.Price flat, in rupees, by billing volume. Starter ₹2,499, Growth ₹6,999, Scale ₹14,999 a month. Annual plan at 10× monthly. Guarantee: if verified incremental recovery is under 3× your fee, next month is free.
Target: Blended ≥₹6,500. ≥40% on annual by month 12.
Why: Churn Buster, Churnkey and Stunning all charge a flat fee by volume. Baremetrics offers a similar guarantee. A share of recovered revenue creates attribution fights.
7.Sell founder-led for the first 50 merchants. Use warm intros, Indian SaaS and D2C founder communities, and LinkedIn posts that show real (anonymised) recovery numbers.
Target: 50 paying by month 12
Why: Churn Buster grew through hands-on sales at high prices. At 15–130 customers, you can reach every buyer by hand.
8.Get listed as a Razorpay technology partner or app, and apply for OAuth access instead of asking for raw API keys.
Target: Listed by month 9
Why: It's the cheapest distribution you'll get, and it makes the security conversation easier. Partner terms are unverified: check them in week 1.
9.Publish an "Indian subscription payments failure report" every quarter, using anonymised data across your merchants: failure rates by method, by bank, by day.
Target: First report by month 9
Why: Nobody publishes Indian involuntary-churn data (the research found none). It earns backlinks, press and trust, and it becomes your data moat.
10.Automate operations. Onboarding in 15 minutes, template library in 4+ Indian languages, self-serve reports, no custom work under the Scale plan.
Target: ≤2 support hours per 10 merchants a month
Why: Keeps the product running on ~15 hrs/week and keeps margin ≥85%.
11.Keep the merchant as data owner. Sign a DPA with each merchant, register SMS templates under DLT, use WhatsApp utility templates with opt-in, never hold money, and encrypt API keys.
Target: Zero security incidents. Zero funds held.
Why: DPDP, TRAI and WhatsApp rules all apply to messaging someone else's customers. Payment links go to the merchant's own Razorpay account.
12.Add a second rail only after the Razorpay gate: Cashfree or PayU subscriptions, or Indian SaaS on Stripe whose India-issued cards Stripe won't retry.
Target: Second rail live by month 15, only if month-12 gate is hit
Why: It's the only route to $20k+ without owning an implausible share of one gateway's merchants.
Avoid
1.The multi-platform pitch ("we cover the platforms the big players miss")
Why: Most of those platforms aren't underserved. Paddle Retain is free for Paddle Billing. Lemon Squeezy has no retry API and is moving to Stripe Managed Payments. Shopify subscriptions belong to Churn Buster and FlyCode.
2.General Stripe dunning
Why: Stripe includes Smart Retries, recovery emails and a card updater in its 0.7% Billing fee, and says it recovered $8.2bn in 2025. At least 10 other tools (Churn Buster, Churnkey, Baremetrics, Stunning, FlyCode, Rechurn, Redux, Slicker and more) already sell to these accounts.
3.Performance pricing (a share of recovered revenue) as the default
Why: You'd argue every month about what counts as "recovered" when Razorpay retries anyway. A flat fee plus a holdout-backed guarantee is cleaner. Offer a share only to Scale merchants who ask for it.
4.Promising "smart retries" on Razorpay before you've tested the API
Why: RBI rules require a 24-hour pre-debit notice and extra authentication above ₹15,000. Whether a third party can trigger retries is unverified. Your edge is in messaging and mandates, not retry timing.
5.Cancel flows in v1
Why: Churnkey, Churn Buster and Paddle Retain do them well. They need in-app code from the merchant, which slows onboarding. Add them after month 12 if merchants ask.
6.Global, USD-priced sales before the Razorpay gate
Why: You'd go head-to-head with a dozen tools that have years of data.
7.Inflated "recovered" numbers (counting payments Razorpay would have recovered anyway)
Why: The first merchant who checks will cancel and tell others. Indian SaaS founder circles are small.
8.Holding or routing money (collecting on the merchant's behalf)
Why: That's payment aggregator territory under RBI rules. Every payment link goes to the merchant's own Razorpay account.
9.Unregistered SMS, or promotional-style WhatsApp messages
Why: TRAI DLT rules block unregistered templates. WhatsApp can downgrade or block a number that sends marketing through utility templates. Either one stops recovery overnight.
10.Human calling ("collections agents") as a product line
Why: Gravy does human-powered recovery at scale. It's staff-heavy, it hurts margin, and debt-collection conduct rules create reputational risk.
11.Custom work for one large merchant
Why: One Scale merchant asking for custom flows can eat your ~15 hours a week. Keep a public roadmap and say no.
12.Raising money
Why: The ceiling on this wedge is modest, and it doesn't need capital. See analysis/06.
13.Adding features when a checkpoint fails
Why: A miss means the wrong segment or the wrong proof. Change the segment (edtech vs SaaS vs D2C) or the report, not the feature list.
14.Storing more customer data than you need
Why: Keep the phone number, email, amount, failure reason and mandate status, for 90 days after the case closes. Don't keep card data, and don't build profiles.