<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="https://www.jain.com/assets/img/6adafce5-1.1"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>vendor claims &#8211; Jain.com</title>
	<atom:link href="/tag/vendor-claims/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description>Data centers, connectivity, and security — news and analysis</description>
	<lastBuildDate>Wed, 19 Aug 2026 21:34:25 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>/wp-content/uploads/2026/08/jain-com-icon-512-150x150.png</url>
	<title>vendor claims &#8211; Jain.com</title>
	<link></link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>The Unverifiable-Claims Problem Isn&#8217;t Advertising&#8217;s Alone. It&#8217;s Infrastructure&#8217;s.</title>
		<link>/ai-infrastructure-unverifiable-claims-problem/</link>
		
		<dc:creator><![CDATA[Deepak Jain]]></dc:creator>
		<pubDate>Wed, 19 Aug 2026 21:20:03 +0000</pubDate>
				<category><![CDATA[AI Infrastructure]]></category>
		<category><![CDATA[AI infrastructure]]></category>
		<category><![CDATA[data centers]]></category>
		<category><![CDATA[GPU cloud]]></category>
		<category><![CDATA[opinion]]></category>
		<category><![CDATA[procurement]]></category>
		<category><![CDATA[vendor claims]]></category>
		<guid isPermaLink="false">/ai-infrastructure-unverifiable-claims-problem/</guid>

					<description><![CDATA[Ad-industry writer Pesach Lattin says the business isn't lying about AI so much as bullshitting — making confident, uncheckable claims. The same epistemics now govern how AI infrastructure gets sold. Here is how buyers of GPU capacity, data centers, and inference can tell a testable promise from an untestable one.]]></description>
										<content:encoded><![CDATA[<p>Pesach Lattin, who writes the advertising newsletter <a href="https://new.adotat.com/p/nobody-is-lying-to-you-about-ai-almost-nobody-is-telling-you-the-truth-either" rel="nofollow">ADOTAT</a>, recently made an argument that deserves a wider audience than the ad industry it was aimed at. Borrowing from the philosopher Harry Frankfurt&#8217;s essay <em>On Bullshit</em>, he draws a distinction that matters: a liar knows the truth and conceals it, while a bullshitter simply doesn&#8217;t care whether what he says is true. Lattin&#8217;s claim is that the advertising business is mostly doing the second thing about AI — making confident, unverifiable assertions with an apparent indifference to whether they hold up. He says he reviewed six months of conference talks and found four claims that were actually checkable.</p>
<p>I run an infrastructure company, not an ad agency. And reading it, I recognized the pattern immediately — because the same epistemics now govern how artificial intelligence gets sold one layer down, in the data centers, networks, and compute that everything else is built on.</p>
<h2>The tell is verifiability, not sincerity</h2>
<p>The useful part of Frankfurt&#8217;s framing is that it takes the argument away from intent. You do not have to decide whether a vendor is honest. You only have to ask a colder question: <strong>is this claim the kind of thing I could check?</strong> Most of the loudest statements in AI infrastructure marketing are not.</p>
<p>&#8220;AI-optimized&#8221; is not a specification. &#8220;Cloud-scale&#8221; is not a number. &#8220;Enterprise-grade reliability&#8221; is not an SLA. A GPU cloud that advertises a headline price per hour has told you almost nothing until you know the utilization you can actually achieve, the queue times at your scale, the egress charges, and whether the accelerators you were sold are the ones you get. A data center that markets a power-usage-effectiveness figure has told you something real only if it says whether that number is a design target or a measured annual average, at what load, in what climate. The gap between those two readings is where a year of operating budget hides.</p>
<h2>The one uncontested number</h2>
<p>Lattin points out that in his world, exactly one figure goes uncontested: the collapse in referral traffic as AI answer engines absorb the clicks that used to reach publishers — reductions he puts in the range of 20 to 90 percent. It is uncontested precisely because it is measurable. Everyone can see their own analytics.</p>
<p>Infrastructure has its own version of the uncontested number, and it is the electricity bill. You can argue about a model&#8217;s benchmark scores; you cannot argue with a utility invoice or a substation&#8217;s interconnection queue. This is why the most honest conversations in our industry right now are the ones about power and cooling. Megawatts do not bullshit. A grid operator&#8217;s capacity map is the least performative document in the AI economy, and it is quietly setting the ceiling on all of the confident projections layered above it.</p>
<h2>A working buyer&#8217;s test</h2>
<p>None of this is a case for cynicism. The technology is real, and the demand is real. The point is narrower and more practical: when someone sells you AI infrastructure, sort every claim into two piles before you sort it into true or false.</p>
<ul>
<li><strong>Testable now:</strong> Can it be written into a contract with a number and a penalty? Latency percentiles, delivered throughput, measured PUE over a defined period, uptime with real credits, a fixed price with the egress spelled out. Ask for the measurement method, not the headline.</li>
<li><strong>Testable later:</strong> Can you run a bounded pilot that produces your own data — a parallel workload, a real month of your traffic — rather than the vendor&#8217;s reference benchmark? Insist on it before the multi-year commitment, not after.</li>
<li><strong>Not testable:</strong> Adjectives, roadmaps, and transformation narratives. These are not lies. They are simply not evidence, and they should carry the weight of things that are not evidence.</li>
</ul>
<p>The vendors worth working with will not flinch at this. In my experience, the willingness to be measured is the single most reliable signal of whether a claim was meant to be true or merely meant to be said. The ones who lead with the utility bill, the SLA, and the pilot are telling you something. So are the ones who change the subject to the future.</p>
<p>Lattin&#8217;s essay is about advertising, and it is worth reading on its own terms. But its real subject is a habit of mind that has spread well past his industry. The infrastructure layer is the last place that habit can safely live, because down here the claims eventually meet a power meter, a thermal limit, and a bill. <strong>Ask for the number. If there isn&#8217;t one, you have your answer.</strong></p>
<p style="color:#6b7a88;font-size:0.9em"><em>Source and inspiration: Pesach Lattin, <a href="https://new.adotat.com/p/nobody-is-lying-to-you-about-ai-almost-nobody-is-telling-you-the-truth-either" rel="nofollow">&#8220;Nobody Is Lying to You About AI. Almost Nobody Is Telling You the Truth Either,&#8221;</a> ADOTAT.</em></p>
<p><script type="application/ld+json">{"@context": "https://schema.org", "@type": "OpinionNewsArticle", "headline": "The Unverifiable-Claims Problem Isn't Advertising's Alone. It's Infrastructure's.", "description": "Ad-industry writer Pesach Lattin says the business isn't lying about AI so much as bullshitting \u2014 making confident, uncheckable claims. The same epistemics now govern how AI infrastructure gets sold. Here is how buyers of GPU capacity, data centers, and inference can tell a testable promise from an untestable one.", "author": {"@type": "Person", "name": "Deepak Jain", "url": "https://www.jain.com/about/"}, "publisher": {"@type": "Organization", "name": "jain.com"}, "datePublished": "2026-08-19"}</script></p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
