Industry

Part of Competitor validation: what beginners should know

Competitor validation examples compared: what the good ones share

Competitor validation examples: five invented cases where one public artifact supported two readings, and the cheap observation that decided between them.

A competitor's public material is only useful once you have practiced reading it, and practice needs worked cases. Five follow. Every company, market and figure in them is invented, and each one is carried through to the decision it produced, because a reading that stops at "interesting" was not worth doing.

The pattern to watch for is the same in all five: an artifact, a reading, a competing reading, and the cheap observation that settled it.

What to take away

  • Each artifact supports at least two readings. The work is naming both and finding the observation that separates them.
  • The decision at the end is rarely "build" or "abandon". It is usually "test this specific slot next".
  • What a competitor stopped doing is as informative as what they started.

Case one: the tier that moved

The artifact. An invented scheduling product for small clinics. Two years ago its pricing page had three tiers and multi-location support sat in the middle one. Today multi-location, an audit log and a compliance report sit behind a "contact us" tier with no printed price.

The readings. Either the company discovered that multi-site groups pay far more and moved the features to where the money is, or single-site clinics turned out to be unprofitable and the company is drifting upmarket to survive.

What separated them. Their job listings. A year of hiring enterprise sales and no hires in self-service support pointed to the second reading. The founder studying this was about to build for single-site clinics.

The decision. Before building anything, find five single-site clinics that left the competitor and ask why. If they left over price, the segment exists and is underserved. If they left because they stopped needing software at all, the segment is thin. The founder ran those conversations before writing a line of code.

Case two: the changelog that went quiet

The artifact. An invented inventory tool for independent bookshops. Eighteen months of changelog entries, almost all about connections to point-of-sale systems. Nothing about reporting, which was the feature the founder intended to lead with.

The readings. Either reporting is finished and nobody asks for more, or nobody asks for it because buyers do not value it.

What separated them. Three users of the tool, asked what they do for reporting now. Two exported to a spreadsheet every Monday and had done for years. One did not look at reports at all.

The decision. The Monday export is a workaround, and workarounds are unserved jobs. But a workaround people have tolerated for years is a low-pain one. The founder reframed the offer around the point-of-sale connection that the competitor's customers had clearly been pushing for, and put reporting third. The reading changed the lead slot of the offer, not the product.

Case three: the hiring pattern

The artifact. An invented compliance service for small food producers. Over four months the competitor posted for three enterprise account executives and a head of regulatory affairs. No product or support roles.

The readings. They are moving upmarket and the small end will soon be underserved. Or the small end was never profitable and they are leaving it because it cannot be served at a price small producers will pay.

What separated them. The founder built a floor from her own numbers: what one small producer would cost to onboard and serve for a year, delivered by hand. Then she quoted that number to eight small producers.

The decision. Five said it was too expensive against what they currently paid a part-time consultant. The competitor was leaving for a reason. She kept the segment but changed the delivery model to a shared group review, which cut the floor enough to requote. The pricing question decided the market question.

Case four: no competitors at all

The artifact. The absence of one. An invented service for residents' associations to manage building maintenance requests. Searches turned up nothing built for them.

The readings. A genuinely open field, or a problem that is not worth paying to remove.

What separated them. Finding the substitute. Six associations were asked what they do now. All six used a group chat and one volunteer who kept a list. Asked whether it was a problem, four said the volunteer handled it.

The decision. The cost was real but fell on one unpaid person who did not experience it as cost, and the people who would pay did not feel it. The founder stopped, then tried the managing agents who serve those buildings instead, because they bear the cost in paid hours. A new buyer, same problem. That is a market validation finding arrived at through competitor work.

Case five: the cancellation page

The artifact. An invented subscription for freelance translators. Canceling required a phone call during business hours, and a win-back discount appeared before the call was even booked. That design is also the subject of a specific federal rule on negative option offers, which is about consent to recurring charges and the ability to stop them without obstacles.

The readings. A retention problem that the company is managing with friction. Or a low-price product where phone support is the only economical way to save an account.

What separated them. Review sites, read for dates. Complaints about cancellation clustered in the last year, not across the product's life. Something changed recently.

The decision. Recent friction suggested recent churn, which suggested a product that had stopped delivering for some segment. The founder went looking for that segment among reviewers who mentioned leaving, and built the first offer for them specifically, with a cancel-anytime term stated on the page as a deliberate contrast.

Running one yourself

Before you start, write down what buyers actually do about the problem today, in the order the SBA's market research and competitive analysis guidance recommends. Reading a competitor's material before that produces a description of their customers and not of the market.

Pick one artifact, not a whole competitor. Write the obvious reading. Then force yourself to write the opposite one, however unlikely it feels. Name the cheapest thing you could observe that fits one and not the other, and go and observe it. Most take an afternoon. None of them requires you to have built anything.

Common questions

Why are the cases invented?

Because a real case is told backwards from its ending, with the facts selected to explain a result already known. An invented one can be stopped at the decision point, which is the only point where the reasoning is useful to you.

Which artifact is the best place to start?

The pricing page, read alongside an archived copy from a year or two earlier. The differences are decisions the competitor paid to learn.

What if the two readings both turn out to be true?

They often are, partly. The decision is still usually the same, because what you are choosing is the next test rather than a verdict on the idea.

How much time should this take?

An afternoon per artifact, and the artifacts are cheap. The expensive part is the observation that separates the readings, and that is usually a handful of conversations.

More in Industry

Costs

Competitor validation mistakes that can derail your plans

Competitor validation mistakes: nine ways the research fails quietly, the symptom that catches each one, and the step that replaces inference with observation.

Industry

Customer interviews framework: facts, examples and context

Customer interviews framework for a whole round: six fields filled before booking, a screener that excludes, a stopping rule, and the write-up shape.

Industry

Offer testing: planning, execution and measurement

Offer testing from a five-slot sentence: change one slot at a time, climb the commitment ladder, and tell an execution failure from a demand failure.

Latest from Field Desk

Reviews

First 100 days: a practical reference for 2027

First 100 days answers arrive in a fixed order: arrival, start, finish, return, pay again, tell someone, and reading one early destroys the next one.

Rules

Founder readiness mistakes that can derail your plans

Founder readiness mistakes that all feel like good practice: nine ways of removing the possibility of a bad answer, each with the correction that restores it.

Guides

Minimum viable offers: common questions and clear answers

Minimum viable offers are a targeting instruction rather than a size: cut the product, never the promise, deliver by hand, and design for ten rather than one.