What I believe about CS leadership, why most organizations are building it wrong, and what it actually costs them.
I have watched companies leak revenue for years — not because they lacked talent, not because the market turned against them, but because the people making decisions about the client relationship were the furthest removed from it. Titles get handed down through org charts. Salaries get defended in budget cycles. Neither one guarantees that the person holding them understands what is actually happening at the account level — what clients are signaling, what is eroding quietly before any metric flags it, what an expansion opportunity looks like six months before it becomes a pipeline entry.
I have never led that way. I will not. The hierarchy I respect is built on proximity to the work, clarity of thinking, and the willingness to say what is true in rooms where the truth is inconvenient. Everything else is furniture.
The conventional revenue architecture of most subscription businesses is structurally incomplete. Sales owns acquisition. Finance owns the model. CS owns the relationship — and then gets evaluated on whether the relationship held rather than on what the relationship knew. That is not a talent problem. It is a design problem. It is a belief problem. It is the organizational equivalent of having the best intelligence operation in the company and filing its reports in a drawer.
CS sees what algorithms miss and what Sales cannot see — because our mindset is fundamentally different. Sales is transaction-oriented by design and necessity. CS is relationship-oriented by nature, which means we are reading signal continuouslty — behavioral shifts, organizational changes, the quality of trust in a room — long before any platform surfaces it as a risk flag. Leaders who fail to build that signal into their revenue model are not just underutilizing a function. They are flying blind on the half of the business that determines whether next year's forecast holds.
Every vendor on the market right now is selling some version of the same story: AI-powered health scores, automated churn signals, intelligent engagement triggers. The pitch is compelling. The dashboards are beautiful. The results, in most organizations, are marginal — because the technology is only as valuable as the operating discipline surrounding it, and right now, the discipline is what is missing.
I have built AI infrastructure inside a regulated enterprise environment — without a budget, without admin access, concurrent with managing a 24-account portfolio — because I understood that the goal was never the tool. The goal was the intelligence layer the tool makes possible. The goal was giving CS a systematic way to convert signal into revenue foresight, not a dashboard that someone looks at and moves on from. That distinction — between AI as decoration and AI as discipline — is the difference between an organization that adapts and one that buys software and calls it transformation.
The measure of CS leadership is not the quarter you saved. It is the system you built that kept saving quarters after you moved on. It is the CSM you developed who is now running their own book with the instincts you helped sharpen. It is the playbook that became standard operating procedure. It is the attribution framework that finally made CS-sourced pipeline visible to a CFO who had been making growth decisions without it.
I have always led this way — not because longevity is a virtue in itself, but because anything worth building is worth building to last. If the system only works when I am in the room, I have not built a system. I have built a dependency. The goal is always to make myself replaceable at the execution level so I can operate at the strategic level — which is where CS leadership has always belonged and has almost never been given the standing to function.
I have spent my career at the intersection of client trust and regulated risk — PropTech, FinTech, Payments — environments where a misread signal is not just a missed renewal. It is a compliance exposure, a contractual liability, a relationship that took three years to build and forty-eight hours to lose. That context does not make CS leadership harder in ways that slow you down. It makes you precise. It makes you systematic. It makes you unwilling to treat relationship management as a soft skill when the stakes attached to it are anything but soft.
The CS Intelligence™ framework I have built — the signal types, the N.O.V.A. operating system, the accountability structure — was not designed in theory. It was pressure-tested in exactly these environments, where the cost of not reading the signal was measured in revenue exposure and client confidence simultaneously. That pressure is not a liability I carry. It is the credential that makes everything I build credible.