<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kieron Summers-Smith · Notes</title><link>https://kieron.me/notes/</link><description>Payments, partnerships and the work itself.</description><language>en-gb</language><atom:link href="https://kieron.me/notes/feed.xml" rel="self" type="application/rss+xml"/><item><title>Nobody churns at renewal</title><link>https://kieron.me/notes/nobody-churns-at-renewal/</link><guid isPermaLink="true">https://kieron.me/notes/nobody-churns-at-renewal/</guid><description>Renewal is when you find out. The decision usually got made a year earlier, during an integration that went badly and never got properly fixed. Here is where it actually happens.</description><pubDate>Mon, 31 Aug 2026 23:46:16 +0100</pubDate><category>On categories</category></item><item><title>Tier 1 is not a tier. It is a temperament.</title><link>https://kieron.me/notes/tier-1-is-not-a-tier-it-is-a-temperament/</link><guid isPermaLink="true">https://kieron.me/notes/tier-1-is-not-a-tier-it-is-a-temperament/</guid><description>Most companies define their top customer segment by deal size. The useful definition is the one that actually predicts how the relationship will behave. Here is what Tier 1 really means, and why so many CS teams get it wrong.</description><pubDate>Wed, 22 Jul 2026 10:00:00 +0100</pubDate><category>On relationships</category></item><item><title>Why most CS frameworks break the moment they meet Tier 1 enterprise.</title><link>https://kieron.me/notes/why-most-cs-frameworks-break-the-moment-they-meet-tier-1-enterprise/</link><guid isPermaLink="true">https://kieron.me/notes/why-most-cs-frameworks-break-the-moment-they-meet-tier-1-enterprise/</guid><description>Customer Success has a literature problem. Most of it was written for SaaS. Almost none of it survives contact with a Tier 1 enterprise customer in a regulated industry. Here is what actually breaks, and what to do about it.</description><pubDate>Wed, 01 Jul 2026 10:00:00 +0100</pubDate><category>On building things</category></item><item><title>Three sides of the rails.</title><link>https://kieron.me/notes/three-sides-of-the-rails/</link><guid isPermaLink="true">https://kieron.me/notes/three-sides-of-the-rails/</guid><description>Most payments people specialise on one side of the rails for their whole career. Having worked across acquiring, orchestration, and issuing, here is what Customer Success actually looks like on each, and why the differences matter more than the industry admits.</description><pubDate>Wed, 10 Jun 2026 10:00:00 +0100</pubDate><category>On the work itself</category></item><item><title>What I learned building Customer Success functions from scratch, twice.</title><link>https://kieron.me/notes/building-cs-from-scratch/</link><guid isPermaLink="true">https://kieron.me/notes/building-cs-from-scratch/</guid><description>Building CS in a payments business from zero. What actually matters, what does not, and why most frameworks you read about online break the moment they hit a Tier 1 customer.</description><pubDate>Wed, 20 May 2026 20:54:27 +0100</pubDate><category>On building things</category></item></channel></rss>