Ask a CX technology vendor where their deals are won and most will point at the demo, the proof of concept, or the commercial negotiation at the end. That is where the effort goes: solution consultants, sandbox environments, reference calls, a pricing model that bends.
Those stages decide which of three vendors wins. They do not decide which three vendors are in it.
The decision before the decision
Somewhere months earlier, a buyer sat down to work out what they were actually trying to fix. Maybe a new CX director arrived. Maybe handle times went the wrong way, or the board asked what the AI plan was, or a platform contract started approaching renewal.
At that point they did not have a requirements document. They had a problem, a vague sense of the category, and three or four names. Those names came from somewhere: an analyst grid, a peer at another company, a conference session, a vendor who had been quietly useful for a year without asking for anything, the thing they read that described their situation more accurately than anyone internally had managed.
That list is the real shortlist. Everything that follows is an elimination process run against it.
By the time there is a scorecard, the hard filtering has already happened. The scorecard just ratifies it.
Why feature differentiation does not help here
Vendors tend to differentiate on capability, because capability is what they control and what their product team talks about. Routing logic, model quality, integration depth, deployment options.
The trouble is that capability arguments only work once a buyer knows what capability they need, and that knowledge arrives late. Early on they cannot evaluate your differentiator because they have not yet decided it matters. A comparison matrix handed to someone still defining the problem is answering a question they have not asked.
What travels at that stage is recognition. The vendor who gets on the list is usually the one whose material made the buyer think: that is exactly our situation, and this person has clearly seen it before.
Who is in the room, and who is not
- The person with the problem — usually operations or CX, rarely procurement at this stage, and often not the eventual signatory
- Their peer network — the single most influential input in this category, and the one vendors have least control over
- Analysts and industry bodies — less decisive than vendors hope, but they set the vocabulary
- The incumbent — present by default, and frequently the one who gets to define what a replacement would have to do
- Internal technology — arrives later, and mostly constrains rather than selects
What this changes
If the shortlist is formed before the process starts, then the pipeline question is not how many RFIs you respond to. It is how many buying committees had already heard of you, in the right context, before they started writing anything.
That has three practical consequences. You need to know which accounts are approaching a trigger rather than which ones downloaded a guide. You need something to say that is specific enough to be recognised, which means it has to come from people who have actually solved the problem rather than from a content calendar. And you need to reach a wider group than the eventual buyer, because the person who first says your name in the room is often not the person who signs.
None of that is fast. It is also the only part of the process where a challenger has any real leverage, because once the list exists, you are either on it or you are being used to make somebody else look reasonable.