Should a PE firm require an independent review before approving a WMS investment?

The instinct is sound. A capital request for a WMS commits the portfolio company to a multi-year, high-switching-cost system, and the people presenting it usually have the least distance from it. Requiring a second look before the money moves is what an investment committee does with any decision it can't judge on its own. The difficulty is timing.

By the time a request reaches approval, most of what determines the outcome has already happened. The requirements were written, usually from the operation's own description of itself. The shortlist was assembled, usually through availability bias. The demos ran on scripts the vendors chose. A review at that point can test the proposals on the table: whether the scope matches the operation, whether the implementation plan is realistic, what the contract leaves out. It can't add the option that was never invited, or restore requirements nobody knew to write.

That still has value. A contract with uncapped annual increases, no exit terms, or a scope that quietly excludes the operation's hardest process is worth catching before signature at any stage. But a review that starts at approval checks the work rather than shaping it, and its findings arrive when changing course costs the most time and goodwill.

Whether to require one depends on what came before. If management documented the operation's requirements first and built the shortlist against them, a review of the proposals is usually enough, and sometimes even that isn't needed. If the request names one vendor and the comparison exists to justify it, the review the fund needs isn't at approval at all. It belongs months earlier, before the shortlist exists.

A review timed to the approval memo can protect the fund from a bad contract. Only an earlier one can protect it from a bad choice.