<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>The Legible blog</title><description>Playbooks, essays, and notes from live deployments.</description><link>https://legible.co/</link><language>en</language><item><title>Outsized attrition risk</title><link>https://legible.co/blog/outsized-attrition-risk/</link><guid isPermaLink="true">https://legible.co/blog/outsized-attrition-risk/</guid><description>When an AI-supercharged employee resigns, their agents, prompts, and workflows walk out with them. The fix is structural: build them on shared infrastructure the company owns.</description><pubDate>Mon, 20 Jul 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Do AI-supercharged employees represent outsized attrition risk?&lt;/p&gt;
&lt;p&gt;Of course they do.&lt;/p&gt;
&lt;p&gt;Any time you have an employee performing at 3x-5x-10x their peers, you want them to stick around.&lt;/p&gt;
&lt;p&gt;In the olden days, we used to put retention plans in place for our “key resources” - the people who were so impactful that their departure would be a meaningful setback.&lt;/p&gt;
&lt;p&gt;In 2026, these key resources tend to share something in common - they have red pilled on AI.&lt;/p&gt;
&lt;p&gt;I spoke to a founder today who listed this dynamic near the top of the list of things keeping him awake; in his mind, the problem is exacerbated by the fact that his most red pilled employees are more often than not running their AI automations on their own machine, not visible to the team’s Claude instance.&lt;/p&gt;
&lt;p&gt;This is the new attrition math. When an AI-powered employee walks out the door, you don’t lose one person. You lose the ten people they had become. Their agents, their prompts, their workflows, all of it walks out with them.&lt;/p&gt;
&lt;p&gt;The old version of this problem was tribal knowledge. Painful, but survivable. Someone leaves, the team limps for a quarter, the knowledge gets rebuilt. The new version is worse because the leverage is bigger and the assets are invisible. Nobody knows what agents exist, where they run, or what breaks when the login gets deactivated.&lt;/p&gt;
&lt;p&gt;The fix is structural:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Agents built on shared infrastructure, not personal accounts&lt;/li&gt;
&lt;li&gt;Company workflows in a common repository, not scattered across individual tools&lt;/li&gt;
&lt;li&gt;Model-neutral, so the work survives a vendor switch too&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;And of course, a concerted effort needs to be made to lift up your most AI-averse employees through training and enablement so that they look more like your superstars.&lt;/p&gt;
&lt;p&gt;Individual AI adoption feels like progress. And it is, right up until your best person resigns.&lt;/p&gt;
&lt;div class=&quot;closer&quot; data-astro-cid-kxs3lylb&gt; &lt;span class=&quot;monolabel&quot; data-astro-cid-kxs3lylb&gt;The takeaway&lt;/span&gt; &lt;p data-astro-cid-kxs3lylb&gt;&lt;p&gt;The companies that get this right will treat agents like they treat code:
built by individuals, owned by the company.&lt;/p&gt;&lt;/p&gt; &lt;/div&gt;</content:encoded></item><item><title>Are AI Chat Threads the New Transcripts?</title><link>https://legible.co/blog/chat-threads-are-the-new-transcripts/</link><guid isPermaLink="true">https://legible.co/blog/chat-threads-are-the-new-transcripts/</guid><description>Your team does its best thinking with AI every day, and almost none of it is remembered. Human-to-AI chats are the next transcripts worth capturing.</description><pubDate>Thu, 16 Jul 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;One of my favorite sources of interesting things to write about is conversations that I have with my cofounders. Here’s a pretty cool insight that came from Brandon, Founding Partner at Legible, that suggests that mining AI chats between humans and AI might be as valuable as mining transcripts between humans.&lt;/p&gt;
&lt;p&gt;“I have conversations with AI agents all day. What I share with the team is the result. It’s like sitting in meetings all day and only passing along the summary.”&lt;/p&gt;
&lt;p&gt;His point: the journey that brought him to the summary gets lost. The reasoning, the dead ends, the ideas that went untouched.&lt;/p&gt;
&lt;p&gt;So he built himself a workflow. Every evening, a job runs over all of his AI conversations from the day and summarizes them: what he worked on, what he learned, what might be worth sharing with the team. He’s mining his own chat logs.&lt;/p&gt;
&lt;p&gt;Of course, we’ve seen this movie before. For decades, the knowledge in live meetings simply evaporated the moment everyone left the room. Then AI notetakers exploded, because companies realized how much thinking was buried in those conversations. Memorializing human-to-human conversation went from novelty to standard practice in about three years.&lt;/p&gt;
&lt;p&gt;The same realization is coming for human-to-AI conversation.&lt;/p&gt;
&lt;div class=&quot;pq&quot; data-astro-cid-7bfrgw4o&gt; &lt;hr aria-hidden=&quot;true&quot; data-astro-cid-7bfrgw4o&gt; &lt;blockquote data-astro-cid-7bfrgw4o&gt;Chat threads are the next transcripts.&lt;/blockquote&gt; &lt;/div&gt;
&lt;p&gt;The thinking that goes into a Claude or ChatGPT session is real work: framing problems, weighing options, making calls. Today almost none of it is remembered by anyone. Even the AI forgets it across threads.&lt;/p&gt;
&lt;p&gt;At Legible we call the answer a Shared Brain: team memory that captures the important thinking wherever it happens, in meetings or in chat. Clearly, we need to be thinking more about pulling in the human to AI transcripts, and not just the human to human ones.&lt;/p&gt;
&lt;p&gt;Your team is already doing its best thinking with AI. Do you have a plan to memorialize that knowledge?&lt;/p&gt;</content:encoded></item><item><title>Discretion as a Feature</title><link>https://legible.co/blog/discretion-as-a-feature/</link><guid isPermaLink="true">https://legible.co/blog/discretion-as-a-feature/</guid><description>Sensitive industries don&apos;t have an AI adoption problem. They have a trust problem, and whoever solves it opens a market today&apos;s note-takers can&apos;t touch.</description><pubDate>Sun, 12 Jul 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Most people paying attention would agree that recording your meetings is AI 101. If you are not memorializing that context from when your people share their knowledge, you are already behind.&lt;/p&gt;
&lt;p&gt;So I paid attention when the head of an AI training company emailed me this week with some insights from the field that suggested AI note-taking has not yet reached full saturation because of some feature gaps.&lt;/p&gt;
&lt;p&gt;He works with legal advisors who refuse to let prospect calls be recorded at all. In their quest to mitigate risk, the firms lose the transcripts entirely. And on the calls that do get recorded, something trickier happens: enormously useful knowledge gets shared in the same breath as things that must stay confidential. You can’t share the transcript without exposing the sensitive parts. So nobody shares anything, and everyone misses out.&lt;/p&gt;
&lt;p&gt;That’s the conundrum. The industries where institutional knowledge is most valuable, law, finance, healthcare, are exactly the ones where blanket transcript access is impossible.&lt;/p&gt;
&lt;p&gt;The answer isn’t to stop recording. It’s also not to record everything and hope. It’s infrastructure that treats discretion as a first-class feature: access controls that map to who was in the room, retention policies with teeth, and eventually the ability to reliably separate the shareable knowledge from the confidential material around it.&lt;/p&gt;
&lt;p&gt;Whoever solves that opens up a market the current generation of notetakers can’t touch. Sensitive industries don’t have an AI adoption problem. They have a trust problem, and it’s still unsolved.&lt;/p&gt;</content:encoded></item><item><title>Are Services Companies Venture Fundable in the Age of AI?</title><link>https://legible.co/blog/are-services-companies-venture-fundable/</link><guid isPermaLink="true">https://legible.co/blog/are-services-companies-venture-fundable/</guid><description>AI just made a category built entirely on hours look fundable, maybe for the first time in venture history.</description><pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;A few months ago, Y Combinator issued a call for startups naming a category it has avoided for decades: services businesses. Insurance brokerage. Accounting, tax, and audit. Compliance. Healthcare administration.&lt;/p&gt;
&lt;p&gt;There’s a reason venture had traditionally stayed away. Services businesses have always been “body bound.” Add a client, add a person. Revenue and headcount move together, so there’s no operating leverage, and no operating leverage means no venture-scale return. A firm can be great and still cap out at a normal-business multiple.&lt;/p&gt;
&lt;p&gt;Here’s what’s actually changed, per Gustaf Alströmer, the YC partner leading this category. A few years ago, if you wanted to build a startup around insurance brokerage, you built software that brokers used to do their job. More recently, you built an AI copilot to help them do it faster. YC’s new bet skips both:&lt;/p&gt;
&lt;p&gt;→ Old playbook: build software the professional uses&lt;/p&gt;
&lt;p&gt;→ Recent playbook: build an AI copilot that speeds the professional up&lt;/p&gt;
&lt;p&gt;→ New playbook: replace the professional, AI does the labor directly&lt;/p&gt;
&lt;p&gt;That third version is what makes services fundable. If a team of five can deliver what used to take fifty, revenue can finally grow faster than headcount. That’s the exact return profile venture capital has always required, showing up in a category built entirely on hours.&lt;/p&gt;
&lt;p&gt;The categories YC named aren’t random either. Insurance brokerage, accounting, compliance, healthcare admin are all already outsourced. A company doesn’t have to develop a new habit to work with an outside vendor. They already do. The only question becomes who’s doing the work.&lt;/p&gt;
&lt;p&gt;That’s the real headline. AI just made a category built entirely on hours look fundable, maybe for the first time in venture history.&lt;/p&gt;
&lt;p&gt;If you run a services company and are interested in leveraging AI to achieve product-like software margins, the &lt;a href=&quot;/#contact&quot;&gt;Legible team&lt;/a&gt; and I would love to talk to you.&lt;/p&gt;</content:encoded></item><item><title>Hourly Billing Needs to Die</title><link>https://legible.co/blog/hourly-billing-needs-to-die/</link><guid isPermaLink="true">https://legible.co/blog/hourly-billing-needs-to-die/</guid><description>Once AI makes an expert hour cheap, billing by the hour turns every productivity gain into a pay cut you volunteer for. The firms that fix it stop pricing the hour and start pricing the outcome.</description><pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;For a hundred years, professional services ran on one assumption: an hour of an expert’s time was worth roughly the same amount, regardless of what tools that expert had. The assumption made billing simple. It also built in a trap nobody noticed until now.&lt;/p&gt;
&lt;p&gt;AI breaks the assumption completely. If a senior analyst can now produce in one hour what used to take five, hourly billing punishes that gain instead of rewarding it.&lt;/p&gt;
&lt;p&gt;Walk through what actually happens inside a firm that keeps billing by the hour once AI shows up:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The firm gets faster and earns less for the same outcome&lt;/li&gt;
&lt;li&gt;Partners quietly discourage staff from using AI, because efficiency shows up on the invoice as lost revenue&lt;/li&gt;
&lt;li&gt;Junior staff learn to stretch two hours of real work into five billable ones, because that’s what the model rewards&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;None of that is hypothetical. It’s the default outcome of pricing the input once the input gets cheap.&lt;/p&gt;
&lt;p&gt;Here’s the part that should bother every owner of a services firm: hourly billing turns every productivity gain from AI into a pay cut you volunteer for. You do the hard work of getting faster, and the pricing model hands the savings to the client for free.&lt;/p&gt;
&lt;p&gt;The firms that fix this make one change. They stop pricing the hour and start pricing the outcome.&lt;/p&gt;
&lt;p&gt;Hourly billing was built for a world where speed and value moved together. AI just severed that link, and the billing model hasn’t caught up.&lt;/p&gt;</content:encoded></item></channel></rss>