Your Customer Experience Should Be Designed for Retention, Not Just Acquisition

Think about how much effort companies put into acquiring a customer.

Marketing campaigns are designed.

Sales processes are defined.

Opportunities move through stages.

Teams know what needs to happen next.

Progress is measured.

Revenue is forecasted.

Then the customer signs the contract.

And something strange happens.

Much of that discipline disappears.

The customer moves into an experience that often depends on individual people figuring out what to do next.

A good CSM might create an incredible experience.

Another might struggle.

Implementation might have a well-defined process, but what happens after onboarding is less clear.

Product, Support, Sales, and Customer Success each have their own priorities.

And somehow, all of that is supposed to produce retention.

I've spent much of my career wondering why we accept that.

If retaining customers matters as much as acquiring them, why haven't we put the same effort into designing the experience that produces retention?

Acquisition is only the beginning of the revenue relationship

I don't think companies are wrong to invest heavily in Sales.

New customers matter.

Without acquisition, there isn't a customer base to retain or grow.

But the sale is only the beginning of the financial relationship.

The customer still needs to achieve the outcome they purchased.

They need to develop confidence in the product and the company.

They need to change how they work.

They need to continue finding value as their priorities evolve.

And eventually, they need to decide whether continuing the relationship makes sense.

Those things don't happen simply because the customer signed a contract.

They happen because of what the customer experiences afterward.

Yet many organizations still manage acquisition with tremendous discipline while treating retention as an outcome they hope their people will produce.

We design the process that creates new customers. Why wouldn't we design the process that keeps them?

Consistency doesn't mean treating every customer the same

One of the most important lessons I've learned is that consistency doesn't come from hiring enough talented people.

Talented people matter enormously.

But when every CSM has to figure out how to deliver a great experience independently, the organization becomes dependent on individual judgment, experience, and effort.

Some customers get an exceptional experience.

Others don't.

And when a great CSM leaves, much of what made their customers successful can leave with them.

The answer isn't to script every interaction or remove human judgment.

It's to define the important moments in the customer journey.

What needs to happen after purchase?

What should the customer experience during the first meeting?

What decisions need to be made during onboarding?

What does First Value look like?

How do we help the customer achieve their goals?

How do we keep the relationship aligned as priorities change?

These are moments that matter to customer progression.

I call them Inflection Points.

Once they're defined, we can design the plays that support them.

Now the team doesn't have to invent the experience from scratch.

They have a shared understanding of what needs to happen, why it matters, and how to help the customer move forward.

The customer still gets a personalized experience.

But the quality of that experience no longer depends entirely on which CSM happens to own the account.

The customer doesn't experience your departments

Here's another problem with how companies approach customer experience.

We organize our businesses into functions.

Marketing.

Sales.

Implementation.

Customer Success.

Support.

Product.

Finance.

Each function has its own responsibilities, processes, metrics, and priorities.

That makes sense internally.

But the customer doesn't experience your departments.

They experience the seams between them.

A salesperson makes a commitment that Implementation doesn't know about.

Implementation completes its project, but the customer hasn't achieved the outcome they purchased.

Support resolves individual tickets without understanding the larger business problem.

Product makes a change that disrupts an established customer workflow.

Finance sends an unexpected invoice.

Customer Success is left trying to hold the relationship together.

From inside the company, these might look like separate operational issues.

To the customer, they're all part of one experience.

And every one of them can influence whether the customer stays.

That's why retention can't be designed inside Customer Success alone.

The company needs a shared understanding of the customer journey and the progression it's trying to create.

Different teams may own different parts of the work.

But the customer should experience one connected relationship.

Customer activity isn't the same as customer progression

This is where I think many customer experience frameworks fall short.

They describe what the company intends to do.

Kickoff meetings.

Training.

Implementation milestones.

Business reviews.

Support processes.

Customer communications.

All important.

But completing those activities doesn't necessarily mean the customer is making progress.

A kickoff can happen without creating alignment.

Training can be completed without changing how someone works.

A business review can take place without advancing a customer goal.

The activity happened.

The customer didn't necessarily move forward.

That's a critical distinction.

A customer experience designed for retention needs to answer a different question:

What needs to become true for this customer to move forward?

Maybe the customer needs to experience First Value.

Maybe they need to achieve a meaningful business outcome.

Maybe a new process needs to become an established habit.

Maybe an executive sponsor needs to reconnect the product to a changing business priority.

Whatever the moment, we should know what progression looks like.

And we should be able to see whether it happened.

That's how customer experience becomes something we can manage rather than simply describe.

Follow the revenue beyond the initial sale

The original version of this article made an argument I still believe strongly:

Companies need to follow all the money.

Not just the revenue associated with acquiring a customer.

The revenue associated with keeping and growing them.

Think about what happens when a company acquires a customer who isn't a good fit.

Sales gets credit for the deal.

But Implementation struggles to deliver.

Product gets pulled toward requirements that don't fit the broader market.

Support absorbs additional demand.

Customer Success spends disproportionate time trying to save the relationship.

Leadership gets involved.

Eventually, the customer may leave anyway.

The cost of that decision extends far beyond the CSM assigned to the account.

And the opposite is also true.

When customers achieve meaningful outcomes, develop established habits, and continue progressing, the financial contribution can extend well beyond the original purchase.

Renewal revenue.

Expansion revenue.

Lower costs to serve.

Longer customer relationships.

Potential advocacy and referrals.

That's why I believe customer experience belongs in the revenue conversation.

Not simply because happy customers are more likely to stay.

But because the way we design and execute the post-sale experience directly influences the economics of the business.

Retention should be visible before renewal

There's one more piece that I couldn't articulate as clearly when I originally wrote this article.

Designing the customer experience isn't enough.

We also need visibility into whether it's working.

Before the sale, we can look at a pipeline and understand where opportunities stand.

We can see what needs to happen next.

We can identify stalled deals.

We can connect that progression to potential revenue.

After the sale, we often have plenty of customer data but much less visibility into the progression producing future revenue.

We know renewal dates.

We track usage.

We calculate health scores.

We measure GRR and NRR.

But can we look across our customer base and see where customers stand in the journey?

What they have accomplished?

What needs to happen next?

Where progression has stalled?

And what revenue is connected to it?

That's the missing connection between customer experience and revenue management.

When we make customer progression visible, retention becomes something we can influence throughout the relationship instead of something we primarily evaluate at renewal.

A customer experience framework should become an operating system

This is ultimately where my thinking has changed the most.

Years ago, I believed companies needed better customer experience frameworks.

I still think frameworks are useful.

They help us understand the customer journey, identify gaps, and define what a good experience should look like.

But a framework alone doesn't ensure that experience actually happens.

Someone still needs to execute it.

Someone needs to know when an important moment has been missed.

Someone needs to understand what happens next.

Leadership needs visibility into whether the experience is producing the progression and revenue outcomes the business expects.

That's the difference between a framework and an operating system.

A framework helps you understand the business. An operating system helps you run it.

For post-sale, that means connecting the customer journey, Inflection Points, plays, progression, health, pipeline, and capacity into one system.

The journey defines the experience we're trying to create.

The plays help make it happen.

Progression tells us whether the customer is moving forward.

The pipeline connects that progression to revenue.

And capacity planning ensures the organization has the resources to deliver the experience consistently.

Now customer experience isn't simply a collection of good intentions.

It's something the company can design, execute, inspect, and improve.

Retention is a designed outcome

I don't believe companies lose customers simply because they lack talented people or don't care enough about customer experience.

Most of the teams I've worked with care deeply.

They work incredibly hard.

They want their customers to succeed.

But effort alone doesn't create consistency.

And a collection of disconnected departmental processes doesn't create a coherent customer experience.

That takes design.

It takes a shared understanding of what customers need to accomplish.

It takes plays that help them get there.

It takes visibility into whether progression is happening.

And it takes the ability to act when it isn't.

We already accept that kind of discipline when acquiring customers.

It's time we applied it to keeping and growing them.

Retention is a designed outcome.

The question is whether we've designed the system that produces it.