Why your PMO partner should not be selling you the platform

Where the conflict actually bites

A transformation programme generates a steady stream of moments where the client's interest and the supplier's interest quietly diverge.

The scope conversation. Someone has to say that a third of the requirements backlog is gold plating. If the party chairing that conversation bills by the configured module, the backlog survives.

The vendor performance conversation. Someone has to put the system integrator's slippage on the steering committee agenda, in plain language, with a recovery demand attached. If the party writing that paper has a partnership agreement with the SI, the language softens. Slippage becomes rebaselining. A missed milestone becomes a timeline refinement.

The platform conversation. Someone has to be able to say the tool is wrong. Or that the licence count is inflated. Or that the module being pitched in the upsell meeting solves a problem you do not have. If the party advising you earns margin on that licence, the advice arrives pre-shaped.

The go or no-go conversation. The most consequential decision in the programme. Someone has to walk the executive through the evidence and say not yet. Every supplier in the room earns more if the answer is yes.

The budget conversation. Halfway through, the contingency is gone and the change requests are stacking up. Someone has to tell the board which of those change requests are real and which are the supply side recovering its own underquote. If the party giving that advice wrote the original estimate, or partners with the firm that did, the board hears a defence rather than an assessment.

None of this requires bad faith. It requires nothing more than ordinary commercial gravity. People do not argue hard against their own revenue, and organisations argue against it even less.

Four parties, one empty chair

Every major implementation has at least three parties at the table. The vendor brings product knowledge. The system integrator brings delivery methodology. The client brings the money, the outcome, and a business that has to keep running while everything changes.

The vendor and the integrator have done this dozens of times. Most client organisations do it once a decade.

That experience gap is where programmes drift. The vendor and the SI are not villains. They are simply better at this than you are, on their tenth programme this year against your first this decade. Every assumption they bring defaults in their own favour. Commercial assumptions. Scope assumptions. Risk assumptions. Who carries the cost when something slips.

The answer is a fourth party. A senior practitioner who sits on the client side of the table, inside the steering room, with no stake in any of the suppliers. The owner's representative.

Their job has three parts. Hold the vendor and the integrator to the standard the contract promised. Protect the business case. Give the sponsor an unfiltered view of where the programme actually stands.

The fourth chair only works if it is genuinely independent. Put a platform reseller or an implementation firm in that chair and you have not added a fourth party. You have added a third supplier and lost the only seat that was yours.

The test

Independence is easy to claim and easy to verify. Three questions do it.

First, what do you earn from the vendor or the integrator on this programme? The only acceptable answer is nothing. No referral fees, no margin, no certification incentives, no co-selling arrangement with the parties being held to account.

Second, what happens to your revenue if we descope, switch platforms, or replace the SI? A conflicted partner loses money on every one of those calls. An independent one does not, which is precisely what allows them to recommend any of them.

Third, will you put that in writing? Disclosure separates the firms with nothing to hide from the firms with a careful answer.

What good looks like on paper

Independence should not live in a slide deck. It should live in the engagement contract, where it can be tested.

Four clauses do most of the work.

A disclosure schedule. Every commercial relationship the governance partner holds with any party connected to the programme, listed by name, updated as the supplier landscape changes. An empty schedule is a fine answer. A missing schedule is not.

A supplier revenue warranty. The partner warrants that it receives no fees, margin, rebates or incentives from the vendor or the integrator in connection with the programme. If that warranty cannot be given, you have learned what you needed to learn before signing rather than after.

Direction-neutral fees. The partner's remuneration must not move when the programme changes shape. Time and materials at a disclosed rate achieves this. So does a fixed advisory fee. What never achieves it is any structure where descoping, replatforming or replacing a supplier costs the adviser money.

A direct-licence option on any tooling. Where the partner proposes its own delivery tooling, the contract should record the client's right to licence that tooling directly from the provider. The option will rarely be exercised. Its presence is the proof.

None of this is exotic drafting. It is the same hygiene boards already apply to auditors and probity advisers, transplanted into the steering room. A governance partner who resists it is answering your second question the slow way.

What disclosure looks like, including ours

We hold a partnership ourselves, so this is the right place to be specific about it.

Rydel Group is a FocusHQ Gold Partner. FocusHQ is a project portfolio management platform. It is the tooling we use to run client-side governance. One source of truth for the plan, risks, decisions and dependencies. Steering reporting generated from the working record, not assembled by hand the night before the meeting.

Note what FocusHQ is not. It is not an ERP, not an HRIS, not a payroll engine, and not an implementation service. It is never the system being implemented and never the party being held to account. It sits on the client's side of the table because that is where we sit.

When we propose it, three things happen. The relationship is disclosed in the proposal. The licence is scoped to the project team, not the workforce. And the client is free to licence directly from FocusHQ instead of through us. Our only commercial relationship is with the client. That line survives the disclosure because the disclosure is the point. A governance partner who hides a commercial relationship has told you something. One who documents it and offers you the direct path has told you something too.

That is the standard we think every client should demand. Not no partnerships ever, which is unrealistic in a market where tooling matters. No undisclosed partnerships, no stake in the systems being implemented, and no revenue tied to the suppliers under review.

Why the market is built this way

It is worth understanding why conflicted governance is the norm rather than the exception, because the reason is economic, not ethical.

For a large consultancy, governance advisory is a small revenue line. Implementation is the profit pool. The PMO engagement that bills a few hundred thousand sits beside a delivery engagement that bills tens of millions. So the governance seat becomes a beachhead. Win the trusted adviser position, then convert it into the build.

The big firms are open about this in their own strategy documents. Land and expand. The advisory engagement is priced to win because its real value is the pipeline it opens.

Once you see the model, the behaviour makes sense. The PMO partner who never quite forces the SI's slippage to a crisis. The health check that recommends more of the assessing firm's own services. The platform recommendation that happens to match the reseller agreement. These are not failures of the model. They are the model.

The fix is not better people inside that structure. The fix is a seat that sits outside it.

What it costs you to get this wrong

A conflicted governance partner does not fail loudly. The programme does not collapse in month two. It drifts.

Scope grows a little, because nobody with authority was paid to argue against it. The SI's slippage compounds quietly, because the language describing it was softened paper by paper. The licence bill arrives larger than the business case assumed, because the advice on sizing came from the seller. Go-live lands three months late and the post-implementation review politely calls it a learning.

Each of those costs more than independent governance would have. Most of them cost ten times more. The owner's representative is not an overhead on the programme. It is insurance on every other dollar in it, priced at a fraction of the drift it prevents.

Boards understand this instinctively in other domains. Nobody lets the auditor sell the accounting system. Nobody lets the building certifier own the construction firm. Transformation programmes deserve the same hygiene, and the budget holders who fund them are entitled to insist on it.

The question that remains

Your vendor works for your vendor. Your integrator works for your integrator. Both will tell you, correctly, that your success matters to them. It does. Right up until the moment it conflicts with their margin.

So the question stands. Who, in your steering room, earns nothing from the suppliers and answers only to you?

If there is no good answer, that is the gap. Not a tooling gap or a methodology gap. An accountability gap, sitting in the most expensive room in your organisation.