In a services firm, the operating model is the product
A professional-services firm doesn't ship a product off a line. It converts a lead into a scoped engagement, staffed delivery, and a paid invoice. That end-to-end chain — new business, pre-sales, delivery, support, and the practice-performance loop that proves and improves it — is the operating model. Margin lives or dies in how cleanly work moves through it.
So when utilization sags or DSO stretches, reaching for a new PSA tool or a staffing push treats the symptom. The leak is usually structural: demand entering through side doors, rates set by judgment, staffing decided on gut, revenue managed after the fact.
The margin is leaking where you can't see it
The sector is running below its own healthy line — and the causes are operating-model causes.
average billable utilization has fallen below the 70% that SPI Research calls the minimum healthy benchmark — an all-time low.
of CFOs describe revenue leakage as "systematic" — a structural property of how billing, contracts, and delivery systems interact, not an occasional error.
Industry EBITDA has slid from the 15–16% held through 2023 to under 10% — a cliff, not a drift. SPI's own read: most firms stall because they lack integrated, real-time visibility across delivery, resources, and financials. That is an operating-model gap, not a tooling one.
Anonymized ETEGY Zero-Based read of a professional-services value chain, mapped to GSDPI. Real counts; client-identifying detail removed. Shaded cells mark the heaviest-loss stages.
The prerequisite isn't a tool — it's a standardized model
The instinct is to buy the platform — PSA, CPQ, a billing engine, or an AI copilot — and expect it to close the leak. But a tool inherits the model it lands on. Automate an intake that runs through side doors and you get faster side doors; digitize rate-setting that's subjective and you scale the inconsistency. The sequence matters more than the software.
- Side-door demand now enters faster
- Subjective rates scale as inconsistent rates
- Manual time capture is digitized, not fixed
- Dashboards report numbers no one can trace
- The leak accelerates instead of closing
- One governed front door for demand
- Rates set by rule, not judgment
- Billable work captured at the source
- Every number traces to a governed origin
- Automation compounds a model that works
Standardize how work enters, is priced, staffed, delivered, and proven — then automation earns its return. Stability and standardization are the prerequisite for automation and, past that, for any agentic AI that acts on the model without a human in every loop.
GSDPI, applied to a services firm
The same five stages that read the value chain also fix it. Here is the sequence, stage by stage — each one a place where a services model is usually leaking, and what "governed" looks like instead.
-
G
Get Pipeline & demand
Close the side doors. Every opportunity enters one governed intake with the signal needed to staff it — instead of commitments made at ~50% confidence on a verbal yes.
-
S
Sort Scope, price & staff
Replace judgment-based rates with a governed pricing and staffing rule. Work is classified, priced, and matched to capacity the same way every time — so margin is designed in, not discovered later.
-
D
Do Deliver & capture
Capture billable time and expense at the source, not from memory at month-end. Contractor and blended-team utilization becomes visible in real time — the single biggest pool of recovered margin.
-
P
Prove Bill & realize
Invoicing reconciles to delivered work automatically, cutting errors and DSO. Utilization and realized revenue become numbers held to a Traceability Ratio — defensible, not estimated.
-
I
Improve Close the loop
Give improvement work a governance owner so it actually lands. The loop feeds the next engagement — the model compounds capability instead of repeating the same leaks.
New Insights, the day they publish.
The operating-model reads behind ERP, AI & services — a short note when one’s worth your time.
New posts & Insights only. Unsubscribe anytime.
What the read surfaced — point by point
The problems a services firm feels as "a margin issue" resolve, on inspection, into specific breaks in the value chain. The six that carried the most weight:
Billable time & expense lost at the sourceDo
Time and expense captured manually, from memory, days after the work — leaking revenue before an invoice is ever raised. It's the quietest loss in a services firm because it never appears as a line item; the hours simply never make it onto the bill.
Contractor utilization eroding marginDo
Blended delivery runs without a governed, real-time view of who is billable and at what recovery. Subcontractor cost is committed up front; the margin on it is discovered at close. Across a portfolio of engagements, that gap is the single largest recoverable pool.
Rate determination is subjectiveSort
Pricing set by individual judgment rather than a governed rule means two similar engagements are quoted two different ways. Discounting has no floor, and margin leaks at the moment of sale — before delivery even begins.
Staffing committed on incomplete signalGet
Engagements are staffed at roughly half-confidence — a verbal likelihood, not a governed forecast. The result is bench held against work that slips, or scramble-staffing against work that lands early. Either way, utilization pays for it.
Invoicing errors & long DSOProve
When revenue is managed after the fact, invoices don't reconcile cleanly to delivered work — so they're queried, reworked, and paid late. Every day of rework is a day of DSO, and cash the firm has already earned sits uncollected.
Improvement work never reaches governanceImprove
Fixes are identified but have no owner with authority to land them, so the same problems recur engagement after engagement. The loop never closes — which is why a services firm can run the same transformation twice and feel no different.
How ETEGY reads it
Every line above is a stage of the services model that was never made governable — and a dollar of margin that can't be traced. We fix the model first, then let the tools earn their keep.
A Zero-Based read of the services value chain across the GSDPI lifecycle, ranking the pains, gains, and requirements — then holding billable work to a Traceability Ratio so utilization and revenue are numbers you can defend, not estimate. Stabilize the model; then automate it. See the ZBT Discovery →
The Services Value-Chain Leak Map
The whole argument on a single page — the six leak points mapped to GSDPI, with the question to ask at each. Built to circulate: take it into an operating review.
Zero-Based Transformation — be first to read it.
Be first to know when Zero-Based Transformation™ publishes.
Occasional launch updates only.