Live data from Hacker News

Lessons from a Startup Pivot

haacked.com

21–28 of 28 posts

Re: Lessons from a Startup Pivot

#21
post #9

> Lesson: Start with selling a Product not a Platform Good advice. People rarely want a platform, especially from a new entrant. They want an aspirin tablet. Once they are hooked you can expand.

I remember VCs telling me to be a platform, not a product. "Look at what FB is doing!" It made sense for FB, but that doesn't mean it makes sense for everyone. A sticky platform will be stickier than a sticky product. But that doesn't mean every product should be made into a platform.

> I remember VCs telling me to be a platform, not a product.

VCs incentives may not be aligned with your incentives. They are looking for Unicorns (Decacorns? Centocorns?) and are prepared to have _you_ take on a high risk of failing to improve their 1:100 successful investment upside calculations. You building a comfortable 8 figure revenue and 7 figure profit company over 5 or 10 years is basically a failure in their eyes.

For every Facebook or AWS, there are a 100,000 profitable "product companies" and probably a million successful-enough "lifestyle businesses".

If you want to take on the risk and shoot for the stars, sure - follow that VC advice. If you'd personally be happy with an 8 figure exit or a high six figure salary for as long as you want it, you can reduce your risk of failure substantially by _not_ following that advise to the letter.

Re: Lessons from a Startup Pivot

#22
post #21

Earlier quoted context omitted.

I remember VCs telling me to be a platform, not a product. "Look at what FB is doing!" It made sense for FB, but that doesn't mean it makes sense for everyone. A sticky platform will be stickier than a sticky product. But that doesn't mean every product should be made into a platform.

> I remember VCs telling me to be a platform, not a product. VCs incentives may not be aligned with your incentives. They are looking for Unicorns (Decacorns? Centocorns?) and are prepared to have _you_ take on a high risk of failing to improve their 1:100 successful investment upside calculations. You building a comfortable 8 figure revenue and 7 figure profit company over 5 or 10 years is basically a failure in the…

You read my mind (err—my downstream comment)!

Re: Lessons from a Startup Pivot

#23
post #2

Hey! I'm the author of this blog post. If you have any questions, let me know! One of the lessons I omitted (because the post was getting a bit long), is we started off as cross-platform (Slack, Teams, and Discord) but in the end we decided to focus on a single product. In retrospect, we've struggled to decide if that's a lesson to learn. Should we have started with a single platform? It certainly makes it much faste…

Just wanted to say that I like your writing style. It's approachable and entertaining to read. Good luck with Abbot and thanks for sharing your lessons learned!

Re: Lessons from a Startup Pivot

#24
post #9

> Lesson: Start with selling a Product not a Platform Good advice. People rarely want a platform, especially from a new entrant. They want an aspirin tablet. Once they are hooked you can expand.

This works for video games too. Warcraft 3 had a comprehensive editor and cloud functionality built in which allowed games such as DotA to be made. However, the base Warcraft 3 game is a masterpiece in its own right, which drove users to the platform. If only the editor had been released, it would have never gathered the critical mass for acquiring users.

Re: Lessons from a Startup Pivot

#26
post #8

Can you talk a little more in detail about your tech stack? Perhaps it would help more readers like me who are curious given your history in the .NET space.

Sure! Because of my background in .NET, it made sense to stick with what I know. I don't believe the tech stack makes or breaks a product (unless you choose egregiously poorly). A product's success is primarily determined by how well you hit product market fit. That being said, a good stack that you know well can affect how quickly you build and how quickly you can adapt the product to changing market conditions. So…

> The other part is we got a lot of Azure Credits when we joined the [Microsoft for Startups]

Wow, Microsoft must have really drowned you with free credits to choose Azure. We also tried Azure 2.5 years ago when my small team (3 founding devs) started with our startup, but after 6 months of constant problems, broken services, outages, and completely out of the blue unexplained service failures we had to give up. We wasted a lot of engineering time on bending our app to Azure's needs and still had issues. We eventually migrated to Google Cloud and hadn't had any problems since then. I am not kidding, the first 6 months we must have spent at least 70% of our time on issues which we wouldn't have had on AWS or Google. Azure really under delivered on all fronts. Things looked extremely promising and then when we used a service we realised that most useful (often necessary) features were behind extremely expensive tiers and then it meant we had to either take huge hits on our hosting costs or build weird workarounds. We didn't want to go against Azure and often chose to pay, but even the higher tiered services then started to act up and often result in totally unexpected behaviour. Good luck to you though!

Re: Lessons from a Startup Pivot

#28
post #8

Earlier quoted context omitted.

Sure! Because of my background in .NET, it made sense to stick with what I know. I don't believe the tech stack makes or breaks a product (unless you choose egregiously poorly). A product's success is primarily determined by how well you hit product market fit. That being said, a good stack that you know well can affect how quickly you build and how quickly you can adapt the product to changing market conditions. So…

> The other part is we got a lot of Azure Credits when we joined the [Microsoft for Startups] Wow, Microsoft must have really drowned you with free credits to choose Azure. We also tried Azure 2.5 years ago when my small team (3 founding devs) started with our startup, but after 6 months of constant problems, broken services, outages, and completely out of the blue unexplained service failures we had to give up. We w…

I have experience the other way around. AWS was utterly holding us back and we gained a lot of speed when we switched to Azure. Azure has changed a lot over the years though and a lot of features behind a premium tier are now more available to lower cost tiers. Comparing something to 2.5 years ago is a long time in the fast moving cloud world.
Post reply on HN