Parallel point: the tech stack is more of a business decision than a tech decision for early stage startups.<p>I’ve seen many clients fail, or lose a lot of money and/or velocity when they’ve had to shift their tech stack in order to scale their engineering team.<p>So many of my clients have just given the first techie who could live off next to nothing for a few months the keys to the kingdom, and then you end up with someone who just picks whatever they were excited by as the foundation for your company. “We’ve decided to build this SaaS in Erlang because we need extreme parallelism”<p>I’ve had a few clients who built products using languages/stacks that were impossible to recruit for. A bootstrapped startup won’t be able to compete for engineers in $LANG if a bank and a successful corp hire everyone in that space at twice your salary range.<p>One of the things I’ve done with clients is to educate the non-technical founders enough to understand the basic stack their MVP is built with, the architecture, and the kind of profiles they’re going to need in their tech team. After all, it’s very often going to be the non-technical founders who are going to be arguing with VCs and investors to justify the hiring strategy.