Read on Twitter
1/ A story on developer first products on day 1 + the road to your next round…
You want to be/are a dev first product.
You focus on one developer, solving their pain, having them come back over and over again. However there is falloff and lots of features to add - user
You want to be/are a dev first product.
You focus on one developer, solving their pain, having them come back over and over again. However there is falloff and lots of features to add - user
2/ Enterprise 1, then Enterprise 2 knocks on your 
They ask for all the http://enterpriseready.io features you will need
You have limited cycles + need to manage resources appropriately
Each new enterprise design partner + feature takes away from user
Which path to take?
They ask for all the http://enterpriseready.io features you will need
You have limited cycles + need to manage resources appropriately
Each new enterprise design partner + feature takes away from user
Which path to take?
3/ Working backwards, which is better?
I can certainly say which is harder and more valuable in the long term…
3-5 design partners at next round, some nice logos, but one off acquisition engine?
True developer first motion, product for 1 developer who can’t live without it
I can certainly say which is harder and more valuable in the long term…
3-5 design partners at next round, some nice logos, but one off acquisition engine?
True developer first motion, product for 1 developer who can’t live without it
4/Incredible patience, perseverance, focus on 1 user needed for true dev first motion
Temptation for enterprise design is there but every second u spend on that means less engineering cycles for dev first product
Stay the course…don’t be tempted…
Temptation for enterprise design is there but every second u spend on that means less engineering cycles for dev first product
Stay the course…don’t be tempted…
Remember it feels like this in the beginning…
But can end like this…
