April 4, 2026 · Tim Fraser, Cloud Operations Lead

How MSPs Use Automated Reports to Find Billable Work

Most MSPs think of monitoring as a cost centre. You check on client environments because you have to, not because it generates revenue. The time you spend reviewing AWS accounts is time you can't bill for — or time the client resists paying for once the novelty wears off.

But there's a different way to look at it. Every security finding, every cost anomaly, every operational risk sitting in a client's AWS account is potential billable work. The problem isn't that the work doesn't exist. The problem is that nobody's looking for it systematically.

Reports as a work pipeline

When you deliver a weekly infrastructure report to a client, you're not just proving you're watching. You're building a pipeline of remediation work.

A typical weekly report on a client's AWS account will surface findings like:

• Security groups with overly permissive ingress rules — fixing each one is a billable task
• RDS instances without automated backups — configuring and testing backup strategies is a project
• Unattached EBS volumes and idle Elastic IPs — cleanup work that also saves the client money
• IAM users with long-lived access keys that haven't been rotated — credential rotation and policy tightening
• EC2 instances running oversized instance types — right-sizing analysis and migration
• SSL certificates approaching expiration — renewal and automation setup

Each of these findings is a conversation with the client. Each conversation is a potential ticket. Each ticket is billable work.

The economics for MSPs

Consider a client paying your MSP a monthly retainer. You set up an plainfra subscription for their AWS account at $79/month. Every week, you receive a health report covering security, cost, and operational findings.

In the first month's reports, you find: three security groups need tightening, two EBS volumes are unattached and costing the client money, an RDS instance has no backup configured, and the client is running a t3.2xlarge that could be a t3.large based on utilisation.

That's easily 8-10 hours of remediation work. At typical MSP rates, you're looking at $1,500-$2,500 in billable work surfaced by a $79/month subscription. And that's month one — new findings appear every week as the client's environment changes.

The subscription doesn't just pay for itself. It generates a consistent stream of work that you'd otherwise miss because nobody was looking.

What a good report covers

A useful client report answers the questions that matter to both you and the client. Not raw CloudWatch metrics — actionable findings.

• New findings since last report (public-facing resources, permissive security groups, IAM issues)
• Trend direction: improving or degrading?
• RED/AMBER/GREEN summary the client can show their leadership

• Total spend and week-over-week change
• Top services by cost
• Identified waste with dollar amounts
• Anything that spiked, with a plain-English explanation

• Resource utilisation and right-sizing opportunities
• Backup status across all databases
• Certificate and domain expirations approaching
• Single points of failure

• Prioritised by risk and effort
• Written clearly enough that you can turn each one into a ticket

The format matters. Your client probably isn't an AWS expert — that's why they hired you. Write findings in language a competent manager can read without Googling acronyms.

From report to revenue

The workflow is straightforward:

• plainfra scans the client's account and delivers the weekly report by email as a PDF
• You review the report and identify findings that need action
• You create tickets in your project management system — one per finding
• You discuss with the client — walk them through the findings, agree on priorities
• You do the work — remediation, optimisation, hardening
• You bill the client for the work completed

Some MSPs forward the report directly to clients. Others review it first and present the findings in their own format during a weekly call. Either approach works. The point is that the data collection and analysis happen automatically — your time goes into interpretation, communication, and execution.

Scaling the model

As you add clients, each one gets their own plainfra subscription at $79/month. Each subscription monitors one AWS account and generates its own weekly report. Your Monday morning becomes: open each report, scan for new findings, create tickets, move on.

Ten clients means ten reports. The scanning takes maybe an hour total. The remediation work those reports surface could fill the rest of your week — and it's all billable.

This is how MSPs grow revenue without growing headcount at the same rate. The reports find the work. You deliver the expertise.