Laggard

For a long time there was only one way to explain a product that wasn't selling. Everyone who hadn't bought yet was treated as someone who hadn't been convinced yet, so the same deck went out again to accounts that had never replied to the first one.

Sales meetings kept landing in the same place. A company that had gone quiet six months ago would come up, someone would say they'd try one more visit, and the next quarter the same name sat in the same row. There was no vocabulary for sorting price from missing features from something else entirely.

In 1962 Everett Rogers cut a single market into five groups by when people take up something new. The group at the back — the one that still hasn't moved long after everyone else has — got the name laggard. What changed once the name existed wasn't the pitch. It was the account list. Companies not yet convinced could finally be counted separately from companies that never would be.

This group stays put not because it hasn't heard about the new thing, but because the cost of switching is certain while the benefit is not.

Rogers drew take-up over time as a distribution and cut it into five slices. Innovators, who try things first, are about 2 to 3 percent. Early adopters, who spot the advantage and accept the risk, are around 13 percent. The early majority, who come in once something is proven, and the late majority, who move only after it is the norm, are roughly 34 percent each. The last 16 percent are laggards. That is not a rounding error at the edge of a market; it is closer to one company in six.

What separates this group from the four in front of it is the question each one asks. The early majority asks whether companies like itself are already using the thing. The late majority asks whether staying put has started to cost money. Both are looking outward. Laggards look inward. They ask whether the current way has caused a problem so far, and if the answer is no, that settles it.

The arithmetic of switching is what keeps producing that answer. The current way has already been paid for. The templates exist, the staff know them, and everyone knows who to ask when something breaks. Moving means paying all of it again at once: migrating the records, retraining people, and absorbing the risk that work stops during the handover. Ten people spending two days each to adopt a $25-a-month tool puts the first-year cost at several times the subscription. When the benefit side of that sum has no firm number in it, the total always favors staying.

So the conditions that actually move this group are three, and all three sit outside the product.

1. The current thing stops working. When a vendor ends support, there is no choice left.
2. A rule forces the change. A large customer that will only accept documents in one format moves the decision for you.
3. The person deciding changes. When someone who has worked that way for twenty years leaves, the reason the practice survived leaves with them.

None of the three comes from a better product or a better sales rep. No feature and no discount can manufacture them.

The word comes up in the meeting that decides who to leave out of a count, not the meeting that decides who to go after.

The first of those is market sizing. A hundred thousand companies in a category does not mean a hundred thousand prospects. Subtract the share that behaves like laggards and the reachable market drops to the low eighty thousands. Skip that subtraction and the market figure inflates, and the revenue target built on it comes back as a miss the following year.

The second is pipeline cleanup. The call is made from the record rather than from a feeling. Did the account ignore an offer priced 20 percent lower? Was the stated reason for not switching the price, or the risk of migrating? If the objection was price, this isn't a laggard yet.

The third is rolling out an internal tool. Put a collaborative document tool into a fifty-person company and about eight people will still be mailing attachments around at the end. Trying to win those eight over one at a time is how a rollout slips indefinitely. Setting a date to shut off the old way works faster.

One caution: laggards sit nowhere near where the chasm opens. That gap falls between early adopters and the early majority, and this group is far behind it. Blaming laggards for an early product that isn't selling hides the part of the curve where the real problem is.

"I'm treating these three as laggards and taking them out of the quarter's target."

Six months with no movement, so the time goes to other accounts instead of more persuasion.

"That market size counts laggards, so it's larger than the real prospect pool."

A brake on copying a number out of a report straight into a target.

"We've got laggards inside our own company. They're still mailing files around."

A signal to solve it with a shutoff date rather than more convincing.

The word came up at Pagedeck while the team set targets for the following year. Grace wanted to use the total count of companies in the category as the target market, and Sofia pulled out a year of sales records. One sixth of the list had never replied, even to an offer priced 20 percent lower, and the handful reachable by phone all gave the same reason: they had worked this way for twenty years and had no plans to change. Sofia proposed moving that sixth to a different column rather than deleting it — one to reopen if a customer starts demanding electronic forms or the person in charge moves on.

The most common mistake is reading laggard as a word about backward people. The name points that way, so the reading comes easily. But the slot is set by what someone has riding on that particular product, not by their temperament. The person who installs a new developer tool before anyone else stands at the very back when the accounting system is up for replacement, because the numbers there have to be right. Left uncorrected, this reading stops anyone from asking why the account isn't buying. The company gets filed under one word without anyone separating a migration risk from a regulatory block, and when the blocking condition finally lifts, nobody notices.

The second mistake is hearing laggard as never buys. The three conditions above say otherwise: this group does change, it just isn't the seller who picks the moment. Treat the two as the same thing and the accounts get erased from the list rather than parked, so when a rule change moves a whole cluster of them at once, there's no contact left to call. Dropping a name from this year's target and deleting it from the list are different acts.