The hidden cost of managing a software vendor

Your software project invoice shows €500,000. It does not show the 14% of your CTO's working year that went to managing it.

Every enterprise software project has a published cost and a real cost. The published cost is what the vendor charges. The real cost includes the internal time your organisation spends on that project: coordinating requirements, reviewing deliverables, chasing clarifications, running status calls, managing escalations, and re-negotiating scope.

For most organisations, this overhead is never measured. It is absorbed into senior staff time and written off as the cost of doing business. But it is substantial, it compounds across multiple vendors, and it is often larger than the efficiency gains the software was supposed to deliver.

The four categories of overhead

Internal management overhead on software projects typically falls into four buckets.

Requirements coordination. Translating business needs into specifications that an external team can build. Writing documents, running workshops, reviewing and revising. For a medium-sized project, this typically runs 2–4 weeks of a senior business analyst or product manager's time.

Deliverable review. Evaluating what the vendor has built. Running demos, writing feedback, re-running demos. This is often underestimated because it feels lightweight, but it recurs every sprint.

Escalation management. Handling disputes, misalignments, and scope questions. In a typical 6-month project, expect 3–5 significant escalations. Each one involves multiple senior people and a resolution process that can run days or weeks.

Administrative overhead. Purchase orders, invoices, change requests, contract amendments. Legal review of each change. Finance approval cycles. Each one is small; together they add up.

Added together, these typically represent 15–25% of the vendor's invoice, paid in internal senior time.

Running the numbers

A €500,000 software project with a 20% overhead load costs €600,000 in total spend. But because the overhead is in people's time, not on an invoice, the €100,000 is invisible.

At the individual level, a CTO who spends 14% of their year managing one vendor is spending roughly 35 days on status calls, spec reviews, and escalations, time that is not available for architecture decisions, team development, or strategic work.

For organisations running three or four significant software projects simultaneously, the overhead calculation multiplies. Three projects at 20% overhead each means 60% of senior management time absorbed by vendor management, before any strategic work begins.

The hidden cost of vendor management is not a rounding error. For organisations running multiple concurrent projects, it can exceed the cost of a full-time senior hire.

Why the problem compounds at scale

Vendor management overhead is not linear. A second vendor does not add 20% overhead. It adds more, because inter-vendor dependencies create new coordination problems.

When Project A depends on an API from Project B, and Project A is running behind, the status call for Project A now involves Project B's status too. Escalations from one vendor begin to affect the timeline of another. A project manager who was managing two relationships is now managing the relationship between those relationships.

This is the reason large enterprises often find their software development portfolio moving at the speed of the slowest project, regardless of how much is being spent on the fastest ones.

The alternative: embedded accountability

The management overhead problem has one structural solution: fewer, longer-term relationships with partners who hold more of the delivery loop themselves.

An embedded delivery partner (one who functions as an extension of the internal team rather than an external contractor) reduces overhead in a specific way: instead of requirements going out and deliverables coming back, the partner is inside the loop. Requirements are refined in real time. Deliverables are reviewed continuously. Escalations are resolved immediately, because the partner is present, not remote.

The day rate of an embedded partner may be higher. The cost as a percentage of total project spend is typically lower, because the overhead is absorbed into the delivery relationship rather than added on top of it.

Three questions before you sign

If you want to estimate the real cost of a software vendor relationship before committing, ask three questions.

Who on our side will spend time managing this relationship, and for how many hours per week? If the answer is "just a weekly check-in," you are either dealing with a very experienced partner or underestimating the involvement.

What happens when requirements change? The overhead from a traditional vendor spikes at change points: new change request, new negotiation, new contract amendment. An embedded partner absorbs change inside the delivery loop.

What does the escalation path look like? If an escalation goes from project manager to account manager to engagement director, you are looking at overhead. If it goes directly to the person who can fix the problem, you are not.

The hidden cost of managing a software vendor is not inevitable. It is a consequence of the structural distance between your business and the team delivering for it. Close that gap, and the overhead disappears.