Day 460: Road to Launching Browserflow

status

Several weeks ago, I told Shiva that by the end of my stay in Vegas (end of April), I want to hit one of two milestones:

  • Launch Browserflow
  • Get at least one recurring paying customer

I keep putting both of these things off by getting sucked into building new features (e.g. Google Sheets integration) or doing some nasty, soul-sucking work (e.g. moving everything into a monorepo), but there’s really only one thing left to do to hit one of these milestones:

Better onboarding.

When people install Browserflow, they don’t know what to do because it’s a blank slate. It can do anything, which for most people means it does nothing.

Instead of building product, I need to make it easier for people to get started and actually start using it.

Things to do:

  • Upon installation, have people try out flows rather than showing them a blank editor
  • On on the landing page, showcase select flows that demonstrate Browserflow’s value

The more I work on Browserflow Cloud though, it feels like that might be the area to focus on (vs. local execution) due to how useful it is. It’s entirely possible that the extension will become a builder mainly to test out flows before loading them into the cloud. The local execution context can also be pretty useful, but it requires someone to be motivated and knowledgable enough to build their own flow which most people aren’t willing to do.

I feel like I’ve been talking about these same things forever (and I have) — really gotta transition over to marketing and sales rather than development.