Fullstride logoFullstride

How do I check WMS vendor references?

The conventional advice is a list of better questions to ask reference customers: ask about timeline overruns, ask about hidden costs, ask what they wish they'd known, ask to talk to someone in operations rather than the executive sponsor. The questions are reasonable. The problem is that they're being asked of the wrong people.

Vendor-provided references are not a representative sample of the vendor's customer base. They're a curated one. The reference list is built from customers the vendor knows will give a positive account — customers where the implementation went well, where the relationship is intact, where the executive sponsor is invested in the vendor's success and unlikely to volunteer hard truths to a stranger on a phone call. Availability bias dressed up as due diligence. The references that would actually tell you something — the failed implementations, the mid-project pivots, the customers two years past go-live who quietly regret the decision — are not on the list. The vendor will not surface them, and they have no incentive to.

Better questions to a stacked reference list don't fix the stacking. The reference call is structured to produce the same answer regardless of how the founder asks. The customer on the other end is friendly to the vendor by selection. The conversation happens inside that friendliness. The signal the founder is trying to extract — would this vendor be the right call for an operation like mine — is not a signal the reference call is built to produce.

The references that would close this gap are the ones the founder would have to find independently. Customers the vendor didn't suggest. Implementations that didn't end with the relationship intact. Operations similar enough in shape to the founder's that the comparison actually generalizes. None of those are accessible through the vendor's reference channel, which is the only channel most founders have.

This isn't a vendor failure. Vendors curate references because every vendor curates references — it's what reference programs are built to do. Asking a vendor to surface their failed implementations is asking them to do a job their sales motion isn't designed for, and they won't. The reference call is real, the customer is real, the answers are honest — and the input is still structurally compromised by who got into the conversation in the first place.

What founders typically have access to instead, when they want signal that isn't curated, are peers and industry voices — which carry their own version of the same problem. A peer's experience with a vendor reflects their operation, not yours. An industry voice's recommendation reflects their relationships, which usually include the vendors. The kind of vendor-side pattern recognition that would actually inform a fit decision — what specific systems do under stress, where particular vendors deflect, what their contract language signals — accumulates from being on the other side of the table, and isn't something a reference call is designed to surface.

System Fit Sprint

You're inside the process. We can still change what comes out of it.

If you're already in demos but the answers don't feel right, the System Fit Sprint can reset the foundation — your operation's actual requirements, a fit-filtered shortlist, and a ranked recommendation built outside the buyer's frame.