Everyone talks about it, product-led growth, but how does someone actually achieve that?
You need to balance growth with product utility, else you've just created something that can spread but isn't worth spreading
After analysing a crap tonne of product lead growth apps in the market such as:
- Drift
- Linktree
- Canny
- Notion
- Trello
- Loox reviews
Some common patterns arose which we've implemented into our own product to help with growth
Each of these apps have similar patterns:
- Viral co-efficient >1, i.e each customer brings in more customers as they install their app on their website
- Extremely simple in use case (a simple chat app, a review app or a link containing other links)
- Knowledge gaps. Most of these apps are sold to an audience who aren't technically capable of building the same by themselves within a week or so (at least that's the case for Canny or Linktree)
- They're all focused on bottom-line revenue. The theme they all hold is value sustainability. I.e they are directly responsible for revenue. Company revenue increase from understand product feedback easily (canny), sharing product reviews (loox) or sharing a link with all their important products (linktree)
So we kicked off with the same thesis for bugreporting. A ridiculously simple way to collect customer / QA feedback to reach Product Market Fit faster
- Focus on heavy value first, bugs and customer feedback/video recordings is a massive pain for anyone trying to track down bugs
- Direct cost savings for agencies, product managers and QAs trying to collect user feedback
- Proven business model with somewhat competitors out there, but tackling different niches
- Extremely simple use case of helping people record and give feedback
- Our app is installed on our customers' websites
Have you thought of how you can focus on a distribution first product?
100% on the mark with the similar patterns @veebuv - great post!