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.
Conversion path
Not ready to connect Stripe?
Use the benchmark first. It gives visitors a useful estimate before signup and keeps the next step lighter than connecting an account immediately.
Dunlo fit
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.
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 beta |
|---|---|---|
| Primary job | Send product, lifecycle, and transactional emails through a SaaS email platform. | Recover failed 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.
Beta transparency
What can be verified today.
Dunlo publishes assumptions, recovery mechanics, and its proof policy before it publishes customer outcomes.
During beta, customer outcomes are published only with approval and enough context to be useful.
Visible assumptions
The public benchmark exposes the illustrative failed-payment bands and 62% recoverability assumption used in its model. Updated July 2026.
Visible mechanics
Failure reasons, recovery timing, customer update links, and founder review are documented before signup.
Visible proof policy
Customer metrics and stories remain private until the sample is useful and the customer approves publication.
Free beta
Recover failed 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.