The situation

A multi-entity agency, operating across North America and Europe on two disconnected legacy systems, needed to replace one of them ahead of a hard licence-expiry deadline. That forced a broader question: just replace the one system, or take the opportunity to unify the whole group onto a single platform. A formal RFP went out to find out.

The method

This is not a vendor-marketing story. Agency DNA compiled a weighted scorecard covering roughly 140 requirements across finance, HR/payroll, technical, and operational needs, scored against the actual RFP responses from three candidates, then followed up with a second stage of live, scripted demonstrations, independently scored by multiple evaluators against the same real-world scenarios (intercompany billing, revenue recognition, bank reconciliation, and more). The RFP scoring stage put a specialist, industry-specific finance system ahead of the incumbent enterprise ERP, and a considerable distance ahead of two well known generalist mid-market alternatives that scored respectively third and fourth, on functional fit and reference quality.

What a closer look found

The specialist system handled agency finance well but had no native HR or payroll — an expected gap, so a parallel search priced a separate HR/payroll platform alongside it to create a genuine like-for-like comparison. Once that was done, the true combined annual cost still came out roughly a third higher than the incumbent's terms once those were properly renegotiated. Live demonstrations also surfaced real gaps among the other two candidates: the generalist system was found to lack core functionality the RFP had explicitly required, and although the vendor said it would be imminently available, the date they gave fell after the intended go-live. The third vendor didn't follow the script at all, presenting functionality too far removed from the detailed requirements they had been briefed on.

The decision

The client renegotiated the incumbent contract and chose to stay rather than migrate. The incumbent's pricing, when properly re-tendered against live competition, was substantially reduced from its expiring rate — a shift large enough that, once netted against the avoided cost and disruption of a full migration, it produced a meaningfully better financial outcome than switching, even before weighing the loss of embedded systems knowledge that migrating would have meant walking away from.

The takeaway

The evaluation reached a "don't move" verdict because that's what the evidence said. It was thorough and neutral: the same weighted-scoring and live-demo discipline that can build the case for leaving a system built, just as rigorously, the case for staying and renegotiating instead. The client got an honest, quantified answer — not a foregone conclusion.