<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>case studies on carney.wiki</title><link>https://carney.wiki/tags/case-studies/</link><description>Recent content in case studies on carney.wiki</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sat, 23 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://carney.wiki/tags/case-studies/index.xml" rel="self" type="application/rss+xml"/><item><title>Proof as Inventory</title><link>https://carney.wiki/blog/ai-era-proof-as-inventory/</link><pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate><guid>https://carney.wiki/blog/ai-era-proof-as-inventory/</guid><description>Most B2B companies have proof.
Very few have Proof Ops.
That sounds like a small distinction. It is not.
A lot of teams have customer quotes floating around in decks, a case study PDF from two years ago, a few screenshots in somebody’s Google Drive, and one heroic salesperson who somehow remembers which customer story works for which objection. That is not a proof system. That is organizational folklore.</description></item></channel></rss>