2
2 Comments

Is your product a vitamin or painkiller?

Hey everyone,

Just wanted to share a challenging but honest update I think fellow builders should learn from. I've been working on gSweets for nearly a year now. Having done 20+ user interviews pre-launch we had a sense early on that the project was seen more as a vitamin than a painkiller – that is more of a nice-to-have than a must-have. We were ok with that at the time since we thought it was a fun project and that it could be a foot in the door to building more meaningful features on top of Google Docs.

Given that we were building on top of Google Docs, and that we had a high quality bar for the UX, it took us months to get the core feature ready, and then a few more months to build features on top of it like GIPHY, Unsplash and Emojis.

We launched on PH and within a couple of months had nearly 2K installs in the chrome webstore. We were soon nominated for a Golden Kitty Award for productivity. We were feeling pretty motivated and confident that things were heading in the right direction.

Unfortunately, felt we were missing 2 things, users emails and product analytics. We implemented product analytics and user accounts. We could finally communicate directly with our users and see how useful our product was to them.

After a few weeks of tracking, the data didn't lie. We had a very small group of users who would use gSweets a couple of times a week, but it was safe to say that overwhelmingly – users were not using gSweets. It was hard to accept given how much time was sunk into the project but we couldn't argue with the data. The biggest challenge was that although we have ideas on how to increase the value & frequency of usage, the platform risk of building on top of Google Docs was too high.

One of our teammates summed it up well. Normally you accept product risk OR technical risk. We had accepted both and it bit us in the ass.

We're still extremely motivated to continue improving the lives of the many PMs, Marketers and writers who've trusted us thus far. I just know that as we continue on this journey we're going to be try an follow these rules:

  1. If you're not sure if it's a painkiller or a vitamin, launch in less than a month.
  2. Either way launch with a paid plan to validate the pain.
  3. Accept the technical risk for a painkiller that you've validated. Don't accept it if you know what you're building is really a vitamin.

That's it. If you have any questions feel free to drop a comment below.
I hope this is helpful to other builders out there.

posted to Icon for group Ideas and Validation
Ideas and Validation
on March 31, 2021
  1. 1

    Thanks for sharing this, really interesting! I think the painkiller vs. vitamin idea is really helpful, but I'm wondering what it takes for a vitamin to be successful? After all, there are many products that are vitamins but do succeed. Would love to hear your thoughts on this!

    I'm asking because I think I'm headed in the same direction but still want my my product to succeed :D

    1. 1

      Honestly, I don't think vitamins are designed to succeed long term. A vitamin doesn't mean it's small, it means that users don't need the tool. Lots of indie hackers are building small painkillers but if you see the data and users are not using your tool weekly/monthly or that they're not willing to pay monthly to keep it, you don't have a sustainable business.

Trending on Indie Hackers
Stop Spamming Reddit for MRR. It’s Killing Your Brand (You need Claude Code for BuildInPublic instead) User Avatar 219 comments What happened after my AI contract tool post got 70+ comments User Avatar 213 comments $36K in 7 days: Why distribution beats product (early on) User Avatar 91 comments Where is your revenue quietly disappearing? User Avatar 87 comments We made Android 10x faster. Now, we’re doing it for the Web. 🚀 User Avatar 71 comments a16z says "these startups don't exist yet - it's your time to build." I've been building one. User Avatar 57 comments