A good systems integrator is one of the most valuable partners you will have on an ERP program. The right firm brings people who have configured the platform a dozen times, who know where the bodies are buried, and who can move faster than any team you could assemble in-house. I have worked alongside SIs that earned every dollar and a few that earned a great deal more than they were worth. The difference was rarely the brand on the statement of work.
The difference was almost always in how the relationship was set up and how it was managed. Because here is the thing nobody says plainly enough at kickoff: your integrator and you do not want exactly the same thing. That is not a character flaw. It is the structure of the deal, and pretending it isn't is how programs drift.
The tension you are paying into
An SI gets paid to build. Whether the contract is time-and-materials or milestone-based, the firm's revenue is tied to effort and duration, not to how little work the answer turns out to require. Efficiency, simplicity, and "actually, you don't need that" are not what the model rewards.
I am not saying integrators are dishonest. Most of the people on the ground are conscientious and want a successful go-live as much as you do. But incentives are quiet and persistent. Over a two-year program, the gap between "what serves the engagement" and "what serves your outcome" doesn't show up as a single bad decision. It shows up as a hundred small ones, all defensible on their own, that together cost you months and millions.
So you need someone in the room whose only incentive is your outcome. Sometimes that is you. Often it should be someone independent who has no stake in how many hours the program burns.
Selecting the right firm
Most selection processes are won on the pitch and lost in delivery. The slides are excellent, the partner is charming, and the named experts are genuinely impressive. Then the contract signs, those experts rotate to the next sale, and you get a team you have never met. This is the A-team bait-and-switch, and it is so common it is practically a business model.
Score the things that actually predict delivery, and weight them accordingly:
- Relevant, recent, comparable experience. Not "we do ERP." Have they done your platform, at your scale, in your industry, in the last two or three years? Old success on a different product is a reference, not a qualification.
- The real delivery team. Ask to meet the people who will actually staff the program, by name, and get their commitment in writing. If the firm can't or won't name them, that tells you something.
- References you genuinely call and press. Don't accept the curated list at face value. Call them, and ask the hard questions: what slipped, what was the change-order experience, would you hire them again knowing what you know now.
- Cultural fit. You are going to be in hard rooms with these people for a long time. How they handle disagreement in the sales process is a preview.
- Willingness to be measured. A firm confident in its delivery will agree to objective acceptance criteria and holdbacks without flinching. Reluctance here is the most honest signal you will get.
Shaping the SOW
The statement of work is where you either keep your leverage or quietly give it away. Most SOWs describe activity, hours, roles, phases, and stop short of committing to a result. That is comfortable for the integrator and expensive for you.
Contract for outcomes and acceptance criteria, not just effort. Define the deliverables precisely and attach an objective definition of done to each one, so "complete" is something you can verify rather than something you argue about. Write the scope tightly and pair it with disciplined change control, because a vague scope is an open invitation to bill the gaps.
And keep your leverage where it belongs: in milestones and holdbacks. Money that is still in your hands is the only part of the contract that reliably commands attention when a program is under stress. Release it against demonstrated results, not against the calendar.
Hire the integrator for what it can build. Keep someone independent for whether it should be built at all.
Governance that does its job
Governance is not a status meeting where everyone reports green. Done right, it is the machinery that surfaces problems while they are still cheap to fix. You want joint steering with real decision-makers in the room, transparent reporting you can actually interrogate, and an escalation path that everyone has agreed to before anyone needs it.
Most of all, you need a standing forum where the uncomfortable conversations are expected rather than avoided. If the only time hard issues come up is when something has already gone wrong, your cadence is decorative. The point of governance is to make candor routine.
Holding the line
Accountability is mostly a matter of timing and nerve. Hold the firm to the scope and the quality bar you agreed, and have the difficult conversations early and on the record. An issue raised in week six is a conversation; the same issue raised at go-live is a crisis with your name on it.
Watch the change orders above everything. Individually they are reasonable. Collectively, "every issue is a change order" is how a fixed budget becomes a moving one without anyone ever deciding it should. When a change request lands, the question is not only "is this fair" but "is this genuinely outside what we agreed, or is it being framed that way." Keeping that distinction honest is half the job.
What to watch for
The warning signs are consistent across programs, and once you have seen them a few times they are hard to miss. Vague status updates that never quite give you the detail you asked for. Visible reluctance to share the underlying numbers or plan. Quiet churn in their team, with experienced people replaced by juniors you weren't told about. Optimism that arrives without evidence. And scope creep that is somehow always framed as your problem to absorb.
None of these is proof of bad faith on its own. But when they cluster, they are telling you the relationship has stopped being managed and started managing you. The earlier you name it, the cheaper the correction.
Managed well, a good SI earns its fee many times over, that is not a grudging admission, it is the whole reason you hired one. Your job, or your independent advisor's, is simply to keep the relationship honest enough that it can.