Count Who Finished Your RFP, Not Who You Invited

The field that cleared the gates was the field we were trying to replace

In a multi-category sourcing event one of our teams was running, the picture a week before the close date was this. In the category with the thinnest participation, the two incumbents were fully through the RFI and the RFP and had their pricing ready. Of the four challengers invited to create the competitive tension, two had withdrawn, one had gone silent after saying plainly that it does not participate in events of that kind, and one had started the RFI that week.

Nobody had made a mistake. The invitations went out, the pre-bid package went with them, the dates were clear. The event was still on schedule. And the only suppliers who were going to be standing there on close day were the two companies whose pricing the event existed to test.

That is the whole problem, and it is worth stating as a decision rather than a disappointment. One week out, the buyer has to choose: hold the date and award from a field of incumbents, or move the date and go get the challengers in by hand. Most teams hold the date, because the date feels like discipline. It is usually the more expensive choice.

Why the process selects for the incumbent

An incumbent has revenue on the line, so it will learn whatever system you put in front of it. It has answered your RFI before, it knows which of your questions matter, and it has a named person whose job includes keeping your account. The cost of clearing your gates is small against the business at stake, and the incumbent pays it first.

A challenger has none of that. It has no revenue with you, no history with your format, and no internal owner for your event. What it has is a login to an unfamiliar portal and a document set from a company it does not sell to. The cost of clearing your gates is the same work the incumbent does, measured against a chance rather than a renewal.

Then there is the specific fear, which is the part most buyers never hear. Small and mid-sized suppliers often do not distinguish between an online sourcing event and a reverse auction. They see a portal, they assume a price war with their margin as the variable, and they decline. Our pre-bid documents have carried language for years stating that the event is not a reverse auction, and suppliers still read it that way. One of the challengers in this event told our team directly that it does not participate in those kinds of things. It never asked what the mechanism was.

A supplier who is afraid of your process does not negotiate the process. It goes quiet. That is the mechanism that matters: the filter is invisible on your side, because a withdrawal and a slow start look identical in an invitation list, and both look like participation until the gate closes.

There is a smaller version of the same failure inside the tooling. In this event a team member was added to the project but never granted access, so the record showed him as part of the event while he could not log in at all. Being added is not being able to participate. If that can happen to someone on your own team, assume it is happening to a supplier who has no one to complain to.

What the close date is actually buying

The question to ask about a bid close date is what leverage it carries on its own.

Sometimes the date is the leverage. I sat on a weekly call where a prospect asked for 6 weeks instead of 4 to turn its data around, and the answer was that the current process cannot accommodate it. That was correct. In a program that aggregates many buyers into one market approach, the value comes from loading everybody at the same market timing, so a participant who arrives late does not get a slower version of the program, it gets the next cycle. The date is load-bearing because the cohort is the leverage.

A single-buyer event has no cohort. The date buys sequencing convenience and nothing else. The leverage is the depth of the field, and when the field is two incumbents, holding the date converts a renewal into a document that looks like a market test.

The cost of that is not the award. It is the baseline. The price you accept from an incumbent field becomes the reference price the category carries forward, and the next cycle's savings get measured against it. Negotiated savings against a number the incumbent set are arithmetic, not evidence. The cost per unit in your file looks tested, the margin assumption behind it was never challenged, and the working capital terms nobody competed on stay exactly where the incumbent wrote them. You will not find that error later, because the file is internally consistent.

Count completion by incumbency, not invitations

Pull your current event and count gate completion in two columns: incumbents and everyone else. Count by supplier, by category, and by gate, not by invitation sent. Then verify one challenger by having someone watch them log in, or by checking the admin view rather than the invitation record.

Decision: hold the close date, or move it and open a direct lane. Trigger: fewer than 2 non-incumbents through every gate in a category at 48 hours before close. Action: the category owner moves that category's date and offers each remaining challenger a lane that does not require the portal. Our team's version of that offer is the one worth copying, because it answers the fear directly: this is not an auction, it is a real RFQ that happens to be run online, and we will take your numbers one to one, on a call, outside the system if that is easier. Put it in writing, then call.

If the date cannot move, the decision is still yours, and it is a labeling decision. Record in the award file that the pricing was obtained without a challenger field, so the number does not travel into next cycle's baseline wearing a benchmark's clothes.

What a real market test reads like

Every invited supplier has a named human contact who has confirmed, in a conversation rather than an email receipt, that they can and will submit. Every one of them has logged into the event at least once, verified in the admin view. At least 2 non-incumbents per category have cleared every gate before the close date is treated as fixed. The pre-bid package states the pricing mechanism on its first page, in the supplier's language, not yours. And when a date moves, the file records why it moved and what the field count was before and after, so the next event starts from a real number.

Read your own field before you read the pricing

Before the next close date, count the challengers who finished, not the ones you invited. If that count is zero, you do not have a pricing decision in front of you. You have a participation problem, and the only useful next move is a phone call to a supplier who is quietly afraid of your process.