The largest managed-services and consulting firms have spent the past year rewriting how they charge. Where the contract used to be a number of people for a number of months, it is increasingly a result: a process kept running at a cost, a backlog held below a level, a function delivered for a fee tied to what it produces. The reason is not generosity. Agents changed what it costs those firms to deliver an outcome, and a firm whose costs fell while its hourly rates did not would have been undercut by the first competitor to pass the saving on.
A 200-person company will never be those firms' customer. The question is what the same shift means at that size, and the short answer is that it already happened to your suppliers' costs too. Whether it has happened to your bill is a different matter.
Managed services were priced on labour because labour was the cost. A help desk was people answering tickets; an operations contract was people watching systems; an outsourced finance function was people closing books. Price per head, per seat or per hour, with a margin, and the buyer's bill rose with the buyer's volume because the supplier's headcount did.
Agents broke the link between volume and headcount. A support agent handles the first reply on every ticket; a reconciliation agent handles the counts that agree and leaves the people the ones that do not; an operations agent watches the connections and raises the exception. The supplier delivers the same outcome with a fraction of the hours. If the supplier keeps charging hours, its margin balloons until a competitor prices on the outcome and takes the account. So the large firms moved first, because their customers were large enough to notice and to switch.
That is the whole mechanism. It is not about the enterprise. It is about anywhere a supplier's labour per outcome fell.
The mid-market managed-services supplier, the firm that runs the help desk or minds the Zoho estate or keeps the integrations up for a 200-person company, has the same agents available and the same drop in labour per outcome. What it does not have, yet, is a customer asking for the outcome price.
So the typical mid-market bill still reads per user, per device, per hour. The pricing guides for managed services, which is what ranks for the term, describe tiers of coverage per seat as if the cost underneath them had not moved. The saving from the agents is real and it is being kept, by default, by the supplier, because the buyer is still comparing seat prices. We described what the seat and hour models commit a supplier to in managed technical operations versus managed IT: the scope stops at the login screen, and the price stops at the headcount.
That is the practical meaning of the shift for a 200-person company. The cheaper, better-shaped deal exists. It has to be asked for.
The enterprise version is a transformation contract with a fee tied to a business metric and a long negotiation. The 200-person version is simpler, and simpler is better.
A condition, defined as a number: tickets first-replied within an hour; the three inventory counts agreeing at month end; no dropped record between the CRM and the books this quarter; the agent's actions reviewed and found right. A baseline, measured before the contract starts. A subscription priced by usage tier, so the bill moves with volume rather than with the supplier's headcount. One party accountable for the whole condition, including the operations work of keeping the agents, the connections and the permissions right. And a report every month that reads the number.
That is a page, not a negotiation. It is the shape we described from the buyer's side in the piece on hours, headcount and outcomes, and it is the shape the agents make affordable at this size, because the labour inside each outcome is now small enough to price into a tier.
Take the help desk for a 200-person company: forty tickets a day, two people on it. Under the seat model the supplier bills per user covered, and the two people are the supplier's cost. Put a first-reply agent in and one person handles the same forty tickets with the agent drafting replies and resolving the routine third. The supplier's cost halved. The seat price did not move, because the bill was never attached to the cost.
Under the outcome shape, the contract reads: first reply within an hour, first-contact resolution above a stated rate, measured monthly against the baseline taken before the agent went in, at a tier for forty tickets a day. The supplier's cost halved and the price was set on the outcome, so the saving is shared by construction rather than by negotiation. Volume doubles, the tier moves, and the supplier adds capacity through the agent before it adds a person. That is the deal the enterprise firms are signing. There is nothing in it that depends on the buyer's size.
Three things, and two of them are work.
The buyer has to define the outcome as a number and take the baseline. Suppliers on hours never asked for this because they did not need it; suppliers on outcomes cannot work without it. A buyer who cannot say what number the contract should move is not ready for the outcome shape, and should fix that before shopping.
The buyer has to let the supplier run the condition, including the agents, rather than buying agents separately and asking the supplier to mind them. A condition kept by two parties is a condition nobody keeps.
And the buyer gets to stop paying for the labour that is not there any more. That is the part worth doing the first two for. A 200-person company paying hourly rates for work that an agent now does in minutes is paying the supplier's old cost structure, and the only reason it persists is that nobody at the table has said so.
Outcome pricing is not cheaper for every job. Work that is genuinely unpredictable, a migration, a one-off integration, a crisis, is still priced best as a fixed-scope project with a guaranteed estimate, because there is no steady condition to keep. And outcome pricing without a baseline, or with the operations work left outside the price, is the old model with a new name. We said as much from the supplier's side in what IT managed services are long before agents made the point sharper.
But for the ongoing keeping of a business's systems and the agents now acting across them, which is most of what a 200-person company buys from a managed-services supplier, the economics have moved, and the price should move with them.
We price it this way for companies of 5 to 1,000 users: a condition kept, a usage tier, one accountable party, guaranteed estimates for the setup. Discovery is no-risk: we define the condition and take the baseline with you, and you pay only if you go ahead.
In a no-risk discovery we look at your CRM, finance and operations systems and who owns each part, and show what a connected system would do differently. You pay only if you proceed. Or see how we approach it.
More on the same problem:
"Something isn't working." "We're outgrowing our tools." "We're afraid to make the wrong move." No-Risk Discovery is a short, practical conversation that gets you clarity before you commit to anything big. We'll tell you if we're a fit. If we're not, we'll tell you that too.
Say who you are and ask. A person replies within one business day.
