The Customer Success Channel

The episode contains some substantive discussion about CS positioning (revenue ownership, cross-functional models, NRR metrics), but much of the content is soft - discussions of philosophy without concrete examples, operating frameworks, or specific customer case studies. Anika's reflection on CS evolution from 'happiness department' to business outcomes is useful but somewhat obvious in hindsight. The specific recommendations are thin: 'data-driven teams,' 'use of AI/tech,' and 'company-wide CS' are broadly acknowledged industry trends, not novel insights.

“I think CS should own, you know , all post sales revenue”

“CSMs are essentially business analysts or like business strategists”

The core arguments - that CS should drive revenue, that CS identity varies by business model, that data and efficiency matter - are mainstream in SaaS discourse. Malin's framing of CSMs as in-house consultants/business analysts is intuitive but not contrarian. The episode recycles familiar concepts (NRR as north star, cross-functional ownership, health scores are theatre) without pushing back hard on conventional wisdom or proposing fresh frameworks.

“I think it's hard to say in general, okay, this is exactly how CS should be done”

“I think it becomes very aimless if the work that CS does is to ensure that the customer stays and grows, but they don't have much or any at all really insight into what that number even is”

Malin Scottland has genuine operating credentials: 15 years in B2B SaaS, led teams from 5 to 100+ people, managed tens of millions in ARR, worked across SMB, mid-market, and enterprise. She is now Head of CS at Griffin (a FinTech startup), giving her current hands-on experience. However, this is largely an exit interview disguised as a guest episode; the guest is primarily discussing the new hosting role rather than deep expertise in a specific domain. Her perspective is solid but not exceptional - a seasoned operator, not a rare category or breakthrough thought leader.

“I've run teams from, you know, five to 10 people, up to over a hundred people responsible for, you know , tens of millions of , of dollars of a RR”

“I'm currently head of customer success at Griffin, which is a banking as a service platform”

The episode is sparse on concrete examples, metrics, or dollar figures. Malin mentions 'tens of millions of ARR' (vague range, not specific), references product-market fit and NRR as key metrics (well-known), and discusses Griffin having 'select few customers in beta' with a launch 'in a few weeks' (forward-looking but no results). Anika's reflection on CS evolution relies on broad generalization ('before the pandemic') rather than named companies, campaigns, or quantified shifts. Neither speaker grounds arguments in specific customer wins, churn patterns, or cost structures.

“managing revenue growth worth tens of millions of dollars”

“We have only a select few customers that we have in a beta launch that's going live in a , in a few weeks here”

Anika asks competent, open-ended questions and lets Malin develop answers, but the conversation lacks sharp follow-ups or productive tension. When Malin states broad positions (e.g., 'CS depends on business model'), Anika largely affirms rather than probe deeper - e.g., 'how would you structure incentives if ownership is split?' or 'name a company where this failed.' The quick-fire round is lightweight. Malin's counter-interview at mid-point shifts focus from substance to pleasantries (Anika's bio, Griffin details, LinkedIn plugs). There is no real disagreement or challenge, making the dialogue feel more like networking than investigation.

“I love that you said that customer success ends up being the post sales revenue part”

“I love that philosophy to have within business in general”