How would you justify the move to Cypress (or away from Cypress) to leadership?

Tool-choice debates often degenerate into developer preferences. Leadership tunes out. The frame that lands is: what does this change, in business terms, vs the alternative?

The factors to bring:

1. Developer time. Cypress's time-travel debugging and auto-waiting save hours of debugging vs Selenium. Quantify: "our team spent ~6 hours/week debugging Selenium flakes. Switching cuts that to ~1 hour/week, recovering ~250 engineer-hours/year." Compare against migration cost.

2. Suite stability trend. Pull the last 6 months of CI flake reports. If Cypress flake rate is 0.5% and Selenium is 5%, that's a 10x difference in build interruptions. Translate to PRs unblocked per week.

3. Recruiting and ramp-up. "75% of QA candidates we interview have Cypress or Playwright experience; only 30% have Selenium. Onboarding a new hire to Cypress takes 2 weeks vs 6 weeks for our Selenium codebase." Hiring is a real cost.

4. Maintenance cost. Cypress tests average 30% fewer lines than equivalent Selenium tests in our experience. That's both authoring time and review time saved.

5. Migration cost. Be honest. A 500-test migration is 1-2 quarters of dedicated engineering. Plot the break-even: when do the time-savings exceed the migration cost? Usually 6-12 months out.

6. The opposite case. Sometimes the right answer is away from Cypress — multi-tab, multi-browser, native mobile. If the product needs those, Playwright or Selenium is the better choice. Acknowledge it.

The form of the pitch:

"We currently run X tests in Y minutes with Z% flake. Engineers spend N hours/week on automation issues. Migrating to Cypress over 2 quarters costs ~£M in engineering time. After migration, we project flake to W%, time saved to V hours/week. Break-even at month K. Risks: recruiting harder for Cypress + Playwright vs Selenium-only candidates; multi-browser coverage shrinks unless we add a separate Selenium smoke. Recommendation: migrate."

The bullet points might fit on one slide with a chart. That's the right shape for a director conversation.

Anti-patterns:

• "Cypress is more modern" — leadership doesn't care.
• "The team prefers Cypress" — preference isn't ROI.
• Underselling migration cost — the trust hit when you blow past the estimate is worse than picking a slower migration plan.

The honest framing for not migrating: if the existing Selenium suite is stable and the team is fluent, the migration ROI is weak. Don't migrate for the sake of fashion.