On this page
Most MSPs already monitor their clients' sites and servers. Very few get paid for it. The monitoring sits inside the retainer, invisible, until the month a client asks why they're paying so much and nobody can point at what they get. The fix isn't a cheaper tool. It's packaging what you already do as a service the client can see, and pricing it like one.
The short version
- Bare up/down checks resell for $10 to $25 a client and are the first thing cut.
- Clients pay for what they can see: a status page, a monthly report and a response promise.
- Three tiers make the decision easy; aim to land most clients on the middle one.
- At $149 a client, the tooling cost on a flat plan is a rounding error.
- The monthly report is the retention meeting: it re-justifies the whole retainer.
Why bare monitoring doesn't sell
"We monitor your website" is a feature, and features get compared on price. The client can't tell your monitoring from a free uptime service, so the line item drifts down to $10 or $25 a month and is the first thing cut when budgets tighten. Worse, monitoring that works is invisible: the better you are at it, the less the client notices you're doing anything.
What clients actually buy
What a client will pay real money for is an outcome they can see and show their boss. A productized monitoring service bundles four visible things on top of the checks:
- A status page on their own domain, with your branding, that their customers bookmark. During an outage it's where trust is won or lost.
- A monthly report covering uptime, incidents with causes and durations, and response times, ideally opening with whether the uptime target was met.
- A response promise: how fast you'll act when something breaks.
- A review, by email or a short call, where you walk through the report.
Sold that way, monitoring and reporting is commonly priced from about $99 to $299 per client per month. Your market sets the real number; the point is that it's a service now, not a ping.
Three tiers
Three tiers make the decision easy and give clients room to grow. A structure that works:
| Essential | Professional | Premium | |
|---|---|---|---|
| Example price | $99/mo | $179/mo | $299/mo |
| Websites and APIs | Up to 5 | Up to 15 | Up to 30 |
| Server health | No | Up to 2 servers | Up to 5 servers |
| Branded status page | No | Yes | Yes, on their domain |
| Monthly PDF report with SLA verdict | No | Yes | Yes |
| Monthly review | Email summary | 30-minute call | Call + quarterly review |
| Incident response | Next business day | 4 business hours | 1 hour, 24/7 |
Aim to land most clients on the middle tier. Essential exists so the conversation starts with a yes; Premium exists so Professional looks reasonable.
The margin math
The cost side is where flat pricing earns its keep. Ensju's MSP plan is $125/mo for up to 500 uptime monitors, 100 server agents and 50 status pages on custom domains, with no per-host or per-seat metering. Spread across your client book at a $149 example price:
| Clients | Your cost / client | You bill / mo | Margin / mo | Margin / yr |
|---|---|---|---|---|
| 10 | ~$12.50 | $1,490 | $1,365 | $16,380 |
| 20 | ~$6.25 | $2,980 | $2,855 | $34,260 |
| 40 | ~$3.13 | $5,960 | $5,835 | $70,020 |
~$3
tooling cost per client at 40 clients
$149
example price per client
12
uptime monitors per client at 40 clients
Per-host pricing breaks this model: every client you add raises your cost, so you hesitate to add them. On a flat plan, the next client is pure margin until you hit the plan's limits.
What goes in the SOW
One page is enough, as long as it answers six questions:
- What is monitored, and how often.
- How fast you respond to an incident, and during which hours.
- How the client, and their customers, are kept informed.
- What the monthly review contains and how it's delivered.
- Where monitoring ends and billable remediation starts (rebuilds, migrations, capacity projects are quoted separately).
- How either side exits, and what you hand over.
Don't promise what you can't measure
Proving it every month
The monthly report is your retention meeting. Thirty minutes walking through uptime, incidents and response times re-justifies the whole retainer, with evidence. On the MSP plan, Ensju generates a branded PDF per client each month that opens with the verdict: "SLA compliance: MET", or MISSED with the services that missed it named.
The same data is a pipeline. An expiring certificate is a renewal engagement. A disk forecast to fill in three weeks is a capacity project. A site whose response times keep creeping up is a hosting conversation. Every one of them is billable work you'd otherwise never quote.
Rolling it out
- Put your name and prices on a three-tier pricing sheet.
- Pick your three easiest clients and tag their sites and servers so each client filters to one view.
- Stand up a status page for each one on their own domain.
- At the next check-in, present it as "we've been doing this informally; here's the formal service". Many clients already assume they're paying for it.
Built for this
Frequently asked questions
- How much should an MSP charge for website monitoring?
- Bare up/down monitoring is hard to charge more than $10 to $25 a client for, and it's the first line cut in a budget review. Sold as a service, with a branded status page, a monthly report and a response target, monitoring and reporting is commonly priced from about $99 to $299 per client per month. Your market sets the real number.
- Should monitoring be bundled into managed services or sold separately?
- Either works, as long as the client can see it. A separate line item with its own tiers is easier to price and upsell; bundled monitoring still needs a visible deliverable, like a status page and a monthly report, or the client forgets they're paying for it.
- What should a monitoring service agreement include?
- What is monitored and how often, how fast you respond to an incident, how the client is kept informed, what the monthly review contains, what counts as separately billed remediation, and how either side can exit. One page is enough.
- Will my clients see the monitoring vendor's brand?
- Not on Ensju's MSP plan: client status pages run on the client's own domain with your logo and colours, the Ensju footer can be switched off, and subscriber emails go out under your name.