Competitor Positioning Prompts That Quote the Page

Ask for a summary of how a competitor positions itself and you get a fair description of what the company is about. It will usually be accurate. It will also be unusable. Positioning is not a thing you can describe. It is a small number of specific sentences that somebody argued over, and those sentences are what a buyer repeats back to your rep.

The difference shows up the moment the output leaves the document. A rep told that a competitor is “an easy-to-use all-in-one platform for growing teams” has nothing they can use in a room. A rep who knows the competitor’s page says six words, and knows which six, can hear those words coming and answer them.

Near-quotes are worse than no quotes

One failure is specific to this job, and it is quiet. A model asked to quote will sometimes produce a sentence that is almost the page: same idea, same shape, two words different. It passes every internal review, because everyone reads it for meaning. It fails in front of a buyer who has read the actual page. A competitor who can say they never wrote that gets to dismiss everything else you claimed in the same breath. Checking quotes by searching the saved text takes a minute, and it is the only defence. The same discipline decides whether a feature comparison holds up, because a tick is a claim about a document too.

Three sets of pages, and the second is the one that gets skipped.

Save text rather than take screenshots. A screenshot captures one screenful, crops the footnotes, and cannot be searched. That defeats the one checking step this job has.

The first pulls the wording out. The second grades what it found. The third reads what is not there. The fourth is the only one that needs your own pages, and it is the one that turns a teardown into a decision.

Every one of them ends with the same escape hatch: write “not stated” rather than filling the gap. That instruction earns its place here more than on almost any other competitive job. Marketing pages are written to imply things they do not say, and a model reading them helpfully will finish the implication on the author’s behalf.

We asked about a real product, then opened its live page. The answer invented nothing, and it still produced two things you would not want to act on.

The third row is the interesting one. Given nothing, the model produced a comparison that sounded right and that the page never makes. Given the page, and told to work from it, the same model recorded the absence instead. The prompt quality did not change between those two answers. What changed was whether there was a document in front of it.

Once the wording is out, the next question is which of it carries weight. The test is practical rather than philosophical. What could a sceptical buyer actually check?

Sorting a page this way changes what you do next. Assertions can be answered directly, usually by asking the buyer what they would want to see. Proof has to be matched with proof of your own. A competitor with eight named customers in your segment is making an argument that no amount of positioning language answers.

The absences are evidence too, and they are not conclusions

The third prompt above reads the navigation for what it never mentions: roles with no page, industries never named, objections the copy never goes near. That is genuinely useful, and it is the easiest place on this page to overreach. A missing use case may be a retreat, a page nobody has written yet, or content sitting somewhere you did not save. Record the absence, write down what would tell those apart, and go and find out. An absence presented as a strategic choice is a story, and stories about competitors outlive the evidence for them. Who a competitor says it is for is the other half of the same page, and their ideal customer is read from the packaging rather than from the headline.

A teardown is a photograph. It is accurate about a set of pages on the date at the top of your capture. From that moment it starts describing a website that no longer exists in quite that form.

Positioning changes are the worst case for this, because they matter and they are silent. Nobody announces a new homepage. A promise gets rewritten, a buyer segment disappears from the navigation, a proof point is added or quietly dropped, and none of it produces a notification. The first sign is usually a rep reporting that a buyer said something the battlecard does not cover.

Flares watches competitor homepages, product pages and pricing pages, and dates every change. A rewritten promise then reaches you when it is rewritten, rather than the next time somebody decides to look. Reading what the change means stays yours, and it is the part worth your time.

It is also worth saying what monitoring does not settle. Knowing a competitor changed their headline does not tell you whether to change yours. Copying a repositioning is how two companies end up making the same promise to the same buyer, with nothing to choose between them. What you write instead is a positioning statement of your own, and it has to survive the same quoting test. Where it has to be said out loud in a deal it becomes a competitor battlecard line, and the quoting standard gets stricter rather than looser.