An enterprise that sells only to affliction has capped its growth at the rate at which its customers fail, and has quietly made their failure its revenue plan.
Ask an executive team to describe its market and you will usually be given a description of affliction. These are the customers whose equipment has stopped, whose supply has been interrupted, whose programme is late. They announce themselves, arriving with urgency, a released budget, and a tolerance for price they will not show again once the crisis has passed.
Now ask the same team to describe the customers who intend never to be in that position. The answer is generally vaguer, and the vagueness is the finding. That second group is not smaller; it is harder to see, because it generates no incident, no escalation and no inbound enquiry. In most enterprises it is the market the business has decided not to serve without anyone having made that decision.
The question is not whether an avoidance market exists in your category — it almost certainly does. It is whether your enterprise is structurally capable of serving it, and what becoming so would cost.
The Strategic Context
Almost every category contains two demand populations that behave nothing alike. One is defined by an event that has occurred: the breakdown, the breach, the recall, the missed obligation. The other is defined by an event the customer intends never to experience — maintenance that prevents the breakdown, assurance that makes the audit finding unlikely, resilience that removes the need for recovery.
In most categories the second is materially the larger, because at any moment far more organisations are trying to hold a condition than to escape one. Yet almost every commercial system an enterprise operates is instrumented for the first. Demand that does not raise its hand produces no data, and a management system that mistakes measured demand for total demand will conclude, confidently and wrongly, that the addressable market is the one already in trouble.
Why the Afflicted Market Is the Only One Your Systems Can See
Three misreadings do most of the damage.
The first treats enquiry volume as a proxy for demand. It is a proxy for urgency. A customer running a well-managed asset has a genuine need and no trigger to act on it, invisible to any pipeline beginning with an inbound contact.
The second assumes avoidance is a cheaper, earlier version of repair, sellable by the same people with the same material. It is a different product, bought on a different logic and usually by a different person. Repair is bought by whoever owns the incident, at short notice and with delegated authority. Avoidance is bought by whoever carries the consequence over a longer horizon — a risk owner, an asset owner, sometimes a board committee — and that buyer moves slowly, demands evidence, and cannot be closed by urgency.
The third, and most expensive, treats the shift as a marketing exercise. Serving avoidance changes what the organisation must be able to do, how it is staffed, how it contracts and how it earns — an operating model decision mistaken for a positioning decision.
Reframing the Issue
The more productive question is not "who has this problem?" but "who carries the consequence of this problem, over what period, and what would they pay to make that consequence improbable?"
That converts market definition from an event-based question into a liability-based one, and the two produce different maps. The population experiencing the event in any year is a fraction of the population carrying the liability for it continuously — and the liability holder is the buyer able to justify recurring expenditure, because the liability does not lapse between incidents.
Avoidance Is Always Sold Against a Counterfactual
The central difficulty is that you cannot show a customer the failure that did not happen. Repair sells against a visible loss; avoidance sells against a loss the customer must be persuaded was averted, and that shapes everything downstream.
It shapes contracting. A commitment expressed as prevented failures is unverifiable and invites dispute. A commitment expressed as a maintained condition — coverage achieved, standards demonstrated, defects closed within a defined window — is verifiable, and is what a serious buyer can take to their own governance.
It shapes pricing. Fee-per-incident aligns your revenue with the customer's misfortune, which customers eventually notice. A retainer against a maintained standard aligns revenue with their intent, and produces the revenue shape most businesses claim to want and few design for. [Related article: Would This Business Survive If Every Customer Bought Once?] examines what that dependence on repeat purchase does to a model never built for it.
It also creates a distinctive failure mode: success erodes the perceived need. After two uneventful years the maintenance budget looks like an obvious saving to someone who was not there when it was set. An avoidance business must produce continuous evidence not merely of activity but of risk retired, or it will be cancelled by its own effectiveness.
The Operating Model Splits Before the Market Does
A repair business is a response capability. Its economics turn on mobilisation speed, diagnostic depth, surge capacity and the ability to price scarcity. Utilisation is deliberately imperfect, because idle capacity is what makes response possible.
An avoidance business is a scheduled capability, turning on coverage, consistency, roster design, data capture and the cost of producing defensible evidence. Utilisation is planned, margins are thinner per engagement and steadier in aggregate, and the scarce input is discipline rather than heroics.
These are different cost curves, different reward structures and frequently different people. An organisation can hold both, and some should, because repair generates the failure data that makes the avoidance offer credible. But that is a portfolio choice with real overhead rather than a free adjacency, and it should be made rather than accumulated. [Related article: One Thing Exceptionally, or Seven Things Adequately?] sets out what breadth of this kind costs and how to test whether it has earned its place.
Decision Framework
The recurring governance failure here is the leap from anecdote to reallocation. A significant customer says something arresting to a senior executive, and within a quarter capital has moved. Seniority of the listener is not evidence. The ladder below authorises a bounded commitment at each level, and nothing beyond it.
| Evidence level | What it establishes | What it authorises | What it does not |
|---|---|---|---|
| One customer states the need | An observation | Logging it against a written hypothesis | Any spend |
| It recurs unprompted across unrelated accounts and segments | A possible pattern | Funded enquiry, not capacity | Building anything |
| Corroboration in published material — regulatory positions, tender specifications, insurer conditions | A trend, not an artefact of your account base | A bounded pilot with a pre-agreed stop | Reorganising to serve it |
| Customers commit money or contract terms before delivery | Willingness to pay, not merely to agree | Building the capability | Scaling it |
| Delivery economics demonstrated at small scale | That it can be run, not only sold | Reallocation at scale | Assuming those economics hold at volume |
Two disciplines make the ladder work: write the hypothesis down before gathering evidence, so the pattern is tested rather than assembled, and record what would falsify it. An organisation that cannot say what would change its mind is building a case, not researching a market.
Latent demand of this kind also becomes purchasable only when a trigger arrives — a regulatory change, an incident at a comparable organisation, an insurance condition, a contractual obligation of the customer's own. The readiness that matters is theirs, not yours, and [Related article: Are You Timing to Your Own Readiness, or Your Customer's?] treats that distinction directly.
From Strategy to Execution
The immediate action is instrumentation. Add one question to the interactions you already have: what condition is this customer trying to hold, and who is accountable inside their organisation if it slips? That names the liability holder: the buyer you have no relationship with.
The medium-term capability is evidence production: demonstrating a maintained standard at a cost that does not consume the margin. That is a data, reporting and contracting capability, and it is usually the binding constraint rather than the technical work.
The long-term positioning is association with the condition rather than the event — a slow reputational asset built through consistent evidence and destroyed by a single unexplained failure inside a client's coverage.
Signals to Monitor
Track the proportion of revenue from scheduled commitments against episodic response, watching the trajectory rather than the level. Watch renewal behaviour among clients who experienced no incident, because that is the only real test of whether the proposition holds.
Externally, watch regulators, insurers and procurement functions for movement from remediation towards demonstrated control, and watch competitors' contract forms rather than their marketing. Treat a sustained fall in incident volume as a commercial event requiring a response, not simply as good news.
Questions for the Leadership Team
- Who carries the consequence of the problem we solve, and do we have a relationship with that person or only with whoever reports the incident?
- What proportion of our revenue depends on customers experiencing the outcome they are paying us to prevent?
- On what evidence did we last reallocate capital towards a new demand, and where on the ladder above did that evidence sit?
- If a client had two entirely uneventful years, what could we show them at renewal?
- Are we running a response business and an avoidance business inside one structure, and has anyone costed that arrangement?
Closing Perspective
The uncomfortable feature of an affliction-only business is not that its market is small. It is that its interests and its customers' point in opposite directions — and customers notice that sooner than suppliers assume.
Moving towards avoidance is not a softer strategy. It is harder: the evidence burden is heavier, the cycle longer, the buyer more demanding, the margin per engagement lower. What it buys is a market defined by intention rather than accident, and revenue that does not require anything to go wrong.
The decision worth putting to a board is therefore not whether to serve that market. It is whether the enterprise is willing to be measured on a condition it maintains rather than on an event it resolves — because that, not the marketing, is where the choice is actually made.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.