Fractional CTO
Stack choice is rarely wrong in a way that matters technically — most modern stacks can do most jobs. It goes wrong when it is picked for the wrong reasons: what is trendy, what one developer already knows, or what an agency happens to specialise in, none of which are about your product or your team.
Team size and existing skills, expected scale, budget for hosting and maintenance, and how long the product needs to last before a rewrite is acceptable.
Not one 'correct' answer — a short comparison of what each option costs you in speed, hiring pool and long-term maintenance.
One option named, with the specific reason, so you can hand it to whichever developer builds it and have them agree it makes sense.
A developer you are interviewing to build the thing will, consciously or not, favour the stack they are strongest in. An agency will favour whatever they have a team staffed for. Neither is dishonest — but neither is neutral, and you cannot tell which you are hearing without a third opinion.
In roughly the order they matter for most small teams.
No — popularity is one input among several, and often not the deciding one. A smaller, boring stack that your team already knows frequently beats a trendier one you would have to hire for.
No. This is also used to sanity-check a choice already made, before it becomes expensive to change.
CTO & Founder at Punch AI | Building Software Harnesses for AI-Powered Development | PhD Student in Software Engineering
CTO and Founder at Punch AI, building software harnesses that make AI-powered development safer and more reliable. PhD student in Software Engineering, bridging applied AI engineering with academic research.
Tallinn, Estonia
Founder / Senior software developer
Founder and senior software developer building SaaS products end-to-end, from architecture and backend APIs to the shipped frontend. Focused on lean, maintainable systems for early-stage products.