Day 522: The Launch Plan

AC kicked my butt today about not wanting to share Browserflow with the audience I’ve built up from my days making videos on Facebook. I have no problem posting stuff about Browserflow and indie hacking on Twitter, but doing that on my old Facebook page feels weird — it’s like a past life and I’m happy to let it rest. If I were to post there again, I’d want to be about me starting to make videos again or something along those lines rather than sharing a software product I’ve built (as much as I love it).

Anyway, the point she was making was that I should develop a plan for getting this product out there and sharing it with people, and she’s right.

Here’s my plan so far:

  • Go from private beta to open beta on or before 6/16, the deadline I’d set

  • With the added benefit of increased feedback from more users, do the following:

    • Improve the consumer experience (vs. the creator experience that I’ve already optimized for) by improving the gallery

      • Adding more to the gallery, allowing user-created flows in the gallery rather than just the ones I’ve vetted, adding search functionality, etc.
    • Identify a few key use cases to focus on

    • Create content and case studies around those key areas

    • Improve the marketing page to speak to people with those pain points

  • Launch!!! (Post on HN, Product Hunt, etc.)

I currently have around 250 people on the Browserflow waitlist, and it’s highly likely that most of them don’t even remember what Browserflow is given it’s been a long time since they’ve signed up.

I think I should actually try posting Browserflow to HN when I move into open beta after having tweaked the marketing page to focus on the creators (HN crowd) who would be willing to try a new tool and build things with it. Then I can post again after several months once the messaging has been refined and there are use cases and more content.

Less than a week to go until open beta!