Software Engineer to SaaS Founder
hackernoon.com
hackernoon.com
Otherwise, and with absolutely zero gratuitous negativity intended, I get the impression that he wrote this piece to pitch Canny.io as opposed to genuinely wanting to help other entrepreneurs.
I honestly think if I had read this article 2 years ago, I could have gotten as far as I am now in half the time. That's huge, and I genuinely think these words can help others.
I mentioned Canny at the top of the article because I got feedback that I should in order to show my credibility around talking about the subject.
If it didn't somehow benefit Canny, it wouldn't make sense to spend the time writing it. It definitely wasn't my only motivation though.
I probably spend way too much time on HN, random VC Blogs, Medium, and consuming other startup-ey content so it would probably be healthiest to interpret the comment as a reflection of my own skepticism/impending burn-out.
That said, Canny looks pretty cool. Hope it goes well :)
I love how you address value in pricing, too! And how you identify that there are lots of good states between dead and $100MM per year. I know several entrepreneurs who see their SaaS as more of a lifestyle business, and high six figures / low 7 figures gives them a very good lifestyle.
This is the first time I’ve heard of Canny, and the product has an interesting premise. As a user researcher / design strategist who was a developer before, I’d like to see it have a way to map the users giving feedback onto user personas or customer personas instead of treating each user like they’re all the same.
That would make Canny a lot more powerful, in terms of prioritizing features and showing companies how to make higher-value decisions, like redesigning their product, realigning their content, or splitting their product (for different pricing tiers or in general).
Thanks for reading :)
I think you're right, a lot of engineers start with a solution in mind and that's the wrong way to go about this. Sure, you can spend a month building a prototype to validate your idea, but if your idea is something that nobody is willing to pay you for, it's not going to make a good business.
That's what the phrase "do things that don't scale" means -- go out, find something that someone is willing to pay you to do, and do it at a discount so you can work the inefficiencies out of the process. If nobody is willing to pay you to do it manually, it's not a market worth chasing.
The vast majority of products are simply new implementations of an old idea/service with some enabling technologies under the hood that allow you to do those things with less overhead (thus you can undercut your competitors for a sustained advantage).
Definitely wish I could go back and do that differently which is what inspired the post.
False. There is a famous quote by Ford about markets and faster horses. Point being the market doesn't know what it needs or wants until someone actually makes it because typically people just want more of the same but faster and cheaper.
I'm saying you shouldn't ask people what they want, you should understand their problems (they want to get around faster), and then design a solution to solve them. Real people/companies will pay you to solve their problems.
The important part is that it's about problems, not solutions.
The real problem is "I need to move people / things from point A to point B". A horse solves that, as does an automobile, as does a boat. The market won't tell you that directly.
It's all about learning how to ask the right questions.