A lot of smaller MSPs run an RMM like Atera and never adopt a full billing-capable PSA. That's a completely workable setup, but it means pricing and invoicing need a different structure than the PSA-contract model most billing advice assumes.
Why some MSPs skip the PSA
A PSA earns its keep on ticketing, contracts and structured billing rules, but it's another system to configure, maintain, and pay for. For smaller MSPs, or ones running a lean device-management model, the RMM alone often covers what's actually needed day to day: monitoring, patching, and remote access. The gap only shows up at billing time, when there's no natural place to store "what does this client owe."
What ends up happening instead
- Pricing lives in a spreadsheet, updated manually as clients are added or devices change
- Someone manually counts devices in the RMM each month before invoicing
- Resold licences get marked up inconsistently, depending on who set the price
- Invoices are typed directly into the accounting platform from memory or a spreadsheet
This works, until it doesn't. It scales badly past a certain client count, and it's exactly the kind of manual process where revenue leakage creeps in unnoticed.
What a rate card replaces
A rate card is the structural piece a PSA would normally provide: a single place that says what you charge per device type, and what markup applies to resold licences. Instead of building that list manually, it can be populated directly from what's actually in your RMM and distributor accounts, so pricing always reflects what's really being managed.
- Device types are discovered automatically from your RMM, no manual list-building
- Resold products are discovered automatically from connected distributors
- Set a fixed price per device type and a markup percentage on licences, once
- Per-client discounts layer on top for negotiated or long-term pricing
From pricing to invoice
Once pricing is set, the same device and licence data that priced it can generate the invoice, current device counts pulled from the RMM, current licence counts pulled from distributors, priced against the rate card, and pushed to your accounting platform as a draft. No manual counting, no re-typing.
Getting started
If Atera is your system of record, see the Atera integration for how device data flows into pricing, and the rate card for how pricing is set up. From there, invoicing follows the same flow described in automated invoicing.