TL;DR
- Labor costs = 50-70% of engineering opex
- Your stack determines your hiring pool
- Rust premium: $175K-195K (15-20% above baseline)
- Seed stage: optimize for speed. Growth: optimize for scale. Enterprise: optimize for efficiency.
The Stack as Investment Thesis
Your technology stack is a capital asset with three measurable properties:
- Total Cost of Ownership (TCO): Hiring costs, infrastructure, maintenance
- Liquidity Profile: How easily can you hire? How quickly do they ramp?
- Depreciation Schedule: How fast does technical debt accumulate?
CFOs evaluate capital assets on these dimensions. CTOs should evaluate stacks the same way.
The Hiring Liquidity Matrix
| Ecosystem | Pool Depth | Time-to-Hire | Seniority Profile |
|---|---|---|---|
| JavaScript/TypeScript | Deep | 30-40 days | Mixed, high junior volume |
| Python | Deep | 35-45 days | Data science skewed |
| Go | Moderate | 40-50 days | Cloud-native focus |
| Rust | Constrained | 45-60+ days | Senior specialists |
For a Series A with 10 engineers, choosing Rust over Python implies $300K-500K extra annual payroll. That capital could extend runway by months.
The Innovation Tokens Framework
Organizations have limited capacity for technical novelty—roughly three "innovation tokens."
Good token spend: An AI startup uses a novel model architecture. The model IS the product.
Bad token spend: An AI startup uses novel models AND a beta database AND an experimental framework AND bespoke deployment. Four tokens spent, three on non-differentiation.
When Postgres fails, Stack Overflow has the answer. When your six-month-old vector database fails, you're on your own.
The CTO Decision Matrix by Stage
Seed (0-10 Engineers): Optimize for Speed
- Stack: Python/Django, Rails, or Next.js
- Architecture: Monolith
- Goal: Product-market fit
Growth (20-50 Engineers): Optimize for Scale
- Introduce Go/Rust for specific bottlenecks
- Profile first, optimize second
Enterprise (100+): Optimize for Efficiency
- Polyglot architecture
- Kubernetes or hybrid for cost control
Key Takeaways
- Stop asking "what's the best stack?"
- Start asking "what stack minimizes TCO at our current stage?"
- The answer is almost always more boring than you'd expect
Originally published on alexmayhew.dev
Top comments (0)