The Optimization Paradox

Why Your Teams Are Not Optimising for the Same Thing You Are

Nobody in your company is trying to break the revenue engine on purpose. Every team is doing its job. Following its metrics. Hitting its targets.

And yet the engine stalls.

This is one of the more disorienting problems a CEO can face — competent people, clear responsibilities, and still the system underperforms. The instinct is to look for the weak link. The underperformer. The team that isn't pulling its weight.

That instinct is usually wrong.

Local Optimisation, Global Dysfunction

Economists describe this as the principal-agent problem. When one party acts on behalf of another, their incentives are rarely identical. The agent optimises for what they are measured on. The principal needs something broader.

In a revenue lifecycle, every function is an agent. And every function is measured on something different.

Sales is measured on closed deals. Not on the quality of the customers it closes. Not on onboarding success rate. Not on year-two retention. Closed deals. The incentive ends at signature.

Onboarding is measured on time-to-live. Get the customer operational as fast as possible. The metric rewards speed. It does not reward depth — the kind of thorough customer understanding that prevents delivery problems six months later.

Delivery is measured on project completion. Scope delivered, deadline met. Not on whether the customer feels the value. Not on whether the relationship is strong enough to survive the invoice conversation.

Finance is measured on collections. Outstanding invoices resolved. The metric rewards persistence. It does not reward the relationship cost of aggressive follow-up on a customer who was already uncertain about renewal.

Each function is doing exactly what it was designed to do. The problem is that no function was designed to optimise the engine as a whole.

The Gap Nobody Owns

Between every pair of functions, there is a gap. A space where the outgoing team's incentive has ended and the incoming team's incentive has not yet begun.

In that gap, the customer exists without an owner.

Sales has closed. Onboarding hasn't started. The customer is waiting — forming their first post-sale impression of your organisation based on silence, or a welcome email, or a calendar invite that may or may not arrive on time.

Delivery has finished. Invoicing has started. The customer has just completed an intensive engagement with your team and is now receiving a document that asks them for money. Who owns that transition? Who ensures the invoice lands in the context of a positive relationship rather than administrative friction?

The gaps are predictable. They appear at the same places in every revenue lifecycle. And because no function owns them, nobody fixes them.

Why Adding Headcount Doesn't Help

The standard response to these gaps is to add coordination. A customer success manager to bridge sales and onboarding. A project manager to smooth delivery handoffs. An account manager to own the renewal relationship.

These roles help. But they treat the symptom, not the cause.

The underlying incentive structure doesn't change. The new role inherits the same gap — now with the added complexity of coordinating across functions that are still optimising locally. The customer success manager cannot fix a handoff that was never designed. The account manager cannot manufacture renewal evidence that was never collected.

Coordination roles patch the gaps. They do not close them.

This Is Not a People Problem

That distinction matters more than it might seem.

If the dysfunction is a people problem, the answer is hiring, training, or replacing. If it is a design problem, the answer is architecture — redefining what each function hands off, what the next function receives, and what the system requires at each boundary to keep the engine running cleanly.

Most revenue lifecycle failures are design problems wearing the costume of people problems. The team that missed the renewal signal wasn't careless. They were operating inside a system that never gave them the signal in the first place.

The engine does not perform better when you blame the parts. It performs better when you redesign the system the parts are trapped in.

The Revenue Engine Risk Assessment identifies where misaligned incentives and ownership gaps are costing you revenue. Take the assessment →