All articles
More Outcome7 min

Why complex tenders end up back in Excel

Every senior procurement team knows the pattern. The organisation licenses a sourcing platform. Onboarding happens, templates are configured, the first events run smoothly. Then the tender that actually matters arrives: multi-country, multi-spec, suppliers with capacity limits and package offers, a board that wants risk and ESG weighed next to price. And somewhere between round one and the award recommendation, the real work quietly moves to a spreadsheet.

The instinct is to call this an adoption problem: more training, a cleaner template, a refresher workshop. It is not an adoption problem. The analyst who exported the event to Excel made a rational decision. The spreadsheet was the only place the complexity fit.

The line-item assumption

Standardised sourcing tools standardise. That is their economic model: one workflow, configured thousands of times, priced as a licence. The workflow's core assumption is that an offer is a list of line items, each with a price, comparable down a column.

Real strategic offers refuse that shape. A supplier wants to say: five percent off lot one if we win the full bundle. A fixed price if volume commitments hold. An alternative specification that is cheaper to make and just as good in use. A capacity ceiling in one region and spare capacity in another. These are package conditions, and they are where the value lives, because they are where a supplier's true cost structure shows.

A line-item template cannot hold them. So the buyer faces a choice nobody states out loud: simplify the event until it fits the tool, and lose the value that lived in the structure; or take the event out of the tool, and keep the complexity in the one place flexible enough for it. Excel.

Excel keeps the complexity and loses the optimum

The spreadsheet deserves respect: it holds the package conditions, the exceptions, the footnotes. What it cannot do is search. An award across dozens of suppliers, hundreds of line items, conditional packages and multi-spec alternatives is a combinatorial space with more candidate allocations than any team can enumerate. The optimum exists. No spreadsheet can find it.

What a team finds instead is a defensible allocation: a handful of scenarios, built by hand over late evenings, each one a compromise between what the data says and what the deadline allows. The gap between that defensible allocation and the true optimum is real money, and it never appears in any report, because nobody can see the road not taken.

And price is only one channel. The award that holds also weighs quality, risk and ESG, quantified, not as a qualification gate but inside the decision itself. That coupling, where pressing one dimension moves the others, is exactly what manual scenario-building cannot keep stable.

The honest diagnosis is structural

None of this is the analyst's fault, and little of it is the tool vendor's. A licence business must standardise to scale; depth is traded for access by design. The first generation of sourcing optimization, Wave 1, locked serious solving power inside heavyweight enterprise modules that needed specialist teams to operate. The second, the SaaS wave, made sourcing accessible through clean web tools and accepted a thinner model as the price. Both trade-offs were rational. Both leave the complex tender homeless. Wave 3 is the structural answer: the model, the methodology and the senior expert on a single engagement, paid on the outcome.

That is why the export to Excel keeps happening in companies that already pay for sourcing software. The event is not too unusual for optimization. It is too specific for standardisation.

What the alternative looks like

The alternative is not a better template. It is a constraint model built for your event: the package conditions, the capacity ceilings, the multi-spec alternatives, your risk appetite and your award rules, encoded as the model rather than squeezed into one. A hard-coded methodology supplies the proven foundation; code-on-the-fly customisation tailors it to the category, the strategy and the stakeholders at hand.

Inside that model, Expressive Bidding lets each supplier add package conditions within the buyer's structure, so the offer that reflects their real cost base can actually compete. Between rounds, Inter-Round Optimization re-decides the award and pinpoints the edges where each scenario flips, returning every participant a precise Path to Win rather than a generic rejection. Transparency of the rules, never of the hand: suppliers see how the award is scored, never your reserve and never each other's bids. The field sharpens because the honesty is the leverage.

And the decision stays where it belongs. Scenarios come back ranked across value, quality, risk and ESG with the trade-offs visible and the trace auditable from input to award. The Category Lead owns the recommendation, and legal, finance and the steering committee sign off on a trace they can actually read. The codified strategy stays with the team afterwards, which is more than the spreadsheet ever did.

The question to ask

If your most consequential tender of the year cannot be run inside your sourcing tool, the tool is not the problem and neither is your team. The model is. The question worth asking any vendor, including us: show me where my package conditions live in your model, and show me the trace from those conditions to the award.

Bring us a live category and we will show you exactly that, on your own data, before you sign anything.