A client's e-commerce site went down for 15 minutes on a Tuesday afternoon. You got the alert, fixed it, and moved on. The client was unhappy but understood.
What you probably didn't tell them: that 15 minutes cost them $180.
Not in some theoretical sense — in actual lost orders. If that site does $30,000/month in revenue, every minute of downtime costs $0.69. Fifteen minutes is $10. But if the site was down during peak traffic — Tuesday lunch, say — the real cost is 3-4x higher.
Now multiply that across 20 client sites, dozens of incidents per year, and throw in the silent killer that nobody talks about: PageSpeed.
The problem nobody measures
A PageSpeed score of 41/100 doesn't feel urgent. It's not a red dot on a dashboard. Nobody calls you at 2am because the LCP is 4.2 seconds.
But Google's own data shows that a 1-second delay in mobile load time reduces conversions by up to 20%. A site scoring 41/100 versus 80/100 can mean 40-50% fewer completed purchases. For a $30k/month site, that's $12,000-15,000 in lost revenue every month — silently, continuously.
This is the problem Revenue Guard solves.
How Revenue Guard works
Set a monthly revenue figure on any monitored site. SiteBrief does the rest:
Lost to downtime is calculated from actual incident data: total minutes down × revenue per minute. This is precise — SiteBrief checks every 5 minutes, so it knows exactly when each incident started and ended.
At riskis the PageSpeed impact estimate. A score below 70 triggers a conversion rate reduction estimate based on Google's published data. The lower the score, the larger the estimated loss.
The AI explanation at the top contextualises both numbers: "Your website lost an estimated $2,177 in revenue this month, with $2,080 attributable to poor PageSpeed performance (44% conversion rate reduction from your 41/100 score) and approximately $97 lost during the single 15-minute downtime event."
Why this changes client conversations
Agencies who use Revenue Guard report one consistent change: conversations about performance upgrades become much easier.
Before: "Your PageSpeed score is 41. We should fix it."
After: "Your PageSpeed score is 41. That's costing you roughly $2,200 per month. Fixing it is a $500 project."
The second version sells itself. The client isn't being asked to spend money — they're being shown how to stop losing money.
How to enable it
- Go to any monitored site in SiteBrief
- Open Settings → Revenue Guard
- Enter the monthly revenue figure in USD
- Save — the panel appears immediately on the site detail page
Revenue Guard is available on all paid plans. The calculation updates automatically after every monitoring cycle.