THE MARGIN — Profitability & Utilisation OS Brain
THE MARGIN — Profitability & Utilisation OS Brain
For finding out which accounts pay for themselves. One orchestrator plus ten specialists that model true margin against real hours, expose over-servicing before it becomes structural, and tell you which client is quietly being funded by the others.
Revenue is easy to see and margin is not. The gap between them is unlogged hours, and unlogged hours stay invisible precisely because nobody wants to log them. The model takes your fee, your team mix, your rate card and your actual hours, then returns realised rate against contracted rate per account. The number that changes conversations is the delta: a client billed at a blended 145 who is actually served at 96 is not a profitable account, whatever the fee says. Most portfolios carry one or two of these, and they are usually the accounts everyone is proudest of.
margin_model.py
Calculates realised hourly rate against contracted rate per account from actual hours and team mix, ranks accounts by margin rather than by fee, and quantifies the over-servicing gap in both hours and money. Every OS Brain in this drop carries its own executable component, so the judgement calls stay with you and the arithmetic stops being a matter of opinion. Runs anywhere Python runs, and the specialists still work on their own if you never open it.
Say it in plain words — it works out the rest
Inside · orchestrator + 10 specialists
Where it refuses to skip ahead
- No margin without actual hours — fee divided by planned hours is a budget, not a margin.
- No account judged on fee alone — the largest account is frequently the least profitable one.
- Over-servicing gets counted even unlogged — estimate it rather than omit it, because omitting it reads as zero.
- No resign decision without the portfolio view — the account may be funding a relationship worth more than its own margin.