The default shape of an MSO contract
A typical enterprise managed services contract reads roughly the same across the industry. The vendor commits to a team — a project manager, two or three engineers, a designer, sometimes a strategist — for a fixed number of hours per month. The client commits to a monthly fee. The work that fills the hours is whatever the client team brings to the weekly intake meeting.
On paper this looks reasonable. It is flexible: the client can direct the work at whatever their priorities are this month. It is predictable: the budget does not surprise anyone. It is low-friction: the engagement does not require either side to do hard up-front work to define outcomes.
In practice, this shape is the structural cause of most managed services engagements drifting. The flexibility means there is no shared definition of what the engagement is supposed to accomplish. The predictability means the budget does not flex with value. The low friction up front means the hard conversation about outcomes happens — if it happens at all — when the engagement is already three quarters in and someone is asking why the program has not moved the needle.
What changes when you treat it as a product
Treating managed services as a product means making four specific decisions explicit at engagement start, and then re-deciding them on a defined cadence.
The first is the definition of success. Not "what work will we do" — that question is too tactical. The right question is "what will be true about the digital program twelve months from now that is not true today." On every engagement our team takes, this is a four-to-six bullet answer locked in week one and reviewed quarterly. If we cannot answer this question with the client, we should not be on the engagement.
The second is the measurement. Each success criterion needs an associated metric and a target. Most managed services engagements measure activity — tickets closed, deployments shipped, hours billed. Activity metrics are necessary, but they do not tell you whether the engagement is succeeding. Outcome metrics — page-speed at p75, qualified pipeline contribution from owned channels, time-to-publish for new campaigns — tell you whether the work is moving the right things.
The third is the operating cadence. When does the engagement review against its success criteria? Most engagements only do this annually at contract renewal, which is too late. Our team runs a monthly business review against the success criteria, a quarterly recalibration where success criteria themselves can change, and an annual contract review that is mostly a formality if the prior three months have gone well.
The fourth is the upgrade path. A productized engagement has explicit stages. Stage one might be "stabilize and instrument." Stage two might be "optimize on the metrics we now have visibility on." Stage three might be "build new capability into the operating substrate." Without stages, the engagement plateaus at whatever level the team reached in the first six months and stays there.
Why most engagements do not work this way
The structural reason most managed services engagements run as retainers rather than as products is uncomfortable to name. The retainer model is more profitable for the vendor and less risky for the client buyer, even when both sides know it is producing worse outcomes.
For the vendor, the retainer is more profitable because billed hours are billed hours. The vendor does not have to demonstrate outcome-level success to keep the contract. The contract renews on relationship trust and the fact that switching is expensive.
For the client buyer — usually a CMO or CDO — the retainer is lower-risk because there is no measurable failure. If the engagement does not produce outcomes, the answer is "we needed more from the team" or "priorities shifted" rather than "the engagement failed against its stated success criteria." A productized engagement is harder politically because failure becomes legible.
Both incentives push toward the retainer shape. Both produce worse outcomes than the productized shape would. Our team decided to default to the productized shape anyway, because the relationship that comes out of an engagement that hit its success criteria is durable in a way that retainer-based relationships are not.
The retainer is more profitable for the vendor and lower-risk for the buyer. Both produce worse outcomes than the productized shape.
What productized MSO looks like in practice
On an active engagement that started in 2024, the productized MSO shape looks roughly like this. The success criteria locked in week one were four: improve organic-traffic conversion on the priority product pages, reduce time-to-publish for paid-traffic landing pages from days to hours, instrument and tighten the p75 mobile experience, and stand up a sustained CRO program with documented hypothesis tree.
Each had a measurable target. Each had a quarterly checkpoint. Stage one (months 1-3) was stabilize and instrument — we could not measure progress against the criteria until the measurement substrate was in place. Stage two (months 4-9) was optimize against the criteria, with a monthly business review against the four metrics. Stage three (months 10-12) was building the operating capacity for the client to continue the work without us, with the engagement winding down on a defined path rather than continuing indefinitely.
At month nine of this engagement, the four criteria are tracking ahead of target on three and behind on the fourth (time-to-publish — turns out the bottleneck is approvals, not engineering, and we are working with the client to redesign the approval workflow rather than the publish pipeline). The engagement has a clear shape, the work is intentional, and the next stage is already scoped.
This is not a unique engagement. It is the default shape we use. Other client engagements have different success criteria and different stages, but the operating model is the same. Our managed services offering is built around this shape by design.
How to evaluate your current MSO engagement
If you are buying managed services right now and want to test whether your engagement is a product or a retainer, four questions are diagnostic.
One: can you and your vendor agree on what success looks like twelve months from now, in four bullet points or fewer? If both sides cannot draft this in 20 minutes, the engagement is a retainer.
Two: when did your engagement last review against outcome metrics, not activity metrics? If the most recent review was activity-focused, the engagement is being run as a retainer regardless of what the contract says.
Three: does your engagement have explicit stages with defined transitions? Or is the work this quarter structurally indistinguishable from the work two quarters ago?
Four: is there a defined endpoint? A productized engagement has an explicit success state. A retainer does not. Engagements without endpoints tend to renew indefinitely past the point where they have stopped producing marginal value.
If three or four of those answers point toward "retainer," the engagement is not working at its potential. The right move is not to fire the vendor. The right move is to restructure the engagement against explicit success criteria, with the vendor as a partner in the restructure. If the vendor cannot or will not engage on that conversation, that is itself the answer. If you are running an MSO contract that has lost its shape, our team is happy to walk a restructure conversation with you.