Ben Rees

Your B2B claim is too broad for AI to cite. Narrow the scope

Why B2B marketing claims that are too broad get absorbed into category noise by AI systems, and how to reframe them into queries AI actually cites.

Ben Rees - 29 October 2026

Most B2B marketing content is written to be impressive (to someone, not quite sure who 😉). It covers the full scope of what a product does, addresses all personas, and uses language that feels authoritative across the widest possible audience.

That instinct is exactly what makes AI systems ignore it.

The problem isn't quality. It's specificity. Broad claims compete for representational space with every other vendor in your category making the same claim. Narrow, precise claims have a structural advantage: there are fewer of them, and the competition for that space is thinner.

What the Reversal Curse reveals about how AI encodes claims

There's a useful piece of evidence for why this matters. A documented phenomenon called the Reversal Curse (Berglund et al., 2023) shows that language models trained on "A is B" cannot reliably infer "B is A." The directionality of encoding matters. Which means what a model learns depends heavily on how a claim was expressed when the training data was processed, not just whether the underlying fact appeared somewhere in the corpus.

For B2B marketing, the implication is uncomfortable. If your case study says "Company X achieved operational efficiency gains with our platform," the model might encode something close to "Platform Y delivers operational efficiency." What it almost certainly won't encode is a specific, retrievable association between your brand and the exact query a buyer types.

The fix isn't better writing. It's reformulating the claim around the specific query you want to own.

Broad to narrow: what this looks like in practice

In a previous job, the temptation was always to lead with category-level positioning: database devops, developer productivity, SQL tooling (the domain in which we worked) at scale. These were real capabilities. They were also shared with pretty much every competitor. What got traction in analyst conversations and, I'd argue, in what got corroborated across independent sources, was the specific, narrow version: "Reducing deployment risk for DBA teams managing multiple SQL Server instances across enterprise environments."

That sentence is harder to plagiarise with a press release. It's also harder for a language model to absorb into generic category noise, because the cluster of terms is specific enough that fewer documents exist to dilute it.

The pattern I've written about in why your B2B scaling story is your most AI-retrievable content applies here directly. The concrete, specific account of what you did, for whom, with what measurable result, in what constraint, is structurally harder to absorb into the generic. Broad claims get averaged away. Narrow claims survive.

The reframe process, concretely

The practical question is how to translate existing broad content into narrow, citable claims. Three moves:

Name the problem, not the solution. "We help enterprises with data governance" is a capability claim. "What do mid-market financial services companies do when their data lineage documentation is out of date before the audit?" is a problem query. AI systems are increasingly structured around answering questions, not describing vendors.

Add the constraint. Specificity of circumstance is what makes a claim narrow. "For 50-person engineering teams running self-hosted infrastructure" is not the same as "for B2B SaaS companies." The constraint is what makes the claim retrievable for the right query, and invisible for the wrong one.

Let the customer name the problem in their own words. Customer interview transcripts, support tickets, sales call recordings: these are primary sources for the actual vocabulary of the problem.

The goal isn't to become less ambitious in your claims. It's to make them precise enough that a language model can form a distinct association, rather than absorbing your content into the same overcrowded representational space as everyone else in your category.

Broad is safe. Narrow is citable.

Related reading