We named four questions in this week’s Library piece on Vistex implementations. Condition-record count. Authorization-design phase. Settlement-to-billing flow. Year-2 SOW shape.
All four work. The partner who answers with specifics has done the reps. The partner who hand-waves is signaling that the timeline in their proposal isn’t grounded in delivery history.
There’s a fifth question. We left it out of the article deliberately — it works better in the room than on the page, and asking it requires being willing to make the partner uncomfortable. Here it is.
“What’s the worst Year-2 surprise you’ve seen across your last ten Vistex customers, and how did you handle it?”
The question forces a choice. The partner can answer honestly. They can deflect. They can pivot to wins. Each tells you something different.
Answer honestly. “Two of our last ten had a multi-entity acquisition in Year 2 we hadn’t planned for. The COA remap added a fourteen-week extension to the Year-2 SOW. We’ve tightened how we surface acquisition pipeline in Year-1 discovery as a result.” This is the answer you want. It signals the partner has institutional memory of their failures and has fed it back into their methodology.
Deflect. “Every customer is different.” “We can’t comment on other engagements.” “Confidentiality precludes specifics.” These are sometimes real reasons. They are also the answers a partner gives when they have not built the internal habit of patternizing their own near-misses.
Pivot to wins. “Our average customer satisfaction score is 4.6 out of 5.” “We’ve been a top Vistex partner three years running.” This is the most common deflection because it sounds substantive. It is not an answer to the question.
The deflection is the signal. Not because the partner is hiding misconduct — they usually aren’t. Because a partner without the habit of naming their own failure modes will sell you the next SOW exactly the way they sold it to the customer whose Year-2 surprise hit them. The lesson stayed inside the firm but didn’t change the playbook.
The partner who answers honestly is the partner whose Year-2 SOW for you is more likely to have already absorbed the lessons. The partner who deflects is the partner whose Year-2 SOW for you will look exactly like their Year-1 SOW — scope that doesn’t account for what they have learned but haven’t admitted.
This is true outside Vistex. It’s true of every category where implementation methodology compounds across customer engagements. It is most acute in rebate management because the failure modes are quiet — Vistex customers don’t usually call out their partners publicly the way SaaS customers sometimes do. The patterns stay inside the partner’s organization, or get lost there.
If you want a calibrated read on how a specific partner answered the fifth question — or a senior practitioner walkthrough of the Year-2 pattern landscape in your specific environment — a strategic conversation is the fastest path.
Dispatch #2 will look at something different. These go up when there’s a pattern worth surfacing.