Five talks.
One original voice.

I did not set out to create an industry. I set out to fix a support organization that had 450 open cases sitting in a database when I arrived, and a CEO who told me we had "narrowly dodged a bullet." My response was that he had been hit with an Uzi. I felt fine saying that, because I knew I could fix it — and I knew exactly where to start.

What followed over the next several years at Vantive CRM was not a methodology. It was a series of convictions acted upon: that engineers who hated calling support were the right people to work in support. That a world-class support organization should have a low call volume, not a high first-call resolution rate — because if something could be solved in one call, the call should never have occurred. That customer success was not a department — it was a culture, an attitude, and a corporate goal. That the person responsible for a customer's success should be compensated for the customer's success, not for your revenue.

This talk traces that story from its actual beginning — not from Vantive, but from a basement EDI operation in a trucking terminal in 1990, where the ideas that would eventually become Customer Success were first taking shape without a name. It moves through the Harbinger years, where the services organization became the primary revenue and lead generation engine, and into Vantive, where we built something that had never been built before and called the person running it a Customer Success Manager for the first time.

The Cisco story is in here. So is the shuttle story. So is the moment I finally understood what we had actually built — not a program, but a religion. And I can tell you that none of us, in that moment, had any idea that the movement we were starting would employ four million people thirty years later.

This talk is the one for audiences who have been working in CS for years and have never heard where it actually came from. It is also for founders and revenue leaders who have been told that CS is a cost center that scales with headcount. Both of those things are wrong, and I have thirty years of evidence.

I want to say something that I have been watching become true for twenty years and have not said publicly until now: the Customer Success industry lost the plot.

It did not lose it maliciously. It lost it the way most good ideas lose their way — through scale, institutionalization, and the very human tendency to turn a philosophy into a job title and call it done. CS became a department. The CSM became an account manager with a better business card. And somewhere in that transition, the original idea — that customer success is the organizing principle of the entire company, not a function within it — got quietly buried under health scores and QBR decks.

I know what it looked like when it was right, because I was there when we built it. The Customer Success Manager at Vantive did not manage relationships. She owned outcomes — across sales, engineering, product, finance, training, and executive sponsorship — for accounts she did not control and could not compel. She succeeded or failed based on whether the customer actually achieved what they set out to achieve.

This talk is a direct challenge to the CS organizations that have settled for account management in a better outfit. It explains what was actually intended, why it matters that we got it wrong, and what it takes to build it right — starting with the question of whether CS in your company is a philosophy that the whole organization lives, or a department that the whole organization ignores.

I will not be gentle about this. But I will be specific, because the antidote to a bad idea is not a better slogan. It is a better design.

This is the one where I get specific.

Not framework-specific. Operationally specific. The kind of specific that only comes from having built the thing, made the mistakes, and had to defend every decision to a skeptical executive team that did not always believe me — until the numbers came in.

Here is what I mean. When I arrived at Vantive, I had a budget for twelve support engineers at $60,000 a year. I hired six at $100,000 a year, and I hired people who had never worked in support before — whose primary qualification was that they genuinely despised having to call a support organization. My executive team thought I had lost my mind. Within weeks, they were the best support team in the industry. By the end of the year, we were closing every day with fewer than ten open cases in the database, had built a customer portal and a solutions database from scratch, and were translating every response into the customer's language of choice. That last capability took two hours to implement, once I suggested it to the team.

This talk walks through the full operational architecture of what we built at Vantive: the kickoff meeting process, the expectations module in the CRM, the corrective action requirement on every closed case, the individual customer surveys tied directly to each recorded expectation, the six-month review cycle, and the 300% revenue lift that came from accounts where a CSM was assigned versus those where one was not.

It also covers the things that did not go as planned. The audit we nearly failed because our first-call resolution rate was too low — and why we were right to challenge that finding. The customers who were genuinely uncomfortable when we asked them to define how they would measure their own success. The behavioral change that was hardest to make: teaching a services organization that their job was not to serve. It was to lead.

AI is automating the transactional work of Customer Success. The QBR preparation, the health score monitoring, the renewal reminder cadences — these are not going to require a human being for much longer, and in many organizations they already don't. What remains when you remove the administrative layer from the CSM role is a question that most CS organizations are not yet prepared to answer.

I think I know what the answer is. I have been working on it, in one form or another, since 1996 — and more recently, I have been building it into the architecture of a company from the ground up.

The CS leader of 2030 is not a scaled-up version of today's VP of Customer Success. She is closer to a Chief Operating Officer for customer outcomes — someone who sits at the executive table not because CS advocates for a seat, but because the entire company's revenue model is designed around what she is responsible for. She does not run a department. She runs a philosophy.

This talk covers what I believe that transition requires: a different hiring profile, a different reporting structure, a different relationship between CS and product, and a different understanding of what "designing for customer success" actually means when you take it seriously. It draws on the original design intent at Vantive, on what I have watched the industry get right and wrong over thirty years, and on what I am building right now at Vision Intelligence — where the CS philosophy is not a function but a feature of the platform itself.

The question I leave the audience with is not "how do you improve your CS organization?" It is: "Is your company designed, at its foundation, to make your customers successful — or have you just hired people to manage the consequences of a company that is not?"