Customer Success Talks

There are a few genuinely useful distinctions (vertical vs horizontal SaaS implying different CS motions, persona-based usage expectations, green/yellow/red portfolio triage), but much is padded with conversational filler, repeated food-name jokes, and generic advice.

“So at the vertical SaaS level, understanding the business, but also the problem statements of the different personas that use your product and the logical usage that would come along”

“an executive may only log in to pull reports once a quarter”

The vertical/horizontal framing and the NPS-removal anecdote add some fresh nuance, but most content is standard CS advice (know your customer, use AI, map personas) that circulates widely.

“Vertical SaaS, I used to use NPS, and then I did an in-depth analysis with a particular company and discovered that NPS just wasn't a good indicator if somebody was going to renew or not”

“go a layer deeper and understand, well, it's an executive, they have quarterly board meetings”

Maranda is a genuine practitioner - Chief Customer Officer with 25+ years, multiple named companies (Swiftly, HelloSign, FEXA), and real CS leadership experience, making her highly relevant though the transcript leans on general advice rather than deep war stories.

“Chief Customer Officer with 25+ years of experience scaling operations and team across startups, including 5 successful exits, one of them a unicorn”

“I worked at a company named Swiftly. Swiftly powered public transit agencies”

Named companies and some concrete details (seat/signature funnel, portfolio breakdowns, persona log-in cadences) provide grounding, but most numbers are admittedly invented for illustration and there's little hard outcome data.

“If you purchase 10 seats, I wanted you to be using— I have people registered to 8 of those seats”

“My top 10 accounts pay us $100,000+ a year”

The host asks reasonable follow-ups (legacy vs new customers, scaling white glove, what CSMs do wrong) but rarely pushes back and frequently adds long tangents, jokes, and self-affirming commentary rather than challenging claims.

“Is there any suggestion on how to make these discoveries?”

“what have you seen CS, individual collaborators, doing wrong when going through this discovery phase?”