Choosing and managing your SI

A good systems integrator is one of the most valuable partners you will have. The right firm brings people who have configured the platform a dozen times and 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. It was almost always how the relationship was set up. Because here is the thing nobody says plainly at kickoff.

What the SI is paid for

Effort and duration, whether the contract is time and materials or milestone based
Building what is asked for, at the pace the engagement can sustain
Protecting the delivery date the revenue plan is built on
Keeping named experts billable across the portfolio, not on your program
Scope questions resolved as change orders

VERSUS

What you actually need

The smallest configuration that runs your business
Someone saying "you do not need that" and meaning it
A date that moves when the evidence says it should
The people who pitched you, in the seats, by name
Scope questions resolved against what was already agreed

None of that is a character flaw. It is the structure of the deal, and pretending otherwise is how programs drift.

Hire the integrator for what it can build. Keep someone independent for whether it should be built at all. Over a two-year program the gap between what serves the engagement and what serves your outcome never shows up as one bad decision. It shows up as a hundred small ones, each defensible alone.

1The tension you are paying into

An SI gets paid to build. Efficiency, simplicity, and "actually, you do not need that" are not what the model rewards. Most people on the ground are conscientious and want a successful go-live as much as you do. But incentives are quiet and persistent.

So you need someone in the room whose only incentive is your outcome. Sometimes that is you. Often it should be someone with no stake in how many hours the program burns.

2Won on the pitch, lost in delivery

The slides are excellent, the partner is charming, the named experts are impressive. Then the contract signs, those experts rotate to the next sale, and you get a team you have never met. Score the things that predict delivery instead, and weight them.

What to score, and what it actually predicts

Weight

Relevant, recent, comparable experienceYour platform, your scale, your industry, inside three years. Old success on a different product is a reference, not a qualification.

The real delivery team, named in writingAsk to meet the people who will staff the program. If the firm cannot or will not name them, that is the answer.

Willingness to be measuredObjective acceptance criteria and holdbacks, agreed without flinching. Reluctance here is the most honest signal you will get.

References you call and pressNot the curated list at face value. What slipped, what was the change-order experience, would you hire them again knowing what you know now.

Cultural fit under disagreementYou will be in hard rooms with these people for two years. How they handle disagreement during the sale is a preview.

The pattern to name out loud

The A-team bait and switch is so common it is practically a business model. The defense is not suspicion, it is paper: named personnel in the statement of work, with a substitution clause that requires your written consent and equivalent seniority.

3The SOW is where leverage is kept or given away

Most statements of work describe activity: hours, roles, phases. They stop short of committing to a result. That is comfortable for the integrator and expensive for you.

What most SOWs say

Deliverables described as activity: workshops held, documents produced, support provided
"Complete" is a judgment call, so it becomes an argument
Scope written broadly, change control written loosely
Payment tied to the calendar, milestone dates that arrive whether or not the work does
Key personnel unnamed, or named with free substitution

What keeps your leverage

Deliverables described as outcomes, each with an objective definition of done you can verify
Acceptance criteria written before the work starts, not negotiated at handover
Scope written tightly, paired with disciplined change control
Payment tied to demonstrated results, with holdbacks released on evidence
Named personnel, substitution only with written consent

Money still in your hands is the only part of the contract that reliably commands attention when a program is under stress. A vague scope is an open invitation to bill the gaps.

4Governance that does its job

Governance stops working the moment it becomes a status meeting where everyone reports green. Done right it is the machinery that surfaces problems while they are still cheap to fix.

1Joint steering with real decision makersPeople who can say yes in the room and have it stick. Not delegates who take it back to someone.Test: can this room release budget today?

2Reporting you can interrogateUnderlying numbers and the plan, not a summary of them. If you cannot open the file, you are being briefed rather than informed.Test: ask for the source data once and watch.

3An escalation path agreed in advanceWritten down before anyone needs it, because agreeing a route during a crisis is how the crisis wins.Test: name the next level up without looking.

The move

You need a standing forum where uncomfortable conversations are expected rather than avoided. If hard issues only surface once something has gone wrong, your cadence is decorative. The point of governance is to make candor routine.

5Accountability is mostly 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 deciding it should.

How a fixed budget stops being fixed

No single decision does it. Twelve reasonable ones do.

When a change request lands, the question is not only whether it is fair. It is whether the work sits outside what you agreed, or is being framed that way. Keeping that distinction honest is half the job, and it is only possible if the scope was written tightly in the first place.

6The warning signs repeat across programs

Once you have seen them a few times they are hard to miss. None is fatal alone. Three together means you are already behind.

Vague status that never answers the question you askedDo thisAsk for the same detail twice in writing. The second refusal is the data point, not the first.

Reluctance to share the underlying numbers or the plan fileDo thisPut access to source artifacts in the SOW, not in the relationship.

Quiet churn, with experienced people replaced by juniorsDo thisTrack the roster monthly against the named-personnel schedule. Churn is visible long before it is admitted.

Every issue arrives priced as a change orderDo thisKeep a running log of change orders by root cause. A pattern of "requirement was unclear" is a scope-writing problem you can fix once.

Optimism that never survives contact with a dateDo thisScore the process, not the reassurance. A milestone that slips twice will slip a third time.

Your integrator and you do not want exactly the same thing, and the contract is where that gets settled. Set it up so candor is routine, results are verifiable, and money moves on evidence. Then most of the difficult conversations never have to happen.