vs MSP billing tools — one-MSP shape vs many-MSP shape.
Gradient MSP, ConnectBooster, Work 365, CloudRadial. These tools are very good at what they were built for: helping a single MSP bill their end-customers, reconcile against a couple of vendor invoices, and ride on top of their PSA. Scale the problem up into distribution — N MSP partners below you, N vendors above — and the shape stops matching.
The data model is the tell.
MSP billing tools are built around a primary entity: my MSP. One PSA, one ConnectWise or Autotask database, one company on the agreement. Vendors plug in as secondary feeds. Customers are the children of that one company.
You, the distributor, are not that shape. You sit above 50-500 partners, each with their own end-customers, their own pricing tier, their own PSA instance you don't control. Your vendors are not background feeds — they're half the business. When you force that into a one-MSP data model, the model fights you at month-end, every month.
Cloud Billing Services is built around a different primary entity: the distributor. N vendors upstream. N partners downstream. Pricing rules in between. Every query, report, and reconciliation starts from that shape — because that's the business.
It's a boring architectural difference. It shows up everywhere: how partner hierarchies model, how price sheets inherit, how disputes route, how reports roll up, how PSA syncs fan out. The shape either matches or it doesn't.
What each category is actually good at.
| Capability | MSP billing tools Gradient, ConnectBooster, Work 365 |
Cloud Billing Services |
|---|---|---|
| One MSP billing their end-customers | ✓ Core use case | — Not the fit — pick an MSP tool |
| Distributor with many MSP partners below | — Partners modelled as "customer groups" | ✓ Native partner-of-partner hierarchy |
| Many-vendor upstream (Microsoft + AWS + Google + security + backup + comms) | — Usually one or two vendor feeds deep | ✓ Normalised across 10+ vendor families |
| Per-partner price sheets with inheritance and overrides | — Customer-level markup, limited | ✓ Tier → partner → override, versioned |
| Partner white-label portal on your domain | — Rarely ships a partner-facing portal | ✓ Branded, scoped, per-tenant |
| Tight integration to one PSA (ConnectWise, Autotask) | ✓ Deep — often the point | ✓ Integrates, plus HaloPSA, plus none-of-the-above |
| Three-way reconciliation at distributor scale | — Two-way billing recon at best | ✓ Three-way, line-level |
| AU-owned, AU-hosted, AU-supported | — Mostly US-HQ | ✓ |
Pick the shape that matches your business.
Pick an MSP billing tool when…
- You are a single MSP billing your own end-customers
- Your PSA (ConnectWise, Autotask, HaloPSA) is the system of record
- You have 1-3 vendor feeds and they are manageable today
- Partner-of-partner hierarchy is not in your model
We say this directly: if you're a single MSP, a dedicated MSP billing tool is probably the right answer. Don't buy distributor infrastructure for MSP-scale problems.
Pick Cloud Billing Services when…
- You sit above 20+ partners, each with their own end-customers
- You have 5+ vendor families and they are getting worse, not better
- Month-end reconciliation is touching 60+ hours and growing
- Your partners want a branded portal on your domain, not a login to someone else's tool
- Compliance, AU data sovereignty, and multi-entity (AU/NZ/SG) are commercial requirements
"We grew out of a ConnectWise-plus-spreadsheet setup. The gap wasn't the PSA — it was that we'd become the thing above our partners' PSAs. That needed a different tool."
CTO, security-led AU aggregator (reference available on request)
Find out which shape you are.
If you're not sure whether you've outgrown an MSP tool or not, ask us. 20 minutes, your real data, honest answer.