Conversation
Highlights

Building CS Before You Need It: Sara Masson’s Framework for Getting Customer Success Right

Sara Masson remembers the exact moment her understanding of customer success locked into place. She was in her third job interview at a promising tech startup, asking a co-founder the most generic question in the book: what can I do to help you sleep better at night?

The answer was not generic. “He said, hey, you want me to sleep better at night? You make our CEO sleep better at night. He has not taken a vacation since we started.”

That exchange reframed everything. The founders had staked careers, relationships, and stability on the customers who took a chance on them first. The first CS hire was not there to manage accounts. They were there to protect the most important thing in the company’s world.

Sara went on to become that first CSM, scaled the org, then took that playbook to multiple companies across fifteen years. She has watched the same preventable mistakes play out at nearly every company she has touched.

In this new episode of The CX Front Lines, Sara Masson, Global VP of Customer Success at Novisto shared the frameworks she has developed for building CS before it becomes a crisis function — and why most founders get the sequencing completely wrong.

The Cost of Accidental CS

The most common CS strategy at early-stage companies is not a strategy. It is a posture: say yes to everything, serve every request, and hope retention follows.

Sara calls it investing in CS by accident. “If you’re not investing in customer success thoughtfully, you’re investing in it by accident. Like you’re fighting fires, you’re fighting churn, you’re over serving because you’re doing things that you don’t have any conviction in.”

The structural cost compounds in a way founders underestimate. Over-serving without a repeatable motion means every customer gets a different experience, nothing is documented, and the second CS hire inherits chaos instead of a playbook. “You’re handing basically a drunken toddler the steering wheel and then wondering why you’re spending so much trying to get them back on the road instead of like putting them in their car seat and driving and being like, hey, I’ve got you.”

Hiring the Right First Profile

When founders do decide to hire, they face a binary that Sara says produces two failure modes. The first is the pure process builder who documents everything before learning anything. The second is the pure executor who moves fast and never writes anything down.

The second failure mode is more common in startups, and more damaging than founders expect. “Most tech companies I find lean too far the other way and hire someone who like will jump in and do, but never remembers to write it down.”

The profile Sara hires for sits between both: someone who runs an experiment two or three times, develops conviction, documents what worked, then moves to the next problem. “You need essentially a doer with a process-backed heart.” The first CSM will encounter more unknowns than knowns. The ability to form a hypothesis, test it, and extract a repeatable principle is the core competency — not process fluency, not raw execution speed.

The Generalist Ceiling

Founders who promote their first CS hire into leadership should understand where that path typically ends. The generalist who built the early org hits a structural wall around 50 employees, and again at 100.

“You hit this critical inflection point, usually around 50 employees and then again around 100 employees where you need specialists.” Generalists who resist specialization start losing political capital. They resent being asked to stay in a lane after years of owning everything.

Sara’s reframe is direct: this is not failure, it is fit. “This just means you have a really specific area and stage of your company where you thrive and where you are exceptional.” The right response is not to force a generalist into a specialist role. It is to recognize which stage produces their best work and let them replicate it elsewhere.

Global Teams as Market Access

Sara manages teams across five cities on three continents. She pushes back hard on the instinct to treat global CS as a time zone coverage play.

The actual value is cultural fluency in high-growth markets. Her Dubai team does not just cover early morning hours. They understand a market that remote hires structurally cannot serve. “I have people who understand the culture in a way that me and ChatGPT cannot match up to.”

The operational unlock is not talent selection — it is handoff structure. Her teams document completed work and assign explicit ownership one to two hours before their day ends. Without that structure, resolution cycles stretch from one day to 72 hours. “Really clean handoffs and really clear ownership make global talent your superpower.”

The Health Score Trap

Sara’s most direct message to founders building CS for the first time: do not start with a health score.

“Customer health scores are gimmicky on a bad day and a lagging indicator on a good day.” Founders reach for instrumentation before they have earned anything worth measuring. A health score built on zero customer conversations delivers false confidence.

The correct Day 1 mandate is narrower and harder. “If you hire your first CSM on day one, their task is deeply understand our customers and then develop a really high conviction customer journey that is super dead simple.” Then drive customer empathy across the entire organization. Build the health score after the basics are working.

The pattern Sara has observed across every company she has joined is consistent: the teams that win on retention are not the ones with the most sophisticated instrumentation. They are the ones with the highest conviction about the path they are taking customers down — and the discipline to stay on it.