The operating model as the subject
Is your utilization real — or borrowed from heroics?
In a services firm, the operating model is the product — how a lead becomes a scoped engagement, delivered work, and a paid invoice. When margin leaks, the cause is rarely the people; it's a value chain no one can fully see. Here are the six places it leaks, mapped to the GSDPI lifecycle — and the question to ask at each.
Staffing committed on incomplete signal
Engagements staffed at ~50% confidence — a verbal likelihood, not a governed forecast. Bench held against slipping work; scramble against work that lands early.
Rate determination is subjective
Pricing set by individual judgment, so two similar engagements are quoted two ways. Discounting has no floor and margin leaks at the moment of sale.
Billable time & contractor margin lost
Time and expense captured from memory, days late — revenue gone before an invoice exists. Blended-team recovery is discovered at close, not managed in real time.
Invoicing errors & long DSO
Revenue managed after the fact, so invoices don't reconcile to delivered work — queried, reworked, paid late. Cash already earned sits uncollected.
Improvement work never reaches governance
Fixes identified but with no owner empowered to land them, so the same problems recur engagement after engagement. The loop never closes.
Every line above is a stage of the services model that was never made governable — a dollar of margin that can't be traced. A Zero-Based read across GSDPI ranks the pains, gains, and requirements; the Traceability Ratio then holds utilization and revenue to numbers you can defend. Stabilize and standardize the model first — then automation and agentic AI amplify a model that works.