I am always open to helping interesting people solve compelling problems. I approach problems systematically and from first principals; my process provides the most value when collaboration starts as early into the ideation → iteration cycle as possible (ideally pre-MVP).
My process bears from personal experience – successes and failures for a multitude of reasons. Success is much harder to engineer than failure; it has identifiable principals which can improve your chances of achieving it but nothing is certain.
- The idea solves a problem.
- This is validated as a ground truth prior without writing a line of code.
- Even better, the solution is validated to be a pain killer rather than a vitamin.
- Best, the problem is your own and you know other people, like you, who share it. You’re within the population mean and solving your problem has a large TAM.
- You bias action.
- Don't try to be perfect; do things that don't scale to gain momentum.
- Talk to your users, build feedback loops, and maintain product flexibility.
- If you're not technical, find a technical co-founder. Outsourcing is a form of debt.
- Stay focused, transparent and honest with yourself and your team.
- Hire smart people, provide them with a sense of ownership and agency, and trust in their judgement.
- Raising Money
- Don't treat it like it's yours.
- Don't go on a hiring spree. If you're not hungry you're dead.
- Stay default alive.
Failure, on the other hand, is certain and comes down to one of two things: you are a) not solving a problem, or b) care more about your idea than the problem.
[Shoot me an email](mailto:[email protected]?subject=Let's%20Build)