The question that paralyzes
"What tech stack should we use?" is the question that stops non-technical founders in their tracks. The answer matters — the wrong choice can mean years of technical debt — but the anxiety around it is disproportionate. Most stacks are fine. The decision is less about which technology and more about understanding your own constraints.
Start with constraints, not technologies
Before evaluating any technology, answer four questions about your own situation:
- Who is building this? — If you have a technical co-founder, use what they know. If you are hiring, use what is common in your market. If you are using an agency, use what they specialize in.
- How fast do you need to ship? — Speed favors proven, boring technology over cutting-edge. You can always migrate later; you cannot get back lost time.
- How will you maintain it? — The best stack is the one you can find help for. Obscure technologies are cheap to start and expensive to maintain.
- What is the scale? — Most products never reach the scale where stack choice matters for performance. Optimize for developer speed, not theoretical throughput.
The boring technology principle
The technologies that power the most successful products are usually not exciting. They are proven, documented, and widely supported. Choosing boring technology is not a lack of ambition — it is a recognition that your competitive advantage is unlikely to be in the infrastructure layer.
When to choose differently
Choose exciting technology when the technology is the product. If you are building a database company, the database matters. If you are building a marketplace, it probably does not.
The principle
The right tech stack is the one that lets your team ship, maintain, and iterate. Everything else is secondary. The founders who agonize over stack choice and ship late lose to the ones who choose adequately and ship now.
Knowing better means knowing which decisions deserve deliberation and which just need a decision.