The MSP Margin Playbook: How Reseller Margins Become Your Lost Wage Growth
The 5x Math Problem
Every MSP engineer intuitively knows this: the client pays far more for your time than you receive. But the gap is wider than most realise.
| Item | Typical Amount | Who Gets It |
|---|---|---|
| Client billing rate (per hour) | $180β$350 | MSP revenue |
| Your salary (per hour) | $45β$75 | You (taxed) |
| On-costs (super, leave, WC) | +25% | Government/insurer |
| Effective gap | 3xβ5x | MSP overhead & profit |
That gap isn't all profit. It covers sales commissions, account managers, tools/licenses, office space, insurance, after-hours loading, and the utilisation gap (the 20-40% of billable hours that go unfilled). But the margin between what you're worth to the client and what you're paid is still the industry's most guarded number.
Where the Money Actually Goes
Using data from 60+ MSP profiles on this site and public financial disclosures from ASX-listed MSPs, here's how a typical $200/hour billing rate breaks down:
| Cost Centre | per hour | % of billable |
|---|---|---|
| Your salary+oncosts | $62 | 31% |
| Tools & licensing | $14 | 7% |
| Account management | $20 | 10% |
| Sales commission | $16 | 8% |
| After-hours/on-call loading | $10 | 5% |
| Office & overhead | $18 | 9% |
| Subtotal cost | $140 | 70% |
| EBITDA margin | $60 | 30% |
The 30% EBITDA is above the industry average (typically 15-22% for small MSPs, per the CT Acquisitions Multiples Report). But that margin disappears fast when utilisation drops below 65%.
The Utilisation Trap
MSPs operate on a simple model: they sell your time, and unsold time is pure cost. Most MSPs target 70-80% billable utilisation. In practice, engineers average:
- Level 1: 35-50% (training, shadowing, internal tasks)
- Level 2: 55-70% (project work, escalations)
- Level 3/Lead: 65-85% (consulting, architecture)
When utilisation drops below 65%, the MSP starts losing money on that engineer. This is why timesheet pressure is the #1 non-salary complaint in our anonymous engineer surveys.
What This Means for Your Career
Know Your Revenue Number
If you're being billed at $250/hour and achieving 70% utilisation, you generate approximately $350,000 in annual revenue (250 Γ 0.70 Γ 2000 hours). Your salary + on-costs of ~$80,000 means you generate $270,000 in gross margin for the firm.
That's not profit β sales, management, tools, and overhead consume most of it. But it gives you power: every hour you're not billable costs the MSP money. When you're good, you're valuable. When you're good and specialise, you're irreplaceable.
Negotiation Levers
| Lever | How to Use It |
|---|---|
| Specialisation | Cybersecurity, Azure, M365 migrations = $300+/hour billing rates |
| Certification | Industry certs justify 15-25% rate premium |
| Client relationships | If clients ask for you personally, you have leverage |
| After-hours work | On-call and after-hours should command 1.5xβ2x rate |
| Utilisation history | If you consistently hit 80%+, ask for a pay review |
The Hidden Numbers
The most important financial metric in any MSP is net revenue per employee (NRPE). For Australian MSPs, this ranges from $180,000 to $350,000. The higher the NRPE, the more room for salary growth β and the more pressure to deliver.
When your MSP tells you "margins are tight," what they mean is: their billing rates haven't kept pace with cost inflation, or their utilisation is below target. Either way, it's a management problem, not a justification for below-market pay.
What to Do Next
- Find your real billing rate β check your MSP's public pricing page, or ask a friendly account manager
- Calculate your utilisation β divide billable hours by total available hours
- Know your leverage β specialisation + client relationships = negotiating power
- Use the salary calculator on this site β it's built from 3,800+ data points
The MSP industry runs on margins. The more you understand them, the better you can navigate your career β whether that means negotiating harder, specialising smarter, or leaving for a firm that values transparency.
Was this helpful?