7. What's Missing: The Gap Between Built and Paid, Renewed, Referred

Assumption: nothing is built yet. So these are gaps between the plan and a business.

7.1 Gaps to pay

Gap	Why it blocks payment	Fix
No single wedge	You can't write a landing page, a sales script or an integration for five platforms at once	Razorpay Subscriptions and UPI Autopay merchants in India. Nothing else until month 12.
No price	Undefined. The price decides who you sell to.	Starter ₹2,499 (up to ₹5 lakh a month billed), Growth ₹6,999 (₹5–25 lakh), Scale ₹14,999 (₹25 lakh–1 crore), custom above. Annual = 10× monthly.
Silent pain	Merchants assume "Razorpay handles retries" and have never measured leakage	Free leakage audit: 90 days of failures turned into one ₹ figure. Run it by hand for the first 20.
No risk reversal	A small merchant won't pay ₹7,000 on a promise	Guarantee: if verified incremental recovery is under 3× the fee, next month is free. Baremetrics offers a similar guarantee.
No trust signals	You're asking for API access to their payments	Security page, DPA, encrypted keys, OAuth or partner-app connection, named founder, and case studies with ₹ figures.

Gap	Fix
"It's fixed now" churn. Once failures drop, the merchant forgets why they pay.	The monthly report shows the counterfactual: "without RecoverPay, the holdout group lost X%, so you'd have lost ₹Y."
Low visible activity. Recovery runs in the background.	A weekly one-line WhatsApp or email to the merchant: "₹42,300 recovered this week, 18 customers saved."
Attribution doubts	Holdout on every account. Export the raw case list so their finance team can check.
Billing-system switch (moving to Chargebee or another gateway)	Support the second rail by month 15. Offer to migrate with them.
Messaging channel breaks (WhatsApp quality drop, DLT rejection)	Channel health monitoring, automatic fallback to SMS and email, and alerts to you before the merchant notices.

Gap	Fix
Nothing visible to other merchants	A subtle "Recovery by RecoverPay" line on the pay-now page. It's seen by customers, not merchants, so its value is low. The real loop is founders talking.
No free hook	The leakage audit and a public "failed payment leakage calculator" for Razorpay merchants.
No community reason to talk about you	The quarterly Indian subscription failure report: benchmarks every founder wants to compare against.
No referral economics	One month free for each referred paying merchant. A revenue share for billing consultants and Razorpay partner agencies who bring merchants.

Missing entirely from the idea. There's no mention of how the first 15 merchants arrive.
Channels that fit this buyer: warm founder intros (Indian SaaS, edtech and D2C founder networks), LinkedIn posts with real anonymised ₹ figures, a Razorpay partner or app listing, billing and payments consultants, and the quarterly report for press and backlinks.
Channels that burn cash: paid search on "dunning" (global competitors bid on it), and broad ads to "subscription businesses".

Current: "dunning for underserved billing platforms". Weak. Most of them aren't underserved.
Better: "Get back the renewals UPI Autopay and card mandates lose you. On WhatsApp, in your customers' language, with proof every month."
One sentence, one buyer, one outcome.

Founder-led for the first 50. Audit → call → 30-day pilot → paid.
Self-serve onboarding from about merchant 30, once the flows are stable.
At ~15 hrs/week: at least 5 hours a week on sales, or the ladder odds don't hold.

Area	Requirement
Data protection	India DPDP Act 2023 and its rules: the merchant is the data fiduciary and you are the data processor. Sign a DPA, keep data only as long as needed, delete on request. GDPR only applies if merchants have EU customers.
SMS	TRAI DLT: register the sender header, the content templates and the consent. Unregistered messages are blocked.
WhatsApp	WhatsApp Business Platform: opt-in required, utility templates for payment reminders (no promotions), quality rating per number. Per-message pricing applies (current Indian rates not verified).
Payments	Never hold or route funds. Payment links and mandates belong to the merchant's own Razorpay account. RBI e-mandate rules (24-hour pre-debit notice, extra authentication above ₹15,000) limit what you can automate. Read the reported 2026 e-mandate framework before building (unverified).
API access	Follow Razorpay's API terms and partner rules. Use the smallest permissions needed. Store keys encrypted, rotate them, log every action.
Debt-collection conduct	Message tone must be a reminder, not a threat. No calls, no contacting third parties, no messages at night.
Claims	"Recovered" figures must be incremental and checkable. Inflated ROI claims are a consumer-protection and reputation risk.

Not provided. At minimum you need one engineer comfortable with payment webhooks and security, and one person who can sell to Indian founders and finance heads. It can be the same person. If it is, sales has to be protected in the calendar.

Minimum set: failed-payment volume (₹ and count) per merchant; recovery rate (treatment vs holdout); incremental ₹ recovered ÷ fee; time to recovery; channel share (WhatsApp, SMS, email); audit-to-paid conversion; month-1 and month-3 logo retention; support hours per merchant.