How to build USP's and not features
Customers growth is happening consistently and most important of all - our customers and actual daily users, love our product.
What they say about our product bugasura.io ?
- It is clean.
- It is simple.
- It is fast.
- It is flexible.
The truth is everyone starts with such a prouct.
As they grow they screw up when they become obsessed to features.
That's not what we are doing in Bugasura.io
Our culture of building USP's
- We do cleanup sprints
Our job as founders - is to keep cleaning. One sprint for building - one sprint for cleaning. Sometimes two. Totally unaffordable by many startups. In that sense we are richer than many.
- We build USP's - not features
After building an elephant that we couldn't feed in our previous product stint - we decided we will build USP's and not features. We realized that we can't compete with our competitors on features but we can compete with them on how the feature is simplified in our product to put it to great use. We fine tuned our signup wizard for 5 months before we started seeing conversions.
- We remove stuff
We built something very passionately. It certainly was loved by people when we showed them but they didn't use and also it was a bit confusing. So, we removed it. We are looking to remove 1 more thing. No debates. Just ruthless removal.
- We know the shittiest part of our product
Absolutely. Every day I go to that part of our product - my heart rate raises (and I wish I could capture that and show you). My partner and I totally know the shittiest part of our product and we are spending months to re-think it out. The ugly stays there but when we replace it - we should move to world leading usage. No user every complained about it but we know why they aren't even talking about it.
- There's more features than we can sell
One common mistake from even our own past is to think we need features to sell. We have overcome that in Bugasura.io We strongly believe that we have more already and hence much more is not going to make a big difference. This itself puts less pressure on product engineering teams and hence eases them to put something lovely out instead of put more out.
Just that for now folks.
