Every stack decision is a bet on future hiring, maintenance and vendor direction. The most expensive choices are rarely wrong on day one — they become wrong as the organization grows around them.
Questions worth asking
- Can we hire and train people for this in our markets?
- Is the community and vendor support healthy and growing?
- Does it integrate cleanly with what we already run?
- What will it cost to operate, not just to build?
- How hard would it be to move away from it?
Prefer boring where it matters
Use proven, well-supported technology for core systems of record, and reserve newer tools for areas where they offer a clear advantage. Document the reasoning in short architecture decision records so future teams understand the trade-offs.