Every SaaS founder fears the same thing: a refund policy that gets abused. Generous refund windows sound like money bleeding out the door. Except the data disagrees. Velocity X runs a 30-day full-refund guarantee — no asterisks, no "restocking fee," no repo clawback. Three years in, the refund rate sits at 3%. The reputation it builds? Worth 10× the refunded money.
Here's why a transparent refund policy flips the conversion math and when to push back on refund requests.
Why Generous Refunds Convert More Than They Cost
A refund guarantee compresses buyer's remorse into a specific window. Right now, a prospect is thinking: "What if this breaks my workflow? What if I hate the new branding? What if I get buyer's remorse in three months?" A 30-day window answers that fear instantly. "Take a month. If it doesn't work, you're out nothing." The objection evaporates.
Most refunds come from genuine misalignment, not scams. Someone bought expecting a white-label template and got a build-your-own-site framework instead. A clear onboarding + expectation-setting in your sales calls filters out 80% of refund risk before the customer even signs. The remaining 3% are people who genuinely needed out, and refunding them fast builds loyalty (they talk about your honesty more than they talk about the refund).
The Velocity X 30-Day Policy — Template
Full refund within 30 days of purchase if the live site doesn't out-perform your existing solution. That's it. No conditions except one: you show up to a 30-minute onboarding kickoff. The kickoff isn't hazing — it filters tire-kickers and clarifies expectations. If someone skips the kickoff and asks for a refund at day 29, that's a stronger signal they weren't serious.
Key rules: refund is issued within 7 business days via Stripe (instant for the customer), the repo remains the customer's property (no clawback), and domain DNS stays theirs. You're selling confidence in the product, not renting it out with an ejection seat.
How to Execute the Refund Without the Drama
Set expectations early. In your sales call, say: "You've got 30 days. If the site isn't moving the needle, you get your money back. The code is yours forever — I'm not taking anything back." That clarity is 80% of the refund-handling battle. When a refund request comes, you're not discovering a surprise; you're processing a known condition.
Stripe Refund API handles this in one call — no manual bank transfers, no excuses. In your Stripe dashboard, hit "issue refund" and it lands in their account in minutes. Document it in Slack or your CRM so you have a record if a customer disputes it later. In three years of Velocity X, zero disputes. The policy stands on its own.
When to Push Back on a Refund Request
Three scenarios where you politely decline:
1. They skipped onboarding. "I notice you didn't attend the kickoff call. Let's schedule one now — that usually unblocks things."
2. The 30 days passed. "Your 30-day window closed on [date]. Happy to discuss a refund extension if something came up."
3. They tried to abuse the guarantee. "You've requested refunds on three projects in four months, all after day 25. That pattern suggests the model doesn't fit your workflow. Let's talk about whether this is right for you."
In practice, scenario 3 happens maybe once per year. People are honest if you're honest first.
FAQ: The Six Questions That Come Up
What about chargeback fraud?
Stripe handles it. If someone disputes the charge after you've already issued a refund, Stripe's fraud team sides with you. Refunding first kills 99% of chargebacks because the customer has no standing to dispute a charge they agreed to refund.
Doesn't this attract low-quality leads?
Nope. A transparent refund policy actually filters better. Tire-kickers see "30-day guarantee" and assume it's hard to get a refund. Serious buyers see it and think "they're confident." Your sales call closes harder prospects.
Should I mention the repo stays theirs upfront?
Absolutely. "You own the code forever. If you refund, the repo is still yours — I'm not taking it back." That removes the last objection for custom-build buyers. They're buying peace of mind, not renting it.
What if they refund, keep the code, and relaunch it?
That's fine. You've sold them the code (embedded license is in there). Your leverage is your reputation, not the repo. Zero Velocity X customers have tried to resell a refunded build — the cost of stripping branding and relaunching is higher than just buying it legitimately.
How do I handle a refund request at day 28?
Process it. The policy says 30 days. Honor it. A refund at 99% of the window is still cheaper than the goodwill and referral damage from fighting a customer over two days.
Do I need a separate cancellation policy?
Only if you have ongoing services (retainers, support tiers). For one-time builds, the refund policy IS the cancellation policy.
The Bottom Line
A 30-day full-refund guarantee isn't generosity — it's a conversion tactic that pays for itself. At a 3% refund rate, every 33 customers covers the one refund with Stripe fees and still pockets 3,200% ROI. The policy works because it removes the last psychological barrier to purchase. For SaaS or service-based products with real onboarding, this model is table-stakes. For deeper thinking on pricing and scarcity, see trust badges and guarantees or explore the full pricing strategy.