What Happens Between “Signed” and “Profitable”
The client signs the contract, the contact is marked as “Closed Won”, your team is getting the kickoff scheduled. On paper, everything is going super well.
Then you reach 90 days in. Revenue is increasing, but the margin for this clients engagement looks a bit thin. You’re barely breaking even. What happened??
Nobody did anything wrong, exactly. There’s rarely a singular large mistake to point at, that explains everything. Usually, the work is still getting done, the client is happy, and the invoices are paid on time.
Just because you sign a client with a cozy looking price tag attached does not automatically mean it will be profitable work.
The P&L Statement Surprise
Here's what we see with many client services teams: an engagement gets scoped and priced based on a historical estimate and the team gets to work. Let’s say you scope 80 hours of work per month. Tasks take a little longer than expected here, a scope conversation adds unplanned work there, and there’s a few miscommunications during handoffs. But your team is smart and hardworking, so nobody misses a beat. The work carries on.
At the end of the quarter, after you tell your Director of Operations to do a deep dive on what happened, they report that the team is spending roughly 130 hours per week on this client, instead of the 80. And the additional 50 hours have not been billed for.
This is the first and most overlooked stage of fixing delivery margin: Capture. It’s not adding a new reporting tool or using Claude to build another dashboard that is only useful for a week. Capturing current state provides an honest, real-time view of where time is actually going relative to what was sold.
Why this stage gets skipped
Most operations improvements start at the wrong end. Leadership feels the pain: margin's off, something's off they just don’t know what…so they jump into fixing process, retraining the team, or buying new software. All of that might eventually help. But without understanding current state first first, these are just guesses, at best.
You can't Connect the dots between a bottleneck and what that costs your organization if you never captured where the time actually went. You can't Clarify a broken handoff if nobody logged that the handoff was where the delay happened. Every later stage depends on capturing current state.
People avoid this step because it can be genuinely uncomfortable to look at. Capture often reveals that the problem isn't a lazy team or bad luck; it's an invisible pattern nobody has caught onto. That's not a fun thing to find. But it's a fixable one.
What Capture actually requires
This doesn’t require hours of your teams time or manually going through time tracking to log and understand where time went. It doesn’t require an emergency huddle with your team to hash out what’s going on (they won’t know). It’s not six weeks of process or tooling training. It requires:
A lightweight way to see hours logged against original scope, that stays visible during the engagement
Enough visibility to catch an engagement drifting off-scope while there's still time to course-correct
A habit of asking "how does this compare to what we planned?" at natural checkpoints, not just at the close of an engagement
That's it. It's a visibility problem before it's anything else.
How do you start the Capture process?
Start smaller than you think. Pull one active client engagement, ideally one where something already feels "off," even if you can't say why. Compare the hours actually logged against it this month to the hours you originally scoped. Just pull what you already have: time tracking, project notes, whatever's lying around.
If the gap between expectations and reality is small, you've confirmed things are fairly healthy. If it's not (and for most teams, it isn't) you've just found your starting point. Not a crisis. A starting point.
From there, the question becomes: is this a one-off, or a pattern across every engagement?
We can help get you started with a Live Workflow Mapping Session.
