Every proposal for operations help prices the same thing three different ways, and the three ways are not three prices for one product. They are three different products, because each one commits the supplier to something different. A buyer who compares them on the monthly figure is comparing a commitment to show up with a commitment to a result, and the cheaper one is usually the one that leaves the risk where it started.
This is the guide to the three, written for a company of 5 to 1,000 users whose business runs on a CRM, a set of books and the systems between them.
The hourly model is the oldest and the most honest about what it is. The supplier sells time. A ticket comes in, someone works on it, the hours are billed. Block hours, retainers of hours, time and materials: all the same product with different payment terms.
What the supplier is committed to is presence. Not the outcome, not the fix lasting, not the problem never recurring. If the integration between the CRM and the books breaks every month, the hourly supplier fixes it every month and bills every month, and nothing in the contract makes the second month's fix different from the first.
That is not a criticism of hourly suppliers. It is the product. The buyer carries the risk that the problem persists, and pays by the hour for it to persist. We set this out for consulting in how Zoho consulting services are priced: each model pays the consultant to optimise for something, and hourly pays them to optimise for hours.
Hours are the right product for genuinely unpredictable, one-off work. They are the wrong product for keeping a business running, because keeping a business running is the most predictable work there is.
The second model is staffing. The supplier provides a person, full time or fractional, with a title and a seat. Managed IT services, at the typical tier, are a variation: a help desk and a set of people behind it, priced per seat or per user, covering a defined list of things.
What the supplier is committed to is a person being there, with a skill set, for the hours in the contract. Whether the business's systems work is still the buyer's problem; the person is a resource for working on it. If the person is good, this is better than hours, because a person who is there every day learns the estate. If the person leaves, the buyer starts again, and the contract says nothing about that.
The scope line matters here more than the price line. Managed IT, as usually sold, covers devices, logins, patches and the network, and ends at the login screen. The business runs on what is behind the login screen: the CRM, the books, the warehouse system, the connections between them, and the agents that are starting to act across them. We drew that line in managed technical operations versus managed IT. A headcount contract that stops at the login screen is a contract for the part of the estate that does not make money.
The third model is the one the enterprise firms have moved to and the mid-market has mostly not been offered. The supplier commits to a condition being true: the quote goes out within a day; the three inventory counts agree at month end; the integration between the CRM and the books has not dropped a record this quarter; the agent's actions were right. The price is a subscription, tiered by usage, and the supplier is paid the same whether the condition took ten hours or a hundred to keep.
What the supplier is committed to is the result. That changes every incentive in the relationship. A recurring break is now the supplier's cost, so it gets fixed properly. A person leaving the supplier is the supplier's problem, because the condition still has to be kept. A usage tier that the buyer outgrows is a conversation, not a surprise invoice.
It also changes what the buyer has to do, which is the part most buyers skip. An outcome has to be defined as a number, measured before the contract starts, and read every month. A supplier who offers an outcome contract without insisting on the baseline is selling hours with a nicer name.
The scope also has to extend to where the business actually runs. An outcome kept at the login screen is worth little. An outcome kept across the systems and the connections between them, with one party accountable for the whole, is what the model is for. That is the same accountability a company buys from a fractional CTO at the leadership level, and we wrote about what that fee buys in what a fractional CTO costs: not hours, a condition kept.
There is a fourth thing on offer that looks like the third and is not: the fixed-scope project. A supplier prices a defined piece of work at a fixed fee and delivers it. That is a real commitment, and a fixed fee is better than hours for a build. But a project ends. The day it ends, the condition it created starts to decay, the connections drift, the rules go stale, and the buyer is back to choosing between hours and headcount to keep it. Operations help is not a project. It is the keeping, and the keeping is what has to be priced.
So when a proposal for ongoing operations arrives as a project with a renewal, read the renewal. If the renewal is hours, the outcome was never bought. If it is a subscription against a measured condition, it was.
The pricing page will not tell you. Ask three questions instead.
What happens to the price if the same problem happens twice? If it costs you twice, you are buying hours. If it costs you the same, you are buying an outcome.
What happens if the person leaves? If you start again, you are buying headcount. If you notice nothing, the supplier has committed to the condition, not the person.
What number will you show me each month, and what did it read before we started? If there is no number, there is no outcome, whatever the proposal calls it.
Agents raise the stakes on this choice. An agent acting across the CRM, the books and the warehouse is a condition that has to be kept true every day: its connections up, its permissions right, its trail read, its actions correct. Buying hours against that is buying a fix after each wrong action. Buying headcount is buying a person to watch it, who may leave. Buying the outcome is buying the agent's actions being right, with one party accountable when they are not.
That is the model we sell, and it is why our proposals carry guaranteed estimates and a usage tier rather than a rate card: the estimate is ours to keep, and the tier moves when your volume does. Discovery is no-risk, which is the same commitment at the front of the relationship. We define the conditions, take the baseline, 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.
