Who should use Loops
- You already use Loops and want all customer email in one platform.
- You have engineering time to wire Stripe events, templates, and reporting.
- You need general lifecycle email more than a dedicated recovery product.
DIY comparison
Dunlo vs Loops for dunning
Loops is a strong email platform. You can use it to send dunning emails if you build the Stripe triggers and recovery logic yourself. Dunlo is purpose-built for Stripe failed-payment recovery, so the failure context, email timing, and reporting are already connected.
Comparison
What changes in practice
This comparison is based on public product pages and documentation. Dunlo details reflect the current beta offer.
| Criteria | Loops | Dunlo |
|---|---|---|
| Primary job | Send product, lifecycle, and transactional emails through a SaaS email platform. | Recover failed Stripe payments with context-aware workflows. |
| Stripe logic | You build the Stripe event handling and decide when each email should send. | Stripe failure context is the starting point for the workflow. |
| Recovery reporting | Email engagement can be tracked, but recovered invoice reporting must be built separately. | Tracks recovery outcomes rather than only email delivery. |
| Best fit | Teams that already use Loops and want to custom-build recovery automation. | Stripe-first founders who want a dedicated recovery workflow without assembling tools. |
Who should use Dunlo
- You need more than email sending: failure codes, recovery state, and reporting.
- You want default dunning logic without building webhook infrastructure.
- You want high-value failed payments to surface for founder follow-up.
Public proof
What we can prove today.
Dunlo should earn trust with visible mechanics, public benchmarks, and approved beta evidence instead of vague recovery claims.
Public benchmark
Failure-rate ranges are visible before signup.
The calculator shows the current public MRR bands, estimated failed MRR, and recoverable revenue assumptions without asking for an email first.
Open benchmarkProduct evidence
The workflow is failure-code first.
Dunlo is built around Stripe failure reasons, timed recovery emails, secure update links, and founder escalation for accounts that should not receive generic automation.
See failure codesBeta proof policy
No anonymous uplift claims before approval.
Customer metrics, screenshots, and testimonials are published only when the beta sample is large enough and the customer has approved the public version.
Read report policyFree beta
Recover failed Stripe payments before they become churn.
Use Loops if you want to own the whole recovery system and only need the email layer. Use Dunlo if you want the Stripe recovery workflow, not just the email sending tool.