Tip: Batch your releases to decrease churn

Your first release is bound to have a few quirks. And while live users are a huge help when it comes to sniffing out issues, they may also bail when they find one. Batch your releases and start with your warmest leads to mitigate risk.

A batched release means fewer people will be affected by each bug. It also allows you to get feedback from friendly faces and iterate before releasing to people who might be less forgiving. And the result is lower churn right out of the gate. There are plenty of ways to execute a batched release, but consider taking a page from KP (@trulykp) of LetterDrop's playbook. He builds in public and creates a waitlist. When he's ready to launch, he shares it with his founder friends and mastermind group. He iterates on their feedback, then does a launch with his biggest supporters. Next comes the waitlist. Then his Twitter audience. And finally, he releases to the general public via IH and Product Hunt.

More 30-second growth tips?

Every day we share a tiny, bite-sized tip for growing your business. Click here to see more and get Growth Bites in your inbox 👌

  1. 3

    Being a team of two, this is actually my biggest fear regarding doing a big launch using Facebook ads (we previously launched a course well this way, but for a SaaS bugs could definitely happen). A progressive release definitely makes sense. Great tip!

  2. 3

    Doing this now thanks to KP's advice actually! It's been working well and I feel less pressure each time I mini-launch

    1. 1

      Glad it's working out! 💪

Trending on Indie Hackers
Looking for Indie Hackers on Twitter, drop your handle 👇 47 comments List of places to submit your startup (for free!) 19 comments I'm 20 years old and launched an app that went #1 on the App Store. AMA. 17 comments Unpopular opinion: I don't like AI content generator tools 10 comments 💔 Y-Combinator rejection to new SAAS launch 🚀 5 comments I'm bootstrapping a Relationship Management platform, currently at $600/MRR. AMA. 5 comments