<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Partenero Blog</title>
    <link>https://partenero.com/en/blog</link>
    <atom:link href="https://partenero.com/en/blog/feed.xml" rel="self" type="application/rss+xml" />
    <description>Customer Success, CX and AI agents from the Partenero team.</description>
    <language>en-US</language>
    <lastBuildDate>Fri, 02 Oct 2026 22:08:13 GMT</lastBuildDate>
    <item>
      <title>Pillar 7: Strategic Advisor — why being a &apos;trusted advisor&apos; is no longer enough</title>
      <link>https://partenero.com/en/blog/pillar-7-strategic-advisor-customer-success</link>
      <guid isPermaLink="true">https://partenero.com/en/blog/pillar-7-strategic-advisor-customer-success</guid>
      <pubDate>Tue, 26 May 2026 12:00:00 GMT</pubDate>
      <description>Trusted advisor is the floor. Strategic advisor is the ceiling. McCulloch surgically separates the two concepts and proposes the KSE model (Knowledge × Skills × Experience) as the framework for the CSM elevated to real advisor.</description>
      <category>Customer Success</category>
      <category>Strategy</category>
      <category>Framework</category>
    </item>
    <item>
      <title>Pillar 6: Advocacy — having advocates is not doing advocacy</title>
      <link>https://partenero.com/en/blog/pillar-6-advocacy-customer-success</link>
      <guid isPermaLink="true">https://partenero.com/en/blog/pillar-6-advocacy-customer-success</guid>
      <pubDate>Mon, 25 May 2026 12:00:00 GMT</pubDate>
      <description>Most companies have advocates and zero advocacy — because they don&apos;t capitalize on them. Advocacy is a deliberate program, with assets and a maturity flow, not a positive sentiment on NPS.</description>
      <category>Customer Success</category>
      <category>Advocacy</category>
      <category>Framework</category>
    </item>
    <item>
      <title>Pillar 5: Expansion — CSMs don&apos;t sell, they uptell (and the math is unforgiving)</title>
      <link>https://partenero.com/en/blog/pillar-5-expansion-customer-success</link>
      <guid isPermaLink="true">https://partenero.com/en/blog/pillar-5-expansion-customer-success</guid>
      <pubDate>Sun, 24 May 2026 12:00:00 GMT</pubDate>
      <description>At scale, you can&apos;t offset churn by adding new logos. The math only closes through expansion in the base — and the only sustainable way is for the CSM to uptell, not sell. CSQLs convert at 60–70% vs 5–20% for MQLs.</description>
      <category>Customer Success</category>
      <category>Expansion</category>
      <category>Framework</category>
    </item>
    <item>
      <title>Pillar 4: Retention — customers don&apos;t renew on the past, they renew on the future</title>
      <link>https://partenero.com/en/blog/pillar-4-retention-customer-success</link>
      <guid isPermaLink="true">https://partenero.com/en/blog/pillar-4-retention-customer-success</guid>
      <pubDate>Sat, 23 May 2026 12:00:00 GMT</pubDate>
      <description>The renewal is a milestone. Retention is the process. And the subtlety that changes everything: customers don&apos;t choose to stay because of the value you already delivered — they stay because of the future value you&apos;re promising.</description>
      <category>Customer Success</category>
      <category>Retention</category>
      <category>Framework</category>
    </item>
    <item>
      <title>Pillar 3: Adoption — the lever that stops churn (and what most teams measure wrong)</title>
      <link>https://partenero.com/en/blog/pillar-3-adoption-customer-success</link>
      <guid isPermaLink="true">https://partenero.com/en/blog/pillar-3-adoption-customer-success</guid>
      <pubDate>Fri, 22 May 2026 12:00:00 GMT</pubDate>
      <description>Adoption is not license utilization. Adoption is operational dependence plus business value delivered through the right features. Teams that confuse them think they&apos;re healthy — until the customer tells them they&apos;re not renewing.</description>
      <category>Customer Success</category>
      <category>Adoption</category>
      <category>Framework</category>
    </item>
    <item>
      <title>Pillar 2: Onboarding — the pillar that decides if the first renewal happens</title>
      <link>https://partenero.com/en/blog/pillar-2-onboarding-customer-success</link>
      <guid isPermaLink="true">https://partenero.com/en/blog/pillar-2-onboarding-customer-success</guid>
      <pubDate>Thu, 21 May 2026 12:00:00 GMT</pubDate>
      <description>Onboarding is finite, has a clear start and end, and is the pillar with the biggest influence on whether the first renewal happens. Trip here and you spend the whole contract catching up — and sometimes you can&apos;t.</description>
      <category>Customer Success</category>
      <category>Onboarding</category>
      <category>Framework</category>
    </item>
    <item>
      <title>Pillar 1: Operationalizing CS — the foundation everyone skips</title>
      <link>https://partenero.com/en/blog/pillar-1-operationalizing-customer-success</link>
      <guid isPermaLink="true">https://partenero.com/en/blog/pillar-1-operationalizing-customer-success</guid>
      <pubDate>Wed, 20 May 2026 12:00:00 GMT</pubDate>
      <description>Wayne McCulloch calls Pillar 1 &apos;the most important and least understood&apos; pillar. It&apos;s the one new CS teams skip — and the reason most stall at 200 accounts per CSM and can&apos;t move past it.</description>
      <category>Customer Success</category>
      <category>Operations</category>
      <category>Framework</category>
    </item>
    <item>
      <title>Time to Value: the leading indicator that decides whether the customer renews</title>
      <link>https://partenero.com/en/blog/time-to-value-leading-indicator</link>
      <guid isPermaLink="true">https://partenero.com/en/blog/time-to-value-leading-indicator</guid>
      <pubDate>Tue, 19 May 2026 12:00:00 GMT</pubDate>
      <description>If onboarding takes 11 months and the contract is 12, the renewal is already lost. Time to Value is the most underrated CS leading indicator — and the only one with a concrete timeframe rule (30 or 90 days, depending on touch model).</description>
      <category>Customer Success</category>
      <category>Metrics</category>
      <category>Onboarding</category>
    </item>
    <item>
      <title>The 7 Pillars of Customer Success: a framework for operating CS with method</title>
      <link>https://partenero.com/en/blog/seven-pillars-customer-success</link>
      <guid isPermaLink="true">https://partenero.com/en/blog/seven-pillars-customer-success</guid>
      <pubDate>Mon, 18 May 2026 12:00:00 GMT</pubDate>
      <description>Most CS teams operate reactively. Wayne McCulloch&apos;s seven-pillar framework gives a clear architecture — 5 sequential customer-journey stages and 2 cross-cutting capability layers — to move from firefighting to building CS as a company capability.</description>
      <category>Customer Success</category>
      <category>Framework</category>
      <category>Strategy</category>
    </item>
    <item>
      <title>How to build a CS health score nobody ignores</title>
      <link>https://partenero.com/en/blog/account-health-score-b2b</link>
      <guid isPermaLink="true">https://partenero.com/en/blog/account-health-score-b2b</guid>
      <pubDate>Wed, 08 Apr 2026 12:00:00 GMT</pubDate>
      <description>Most health scores die in the dashboard. The problem is rarely the formula — it&apos;s the missing trigger. Here&apos;s the framework we use with real B2B teams.</description>
      <category>Customer Success</category>
      <category>Metrics</category>
      <category>Playbooks</category>
    </item>
    <item>
      <title>Omnichannel without fragmentation: 3 design rules</title>
      <link>https://partenero.com/en/blog/omnichannel-without-fragmentation</link>
      <guid isPermaLink="true">https://partenero.com/en/blog/omnichannel-without-fragmentation</guid>
      <pubDate>Fri, 20 Feb 2026 12:00:00 GMT</pubDate>
      <description>Most omnichannel rollouts end up multichannel — separate inboxes pretending to be unified. Three design rules to avoid the trap.</description>
      <category>Customer Experience</category>
      <category>Playbooks</category>
    </item>
  </channel>
</rss>
