Non-exhaustive list of things I learned (mostly the hard way) from building yourmove.ai and all the projects that failed along the way.
- Good advice is domain-specific. Find mentors in your space. If you’re bootstrapping a consumer product, the advice that follows is probably useful. When I first started soliciting feedback on startups I was frustrated at the amount of conflicting and contradictory feedback. Once I honed in on bootstrapped, consumer startups - the dots started to become a line.
- You don’t have to be an engineer to bootstrap a software product. But be prepared to either learn how to dev, or pay 10x the price you expect to get anything off the ground. Early stage software is a process of constant rapid-fire iteration. Unless you’re extremely lucky (or have a lot of cash to spare), devs and designers you hire will work 50% your speed at best. They don’t work weekends, and they’re not as maniacally consumed by your work as you are.
- Just ship it. No amount of thinking has worked better for me than just launching a product and putting it into customer hands. If your product solves a real problem, customers will pay for a poorly-designed MVP. Sequoia talks about hair-on-fire problems: “If you handed them a brick they would still grab it and try to hit themselves on the head to put out the fire”.
- Most of your products will fail. The same power laws that make technology so valuable - being a single developer creating software used by millions - also mean that there’s only so many successful products that can exist.
- …but there’s plenty of real problems to go around. So don’t get discouraged. Patio11’s law: The software economy is bigger than you think, even after accounting for Patio11’s law.
- If you keep trying, one of them might succeed. Most indie founders I know built a dozen products before one took off. “All things equal, a team with more shots at bat will win against a team with an audacious vision.”
- “First-time founders are obsessed with product. Second-time founders are obsessed with distribution.” An okay product with great distribution will still make money. A good product with bad distribution is almost guaranteed to fail.
- Don’t paywall too late. The fastest way to validate “will someone pay for this” is to set up a pre-order, or a Stripe checkout page that redirects to a Google-form operated version of the product. Often times there’s no need to build out the software until you’ve validated that someone will actually pay for it.
- Don’t paywall too early. While pay-gating early is a great way to test “will people pay”, it will reduce the amount of data and feedback you get from users. It also slows down organic growth. Demonstrating value before asking for payment can massively improve LTV. In our case - opening a free set of features on our AI profile writer increased conversion by 2.5x while also resulting in more organic growth from users sharing the product.
- Stop reading articles about building startups and just go build one. My first project that earned anything took 6 months to make a single dollar from a cold start. My latest one took 3 days.
| Product | Distribution | Outcome |
|---|---|---|
| Bad | Good | $ |
| Good | Bad | Dead |
| Good | Good | $$$ |