22
1 Comment

10 Reasons to Have a Flexible Refund Policy 💸

I've been selling all kinds of digital products for nearly 10 years and always approve any refund request and offer a 60 refund period.

Here's why.

  1. A refund request creates an opportunity to talk to the customer before they churn.
  2. There's less risk of purchasing the wrong product resulting in a better conversion rate.
  3. A long refund period communicates confidence in your product.
  4. There's just not many customers that ask for a refund.
  5. When a customer forgets to cancel their subscription, refund. We all forget sometimes. It's the perfect moment to show great customer service.
  6. Your brain cycles are better spend working on your product than debating a refund request. Approving a refund results in instant mind space.
  7. If customer requests don't match up with the roadmap, be pro-active and offer a refund. In my experience customers often don't want one but very much appreciate the gesture.
  8. Having a clear path to a refund request reduces the risk of creditcard chargebacks.
  9. Customer very demanding on support? Looks like the product isn't a great match? Take your loss and offer a refund. It's often a win for both parties.
  10. If you make a big deal out of every refund request you risk losing a customer forever. Approve that refund and create goodwill. Instead of badmouthing you, that customer can share a positive experience even though the product wasn't perfect for them.

See refund requests in a positive light. Learn about your customer. Say goodbye with a positive vibe. Don't spend your energy debating, that energy is better spend elsewhere.

on November 17, 2020
  1. 1

    Yes, I have a similar refund philosophy. I offer free extensions and do occasional refunds past the refund duration.

Trending on Indie Hackers
Your AI Product Is Not A Real Business User Avatar 116 comments Stop Building Features: Why 80% of Your Roadmap is a Waste of Time User Avatar 74 comments I built an enterprise AI chatbot platform solo — 6 microservices, 7 channels, and Claude Code as my co-developer User Avatar 38 comments The Clarity Trap: Why “Pretty” Pages Kill Profits (And What To Do Instead) User Avatar 34 comments I got let go, spent 18 months building a productivity app, and now I'm taking it to Kickstarter User Avatar 22 comments I went from 40 support tickets/month to 8 — by stopping the question before it was asked User Avatar 19 comments