You don't have to have superpowers. You just have to have some product sense, some engineering chops, and the ability to take 6 months off (not everyone can afford this, and that sucks) to build the thing and see if you can get people to look at it and buy it. You'll learn all the other stuff along the way (taxes, marketing, and eventually: hiring). Just give it a shot. If you run out of savings and have to go back t…
> My company is bootstrapped. It isn't growing fast enough to fit PG's definition of a startup, but it's 5 years old and makes 7 figures. Very impressive. Thanks for sharing! Is this https://interviewcake.com ?
Ask HN: How to found a company as a single founder?
111–120 of 243 posts
Re: Ask HN: How to found a company as a single founder?
#112Serial single founder here. Start building and start selling. If you can’t deliver a product to a paying customer solo then you’re not cut out to be a sole founder.
I agree with this except switch the order. First, start selling. Then start building. It is so easy to waste so much time building something nobody wants, and you won't know until it's too late if you try to sell it afterward. Selling first will inform your decisions on what to build.
How do you sell first? There isn’t a product to show. How do you find Customers? Is it the philosophy that the customer doesn’t know better and you have to tell them what they need, all the while understanding what your capabilities are. Like undersell and overdeliver? I’m genuinely curious how you go about selling first.
Re: Ask HN: How to found a company as a single founder?
#113Earlier quoted context omitted.
This pretty much sums up everything. I had a similar problem trying to sell my products. If you're a solo founder learn how to sell first. Finding cool marketing strategies is great, but people need to see real faces before buying your products. It is not always true, but in general that is what I've seen so far.
Could you expand on the "real faces" part as opposed to, say, a good stable of content and decent testimonials? Do you mean full on sales calls (vs. just marketing) would be needed for a SaaS product of relative complexity? Or am I missing the point? Thanks
Re: Ask HN: How to found a company as a single founder?
#114edit: assuming you are in the USA. If in a bureaucratic nightmare of a country then you should avoid incorporation until you are extremely profitable. My own experience in Thailand: I incorporated early and was forced to hire a full time bookkeeper plus about 1 month/year accountant contractor to handle the government red tape
Re: Ask HN: How to found a company as a single founder?
#115Re: Ask HN: How to found a company as a single founder?
#116Earlier quoted context omitted.
No they’re not. You can’t even patent or copyright business ideas. The only justification for a business idea is a customer, so GP is correct: no business has value without sales.
Then give us your best ideas.
There are certainly things that I suspect there would be a huge market for. That, I suppose, is my "good ideas" list (or, because I'm not an oracle, my "wish list").
Re: Ask HN: How to found a company as a single founder?
#117Earlier quoted context omitted.
> ideas have no values Fully fleshed and well-justified ideas worth hell of a lot.
No they’re not. You can’t even patent or copyright business ideas. The only justification for a business idea is a customer, so GP is correct: no business has value without sales.
Re: Ask HN: How to found a company as a single founder?
#118Serial single founder here. Start building and start selling. If you can’t deliver a product to a paying customer solo then you’re not cut out to be a sole founder.
I agree with this except switch the order. First, start selling. Then start building. It is so easy to waste so much time building something nobody wants, and you won't know until it's too late if you try to sell it afterward. Selling first will inform your decisions on what to build.
But I'm not going to argue against it right now. It's too deeply ingrained as startup wisdom to fight it. So instead, I'll offer this compromise: if you're going to sell first and build later, at least build some basic things up front that you are guaranteed to need and that most startups don't build until long after they should.
1. You already know what your programming language strengths and weaknesses are. You can make decisions for your first product iteration already. Are you going to start with a web app? You probably already know what language you want to use. Choose your frameworks, and choose frameworks that address the OWASP top 10 at least. If you are storing data, you have a responsibility--even as a sole founder--to take security seriously. You can think about that and make decisions while you are selling, so do it. You can also make a decision to not store data or store as little as possible and choose frameworks and plugins that help you do that.
2. Along the same lines, if software is involved you have to have a way to deploy it. Set up your DevOps pipeline. If you listened to the first point, you've got somewhere to start. Take your app framework and your plugins and set up a pipeline for deploying/rolling back/backing up/restoring the very basic "hello world" version of the app + plugins. Use a service if you aren't already into DevOps personally--most of these things have a free tier. If you are looking for a native app of some kind, navigate the platform's app store at least once so you know what you're in for. Or if it's cross-platform how you will get the latest version to your users. None of these decisions matter right now in terms of what decisions you make, just that you do make them and learn how to use things.
If you are going to commit to selling first and then building, you are already shortchanging the amount of time you have to deliver after the product is sold. If you haven't made any of these decisions, the time between when you make your first sale and when you deliver it is going to be absolute shit. Give yourself the ability to use that time 100% focused on building the product confidently because you already know how you're going to build it and how you're going to deliver it.
Re: Ask HN: How to found a company as a single founder?
#119Earlier quoted context omitted.
The advice makes sense, but isnt it a bit of chicken-and-egg? How do you sell something you haven't built? (or is it really .. build a little, or enough to illustrate; then 'sell' to validate and seek market fit; and then finally truly build?)
Or, even better, build a minimal MVP (1-2 weeks dev time) and use this to attract attention and get feedback.
I do think that building a UI prototype that you can click through is a good first step for complex software.
Re: Ask HN: How to found a company as a single founder?
#120Earlier quoted context omitted.
Taxes, VAT, compliance are mundane. Marketing/Selling, and building the right thing ... this is the hard part. If you can do the later, most of the ops becomes ... just ops. It's just work. It can be done.
So what do you suggest if the ops thing freaks me out to the extent of stress? I'd be happy to take on a cofounder to handle that.
If you need to hire people, open an office, write up contracts, deal with immigration lawyers, deal with tricky shareholder stuff, manage customer accounts ... then maybe you need someone to help.