For most of my career, I sat on the vendor side of the table. I led the teams whose job was to keep customers happy, renewing, and expanding. I believed I understood what made that work.
Then I became the customer, and much of what I believed got tested.
At a Fortune 100 pharmaceutical company, I was responsible for IT delivery across six global functions and more than 190 technologies. I was not managing one vendor relationship. I was living inside dozens of them at once.
Most of them let me down.
Products we depended on every day came with almost no real engagement from the companies that sold them. Their teams talked at us. They showed up to defend their price, not to understand our business. Some had won hard, multimillion-dollar deals and then stumbled inside the first ninety days, before they had earned a thing.
What struck me was not that vendors failed. It was that they failed the same way, again and again.
The pattern barely changed from one company to the next. A strong sales process won the deal. Then the energy that closed it simply evaporated. Onboarding became a checklist. Value was assumed instead of proven. By the time anyone noticed the relationship had gone cold, we were already sketching out a replacement. In a few cases, the vendor did not find out they were being replaced until years later, before their original rollout was even finished.
I watched capable, well-funded companies lose customers they had every reason to keep. And I kept circling the same question.
Why had it felt so different where I came from?
Years earlier, at an early martech company, I had led the organization responsible for our largest customers, roughly 65% of a $100 million revenue base. At the time, I did not think of what we did as unusual. We just did the work.
The results were hard to argue with. For six straight years, not one of those customers left. Not one. We grew the accounts and held our margins, and we could tell our leadership what retention and revenue would look like a year out and be right within a few points.
Looking back from the customer's chair, I finally understood what we had built. It was not a roster of extraordinary people, though the people were extraordinary. We had built a system. We just never called it that.
The relationship never depended on who happened to own the account. Expectations were clear. Progress was visible. Customers always knew where they stood and what came next. Success was not something we hoped for as renewal approached. It was something we produced, on purpose, week after week.
Which left me with a question I still have not fully let go of. If we could do that, and barely knew we were doing it, why can so few companies reproduce it on purpose?
The first time I tried to build it on purpose, the company was nearly out of time.
I joined a tech-enabled SEO agency with a few months of runway and a business that was losing money. We could not hire our way out or sell our way out. Worse, we were losing customers at almost the exact moment our work was about to pay off. Our results tended to arrive around month eight. Our customers tended to leave around month seven.
On paper, it looked like a retention problem. It was not. It was a progression problem.
Our customers were not leaving because the product failed them. They were leaving because they never made it far enough to see it work.
So we rebuilt the experience around the wait. We could not make search engines move faster, but we could change everything the customer felt along the way. We reset expectations on the first call. We created small, early wins so momentum was visible long before the big results landed. We built a rhythm of communication that always answered three questions: where are you, what have we accomplished, and what happens next.
It worked because it solved the real problem. Our customers did not need faster results. They needed to believe results were coming.
Trust, I learned, is not built when customers finally get what they came for. It is built while they are waiting for it.
As customers came to see the path, they stopped leaving. And something else shifted. They stopped behaving like buyers waiting to be impressed and started behaving like partners who understood the plan.
Somewhere in that scramble to save a company, I drew my first customer journey map. I had no language for it yet. I only knew that, for the first time, I had designed the entire post-sale experience on purpose, from the first meeting to the renewal, as one deliberate thing.
I did not know it at the time, but these experiences became the foundation of what would eventually become the Post-Sale Operating System.
In the years that followed, I kept seeing the same pattern in different forms. Different companies. Different products. Different customers. The visible problems changed, but the underlying breakdown rarely did. Customers were surrounded by activity without gaining enough clarity, confidence, or momentum to keep moving forward.
Eventually, I stopped asking why customers churned. By the time a customer leaves, the most important failures have already happened. I became more interested in a different question: What must happen after the sale so customer progression becomes predictable?
That question became an obsession. This book is the result. The challenge facing most companies is not a lack of effort, intelligence, or commitment after the sale. It is the absence of a system that turns all of that effort into consistent customer progression.
Ask me directly, or tell me what happened when you tried it. The best questions get answered in the open, and results from the field shape the next edition.