Your Sourcing Event Is Selecting For Incumbents
A packaging sourcing event has a close date on the calendar.
The decision hiding inside a bid close date
A packaging sourcing event has a close date on the calendar. A week out, the picture is clean on one side and empty on the other. The two incumbents are fully through the RFI and the RFP, with pricing loaded and questions answered. The challengers are not. One started the RFI and stalled. Two have formally withdrawn. One went quiet after saying it does not participate in events of that type.
The decision in front of the category lead is not whether to run a competitive process. That decision was made months earlier. The decision is whether the close date holds. Hold it, and the event produces a tidy comparison of two incumbent quotes, which is then presented internally as the market's answer. Move it, and the schedule slips while somebody works the phones.
I have watched this exact choice get made in sourcing events I help run, and the instinct to protect the date is strong. It is the wrong instinct, because the date is not what the event is for.
Why process friction is never neutral
The absolute cost of bidding is close to equal across suppliers. The RFI questionnaire takes the same hours. The pricing template has the same cells. The portal demands the same registration, the same task list, the same uploads.
The relative cost is not equal at all, and that asymmetry is the whole mechanism.
For an incumbent, those hours are account maintenance on revenue they already hold. They have your specifications, your volumes, your pricing history, and a commercial reason to defend the position. Someone on their side is already paid to talk to you. The RFP is a cost of keeping what they have.
For a challenger, the same hours are speculative business development against a buyer who may simply be benchmarking. They do not have your drawings. They may have to quote around specification language written for the incumbent's process. They are weighing your event against other work with a shorter path to revenue.
Then the mechanics add their own tax. Invitations have to reach the right person. Access has to actually work, and access failures are silent on your side; a supplier locked out of an event looks identical to a supplier that cannot be bothered. Portal roles and permissions have a habit of being half configured, including for your own team. Every one of those small frictions is paid almost entirely by the party with the least reason to pay it.
The result is selection, not competition. Run a portal-mediated event on a fixed date and the completion rate sorts suppliers by how much they already depend on you.
The mechanism has limits worth naming. A challenger chasing a category it wants strategically will push through almost any process. The bias is strongest where your volume is a small share of the supplier's book, where the specification is custom, and where the supplier sells through relationships rather than bid desks. It is weakest in commodity formats with standard specifications and active bid teams.
What this does to the number you report
A quoted price, an awarded price, an implemented price, and a verified savings are four different things, and this mechanism corrupts the first one, which quietly corrupts the rest.
If the only complete submissions are incumbent submissions, the award is a renegotiation with extra steps. The incumbent knows it. Account teams track participation in your event; silence from the alternatives is visible to them too. A supplier that believes it has no credible challenger does not price unit cost aggressively. It prices term, index mechanics, and the conditions under which savings can be revisited later. That is where the value leaks, because term and indexation rarely appear in the savings number presented to the executive team.
The compounding effect is worse than the single cycle. The awarded price becomes next cycle's baseline. Build the following event's savings target off a number the incumbent set without pressure and the understatement is now structural, carried forward as an assumption nobody rechecks.
Run the event so the market can actually answer
Four changes, in order of how much they return.
Define bid coverage per lot before the calendar publishes, and make the close date conditional on it. Coverage, not invitations, is the thing worth tracking. Invitations measure your effort; complete submissions measure the market's interest.
Give challengers a channel that fits how they sell. A direct call, a spreadsheet, a one to one walkthrough of the specification, a short offline submission that your team loads for them. Capable suppliers decline portals for reasons that have nothing to do with capability, and treating that as disqualification shrinks your market for free.
Make access a task with an owner and a confirmation. Somebody verifies that each invited supplier can log in and see the event, and records the result. Until that check exists, you cannot tell disinterest from a configuration error, and you will read one as the other.
Name who decides to extend, and the rule they decide by, before the date is in play. An extension argued on the day becomes a negotiation about schedule credibility. An extension triggered by a coverage rule written in advance is just the process working.
Ownership sits with the category lead, not the project manager holding the timeline. Verification is the comparison itself: the award against the incumbent's prior price curve, and against at least one complete submission from a supplier that is not already in the account.
What a well-run sourcing event looks like
Coverage is defined per lot before any date is published. Access is confirmed for every invited supplier within two business days of invitation, with the check recorded. Each lot reaches close with at least three complete, comparable submissions, at least two from suppliers that are not incumbents. Every non-responder has a recorded reason, sorted into declined, no capability, channel mismatch, or never reached. Close dates move by a written rule rather than by argument, and when a lot closes under coverage, the award memo says so in plain language.
The next call to make
Open your active event and count complete submissions per lot, split by incumbent and non-incumbent. Any lot under two non-incumbent submissions is a renegotiation wearing an RFP's clothes, and you should decide now, in writing, what coverage level earns an extension. Deciding that rule before the date arrives is the entire difference between testing a market and documenting one.