Technical
AI Tool Maturity Curves: Reading Where Each Tool Actually Is
Clients ask me to pick tools. The wrong question is which tool is best. The right question is which tool is at the maturity stage that fits the risk profile of this project. Eleven months of field work taught me to read maturity curves.
The Four Stages I Track
- Experimental: fun to try, dangerous to depend on
- Emerging: works for specific workloads, loud changes between versions
- Mature: works for most workloads, quiet changes between versions
- Commoditized: works for all workloads, pricing pressure downward
I map every tool in my stack to one of these four stages every quarter.
March 2026 Snapshot
- Claude Code: mature
- Cursor: mature
- Codex async tasks: emerging
- MCP servers: emerging
- Multi-agent orchestration frameworks: experimental
- ChatGPT-based coding assistants: commoditized
Mature is the sweet spot for production. Emerging is the sweet spot for competitive advantage. Experimental is the sweet spot for learning. Commoditized is the sweet spot for scale.
Client Rules I Apply
If the client is risk averse: mature and commoditized only. If the client wants edge: add one emerging tool. If the client is just curious: one experimental tool in a sandbox, never in production.
Risk profile -> allowed stages
Conservative -> mature, commoditized
Standard -> mature, emerging (limit 1)
Aggressive -> mature, emerging (limit 2), experimental (sandbox only)The Signal I Watch
A tool is maturing when its changelog entries shift from new features to bug fixes and performance improvements. A tool is regressing when its changelog entries shift from improvements to pricing changes without capability changes. Read the Claude Code release notes for an example of a mature cadence.
The Mistake I Keep Seeing
Teams adopt experimental tools for production work because a blog post impressed them. Three months later the tool either pivots or sunsets. Cost of migration: everyone. Cost of reading maturity correctly: nothing.
Pick tools at the right stage for your risk posture. The stage matters more than the brand.
RELATED READING
The Consulting Shift I Am Making In Year Two
After a year of writing and building, my consulting practice is changing shape. Shorter engagements. Sharper outcomes.
ReadThe Frontend Shift: Shipping Less JavaScript In Year Two
A year ago I reached for Next.js for everything. This year I often reach for nothing.
ReadThe Serverless Lesson I Would Write On A Sticky Note
After a year of shipping serverless projects, one rule explains most of the wins and all of the losses.
Read