Iliyana's Blog

CS as a Predictable Revenue Driver — What It Actually Takes

iliyana.stareva@gmail.com (Iliyana Stareva) — Thu, 28 May 2026 12:44:44 GMT

I started my SaaS career in Customer Success.

Not the version of CS that exists in most companies today. The version where you were responsible for the full customer relationship — adoption, outcomes, retention, and growth. Where upsell and cross-sell were part of the job, not someone else's quota. Where working with partners to drive expansion was expected, not exceptional.

I was 24. I had never done anything sales-related in my life.

And I loved it.

I loved it because it made sense. If a customer was succeeding with the product, achieving real business outcomes, getting value they could measure — of course they would want more. And who better to spot that opportunity than the person who had been working alongside them, understanding their business, guiding their adoption journey?

That year, I made President's Club. Not as a salesperson. As a CSM, on the channel side.

Not because I was selling. Because I was succeeding — and success, when it's genuine, creates its own commercial momentum.

Then Something Changed

Why Most Customer Success Org Designs Prevent Growth

iliyana.stareva@gmail.com (Iliyana Stareva) — Wed, 20 May 2026 09:45:59 GMT

Most Customer Success organisations are not designed to fail. They're designed to survive.

Survive renewals. Survive escalations. Survive the quarter.

And that survival instinct — built into the org structure, the hiring profiles, the incentives, the mandate — is precisely what prevents growth.

This isn't a people problem. It's a design problem. And until CS leaders are honest about it, no amount of AI investment, tooling, or training will change the outcome.

The Narrow Design Problem

When most companies build a CS organisation, they start with two things in mind: onboarding and retention.

Get the customer live. Keep them happy. Renew the contract.

How to Get CSMs to Actually Trust AI Signals

iliyana.stareva@gmail.com (Iliyana Stareva) — Tue, 28 Apr 2026 08:05:47 GMT

There's a common assumption in CS leadership: CSMs don't act on AI signals because they don't trust them. That's not quite right. In most cases, the signal isn't the problem. The gap is what comes after it.

A CSM sees a risk score drop. An alert fires. A flag appears in the dashboard. And then — nothing. No context. No direction. No clear next step.

So they do what any reasonable person does when faced with ambiguity: they fall back on what they know. Their instinct. Their relationship read. Their experience.

Not because they're resistant to AI. Because the system handed them a problem without handing them a path.

Why CSM don't trust AI Signals

Why AI Adoption Fails Inside Customer Success Teams (And It's Not What You Think)

iliyana.stareva@gmail.com (Iliyana Stareva) — Tue, 07 Apr 2026 09:21:32 GMT

Every Customer Success leader I know is under pressure to adopt AI. The tools are being deployed. The dashboards are being built. The announcements are being made.

And yet — adoption stalls. CSMs quietly ignore the signals. Workarounds emerge. People revert to instinct over insight. This isn't a technology problem. It's a human one.

After years of building and running Customer Success and Customer Health operations across three major SaaS organisations, I've seen this pattern repeat. AI gets introduced. Behaviour doesn't change. Leadership assumes the team needs more training. What they actually need is something much harder to fix.

The real reasons AI fails in CS teams

Retention as a Capital Efficiency Lever in SaaS

iliyana.stareva@gmail.com (Iliyana Stareva) — Sat, 21 Mar 2026 06:25:02 GMT

Retention is often discussed as a Customer Success metric. It's tracked as a percentage, reviewed in quarterly reports, and used to evaluate the performance of CS teams. When retention improves, it is seen as a positive signal. When it declines, it triggers concern.

But this framing significantly underestimates its impact. Retention is not just a Customer Success outcome. It is one of the most powerful levers of capital efficiency in a SaaS business.

And once companies understand it that way, it changes how they design their operating model.

Retention Is a Financial Variable, Not Just an Operational Metric

At its core, retention determines how efficiently a company converts customer acquisition into long-term value.

The Hidden Cost of Reactive Customer Success

iliyana.stareva@gmail.com (Iliyana Stareva) — Wed, 25 Feb 2026 10:29:04 GMT

Most SaaS organisations do not consider themselves reactive. They describe their teams as customer-centric, responsive, and committed to resolving issues quickly. And in many cases, that is true. Problems are addressed. Escalations are handled. Renewals are saved.

But responsiveness is not the same as proactivity. Reacting well to problems does not mean the operating model is designed to prevent them. And when Customer Success functions primarily in reaction mode, the costs are not only operational — they are economic.

These costs rarely appear on a dashboard. They are not neatly summarised in quarterly reports. Yet they accumulate quietly in forecast instability, margin compression, and missed expansion opportunities.

Reactive Customer Success feels busy. It feels urgent. It often feels heroic. But economically, it is unstable.

The volatility tax

Why Customer Health Is a Financial Forecasting Tool

iliyana.stareva@gmail.com (Iliyana Stareva) — Tue, 17 Feb 2026 05:40:26 GMT

Customer health is still treated as an operational metric in most SaaS companies. It sits inside Customer Success dashboards. It’s reviewed in QBRs. It informs renewal discussions. But rarely does it influence financial forecasting, capital allocation, or board-level revenue planning.

I believe that's a mistake.

In an AI-enabled environment, customer health is no longer a sentiment score. It's a forward-looking revenue signal.

And once you treat it as such, it changes how you think about retention, growth, and capital efficiency.

Customer Health Has Been Under-Leveraged

From Customer Success Function to Growth Engine: The Leadership Shift Required

iliyana.stareva@gmail.com (Iliyana Stareva) — Mon, 02 Feb 2026 05:50:57 GMT

Many organisations say Customer Success is a growth engine. Very few are actually designed for it.

In practice, Customer Success is still treated as a defensive function: protect renewals, manage risk, keep customers “happy enough” to stay. Expansion is encouraged, but rarely owned. Growth is expected, but inconsistently enabled. And when targets are missed, the root cause is often unclear.

AI has not changed this reality on its own. What it has done is make the gap between intention and execution impossible to ignore.

AI gives Customer Success unprecedented visibility into customer behaviour, risk, and opportunity. But visibility alone does not create growth. Leadership decisions do.

This post builds on the earlier parts of this series — from the evolution of the CSM role, to AI-ready operations, to trust, governance, and board relevance — to answer a harder question: what actually has to change for Customer Success to become a true growth engine?

Why “Customer Success as a growth engine” is mostly a myth today

Why AI Will Finally Make Customer Success a Board-Level Topic

iliyana.stareva@gmail.com (Iliyana Stareva) — Wed, 21 Jan 2026 13:47:11 GMT

For years, Customer Success has struggled to earn a consistent seat at the board table.Not because it wasn’t important — but because it was hard to translate.

Too often, CS updates sounded like anecdotes instead of evidence, sentiment instead of signal, reassurance instead of foresight. Boards don’t lack interest in customers; they lack predictable, decision-grade insight.

AI changes that.

Not because it suddenly makes Customer Success strategic — but because it makes it legible at the highest level of the organisation.

This post builds on the earlier parts of this series, where I explored how AI reshapes the role of the CSM, the systems that support Customer Success, the experience customers have at scale, and the trust and governance required to make AI usable. The final step is understanding what all of this means at the board level.

What AI Changes About Leadership at Work (And What It Doesn’t)

iliyana.stareva@gmail.com (Iliyana Stareva) — Mon, 12 Jan 2026 11:57:33 GMT

AI is no longer a future capability. It's already embedded in inboxes, browsers, and workflows, quietly shaping how work gets done across organisations. And yet, many companies still approach AI as a tooling decision rather than a leadership one.

What is becoming increasingly clear is that AI does not fundamentally change what leaders are responsible for. Instead, it changes how quickly weaknesses become visible. Poor decision-making, unclear priorities, and lack of accountability were always present; AI simply exposes them faster.

This is why AI adoption feels uneven across organisations. The challenge is rarely access to technology. It's leadership readiness.

In earlier posts, I explored how AI reshapes the role of the CSM, the systems that support their work, and the customer experience at scale.

This post builds on that foundation by looking at what AI demands from leaders themselves.