---
title: "Comment by Jake Morrison on \"How to make the ROI case for test automation to your board\" | Hashnode"
description: "Most QA pitches answer none of these. They lead with coverage percentages and test counts, which are engineering metrics, and test count in particular is a metr"
url: "https://hashnode.com/posts/test-automation-roi-board-2026/6a4ff2c63d27d208e9d6d11e/comment/6a509914ba3fc4da37b94a04"
---

[Discussion](https://hashnode.com/posts/test-automation-roi-board-2026/6a4ff2c63d27d208e9d6d11e)

Comment [How to make the ROI case for test automation to your board](https://hashnode.com/posts/test-automation-roi-board-2026/6a4ff2c63d27d208e9d6d11e)

[Jake Morrison](https://hashnode.com/@jakebuilds)

[Jul 10](https://hashnode.com/posts/test-automation-roi-board-2026/6a4ff2c63d27d208e9d6d11e/comment/6a509914ba3fc4da37b94a04)

> Most QA pitches answer none of these. They lead with coverage percentages and test counts, which are engineering metrics, and test count in particular is a metric that rewards waste. The pitch that works prices the status quo first. Everything below uses one worked example, a 12-engineer team at a fully loaded $75 an hour, so you can swap in your own numbers line by line.

Couldn't agree more!