Monitoring
Status Pages
Pricing
42 may be “The Almighty Answer to the Meaning of Life, the Universe, and Everything”; and according to De La Soul 3 may be the “Magic Number”; but when it comes to SaaS KPIs there’s only one number you need to keep at the front of your mind – 78.
78 is the magic number when it comes to SaaS, to predicting the MRR (monthly recurring revenue) you need to keep hitting month-in-month-out to reach your ARR (annual recurring revenue) goal for the next year. Simply subtract your target ARR from your last year’s ARR and divide by 78. It really is that simple.
So let’s give it a go. Assume your target this year is $1m ARR and that last year you hit $610k ARR. So what new MRR do you need to hit each month to reach your goal?
| 2016 ARR goal is: | $1,000,000 |
| 2015 ARR was: | $610,000 |
| Jump in ARR for 2016: | $390,000 |
| Target MRR | ($1,000,000 – $610,000) / 78
= $5,000 per month
|
Still not convinced? This is how it works. And let’s make the numbers even simpler. Let’s say you get 1 new customer each month who brings you in $1 per month. We’ll also assume that they never churn. The customer that signs up in January is worth $12 to you; the February customer $11 and so on right down to December’s customer who earns you $1. And there you have it, $78!
Can’t be bothered to do the math? Use our SaaS Rule of 78 Calculator below to work out your target MRR!
| Last Years ARR | |
| Your Target ARR | |
| Your Target MRR is |
It’s that simple. Now getting selling!
Share this
4 min read On 13th August 2026, a storm knocked out cooling at RadiusDC’s Phoenix data centre, which hosted essential Namecheap operations. To protect hardware from thermal damage, Namecheap took services offline while temporary chillers were brought in. The incident and recovery ran for roughly 30 hours, with Namecheap’s own site unreachable for about 11 hours 42 minutes
3 min read On Wednesday 19 August, Monzo had an outage. DownDetector logged more than 3,000 reports by midday. Monzo’s own statement was direct about what it did next: it activated Monzo Stand-in, its fully independent backup bank, while it investigated an issue affecting customers. By the end of the day, Monzo said the issue was resolved and
3 min read GitHub’s incident on 17 August 2026 ran from 13:28 to 21:15 UTC, seven hours and forty-seven minutes. At peak, web and API traffic saw error rates of around 20%, while archive and raw-content downloads reached roughly 50%. SAML and OIDC authentication, SCIM and Team Sync were affected alongside Git operations, Actions, Pages, Issues, Pull Requests
3 min read Adding a new website, launching a customer portal, or handing a service to a new team should be straightforward. Setting up monitoring is part of that job, but it is easy for a manual step to be missed when information is spread across several systems. StatusCake now integrates with viaSocket, giving teams a way to connect
7 min read A website may be standing and still be in trouble. It may answer a request, return a cheerful 200 OK, and yet load slowly enough that visitors begin to lose patience. Its certificate may be nearing expiry. Its domain records may have changed. A server may be filling its disk in the background, patient and
6 min read StatusCake tells you that something might be broken. Hermes can check whether it really looks broken, decide who should hear about it, send the email, and keep the record for tomorrow morning’s summary.
Find out everything you need to know in our new uptime monitoring whitepaper 2021
