Your Effective Hourly Rate: What Flat-Fee Clients Really Pay You
Published by
Throne of Profit EditorialReviewed by
William Hassell
Founder & Chief Editor, Throne of Profit
A flat monthly fee hides something a break-fix invoice never could: how many hours a client actually consumed to earn it. Two clients can both pay $2,500 a month and look identical on your revenue report. One quietly eats forty hours of your team's time; the other barely files a ticket. On paper they're twins. In reality one is a strong account and the other is losing you money every month you keep it.
The number that tells them apart is your effective hourly rate — the contract's monthly revenue divided by the hours your team actually spent servicing it. Flat fees were supposed to free you from the clock, and they should. But when you stop tracking hours entirely, you lose the only view that shows which agreements pay and which ones bleed. The point of a flat fee is to stop billing by the hour, not to stop knowing your hours.
EFFECTIVE HOURLY RATE = MONTHLY FEE ÷ HOURS CONSUMED
Client A $2,500 ÷ 8 hrs = $312/hr ▇▇▇▇▇▇▇ healthy
Client B $2,500 ÷ 20 hrs = $125/hr ▇▇▇ thin
Client C $2,500 ÷ 42 hrs = $60/hr ▇ underwater
└─ same fee, three different businessesOwner symptoms
Revenue looks fine, but certain accounts always feel like they swallow the whole week.
You can't say, off the top of your head, which managed clients actually earn their fee.
A "good" client by monthly revenue is one your best tech dreads seeing in the queue.
Why this happens
Flat-fee managed services were designed to smooth revenue and align you with the client's uptime instead of their downtime — all good things. But the same move that stabilizes revenue detaches price from effort. Once nobody's billing hours, most shops quietly stop logging them too, or log them without ever rolling the numbers up per client. So the link between what a client pays and what they cost you goes dark. Ticket volume creeps, a client's environment gets messier, a demanding contact learns they can call anytime — and none of it shows up anywhere, because the fee doesn't move and the hours aren't counted.
Common mistakes
Treating monthly revenue as the health metric, when revenue-per-hour is what tells you whether an account pays.
Not logging time on flat-fee work because "we don't bill it" — so the cost side goes invisible.
Averaging across the whole book, which lets a few great accounts hide several underwater ones.
Ignoring soft consumption — after-hours calls, hand-holding, scope creep — that never becomes a formal ticket but eats real hours.
Never recomputing, so a client that was healthy at signing stays "healthy" in your head years after their usage doubled.
Business consequences
An underwater client isn't neutral — it's actively expensive. Every hour your best technician spends over-serving a $60-an-hour account is an hour not spent on the $300-an-hour accounts, or on winning new ones. The account looks like revenue while functioning as a subsidy you pay out of your other clients' margin and your own time. Left unmeasured, it compounds: the hours climb and the fee stays frozen. The owner who computes effective hourly rate can see which handful of contracts are dragging the book — and then has a real choice: reprice, rescope, fix the underlying usage, or exit. You can't make any of those decisions on a number you've never calculated.
How experienced operators think about it
They treat the flat fee as a bet and the effective hourly rate as the scoreboard. The fee wagers that a client's usage stays inside a band that leaves you a healthy margin. Most bets land fine; a few don't. Seasoned operators don't take that personally — usage just drifts — but they do check the scoreboard on every account, on a schedule, not only when one screams loudly enough to notice. They also treat the number as diagnostic, not a verdict: a low effective rate is the start of a conversation about scope, price, or a fixable root cause in the client's environment — not an automatic firing.
Practical actions
Log every hour against a client, billable or not — remote fixes, on-site visits, after-hours calls, project spillover, and the informal "quick questions."
Compute revenue ÷ hours per account, monthly or quarterly, one line per client. The math is simple; the discipline of actually running it is the hard part.
Rank the whole book by effective rate, lowest first, so the underwater accounts surface instead of hiding inside an average.
Set a floor you won't work below, then flag every account beneath it for a deliberate decision rather than drift.
For each flagged account, choose one path — reprice at renewal, tighten scope, fix the usage driver, or exit — and don't let "we'll deal with it later" be the answer.
Questions every owner should ask
If I ranked every managed client by revenue-per-hour tomorrow, which three would be at the bottom — and am I sure, or guessing?
Am I logging the after-hours and hand-holding time that never becomes a ticket?
When did I last recompute these numbers, versus relying on how an account felt at signing?
Frequently asked questions
Doesn't tracking hours defeat the purpose of flat-fee pricing?
No — tracking hours and billing hours are different things. Flat-fee pricing frees the client from a metered invoice and gives you predictable revenue; that's worth keeping. But you still need to know your own hours internally, because they're the only way to tell a strong contract from one that's quietly losing money. Log time for your own visibility and keep billing the flat fee. You get the stability of the model and the truth about which accounts earn it.
What's a "bad" effective hourly rate?
There's no universal number — it depends on your fully loaded cost per technician hour, your target margin, and your market. The useful move isn't chasing an outside benchmark; it's setting your own floor from your real costs, then ranking every account against it. What matters most is the spread. If your best accounts earn several times what your worst ones do at the same fee, the worst ones are the problem to solve, whatever the figure.
Related articles
Running a Profitable Managed IT Services Business — the pillar.
Finding Out Which Managed IT Clients Actually Make You Money — turning this rate into a per-client profit picture.
Raising Managed IT Rates on Existing Clients Without Losing Them — what to do once you find the underwater accounts.
What Does a Job Actually Cost You? Real Job Costing — the general costing discipline behind this.
Am I Charging Enough? How to Know for Sure — the broader pricing question.
Every business has more decisions than time
Whether you need help solving one problem, evaluating a major opportunity, or making a company-changing decision, Throne of Profit gives you consulting capacity on demand.
Purchase only the consulting capacity you need and use it across Weekly Focus, Strategic Focus, Financial Focus, and ThinkTank engagements.