When I Would Pitch Forbes, and When I Would Not

I would pitch Forbes when the article can answer a buyer question an engine is already assembling, with a claim, a named company, and a proof a later answer can lift. I would not pitch it to put a logo on a slide. The placement is raw material. If the article does not make the company legible, the domain's reputation does not transfer to the next recommendation.

The method is How to Get Featured in Forbes to Boost AI Search Visibility. That page is the deeper resource. This essay is how I would use it as a founder: the test I would run before outreach, the pitch I would actually send, and the result that would make a soft profile worth the effort.

Why I would treat this as a source decision

Forrester wrote on March 25, 2026 that AI visibility had become a 2026 planning priority inside B2B marketing organizations (Forrester). Separately, on January 30, 2026, Forrester reported that generative AI use among consumers had reached meaningful adoption and frequent repeat use. I would not hang a budget on a percentage Forrester did not put in the sentence I am willing to cite. I would hang it on the direction they did state: discovery is moving into answer systems fast enough that a founder cannot file it under experiments.

The trust figure is the one I would keep exact. Forrester reported on March 12, 2026 that 16% of US online adults said they trusted information generated by AI (Forrester). The same day's announcement, that Forrester was putting AI into how research reaches clients, points the same direction from the supply side: proprietary evidence is part of the product, not a coat of paint on it (Forrester). If only 16% of those adults trust the generated text, the source the answer cites has to carry weight the model cannot manufacture. A Forbes URL can be that source. A Forbes URL that says a founder is visionary, and never states a market fact, is a weak source on a strong domain.

I would read our own earlier work on Forbes and AI search, and the Machine Relations research on earned media, as the same pattern from two ends. Answer systems reuse evidence-rich pages on trusted domains that connect a brand to a query they are already trying to answer. They do not award points for the trophy. The discipline I would run the pitch through is Machine Relations. The words "earned authority" and "citation" stay pinned in the glossary, so a PR report cannot swap them for "impressions" without the substitution being obvious.

The pitch I would send, and the one I would kill

I would kill a pitch that is not tied to a buyer-intent query, that contains no fact an engine can extract, or that fails to repeat the same founder, company, category, and proof already published on domains we control. A feature that calls the company visionary fails all three. An article that ties the company to a concrete shift, with named evidence and a category a buyer would type, gives a retriever something to reuse.

What I would bring	Why an editor can use it	Why an answer can reuse it
Original data	A news hook with a number	A fact that still has an attribution after it is lifted
A category definition	A shift an executive is trying to name	A frame a later answer can repeat
A contrarian thesis	A reason to publish	A sentence that stays distinct in extraction
Founder evidence	Execution, not a slogan	A person and a company an entity graph can resolve

Forrester's March 25, 2026 note that AI visibility was a top planning issue for B2B leaders is why the vague prestige pitch is getting weaker in the same season editors are being asked about answer engines. The strongest version of the table is all four rows in one piece. I would bring a sharper account of something the market is already confused about, and I would make sure the draft names the category, the company, the founder, and the evidence in sentences that survive being quoted alone.

Christian Lehman's operating writing matters in that draft because engines resolve people and firms together. I would not send a company-only pitch and a founder-only pitch that describe two different businesses. The category string on the Forbes draft, on our site, and on the research we publish has to be the same string.

Where Forbes sits next to the other work

Work	What it is for	When I would count it as success
SEO	The classic results page	A query that still ends in a click to a URL we own
GEO	Generative answers	The page is cited in the answer
AEO	A direct answer surface	The page is selected as the answer
Digital PR	An editor and a human reader	The piece runs, and a person can use it
Machine Relations	The whole path from authority to measurement	The company is resolved and cited across the engines buyers use

I would not measure a Forbes piece with the digital-PR row alone, and I would not measure it with the SEO row alone. AI visibility asks whether recommendation behavior moved on the query class that fills the pipeline. GEO and AEO are how the answer surface is structured. They do not replace the decision of whether this story belongs on this domain.

A piece I would count looks like a source node. It states what changed, who it affects, and which evidence is closest to the question. Forrester's 16% trust figure cuts both ways. Answer engines need stronger sources because readers do not trust the generated text, and a trusted publication is more valuable when it carries evidence than when it carries atmosphere. Before I sent the pitch I would have the market shift named, the data or the operating evidence in hand, a quote specific enough to survive extraction, the category anchored, and a page of our own that corroborates the Forbes claim after it runs. A hit that contradicts the site makes the graph muddier. A hit that matches the site, the founder, and the research starts to compound. One article rarely moves a market. A set of sources that agree can.

I would read the media-surface account and the retrieval-surface account together. One explains how the piece gets assigned. The other explains what an engine can do with it after it is live. Paying for the first without the second is how logo collections get built.

How I would edit the draft before it was filed

I would read the draft once as an editor and once as a parser, and the parser pass would be allowed to kill the piece. The parser pass looks for four strings that match our other properties exactly: category, company, founder, and the proof. Forrester's March 12, 2026 finding, 16% of US online adults trusting information generated by AI, is why the proof has to be liftable. An answer engine that readers do not trust has to lean on a source. If our sentences dissolve into "visionary," the source is the domain and nothing else, and I do not think the domain can carry a recommendation by itself. The same day's Forrester announcement, AI inside the delivery of research to clients, is the supply-side version. Evidence is becoming part of what serious sources ship. A profile with no evidence is the opposite product, on a domain that could have shipped the evidence.

The March 25, 2026 note, AI visibility as a planning priority for B2B organizations, and the January 30 note on consumer generative-AI adoption and repeat use, are why I would not wait for a perfect dataset before I decided the pitch was a planning item. They do not contain a percentage I am willing to invent. The direction is enough to put the question on the quarter's list. It is not enough to approve a soft feature. The four pitch types I would actually send are original data, a category definition, a contrarian thesis with a boundary, and founder evidence of execution. A piece that manages only the thesis will be memorable and uncheckable. A piece that manages all four gives an editor a reason to run it and a retriever a reason to reuse it. I would rather wait a month for the number than file the thesis alone.

I would also diff the draft against our site, the founder page, and the research we already publish. Engines resolve a person and a firm together. Christian Lehman's public writing is part of that resolution for anyone reading our category, which means a Forbes sentence that describes the work differently from the operating account creates two entities. I would change the draft or change the site before publication, not after an answer starts mixing them. The measurement rows I keep in my head stop this from being scored as ordinary PR. SEO succeeds at a rank. GEO succeeds when the page is cited. AEO succeeds when it is the answer. Digital PR succeeds when a person can use the piece. The system succeeds when the company is resolved and cited on the query that fills the pipeline. A Forbes URL can serve more than one row. I would write down which row we are buying. A logo slide buys none of them.

The corroborating page on our own domain is part of the filing, not a follow-up. A hit that floats without a matching source is one node with no second vote. A hit that matches the research and the site can compound. One article rarely moves a market. I would not describe this pitch as the strategy. I would describe it as a node I am willing to earn when the sentence survives extraction, and I would reread the buyer question with the cited URLs saved, before and after, on the same wording.

What I would do

I would write the buyer question in one line, write the claim the article must be able to support, and list the proof. If I cannot do those three on a page, I would not email an editor. If I can, I would pursue the placement and I would pre-commit to a check: the same question, run before and after, with the cited URLs saved. A feature that does not show up in that comparison was a human win, and I would account for it as a human win.

Scope: a company with a fact an independent reporter can check, and a query class where being absent from the answer costs pipeline. A funding announcement belongs in this system only when the round itself demonstrates the market shift. Otherwise it is news for people who already know the company. I would also refuse the pitch if our own properties describe a different category than the one we want the article to cement. Forbes cannot reconcile a contradiction we are still publishing.

What would change my mind: a disclosed panel of our buyer questions in which Forbes URLs were retrieved no more often than an uncorroborated post on our own domain, and in which extractable claims on lesser-known domains moved the answer as much as the Forbes piece. If the domain stopped adding retrieval and the sentence did all the work, I would take the sentence to wherever it will be crawled and I would stop treating this logo as special. Forrester's 16% trust figure and the March 2026 planning notes point the other way: source quality is doing more work, not less. While that holds, I will spend the outreach on a story that can be lifted, and I will not spend it on a profile that can only be framed.

FAQ

When does a Forbes article change AI visibility?

When it contains a clear claim, a named entity, and evidence an answer engine can reuse for a query a buyer already asks. The domain helps. The extraction decides. A profile with no fact is a logo. I would not pay to add logos to a retrieval problem.

How would I measure it differently from ordinary PR?

Ordinary PR can stop at "it ran." SEO can stop at a rank. I would rerun the buyer question and keep the cited URLs. If the Forbes piece is cited, or if a claim that originated there shows up with attribution, the placement entered the answer. If the clip report is the only change, I would record a media win and leave the visibility budget untouched.

What would I finish before I asked for the introduction?

The market claim, the original proof, and the same category language on our own pages. Forrester's March 12, 2026 figure, 16% of US online adults trusting AI-generated information, is the reason the proof has to be checkable. I would also decide which person and which firm the article is resolving, so the entity graph does not receive two stories.

What would make me walk away from a willing editor?

An edit that removes the number, the category, or the attribution and leaves a character study. I would rather lose the placement than publish a page that cannot be reused. The March 25, 2026 Forrester note makes AI visibility a planning topic. It does not make every Forbes URL a planning asset. The sentence is the asset.