Ask HN: Leaving my job to boostrap my projects. Advice?
I recently quit my job to start a startup, but this isn&#x27;t my first go &#x27;round. The first 8 years of my software development career I freelanced while I &quot;bootstrapped my projects&quot;. I&#x27;ll give you one guess as to how much money I made on my projects vs how much money I made contracting.<p>I took full-time work after it became clear my startup ambitions weren&#x27;t panning out and suffered through that for 3 years. That was, however, enough time for a lot of very important lessons to solidify in my head. This time, I&#x27;m taking a far different approach, which is as follows<p>- put off coding for as long as possible. Every line of code you write before you validated that someone actually wants to use what you&#x27;re writing is time (read: money) that you&#x27;ve thrown down the tube<p>- your big idea sucks by default, so don&#x27;t come up with a big idea. Get as many meetings with as many people as you can (preferably decision makers) and ask them about the sources of pain within their organization. It won&#x27;t take long to find a real opportunity.<p>- speaking of opportunities, be wary of anything that you&#x27;re initially excited about solving. If you&#x27;re excited about it, that means it&#x27;s fun, and if it&#x27;s a fun problem to solve, that means there are more people who are willing to solve it, which means it&#x27;s less valuable to solve. Find problems that are painful and tedious to solve to guarantee your competition is minimal. After all, that&#x27;s what people really pay other people money for - to avoid pain<p>- do the hard things first, which for engineers, is <i>talking to people</i>. The majority of your time should be spent learning about your potential customer. By the time you actually write a single line of code it should be painfully obvious exactly what needs to be built.<p>- Use old, proven tech. The biggest enemy you will contend with is your own desire to use shiny, cutting edge technologies. You want to use tools, languages, and techniques that have no &quot;unknown unknowns&quot;. Use proven tech, but more importantly, use tech you&#x27;re already comfortable with. You don&#x27;t want to be finding and fixing bugs for other people&#x27;s software on top of writing your own.<p>- If you don&#x27;t trust yourself not to over-design, over-engineer, or in general turn your minimum viable product into a maximum viable product, pay someone else to write your code. Because you&#x27;re not paying yourself when you write your own code, the tendency is to devalue the work, which leads to a higher likelihood that you will work on the fun but less important parts of the project first. If you&#x27;re paying someone else real money to do it, you will make damn sure they only build an <i>actually</i> minimum viable solution to the problem you identified.<p>- Design comes last. There&#x27;s such hyper emphasis on UX and design these days that it&#x27;s easy to fall into the trap of thinking that it&#x27;s the most important part of solving someone&#x27;s problem. If craigslist survived for as long as it has by using the native web ui toolkit, your product likely can too. &quot;Does it solve the problem&quot; comes way before &quot;does it look good doing it&quot;. The only exception is if you&#x27;re making a carbon clone of a software solution that has a proven market but severe problems with design and usability (e.g. IRC being cloned by the more usable and pretty Slack).<p>- B2B, not B2C (but it sounds like you already know this)<p>- Avoid empty room problems. If your solution&#x27;s effectiveness relies on a critical mass of users you will likely run out of money and patience before you get there. Only try solving these types of problems if you&#x27;re willing to stick with the community building aspect for a sufficiently long period of time or are independently wealthy to begin with.<p>- You can freelance to pay your bills, but avoid relying on it too much. There&#x27;s no greater motivating factor for creating a product that people actually want to pay for than <i>actually needing them to pay for it in order for you to survive</i>. Deciding which modern framework to use, how you&#x27;re going to scale to a billion users, or tweaking your designs to pixel perfection will suddenly seem a lot less important when your rent is coming due.<p>- Find a co-founder. I know you think you&#x27;ll be fine going about this on your own, but Paul Graham is right; there&#x27;s almost no better measure for success in a startup than the presence of a co-founder. Running a startup can be likened to willingly accepting a bout of temporary insanity because it requires you to believe in a reality that doesn&#x27;t exist... yet. It&#x27;s easier to prop up that reality when you have someone with you to reinforce it. The goal is to turn that insanity into sanity by making that fantasy into a reality. Momentum, morale, and faith in the unproven are the most important and hardest aspects of a startup to maintain (again, not the code). You&#x27;re building a cult, so find your first adherent.<p>Good luck!