Customer Support & Success

Welcome to Customer Support & Success. This is a hands-on course for founders building companies inside the Kaern startup ecosystem. By the end, you'll treat support not as a cost center to minimize but as a growth engine to invest in — and you'll have the concrete systems to run it: channels, helpdesks, response craft, self-serve knowledge bases, onboarding flows, and the metrics that tell you whether customers are staying or quietly leaving.

Who this is for: Early-stage founders who are still answering their own tickets and want to do it well before they hand it off.

Outcomes: You'll be able to design a support operation from scratch, write responses that turn frustrated users into advocates, build self-serve resources that scale faster than headcount, run onboarding that prevents churn, and measure satisfaction and retention with numbers you can act on.

Your tutor: I'm Mara. I've spent fifteen years running support and success teams — from a two-person startup where I was the support team, to a scale-up handling thousands of tickets a day. I've made every mistake in this course at least once. My job is to make sure you only make the new ones.

Module 1: Support as a Growth Lever

Learning objectives

• Reframe support from a cost center to a revenue and retention driver.
• Identify the specific moments where support influences expansion and word-of-mouth.
• Connect support activity to business outcomes you can defend in a board meeting.
• Build a simple model estimating the revenue impact of good (and bad) support.

Lesson 1.1 — The myth of the cost center

Teaching script: Let me start with the lie that nearly sank a company I worked at. Leadership called support "the complaints department" and staffed it like one — minimum bodies, maximum queue. Think of support like the foundations of a house. Nobody walks into a home and says "wow, beautiful foundations." But the day they crack, nothing else matters — the kitchen, the view, none of it. Support is the same. When it works, customers don't notice; they just renew, expand, and tell their friends. When it fails, your best feature can't save you.

Here's why this matters for you specifically. As a founder, every churned customer in your first year is a customer you paid to acquire and then lost — you're refilling a leaky bucket with expensive water. Support is how you plug the holes. A customer who has one great support interaction is measurably more loyal than one who never needed support at all. That's not a soft claim; it's measurable in renewal rates.

So here's my question to take into your company: if I deleted your support function tomorrow, which customers would leave first — and how much revenue walks out with them?

Lesson 1.2 — Mapping support to money

Teaching script: Founders love a dashboard, so let me give you one that actually changes decisions. Imagine support as a tollbooth on the highway of your customer's journey. Every car that passes either speeds up (renews, upgrades, refers) or slows down (churns, complains, warns others) depending on how that tollbooth treated them. Your job is to find the tollbooths that matter most.

Why does this matter? Because not all support touches are equal. A reset-password reply is a speed bump. But a "your invoice looks wrong" ticket from your biggest account is a fork in the road — handle it well and they expand; handle it badly and they're in a competitor's demo by Friday. When you map tickets to revenue at risk, you stop treating every ticket as identical and start protecting what's valuable.

Try this lens: tag your last fifty tickets with the revenue of the account behind them. You'll usually find a small slice of tickets sits in front of a huge slice of revenue. That's where you invest first.

So — which of your tickets are speed bumps, and which are forks in the road?

Worked example

A Kaern startup, Loomwise (project-management SaaS, €40/seat/month), has 200 customers. Their churn is 5%/month. They tag one month of tickets by account size and discover that 12 accounts (€18,000 MRR combined) each filed a billing complaint. Two churned the next month. By assigning a senior founder to personally own billing complaints from accounts over €500 MRR, they cut billing-driven churn in that segment to zero the following quarter — protecting roughly €36,000 in annual recurring revenue with no new hires.

Hands-on exercise

Pull your last 50 support interactions (or your best estimate). For each, record: (1) the account's monthly revenue, (2) the ticket topic, (3) whether the customer's behavior afterward was positive, neutral, or negative. Produce a one-page summary identifying the single ticket category that sits in front of the most revenue. Bring a recommendation: what would you change first?

Common mistakes

• Measuring support by ticket count alone, which rewards closing fast over solving well.
• Treating all customers identically, ignoring that a fraction of accounts carries most of your revenue and risk.
• Hiding support from leadership, so it never gets the investment its impact justifies.

Check for understanding

1. Give two specific mechanisms by which support drives revenue, not just saves cost.
2. Why is tagging tickets by account revenue more useful than tagging by topic alone?
3. A founder says "we'll invest in support once we're bigger." What's the flaw in that reasoning?