All articles

When Insights Come Before Hiring, CS Teams Find Predictable Revenue And Shed Cost Center Stigma

Cresta News Desk
Published
April 20, 2026

Lynell Wagenman, a revenue-focused Customer Success leader, explains why companies that invest in data systems and outcome-based design before scaling headcount build the kind of predictable retention that boards and investors want to see.

Credit: CX Current

Key Points

  • Most companies misbuild Customer Success by treating headcount as the growth lever, when the real driver of predictable retention is data infrastructure and outcome-based design built early.

  • Lynell Wagenman, a revenue-focused Customer Success leader, explains why activity-based CS teams fail to forecast churn and why insight infrastructure must precede team expansion.

  • She recommends bringing in CS leadership early to build analytical systems, aligning go-to-market teams around a continuously refined ideal customer profile, and designing customer engagements around outcomes rather than check-ins.

Headcount doesn't really scale, but the insights that come from customer success do.

Lynell Wagenman

Head of Customer Success

Lynell Wagenman

Head of Customer Success
|
Customer-Led Growth & Net Revenue Expansion

Companies keep getting the Customer Success sequence wrong. The default playbook is to hire a team of CSMs first and invest in systems later, once the team is big enough to justify the spend. The result is a function that stays permanently activity-based rather than outcome-driven, generating check-ins instead of revenue signals, and hoping for retention rather than forecasting it.

Lynell Wagenman is a Customer Success leader specializing in customer-led growth and net revenue expansion for Series A through C SaaS companies. As the senior-most Customer Success executive at Medality (formerly MRI Online, acquired by TrueLearn), she owned retention, expansion, and renewal predictability across 200+ global customers during a period of 200x revenue growth. Over that span, her team sustained 110%+ net revenue retention and improved forecast variance from roughly 20% to 5%.

"Headcount doesn't really scale, but the insights that come from Customer Success do," says Wagenman. "You don't want to explode your headcount to get insights. You want to get insights and then grow your headcount." The problem, she explains, starts with a fundamental mismatch of models. Too often, Customer Success gets muddled in with customer service or treated as broad relationship management without a clear north star. When that happens, the function defaults to activity-based work instead of outcome-based execution. The metrics that matter to a CFO, including ARR, NRR, and cost margin, never reach the CS team's scorecard.

  • Moments that matter: When CS is designed well, Wagenman says, the noise disappears. "You cut out the check-ins just for the sake of checking in, and you become a consulting lever for the customer themselves. You're seen as a strategy partner, as somebody who is helping them drive revenue themselves."

  • Outcomes over activities: The gap between good and great CS comes down to one extra layer of analysis. "If customer A did activities A, B, and C and that made them successful, you also have to take that analysis a step deeper and say they did A, B, and C, and that led to outcome D," Wagenman explains. "That is where the art of Customer Success meets the science of the systems."

  • ICP discipline: When asked what she would tell a CEO who believes in CS but hasn't backed it with real investment, Wagenman is direct. "They need to have a crystal clear vision of their ideal customer profile and then hold each leader accountable for bringing in customers that fit it." That alignment across go-to-market teams requires honest, objective conversation about what's working and what isn't, without making it personal.

The shift from hoping for retention to actually forecasting it depends entirely on the infrastructure underneath. Wagenman describes a system built on reliable data, rigorous tracking, and continuous feedback loops. Without those elements running long enough to generate meaningful patterns, predictive modeling simply cannot work.

  • Surgical precision: "In order to create predictable revenue, you need to consistently review what you're doing," she says. "If your system predicted 10% churn this quarter and you had 12%, you need to evaluate why and feed that back into your modeling. The more analytical, almost surgical you are about understanding your data, the better you can predict what is going to happen."

  • Natural expansion: When CSMs deeply understand a customer's business and how the product impacts it, expansion stops feeling like a cold pitch. "That growth, that expansion within your service line, feels like a natural relationship," Wagenman says. "It makes sense." The key is freeing CSMs from back-end busy work so they can do the deep analytical work of understanding who their clients are and the signals coming into their businesses.

The compounding effect of these early decisions is what separates predictable revenue from guesswork. A CS function built on insight infrastructure generates the kind of reliable NRR and churn forecasting that boards pay attention to. One built on headcount alone stays reactive and unpredictable.

Wagenman recommends bringing in either a CS leader or a fractional consulting leader earlier than most companies think is necessary, before the first five or ten CSMs are even in place. The job is to build the analytical foundation that will make every future hire more effective. "Having predictable revenue early on is going to signal to investors that you really know what you're doing," she says. "It's a smart investment that gets overlooked versus customer acquisition."