Organisations facing a delivery gap tend to compare a day rate against a salary, conclude that hiring is cheaper, and then spend six months recruiting for a capability they needed immediately. The comparison is not wrong, but it answers a narrower question than the one being asked.

Two variables matter more than rate

The first is duration. Capability required indefinitely as part of your core operation should generally be built in-house; that is where institutional knowledge compounds and where a permanent team is unambiguously the better investment. Capability required for a defined programme, or in a specialism you will not need continuously, is expensive to acquire permanently and awkward to redeploy afterwards.

The second is specialisation. A senior integration architect, an ERP functional consultant, or a security engineer may be needed for a fraction of the year. Hiring at that level for partial utilisation is costly; retaining someone underutilised at that level is also difficult, because the work is not sufficiently interesting to keep them.

What to require from a managed arrangement

Where managed capacity is the right answer, the arrangement should look considerably more like an extension of your organisation than a supplier relationship. In practice that means insisting on a small number of specifics.

  • Named individuals, not a pool. You should know who is working on your priorities and be able to keep them.
  • A named delivery lead who is accountable for outcomes, not only for staffing.
  • Defined service levels covering response, escalation, and resolution — in writing.
  • Working hours with substantial overlap with your own team, so collaboration is synchronous.
  • An explicit handover expectation: documentation and knowledge transfer as a deliverable, not a favour.

The failure mode to watch for

Managed teams fail most often not on capability but on ambiguity of ownership. Where the client assumes the partner is managing quality and the partner assumes the client is directing priorities, the gap shows up as rework several sprints later.

The remedy is unglamorous: a written division of responsibility agreed at the outset, and a reporting cadence that would satisfy an internal audit. Arrangements structured this way tend to run for years. Arrangements without them tend to be renegotiated quarterly.

The two models are not mutually exclusive, and the strongest pattern we see is deliberate combination: a permanent core team owning architecture and institutional knowledge, with managed specialists engaged around defined programmes.