Put a number on your grid

Fill in the blanks below with your team’s estimates. If you don’t have a loaded hourly rate handy, the composite organization in a Forrester Total Economic Impact™ study commissioned by Sauce Labs used $65 an hour for QA engineers and $98 an hour for developers, fully burdened. Treat those as a starting point and swap in your own.

People-time

A. Grid upkeep and triage:

___ hours per week × 52 × $___ loaded hourly rate = $_____

B. Browser and driver updates:

___ hours per browser release × ___ browsers supported × 26 releases/year × $___ = $_____

(Chrome, Edge, and Firefox now ship a major version about every two weeks.)

C. Device administration:

___ people × % of their time × 2,080 hours × $ = $_____

Forrester reference point: 2 × 85% × 2,080 × $65 = $216,320

D. On-call and outage recovery:

___ grid outages per month × ___ hours to restore × 12 × $___ = $_____

E. Blocked engineers:

___ engineers waiting per outage × ___ hours waiting × ___ outages per year × $___ = $_____

Hardware and cloud infrastructure

F. Device refresh:

___ devices × % replaced per year × $ average cost per device = $_____

Forrester reference point: 50 × 20% × $800 = $8,000

G. Cloud or data center capacity for grid nodes:

$___ per month × 12 = $_____

H. Mac hardware for Safari coverage:

$___ per year (purchase cost spread over its lifespan, plus upkeep)

Tools and licenses

I. Orchestration, device-management, monitoring, and storage tools:

$___ per year

Total annual cost (A through I): $_____

Roadmap check: $_____ total ÷ $___ fully loaded annual cost of one engineer = ___ engineers’ worth of capacity going to the grid each year

Bring the total to your next planning meeting. A number turns “the grid is a pain” into a line item leadership can weigh against the roadmap.

Want the full breakdown behind each line?

Ready to take the grid off your team’s plate?