Selling prevention: the customers who intend never to have the problem

Ask a service business to describe its market and it will usually describe customers in trouble. The machine has stopped, the cool room has failed, the deadline has been missed, the audit found a problem. These customers announce themselves. They call, they need help now, their budget is suddenly available and they are less sensitive to price than they will be once the crisis has passed.

Ask the same business to describe the customers who intend never to be in that position, and the answer is usually vaguer. That vagueness is revealing. Customers trying to avoid a problem do not generate a call, an emergency or an enquiry, so they are hard to see. In many businesses, they are a market nobody has decided not to serve. It simply goes unserved because nothing in the business is set up to notice it.

This article explains the difference between selling to customers who have a problem and selling to customers who want to avoid one, why the second group buys differently, why serving them changes the way a business operates rather than just how it markets itself, how to prove the value of something that did not happen, and how to test whether the demand is real before committing to it.

Two kinds of demand in the same category

Many categories contain two quite different groups of customers:

• Response demand comes from an event that has already happened: a breakdown, a failure, a complaint, a missed obligation. The customer wants it fixed.
• Prevention demand comes from an event the customer wants never to happen: maintenance that prevents a breakdown, checks that make a failure unlikely, monitoring that catches a problem early.

At any moment, far more businesses are trying to keep things working than are dealing with a failure. So the prevention market is often larger than the response market, even though it is harder to see. A business whose sales process begins when a customer calls with a problem will naturally conclude that its market consists of customers with problems.

Why the prevention market is easy to miss

Three common misreadings keep businesses focused on response demand.

Enquiries are mistaken for demand. The number of calls a business receives measures urgency, not need. A customer running well-maintained equipment has a real need and no reason to call.

Prevention is treated as a cheaper, earlier version of repair. It is a different product, bought for different reasons and usually by a different person. Repair is bought by whoever owns the incident, quickly and under pressure. Prevention is bought by whoever carries the consequence over a longer period, such as an owner, an operations manager, a risk or compliance manager or, in larger organisations, a committee. That buyer moves slowly, wants evidence and cannot be rushed by urgency.

The shift is treated as a marketing exercise. Serving prevention demand changes what the business must be able to do, how it is staffed, how it contracts and how it earns money. It is an operating decision, not just a positioning decision.

Ask who carries the consequence

A more useful question than “who has this problem?” is: who carries the consequence of this problem, over what period, and what would they pay to make it unlikely?

This changes the map of the market. In any year, only some customers experience a failure. Far more carry the risk of one continuously. The person carrying that risk is the one who can justify regular spending, because the risk does not disappear between incidents. In many businesses, the service provider has a relationship with whoever reports the incident but no relationship at all with the person who carries the consequence.

You cannot show the failure that did not happen

The central difficulty with prevention is that its benefit is invisible. Repair is sold against a visible loss. Prevention is sold against a loss the customer must be persuaded was avoided. That shapes everything else.

Contracts

A promise expressed as “failures prevented” cannot be verified and invites dispute. A promise expressed as a maintained condition can be: inspections completed on schedule, equipment kept within agreed limits, defects found and fixed within a set period, records kept and available. That is something a serious buyer can take to their own manager, auditor or insurer.

Pricing

Charging per incident means the provider earns more when the customer has more problems. Customers notice that eventually. A regular fee for maintaining an agreed condition aligns the provider’s income with what the customer wants. It also produces steadier revenue, which most service businesses say they want and few design for.

Evidence

Prevention has a particular weakness: success makes it look unnecessary. After two uneventful years, the maintenance budget can look like an easy saving to someone who was not there when it was set. A prevention business must produce continuing evidence, not just of activity but of risk reduced, or it risks being cancelled because it worked. Useful evidence includes problems caught early, defects found and closed, conditions maintained, records that made an audit straightforward and comparisons with the customer’s history before the service began.

The operating model changes before the market does

A response business is built for speed. Its economics depend on how quickly it can get people to a problem, how well it can diagnose, how much surge capacity it has and its ability to charge for urgency. It deliberately keeps some capacity idle, because spare capacity is what makes a fast response possible.

A prevention business is built for consistency. Its economics depend on coverage, scheduling, routine, recording data and producing evidence efficiently. Work is planned, margins per job are usually thinner but steadier, and the scarce resource is discipline rather than heroics.

These differences affect almost everything:

A business can run both, and many should. Response work produces knowledge about how things fail, which makes a prevention offer more credible. But running both is a deliberate choice with real costs: different scheduling, different skills, different contracts and sometimes different people. It should be chosen and costed, not drifted into.

Test the demand before committing

A common mistake is moving from one memorable conversation to a major commitment. A significant customer says something striking to the owner, and within a few months money and people have moved. The importance of the person who heard it is not evidence.

A simple evidence ladder helps. Each level justifies a limited commitment, and nothing more:

Two habits make the ladder work. Write down the hypothesis before gathering evidence, so the pattern is tested rather than assembled from convenient examples. And write down what would show the hypothesis is wrong. A business that cannot say what would change its mind is building a case, not researching a market.

Prevention demand also tends to become buyable only when a trigger arrives: a change in regulations, an incident at a similar business, a customer’s own contract requirement, a new owner or manager. The timing a new initiative article looks at how to read that kind of readiness.

Start by asking a different question

The simplest first step costs almost nothing. In the conversations the business already has with customers, add one question: what condition is this customer trying to maintain, and who in their business is accountable if it slips? The answer identifies the person who carries the consequence, often someone the business has never met.

Over time, those answers show whether a prevention market exists, who the buyers are and what they care about. They also show which existing customers might value a regular arrangement rather than waiting for the next call.

A worked example

This is an illustration. A commercial refrigeration business with eight technicians earns about $1.2 million a year, roughly 80% of it from breakdown call-outs to restaurants, cafés and small food retailers. Call-out work is profitable but uneven, with intense weeks in summer and quiet periods in winter. The owner notices that when a cool room fails, the customer’s main worry is not the repair bill. It is the stock lost, the disruption and the questions that follow about food safety.

The owner writes down a hypothesis: some food businesses would pay a regular fee to keep their refrigeration within safe temperature limits, with records to show it, rather than wait for a failure. The owner also writes down what would disprove it: fewer than ten customers willing to sign a 12-month agreement at a price that covers the cost of delivery.

Over three months, the owner climbs the evidence ladder:

• Observation: two restaurant owners mention, unprompted, that they would rather not have another failure in summer.
• Pattern: the technicians ask the new question on every job for a month. Many customers say they keep temperature records by hand and worry about gaps. The person responsible is usually the owner or head chef, not the person who calls about breakdowns.
• Published material: food safety rules require food businesses to keep potentially hazardous food at safe temperatures, and a small restaurant group’s supplier requirements, shared by a customer, ask for documented maintenance.
• Commitment: the owner offers a 12-month pilot to existing customers: four scheduled service visits a year, remote temperature monitoring with alerts, defects fixed within ten working days and a monthly one-page report. Twelve sites sign at $2,400 a year each.

The owner estimates the cost of delivering the service per site:

That leaves $910 per site, or about 38% of the fee, before overheads. The margin per job is lower than on emergency call-outs, but the work can be scheduled into quiet periods, and the twelve sites together add $28,800 of steady annual revenue.

During the year, the monitoring catches three cool rooms drifting above safe temperature overnight, and each is fixed before stock is lost. The monthly reports record these events, the defects closed and the temperature records kept. At renewal, eleven of the twelve sites continue, and the reports, not the absence of failures, are what the owners point to. Only then does the owner consider extending the offer to new customers, hiring a technician dedicated to scheduled work and changing how the business’s capacity is planned.

How this applies to a small Australian business

Many small service businesses, including trades, maintenance, IT support, compliance and professional services, earn most of their money from response work. Practical steps:

• Look for the prevention market in your category: the customers trying to keep things working.
• Ask who carries the consequence, and whether you have a relationship with that person.
• Add one question to existing customer conversations about the condition they want to maintain.
• Define a maintained condition you could promise and verify.
• Price for the condition, not per incident.
• Produce evidence of risk reduced, not just activity.
• Cost the operating changes: scheduling, skills, records and contracts.
• Use the evidence ladder before committing significant money or people.
• Check the rules that apply to your customers, such as food safety, workplace safety or building requirements, and describe them accurately.

The selling performance, not products article covers a related shift, from selling equipment to selling the results it delivers.

Signals worth watching

• Most revenue coming from customers experiencing the problem you could help them prevent.
• Customers asking whether you offer regular checks or maintenance.
• Regulations, tender specifications or customer contracts moving from fixing problems towards demonstrating control.
• Competitors offering service agreements rather than call-outs.
• A fall in incident volume in your industry, which affects response businesses directly.
• Prevention customers renewing, or not, after uneventful years.

Common mistakes

• Treating enquiry volume as total demand.
• Selling prevention through the same people and messages as repair.
• Promising “failures prevented” instead of a verifiable condition.
• Pricing prevention per incident.
• Failing to produce evidence, and then being cancelled for succeeding.
• Moving money and people on the strength of one conversation.
• Running response and prevention without costing the differences.

Frequently asked questions

Will selling prevention reduce our repair revenue? It may, for the customers who take it up. That is the point for them. The question is whether steady prevention revenue, plus repair work from customers who do not take it up, gives a better business overall. Many businesses find it does, especially because scheduled work fills quiet periods.

How do we price a prevention service? Start from the full cost of delivering the maintained condition, including visits, monitoring, reporting and fixing defects, then consider what the condition is worth to the customer. Avoid pricing so low that the service depends on selling repairs to the same customer.

What if customers do not see the value after a quiet year? That is why evidence matters. Report problems caught early, defects closed and conditions maintained throughout the year, not just at renewal. Compare with the customer’s history before the service began where you can.

Do we need different staff? Often partly. Scheduled work rewards consistency and good record-keeping, while response work rewards fast diagnosis under pressure. Some people enjoy both. Plan the roster so prevention visits are not constantly cancelled to cover emergencies.

Is this only for maintenance businesses? No. The same pattern appears in IT support, cybersecurity, bookkeeping and compliance, safety services, health services for businesses and many professional services.

Questions to ask

• Who carries the consequence of the problem we solve, and do we know them?
• What share of our revenue depends on customers experiencing what we could help them prevent?
• What maintained condition could we promise and prove?
• What would we show a customer after two uneventful years?
• Where on the evidence ladder is our current idea?
• Are we running response and prevention in one structure, and have we costed it?

Bringing it together

Customers in trouble are easy to see. Customers determined to stay out of trouble are often a larger market, but they buy differently, from a different person, on evidence and over a longer horizon. Serving them means promising a verifiable condition rather than a fixed incident, pricing for that condition, producing continuing evidence of risk reduced and running a scheduled operation rather than only a responsive one. Test the demand step by step before committing. The real choice is whether the business is willing to be measured on a condition it maintains rather than on an event it resolves.

---

Source: KEVOS notes. Examples and figures in this article are illustrations. Requirements such as food safety rules vary by jurisdiction and business type; check the current rules that apply.