New features take too long to build

Stack is outdated, talent pool is shrinking

Vulnerabilities, end-of-life dependencies

Performance bottlenecks, architecture limits

Spending too much on keeping lights on

Still manageable, some tech debt

Accumulated debt, tribal knowledge

Monolith, outdated patterns, few experts

Mission-critical, undocumented, fragile

Can focus full-time on modernization

Split between features and modernization

Mostly firefighting, little room for improvement

Team is 100% on keeping systems running

Startup pace, can move fast and fix things

Can't break production, but can take calculated risks

SLAs, revenue impact, need careful planning

Healthcare, finance, safety-critical systems

Can refactor with confidence

Core paths covered, gaps in edge cases

Manual testing, tribal knowledge

Fear of touching anything, unknown behavior

Easy to deploy, infrastructure as code

Can deploy but it's painful

Deployment days, coordination required

Rollbacks common, frequent outages

Need results fast, willing to invest heavily

Sustainable pace, steady progress

Long-term investment, phased approach

Slow and steady, minimal disruption

Need to minimize spend, prioritize ruthlessly

Can hire or use contractors for key work

Can build team, use consultants, tools

Modernization is a strategic initiative

Can afford extended downtime

Downtime hurts but isn't fatal

Revenue stops if system is down

Zero tolerance for extended outages

Start fresh, migrate data and users

Gradually replace pieces while keeping system running

Upgrade framework, refactor code, keep architecture

Open to recommendations based on situation