Substitute

Back when competitors were only pulled from the same product category, the comparison always came out in your favor. A team building a collaborative document tool lines up four similar tools, counts features, and generally comes out ahead. Then they take that comparison out into the market and paid conversions don't move.

The reason surfaces when you ask the people who left. Asked where they went, they don't name another product. They say meeting notes go into a long thread in a chat channel, and the task list lives in one spreadsheet. They didn't go to any of the four on the chart, and they aren't using your product either. Whoever built the chart has no column that explains this. Worse, the chart keeps getting used, because winning on it feels like proof that the product is fine and only the marketing needs work.

Substitute is the name for that missing column. Move the basis from product category to the job the customer is trying to finish, and the competition becomes every method currently handling that job. The same structure as a coffee company competing not only with other coffee companies but with tea.

Finding substitutes takes one question: yesterday, before your product existed, what did these people use to do this? Everything that comes back is a substitute, and nothing gets struck from the list for falling outside the category.

The answers generally sort into three kinds.

1. Making do with a general-purpose tool. Chat channels, spreadsheets, a folder of email, a paper notebook. None of them was built for the job, which makes them awkward — and they're already in hand and cost nothing extra.
2. Doing it by hand. Someone spends an hour a week tidying it up manually, or a role exists just to handle it. This one costs real money and is still hard to displace, because buying a tool shrinks that person's job and the resistance comes from inside the organization.
3. Doing nothing. Living with the problem unsolved. The meeting notes are scattered and things limp along well enough, so they stay scattered. It's the most common and strongest competitor of the three, and the one least likely to appear on anyone's list.

What makes all three strong is that they cost close to nothing and the customer already knows how to use them. Switching to a new product means creating accounts, moving old material across, and convincing colleagues, and every bit of that cost is paid by the person coming toward you. One more feature doesn't close that gap.

Sizing it up means counting. Ask the people who didn't convert and the ones who left for a reason, then count how many of 100 answers say they moved to a similar product and how many say they kept doing what they were doing. If the second group is 62, the competitor that quarter is inertia, not a company. The work changes with it. Against a competitor you compare features and price. Against a substitute you cut the cost of moving over and make visible what the current method is already costing. Keeping a table intact when someone pastes it in from a spreadsheet moves conversion more than another feature does, and it never appears on a feature chart at all.

There are four places the term gets used.

The first is building the comparison. A competitive matrix puts companies across the top and items down the side, and a spreadsheet and a chat channel each get a column of their own. Most of the feature rows come back empty, and the price and familiarity rows show those two beating you.

The second is pricing. When the substitute is free, the ceiling on what you can charge is tied to that fact. Choosing a freemium structure — open the basics, charge for the advanced parts — comes out of the same reasoning. Let people feel the improvement over the free method first, then ask about money.

The third is ordering requirements. Importing material out of the old method goes ahead of new features, because cutting the cost of moving attaches directly to conversion.

The fourth is sales material. Teams often have a document for handling competitors and none for handling "we'll keep doing what we do," even though the second comes up more often.

Benchmarking, measuring your own level against a leading example, looks the other way around. Benchmarking takes something done well as the baseline and measures the distance to it. Substitutes are things done badly that customers keep using anyway.

"Our competition isn't a similar product, it's a spreadsheet."

There's a competitor in this market that a feature comparison cannot explain.

"Of 100 non-conversion reasons, 62 were people sticking with what they had."

What needs cutting this quarter is the cost of moving over, not a competitor's share.

"Without an import, that team can't move."

The material they've accumulated is what's holding them in place.

Pagedeck collected 100 non-conversion reasons in its second year. Nineteen said they'd gone to a similar product. Sixty-two said they were keeping their current method, and nearly half of those were chat channels and spreadsheets.

Ravi changed the ad copy on the strength of that count. He dropped the line about being better than other tools and led instead with a question about how much time a week goes into hunting for decisions buried in a chat thread. In the same quarter, Mia moved up the work that keeps a table intact when someone pastes it in from a spreadsheet.

The most common mistake is reading a substitute as a cheap, underpowered alternative. Lay the features side by side and it loses badly, so the reading is natural. But customers aren't buying completeness; they're asking whether something is enough for the job in front of them. For a team of six tracking twenty meeting notes, one spreadsheet is enough. Miss this and you keep adding features while nobody can explain why conversion is flat, and the two things that needed work — importing and price — stay exactly where they were.

The second is assuming free substitutes lose on their own as a market matures. The expectation is that people move once something better exists. But inertia doesn't break by itself. Teams move when the way they work changes or when headcount grows enough that the old method collapses, and that trigger is usually not something you can create. Leave the assumption in place and the trigger arrives with nothing ready for the customer to click.