<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sixteen Ventures</title>
    <link>https://sixteenventures.com</link>
    <description>Expansion revenue and customer lifetime value by Lincoln Murphy, who named and popularized Customer Success in 2010. Fifteen years on growth and retention.</description>
    <language>en-us</language>
    <lastBuildDate>Mon, 24 Aug 2026 09:00:00 +0000</lastBuildDate>
    <atom:link href="https://sixteenventures.com/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>It Doesn't Have to Be Resolved on This Call</title>
      <link>https://sixteenventures.com/it-doesnt-have-to-be-resolved-on-this-call/</link>
      <guid isPermaLink="true">https://sixteenventures.com/it-doesnt-have-to-be-resolved-on-this-call/</guid>
      <description>Calling somebody up rather than out requires knowing what is being defended. Without that material the gentler version lands worse, which leaves two options, and debating the merits is not one of them.</description>
      <pubDate>Mon, 24 Aug 2026 09:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Active Listening Is a Filter, Not a Posture</title>
      <link>https://sixteenventures.com/active-listening-is-a-filter/</link>
      <guid isPermaLink="true">https://sixteenventures.com/active-listening-is-a-filter/</guid>
      <description>I took an objection at face value in a client meeting and got it wrong. Active listening isn't a posture, it's a framework you run what you hear through, and being present is not the same as having it loaded.</description>
      <pubDate>Sat, 22 Aug 2026 09:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Automating The First Touch Is A Category Error</title>
      <link>https://sixteenventures.com/automating-the-first-touch/</link>
      <guid isPermaLink="true">https://sixteenventures.com/automating-the-first-touch/</guid>
      <description>A customer pays you real money and the first thing your company does is work out how to message them without a person involved. That's a throughput answer to a question about what the moment is for.</description>
      <pubDate>Sat, 22 Aug 2026 09:00:00 +0000</pubDate>
    </item>
    <item>
      <title>The Uncertain Yes</title>
      <link>https://sixteenventures.com/the-uncertain-yes/</link>
      <guid isPermaLink="true">https://sixteenventures.com/the-uncertain-yes/</guid>
      <description>They said yes. Three weeks later they hadn't done it. The confidence question's real job isn't measuring confidence, it's defeating a yes that was never one.</description>
      <pubDate>Sat, 22 Aug 2026 09:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Why You're Stuck Downstream</title>
      <link>https://sixteenventures.com/why-youre-stuck-downstream/</link>
      <guid isPermaLink="true">https://sixteenventures.com/why-youre-stuck-downstream/</guid>
      <description>Everyone says move upstream. Teams keep not doing it, and the reason isn't discipline. The upstream problem usually isn't a customer success problem to fix, which leaves the save as the only lever anyone actually owns.</description>
      <pubDate>Sat, 22 Aug 2026 09:00:00 +0000</pubDate>
    </item>
    <item>
      <title>You Have Never Been Your Own Customer</title>
      <link>https://sixteenventures.com/you-have-never-been-your-own-customer/</link>
      <guid isPermaLink="true">https://sixteenventures.com/you-have-never-been-your-own-customer/</guid>
      <description>Two things happened to me as a customer this month, and both are the kind of problem the company causing it will never find out about. A vendor's software with your logo on it is you, and it isn't optimizing for your customer.</description>
      <pubDate>Sat, 22 Aug 2026 09:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Your Welcome Email Is A Requisition Form</title>
      <link>https://sixteenventures.com/your-welcome-email-is-a-requisition-form/</link>
      <guid isPermaLink="true">https://sixteenventures.com/your-welcome-email-is-a-requisition-form/</guid>
      <description>Read the last one you sent and count what you asked for before you gave anything. Nobody designed that message. It accumulated, and the ask is the part the customer experiences.</description>
      <pubDate>Sat, 22 Aug 2026 09:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Where Your Customer Context Actually Lives</title>
      <link>https://sixteenventures.com/where-your-customer-context-actually-lives/</link>
      <guid isPermaLink="true">https://sixteenventures.com/where-your-customer-context-actually-lives/</guid>
      <description>The sales conversation holds everything Customer Success never gets. But it isn't one thing: calls, email, phone, messaging apps and in-person meetings are captured at completely different rates, and which ones matter depends on where you sell.</description>
      <pubDate>Thu, 20 Aug 2026 10:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Automate the Work, Keep the Pace Human</title>
      <link>https://sixteenventures.com/automate-the-work-keep-the-pace-human/</link>
      <guid isPermaLink="true">https://sixteenventures.com/automate-the-work-keep-the-pace-human/</guid>
      <description>A personalized welcome email can be in the inbox seconds after signature. It shouldn't be, and I've been saying so since 2014. What changed is that every other tell has been closed, which leaves pacing carrying all the weight.</description>
      <pubDate>Thu, 20 Aug 2026 09:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Exposing Uncertainty Beats Finishing Onboarding</title>
      <link>https://sixteenventures.com/exposing-uncertainty-beats-finishing-onboarding/</link>
      <guid isPermaLink="true">https://sixteenventures.com/exposing-uncertainty-beats-finishing-onboarding/</guid>
      <description>Two questions, asked right after you lay out what the customer is responsible for. If surfacing their uncertainty means onboarding doesn't finish today, that's the correct outcome, because a completed onboarding with hidden uncertainty in it is worse than an unfinished one.</description>
      <pubDate>Wed, 19 Aug 2026 09:00:00 +0000</pubDate>
    </item>
    <item>
      <title>When Your Delivery Gets Good Enough to Make CS Look Optional</title>
      <link>https://sixteenventures.com/good-delivery-makes-cs-look-optional/</link>
      <guid isPermaLink="true">https://sixteenventures.com/good-delivery-makes-cs-look-optional/</guid>
      <description>Bad delivery makes Customer Success look like a drain. Good delivery makes it look unnecessary. The second mistake is quieter, more expensive, and it removes half of what the customer actually bought.</description>
      <pubDate>Wed, 19 Aug 2026 08:00:00 +0000</pubDate>
    </item>
    <item>
      <title>They're Not Disengaged. They're Embarrassed.</title>
      <link>https://sixteenventures.com/theyre-not-disengaged/</link>
      <guid isPermaLink="true">https://sixteenventures.com/theyre-not-disengaged/</guid>
      <description>A customer who stops engaging usually gets filed as not invested. More often they lost the thread early, and deciding it doesn't matter is the cheapest way out of feeling like they should have understood.</description>
      <pubDate>Fri, 07 Aug 2026 09:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Your Retention Number Might Be Measuring Your Calendar</title>
      <link>https://sixteenventures.com/retention-number-measuring-your-calendar/</link>
      <guid isPermaLink="true">https://sixteenventures.com/retention-number-measuring-your-calendar/</guid>
      <description>Two people can pull defensible retention numbers from the same data and reach opposite conclusions. Usually it is metrics built for one revenue model applied to a different one, plus cohort windows nobody checked.</description>
      <pubDate>Thu, 06 Aug 2026 10:00:00 +0000</pubDate>
    </item>
    <item>
      <title>You Can't Qualify Against a Role That Doesn't Exist</title>
      <link>https://sixteenventures.com/qualify-against-a-role-that-doesnt-exist/</link>
      <guid isPermaLink="true">https://sixteenventures.com/qualify-against-a-role-that-doesnt-exist/</guid>
      <description>Most companies hiring their first CS person write the scope before they meet anyone, which means there was never a bar to screen against. Willingness becomes the criterion by default.</description>
      <pubDate>Thu, 06 Aug 2026 09:00:00 +0000</pubDate>
    </item>
    <item>
      <title>The Confidence Question™</title>
      <link>https://sixteenventures.com/the-confidence-question/</link>
      <guid isPermaLink="true">https://sixteenventures.com/the-confidence-question/</guid>
      <description>A leading indicator of customer success. Churn is a decision about the future, so ask customers what they believe about next quarter. Anything less than 100% confidence is a red flag.</description>
      <pubDate>Thu, 06 Aug 2026 08:00:00 +0000</pubDate>
    </item>
    <item>
      <title>AI Gave Everyone a Tool. Nobody Built a System.</title>
      <link>https://sixteenventures.com/a-tool-for-everything-a-system-for-nothing/</link>
      <guid isPermaLink="true">https://sixteenventures.com/a-tool-for-everything-a-system-for-nothing/</guid>
      <description>Building customer-facing tools is close to free now, which is genuinely good. Then three people build the same logic in three places, it drifts, and one day somebody leaves with it.</description>
      <pubDate>Tue, 04 Aug 2026 10:00:00 +0000</pubDate>
    </item>
    <item>
      <title>When the AI Is Wrong and You Can't Stop It</title>
      <link>https://sixteenventures.com/bring-proof-not-feelings/</link>
      <guid isPermaLink="true">https://sixteenventures.com/bring-proof-not-feelings/</guid>
      <description>For the individual contributor who can see a customer getting a bad automated experience and lacks the authority to halt it. Concerns do not travel upward. Proof with a number attached does.</description>
      <pubDate>Tue, 04 Aug 2026 10:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Your Agentic Workflow Learns. Only From Itself.</title>
      <link>https://sixteenventures.com/fast-garbage-is-still-garbage/</link>
      <guid isPermaLink="true">https://sixteenventures.com/fast-garbage-is-still-garbage/</guid>
      <description>Agentic workflows learn. The problem is what yours is learning from. A closed loop reviews its own prior output while every real signal the customer gave you sits outside the system, and it calls that improvement.</description>
      <pubDate>Tue, 04 Aug 2026 10:00:00 +0000</pubDate>
    </item>
    <item>
      <title>"This Looks Like AI" Is a Context Problem</title>
      <link>https://sixteenventures.com/looks-like-ai-is-a-context-problem/</link>
      <guid isPermaLink="true">https://sixteenventures.com/looks-like-ai-is-a-context-problem/</guid>
      <description>When a customer says your work reads like AI, they are almost never pointing at formatting. They are pointing at generic, and generic is what thin input produces. The AI did not fail you.</description>
      <pubDate>Tue, 04 Aug 2026 10:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Slow Down to Speed Up: Three AI Traps in Customer Experience</title>
      <link>https://sixteenventures.com/slow-down-to-speed-up/</link>
      <guid isPermaLink="true">https://sixteenventures.com/slow-down-to-speed-up/</guid>
      <description>AI can deliver the appropriate experience at a scale we never had before. It delivers the wrong one just as fast. Three traps from real engagements, and the rule underneath all of them.</description>
      <pubDate>Tue, 04 Aug 2026 09:00:00 +0000</pubDate>
    </item>
  </channel>
</rss>