The Engagement That Drifts

Last week I set out the four ways a firm buys operational capacity. Picking the model is the easy part. Buying it well is where the money goes.

Here is the pattern when it goes wrong.

Month one is onboarding. Lots of calls, lots of goodwill, no output anyone can point to. Month two the scope widens, because someone asks for a favour and it gets absorbed. Month three there is activity everywhere and progress nowhere. At month six a partner asks what this is costing and nobody has an answer that holds up.

Nothing failed. It just never started properly.

Why Month One Decides It

Because operational work has no natural finish line. A deal closes or it doesn't. A tracker is never done.

Without a defined test, the engagement gets judged on feel. Feel is generous early, because everyone is being helpful, and harsh later, because by then it's a line item. The judgement lands after the money is spent, which is the worst possible order.

The firms that get real value do one thing differently. They decide what success looks like before anyone starts work.

What to Fix Before You Start

Four things, and all of them are your side of the table.

Take a baseline. For two weeks before anything begins, measure the thing you want fixed. How many hours go to CRM hygiene. How long a target list takes to build. How many days a request sits unanswered. Rough numbers are fine. Without them you will never prove improvement, and you will never spot when improvement stalls.

Pick one scope and write it down. Not three workstreams. One. Broad scope is the single most reliable way to waste a first quarter, because it lets everyone stay busy without anything getting finished. Narrow it until it feels almost too small, then start there.

Name the metric. One number that moves if this is working. Hours of senior time released. Days from first call to IC. Percentage of pipeline with current data. Pick it now, while you are still objective.

Name an owner on your side. Somebody internal answers for whether this is working. Not the provider. If the only person tracking value is the one being paid, you have no test.

The Checkpoints

Day 30. Is the process documented? Not finished, documented. An SOP exists, owners are named, the work has a defined shape. If month one produced no artefact you can read, stop and ask why.

Day 60. Is it running without you explaining it? The test is whether the work happens on a cadence without senior input. Still answering questions daily at day 60 means the process was never really specified.

Day 90. Has the metric moved? If yes, widen the scope. If no, you need a straight answer as to why, and it should be a better answer than "these things take time."

What Day 90 Actually Tells You

If the number hasn't moved but the process is documented and running, that is usually a scoping problem. You fixed something real that wasn't the constraint. Repoint it.

If nothing is documented and nothing is running, that is a delivery problem. Ninety days is long enough to know. Firms lose years being polite about this.

The Question Worth Asking

Think about the last operational resource you added, in-house or external.

Could you tell me today, in one number, what it changed?

If you're setting something like this up now, reply and tell me what you're trying to move. I'll send you the baseline and checkpoint structure we use, whether or not you ever work with us.