Philosophy
Founder-in-the-Loop
Most tools automate everything. StayPaid starts manual. Personal touch over robot spam.
The Problem with Automation-First
Most dunning tools are built for scale, not relationships. They send the same generic email to every customer, from a no-reply address, on a fixed schedule. The customer receives a robot email that feels like a bill collector, not a founder who cares.
The result? Low recovery rates. Customers ignore the email, or worse, they churn because they feel like a number. The tool "worked" — it sent the email — but it didn't recover the payment.
Automation-first assumes all failed payments are the same. They aren't. A customer who's been with you for 2 years deserves a different approach than someone who signed up yesterday.
StayPaid Starts Manual
When a payment fails, StayPaid puts it in your dashboard — not in an automated queue. You see the customer, their history, their tenure, their total revenue. You decide what to do.
This is the founder-in-the-loop approach. You're not automating away from your customers. You're staying present while the system handles the busywork.
You can write a personal P.S. note. Choose a tone that matches your relationship with that customer. Send the email when you're ready — not when a cron job decides.
You Review Every Payment
The dashboard shows you everything you need to make a decision:
- •Customer name and email — who they are.
- •Tenure — how long they've been a customer.
- •Total revenue — how much they've paid you over time.
- •Failure reason — expired card, insufficient funds, bank decline.
- •Day in sequence — Day 1, 3, 7, or 14 of the recovery flow.
With this context, you can craft an email that actually resonates. A 2-year customer gets a "Hey, noticed your card expired — want to make sure you don't lose access" email. A new customer gets a "Welcome! Looks like there was a hiccup with your payment" email. Same tool, completely different message.
Add Your Personal Touch
Every email template includes a P.S. section where you can write a personal note. This is where the magic happens.
"Hey John, noticed you've been with us for 8 months. Really appreciate your support! — Robert"
That one line changes everything. It's not a template. It's a founder talking to a customer. The customer sees your name, your email address, and a message that only you could have written.
You can also choose the tone for each email: friendly, professional, or casual. A B2B SaaS might use professional. A creator tool might use casual. You decide per customer, per situation.
Optional Automation Per-Payment
Manual by default doesn't mean manual forever. Once you review a payment and decide the approach, you can enable auto-send for that specific customer. The system handles the rest of the sequence automatically.
This is opt-in automation, not opt-out. You choose which customers get the personal touch and which ones get the automated sequence. A high-value customer who's been with you for years? Manual all the way. A low-value trial user? Auto-send after the first email.
The control is always yours. StayPaid is a tool that amplifies your judgment, not replaces it.
Emails From Your Address
This is the part that makes the biggest difference. StayPaid sends emails from your email address, not a generic no-reply@staypaid.io address.
Your customers see your name in the inbox. They can reply directly to you. The email lands in their primary inbox, not promotions or spam. It's a real conversation, not a notification.
You configure your own SMTP (Gmail, Yahoo, Outlook, or custom) during onboarding. StayPaid never stores your password in plain text — it's encrypted at rest. The email goes through your provider, so it looks exactly like any other email you send.
The Bottom Line
Founder-in-the-loop isn't a feature. It's a philosophy. It's the belief that personal relationships matter more than automation scale, that a founder's voice is worth more than a robot's efficiency, and that customers are people — not transactions.
If you believe that too, StayPaid is built for you.
Want to see how the recovery sequence works?
Read about the recovery sequence