When spreadsheets stop working for your contingent workforce

Nobody buys a vendor management system because they love software. They buy one because a spreadsheet stopped answering a question someone senior asked. This is about recognising that moment before it becomes a problem, and being honest that most organisations do not need to act as early as vendors suggest.

Spreadsheets work for longer than people admit

If you run fifteen consultants, a well-maintained sheet is genuinely fine. One owner, a few columns, a monthly review. Buying enterprise software to manage fifteen engagements is a way to spend money and add process without getting anything back.

The failure is not gradual. It arrives as a specific question nobody can answer.

The four questions that break it

What are we actually spending? Not what was budgeted. What is committed right now across every department, including the engagements someone extended by email. When the answer takes a week to assemble and is contested when it arrives, the sheet has stopped working.

Why did we pay two different rates for the same role? Two teams hire a similar profile from different suppliers, months apart, and nobody compares. Without a rate history you can query at the moment of decision, this happens continuously and invisibly.

Who approved this? An engagement runs eight months past its end date because the renewal was an email nobody logged. The question only surfaces during an audit.

Does this invoice match work actually delivered? Finance receives a supplier invoice and has no independent record of hours, milestones or deliverables to check it against, so it gets paid because querying it is more expensive than paying it.

The threshold, roughly

In practice the breaking point sits around thirty concurrent consultants — not because thirty is magic, but because it is usually where the number of people who can extend an engagement exceeds the number who can see all of them at once.

The better test is not headcount. It is this: can one person answer all four questions above, today, without asking anyone else? If yes, keep the spreadsheet. If no, you are already running a programme you cannot see.

What actually changes

The value of a system is not the interface. It is that every engagement has one record, every rate has a history, every approval has a trace, and every invoice has something to be matched against. The savings that follow are mostly a by-product of visibility: you stop paying for engagements that quietly renewed, and you stop accepting rates you would have negotiated had you known the benchmark.

Fill customers see contractor rate cards fall by 14% and around €2M in first-year savings — nearly all of it from decisions that were always available but not visible in time.

The thing that decides whether it works

Adoption, and nothing else. A system that hiring managers avoid produces less reliable data than the spreadsheet it replaced, because at least the spreadsheet had one honest owner. If the people raising requests find the new process heavier than sending an email, they will send the email.

So when evaluating anything, test it on the person who hires two consultants a year, not the procurement specialist who will use it daily. If the occasional user cannot complete a request unaided, the rollout will fail regardless of the feature list.