# About MRRdue Canonical page: https://www.mrrdue.com/about Content last revised: 2026-10-22 Support: support@mrrdue.com --- ## What MRRdue is MRRdue connects to a Stripe or Dodo Payments account with a read-only key, imports the subscription and invoice history, and turns failed payments into a ranked list of customers who need a human today. For each case it explains what failed, what the provider will do on its own, and what the operator should do now — with a drafted recovery email ready to send. What it does not do: it never charges a card, retries a payment, changes a subscription, or cancels anything in the connected billing account. At connection time it sends a write-shaped request to three record IDs that cannot exist (one customer, one invoice, one subscription) and reports whether the key was able to write. That establishes the key cannot write those three resources; it is not a survey of every resource in the account, and MRRdue says so. MRRdue can email an end customer on the workspace's behalf. That is off by default and gated twice: the workspace must enable managed sending, and automatic sending is a separate opt-in on top of it. --- ## The problem: involuntary churn Not every customer who leaves a subscription meant to. Cards expire, banks decline renewals, and a payment fails quietly. The billing provider records the failure and retries on its own schedule, but it does not tell the business which of those customers to chase first or what to say to them. If nobody acts, the subscription is cancelled when the retries run out. That is involuntary churn: revenue lost to a payment problem rather than a decision to leave. MRRdue is built for founders and small teams running one billing account who do not have a revenue-operations person and want to know which failed payments need a human today. --- ## Principles - Read-only by design: no card charges, payment retries, refunds, subscription changes or cancellations in the connected billing account. - No card or bank data: MRRdue does not ask for or store card numbers, CVCs or full bank account numbers. Provider keys are encrypted at rest and used only on the server. - You decide what gets sent: customer email is off by default, automatic sending is a second, separate opt-in, and AI assistants can draft a campaign but only a signed-in person can approve it. - No invented numbers: every figure comes from the workspace's own billing data. --- ## Company MRRdue is operated by Akash Yadav, a sole proprietor registered in Balrampur, Uttar Pradesh, India. Bootstrapped, no outside investment. Founder: Akash Yadav — X @akashyadav_dev (https://x.com/akashyadav_dev) Support and all enquiries: support@mrrdue.com - About: https://www.mrrdue.com/about - Contact: https://www.mrrdue.com/contact - Security and data access: https://www.mrrdue.com/security - Privacy policy: https://www.mrrdue.com/privacy - Terms of service: https://www.mrrdue.com/terms --- ## Machine-readable versions - https://www.mrrdue.com/llms.txt — site map for language models - https://www.mrrdue.com/llms-full.txt — the full site content as one plain-text file - https://www.mrrdue.com/index.md · https://www.mrrdue.com/pricing.md · https://www.mrrdue.com/about.md · https://www.mrrdue.com/faq.md · https://www.mrrdue.com/mcp.md — markdown versions of the key pages - https://www.mrrdue.com/agents.txt — how AI agents connect over MCP - https://www.mrrdue.com/sitemap.xml — every public URL