You’ve done the hard part. You’ve worked out your costs, factored in your labour, and landed on a number that actually makes the job worth doing. Then you quote it — and something goes wrong. Not a negotiation, not a question. Just a slight flinch, a pause, and the job goes somewhere else.
It doesn’t always mean the number was too high. Sometimes it means the number landed badly.
That distinction matters more than most field service businesses realise. There’s a reasonable amount written about how to *calculate* what to charge for a maintenance contract or service agreement: what to include, how to cover your costs, where your margin sits. That ground is important and we’ve covered it in detail here. But there’s a separate question that gets almost no attention: once you know what you need to charge, how do you actually present it so the customer hears what you intend?
Rory Sutherland is Vice Chairman of Ogilvy and one of the more unusual thinkers working at the edge of behavioural economics and business. His TED talk on perspective has been watched millions of times, and his book Alchemy makes a long, persuasive case that how you frame something changes what people think it’s worth. His central point, put plainly: price is not a number to a customer. It’s a feeling. The same amount of money lands completely differently depending on what you compare it to, how you present it, and what the customer is thinking about when they hear it.
For a field service business trying to sell a service agreement or move a customer from reactive work to a contract, this is practical information.
Jump to a section:
- Why most service agreements fail before the conversation starts
- The comparison problem: what your price is measured against
- How the same number can feel cheap or expensive
- The per-unit shift: what a legal firm figured out that most trades haven’t
- What the KFC example tells you about mid-range pricing
- Three things worth changing when you quote
- Where Fieldmotion fits in
Why most service agreements fail before the conversation starts
The typical approach to selling a service agreement goes like this. You’ve done the job, or you’re on site for a reactive visit. You mention it while you’re packing up. “We do annual service plans if that’s of interest.” The customer says they’ll think about it. They don’t.
There are a few things working against you here. One is timing: you’re asking for a recurring financial commitment when the customer has just spent money they didn’t expect to spend, and they’re still processing that. Another is vagueness: “service plan” means almost nothing to someone who hasn’t had one before.
But the third problem is the subtler one. You haven’t given them anything to compare the price to. A number without a reference point is just a number. And when people have no frame of reference, they default to the one they already have, which in field service is almost always: “what did I pay last time something broke?”
That frame is your biggest competitor, and it tends to make your contract price look expensive even when it isn’t.
The comparison problem: what your price is measured against
Sutherland makes this point clearly in several talks: nothing has a fixed price until you compare it to something. The same object or service can seem like a bargain or an outrage depending entirely on what’s next to it.
His example from the luxury car industry is worth sitting with. Lamborghini and Rolls-Royce stopped selling their cars at motor shows. The reason: at a car show, a £250,000 vehicle is visibly the most expensive thing in the room, and that framing makes it feel extravagant and hard to justify. When they moved to selling at yacht shows, where customers were already looking at eight-million-pound boats and Learjets, the same car became an impulse buy by comparison. Nothing about the car changed. The context changed.
This isn’t a trick. It’s just accurate. When the same £250,000 sits next to an £8 million yacht, it occupies a different psychological position than when it sits next to a £45,000 saloon. What you’re aware of when you hear a price changes how the price feels.
For a field service business, this has a direct application. If a customer is weighing up a £600 annual service agreement against nothing — no competing quote, no reference point, just their general sense of whether £600 sounds like a lot — they are almost certainly comparing it to the last unexpected bill they paid. Which was probably less than £600 and felt unpleasant. So your contract price registers as expensive before you’ve said another word.
But if they’re comparing a £600 contract to the cost of two callouts a year, the maths looks different. You’re not selling against a vague number anymore. You’re selling against a specific, real cost they’ve already paid.
Most businesses let the customer do this comparison themselves, if they do it at all. Doing it for them, explicitly, in the conversation, changes what the number feels like. Not by changing the number, but by changing what it’s sitting next to.
Fieldmotion Brochure
See how Fieldmotion helps field service teams manage jobs, schedule staff, create invoices, and communicate with customers — all from one easy-to-use system.
How the same number can feel cheap or expensive
Sutherland describes an experiment he ran for a direct response campaign where adding a deadline — a time limit on an offer — pushed the response rate up sharply. Economically, this makes no sense. Either the product enhances someone’s life at that price or it doesn’t. The closing date shouldn’t change that calculation. But it does, reliably, because people aren’t calculating. They’re feeling.
The same dynamic operates with price presentation. Three payments of £150 register very differently to one payment of £450, even though the total is identical. The research behind services like Klarna is largely built on this insight: the same sum of money, split and framed differently, feels like less. Not because anything has changed financially, but because the psychological weight of each individual number is lighter.
For a service agreement quoted annually, this matters. If a customer is thinking about writing a single cheque for £720, that number has real weight to it. It sits in the “big purchase” category, which triggers the same scrutiny as buying a new appliance. Whereas £60 a month is a utility. Most people pay that sort of amount for several things already without giving it much thought.
This isn’t about which model you choose. Monthly billing has its own complications, as we’ve discussed in the article on avoiding late payments, and upfront annual payment is often the better business decision. But even if you invoice annually, how you describe the value can reference the daily or monthly equivalent: “that works out to around £60 a month, which includes both scheduled visits plus priority callout.” That single sentence changes what the total feels like without reducing it.
The per-unit shift: what a legal firm figured out that most trades haven’t
There’s a law firm called Backhouse Jones, specialists in road transport regulation, that built their entire business model around a subscription charged per vehicle per day. Their BACKup scheme gives transport operators 24/7 access to specialist legal advice for a fixed monthly fee, priced on a per-vehicle basis so that a small operator with three lorries paid far less than a large fleet, while the daily-rate framing made the cost feel manageable to anyone. The pricing structure won industry awards and is widely credited with making specialist legal services accessible to businesses that would have assumed they couldn’t afford it.
The comparison Sutherland draws is to legal fees for transport operators more generally. Before this model, the question was: “can we afford a solicitor?” Most small operators answered no. The new question became: “can we afford 30 pence per vehicle per day to never be caught out?” Almost every operator could answer yes.
The number didn’t change dramatically. The unit of measurement did.
In field service, the same logic applies. A £480 annual contract sounds like a commitment. “Less than £10 a week, covering both your services and priority response” describes the same thing in a way that sits in a different mental category. Not a capital outlay. A running cost. Something you already pay for other things without thinking about it.
It’s not manipulation, it’s precision. You’re helping the customer understand what the purchase actually costs them in the context of how they’ll experience it: not as a lump sum once a year, but as ongoing coverage.
What the KFC example tells you about mid-range pricing
One of the more counterintuitive stories Sutherland tells is about a fast food product that wasn’t selling. The natural response was to cut the price. Someone suggested raising it instead. They raised it, and demand went up.
His explanation: the product was positioned awkwardly between two reasons someone goes to a fast food restaurant. People go either for a bargain (cheap, quick, fills the gap) or for a treat (it’s someone’s birthday, you’re splashing out a bit). A price in the middle of these two motivations belonged to neither. It wasn’t cheap enough to feel like a win on value, and it wasn’t expensive enough to signal that this was something worth having. Raising the price shifted it from the awkward middle into “treat” territory, and suddenly people had a reason to buy it.
For field service businesses, this has a specific and uncomfortable application. The instinct when selling a contract is usually to make it sound affordable, to come in under what the customer expects, to avoid price resistance. This can backfire. A contract that’s priced too low raises a question the customer doesn’t say out loud: why is this so cheap? What aren’t they covering? If the engineer charges £500 per callout but the annual agreement is £200, something doesn’t add up, and the customer feels it even if they can’t articulate it.
Price signals quality in services more than in products, because with products you can at least inspect what you’re getting. A service is a promise about the future, and a low price on a promise makes the promise feel less reliable.
Setting prices too low can inadvertently communicate to customers that your offering is worth less than it truly is. Customers may associate a lower price with lower quality, even if your service outperforms competitors. The research on this is consistent enough that McKinsey found between 80–90% of mispriced products and services are priced too low rather than too high. The instinct to underprice to avoid rejection often causes the rejection it’s trying to prevent.
If you’re calculating what your agreements should cost and arriving at a number that feels like a tough sell, it’s worth asking whether the number is actually the problem, or whether the problem is a price that looks too low to inspire confidence.
Three things worth changing when you quote
None of what’s above requires you to change your pricing structure. It’s about presentation, the context you build around the number before the customer has to respond to it.
Start with what the problem costs, not what your solution costs
Before you quote an agreement price, make sure the customer has a concrete sense of what unmanaged maintenance looks like financially. A boiler failure mid-winter isn’t just an inconvenience — emergency callouts average around £150 or more outside normal hours, plus parts, plus the disruption. Commercial customers may have operational downtime on top of that. Once that number is established in the conversation, your contract price is measured against it rather than against nothing.
Name what’s included, not just the price
“£650 per year” invites the customer to decide if that sounds like a lot. “£650 per year covers two scheduled visits, all labour on those visits, priority booking for reactive callouts, and your compliance documentation” gives them something to evaluate. Same number, different landing. What you’ve listed should represent genuine, tangible value. Not padding. If it doesn’t, that’s a scope problem rather than a pricing presentation problem.
Be specific about the per-period cost
You don’t need to change how you invoice. But you can describe the annual figure in terms that connect to how the customer experiences running costs. “That’s £54 a month for full planned maintenance coverage” isn’t reducing the price. It’s placing it alongside the other things they pay monthly, where it competes on different terms.
The point is not to make the price feel smaller by sleight of hand. It’s to make sure the customer has what they need to make a genuine comparison, between your contract and the actual cost of the alternative, rather than comparing your price to a vague feeling about whether it sounds like a lot.
This matters particularly for businesses making the transition from reactive work to planned maintenance contracts. The service agreements piece covers the commercial and structural case for making that shift. The conversation itself, why presenting the same contract well closes more deals than presenting it badly at the same price, is what the sections above address.
Book Your Free Demo
Discover how our job management software can streamline your operations, reduce paperwork, and keep your field teams on track.
Where Fieldmotion fits in
Getting the presentation right is harder if your back office is slow. If you’re putting together agreement quotes manually, or if the details of what’s been done for a customer live in an engineer’s head rather than in a system, it’s difficult to build the kind of precise, specific proposals that land well.
Fieldmotion keeps a clear record of what each customer has had done, what their assets are, when they were last serviced, and what’s outstanding. That means when you’re quoting a service agreement for a customer you’ve already worked with, you’re not working from memory. You’re working from data, and you can build a proposal that references their specific situation.
The same system handles the delivery side: scheduled visits in the diary, automatic reminders, job sheets generated and ready to sign off on site, invoices sent without waiting for paperwork to come back to the office. The operational gap between quoting an agreement and delivering it reliably is where a lot of contracts quietly fail. Software that connects both ends helps.
Related reading:
