Opinion · Contracts
Stop pricing the
input.
A hotel does not want a block of attendant-hours. It wants a curb that stays calm, guests who get clear answers, vehicles returned responsibly, and a month that closes cleanly. Yet the contract often sells the hours and leaves the outcomes implied.
Our position
The unit on the invoice quietly decides what the operation optimizes.
When every additional hour is revenue to one side and cost to the other, the relationship begins with opposing incentives. The operator is paid for an input. The property judges a result. Both can behave rationally and still spend the month arguing past each other.
Selling outcomes does not mean promising what nobody can control. It means naming the service the property actually bought, measuring the parts the operator can influence, and designing a commercial model that rewards improvement instead of volume alone.
The mismatch
Hours are easy to count. They are not the whole product.
Two parties, two scoreboards
The standard arrangement asks the operator and the property to look at the same shift through different numbers.
The hour contract sees
Inputs- How many people were scheduled
- How long they remained on site
- Whether the invoice matches the roster
The property experiences
Outcomes- Whether the curb stayed under control
- Whether service matched demand
- Whether issues were resolved cleanly
→An input contract can produce good service. It simply does not make good service the explicit object being purchased.
Outcome pricing begins with controllability
A fair agreement does not turn weather, traffic, and every guest decision into operator liability. It separates what can be managed from what can only be observed.
Own
Coverage discipline
Was the approved plan staffed, adjusted, and communicated as demand changed?
Own
Process quality
Were keys, tickets, requests, payments, and closing records handled consistently?
Share
Demand response
Did the operator and property use the same forecast and escalation path when the curb changed?
Observe
Outside conditions
Weather, street congestion, and guest timing belong in context, not in a simplistic penalty.
→The contract gets stronger when it admits where control ends.
The agreement should create a learning loop
An outcome is useful only when the parties can review it together and change the next plan.
→Better contracting is not a score at the end. It is a mechanism for making the next shift better.
The operating layer
You cannot sell an outcome you cannot see.
Outcome-based relationships need a shared operational record: the plan, the actual demand, the response, and the exceptions. That record lets an operator explain performance without reducing the whole service to a timesheet.
The takeaway: keep hours where they are useful, but stop pretending they are the product. The product is the operation those hours were supposed to produce.
