The Archive

Leadership

The C.A.R.E. Framework

There are countless frameworks designed to make us better sellers.
Some teach us how to challenge a customer’s thinking. Others help us qualify opportunities, navigate complex buying committees, forecast more accurately, or execute with more discipline. I’ve studied many of them over the years and continue to use principles from several today.

They’ve made me a better Account Executive.
But over time I realized they all had something in common.

They taught me what to do.
Very few taught me who I wanted to become while doing it.
That realization didn’t happen overnight. It developed through thousands of conversations—with enterprise customers, internal teammates, implementation partners, executives, entrepreneurs, and even while building a small business alongside my partner, Erica.
No matter the setting, one word kept surfacing…

Care.
Not care as sentiment.
Not care as softness.
Care as discipline.
Care as intentionality.
Care as choosing to understand before trying to persuade.

Eventually I realized that care wasn’t simply something I valued. It had quietly become the philosophy behind nearly every meaningful relationship I’d built.
That’s where the C.A.R.E. Framework began.
Not because I wanted another acronym.
Not because I thought the sales world needed another methodology.
Because I finally had language to describe the philosophy that had been guiding me all along.

Frameworks Organize Conversations. Philosophy Shapes Behavior.

One of the things I love most about sales is that there is always something new to learn.
The Challenger methodology fundamentally changed how I think about bringing insight to customers. MEDDICC refined how I qualify opportunities and navigate complex buying committees. Mutual Action Plans improve alignment. Project management disciplines improve execution.

Every framework has made me better.
The C.A.R.E. Framework isn’t meant to replace any of them.
In fact, I believe it makes each of them stronger.

Frameworks organize conversations. Philosophy shapes behavior.

Frameworks tell us what information to uncover.
Philosophy determines the posture we bring into the conversation while uncovering it.
Customers rarely remember the framework you used.
They remember how they felt.
Whether they felt heard.
Whether they felt understood.
Whether they believed you genuinely cared about helping them solve a problem—not simply closing a deal.
For me, that’s where genuine care becomes a competitive advantage.
And in a world increasingly shaped by automation and AI, it may become one of the few competitive advantages technology can never replace.

C — Customer-Centered Discovery

Most people think of discovery as the first stage of a sales process.
I don’t.
I think it’s the beginning of a relationship.

Early in my career, I approached discovery the way many sellers do.
Ask thoughtful questions.
Uncover pain.
Qualify the opportunity.
Move toward a demo.

Over time I noticed something.
The conversations that created the strongest partnerships rarely followed a script.
They were driven by genuine curiosity.
Customers would occasionally stop and say something that always caught my attention.
“No one has ever asked me that before.”

Those moments didn’t happen because I had ‘better discovery questions’.
They happened because I stopped treating discovery as a prerequisite to selling.
I started treating it as the work itself.
I’ve never walked into a meeting hoping to get to the demo.
I’ve walked into meetings hoping to leave understanding something I didn’t understand when I walked in.

Discovery isn’t about uncovering pain. It’s about earning the right to understand it.

When customers believe you’re genuinely trying to understand their world—not simply qualify an opportunity—they become more transparent.

Transparency creates trust.
Trust creates collaboration.
Collaboration naturally reveals many of the things frameworks like MEDDICC ask us to uncover.
Metrics become conversations about what success actually looks like.

Economic buyers emerge because you understand how decisions are made—not because you asked, “Who’s the decision maker?”

Champions aren’t identified because you went looking for one.
They’re earned because someone believes you’re invested in solving their problem.

Pain isn’t uncovered because you followed a script.
It’s uncovered because curiosity invites honesty.

Customer-Centered Discovery doesn’t replace MEDDICC.
It creates the environment where MEDDICC happens naturally.

The same is true of Challenger.
Teaching, tailoring, and leading conversations only works when customers first believe your intentions are aligned with their success.

Without trust, insight sounds like a pitch.
With trust, insight becomes valuable.

A — Align Solutions to Pain Points

Often sellers are trying to align solutions throughout every customer conversation.
That isn’t wrong.
A customer has a problem.
We represent a solution.
Connecting the two seems like the obvious objective.

But I’ve found that chasing alignment too early often limits it.
When I’m already thinking about which feature solves which problem, my curiosity naturally begins narrowing.
Instead of fully understanding the customer’s business, I’m subconsciously searching for confirmation that my product fits.
I’ve learned to do something different.

I keep alignment in the background while keeping understanding in the foreground.
The deeper my understanding becomes, the more naturally alignment happens later.
For me, understanding develops in layers.

Level One: Understand the current state.
How are things done today?
Where are the inefficiencies?
What’s frustrating?
What’s slowing progress?

Level One and a Half: Understand how they arrived here.
Why were these systems chosen?
Why were these investments made?
What’s working well?
What should never change?

Level Two: Understand impact.
How do today’s barriers affect revenue?
Customer experience?
Operational efficiency?
Employee engagement?
Strategic priorities?
Where does one challenge begin creating several others?

Only then do I begin asking a different question.
What does success actually look like?
Not immediately after implementation.
But six months later.
A year later.
Three years later.
If this initiative succeeds…
What becomes possible that isn’t possible today?

By this point something has changed.
We’re no longer trying to fit a product into a problem.
We’re collaborating on a better future.

Products don’t solve problems. People solve problems.

Products simply help make those solutions possible.
That’s authentic alignment.
Not because it was forced.
Because we uncovered it together.
Transparent truth creates authentic alignment.
And transparent truth only exists where trust already lives.

R — Resourceful Partnership

“Partnership” might be one of the most overused words in business.
Real partnership isn’t a title.
It’s behavior.

It means both parties are genuinely invested in one another’s success.
Sometimes that means recommending your own solution.
Sometimes it means an alternative approach.
I’ve never believed every customer should become my customer.
If another solution genuinely serves them better, honesty should outweigh self-interest.
Trust built through transparency lasts much longer than trust built through persuasion.

Partnership also means becoming resourceful.
Introducing customers to internal experts.
Connecting them with existing customers.
Sharing articles.
Providing research.
Making introductions.
Bringing implementation teams into conversations early.
Helping people think through challenges—even when those conversations don’t immediately move a deal forward.

I’ve often thought of it like a dance.
Sometimes I lead.
Sometimes my customer leads.

When I lead, my responsibility is to create clarity.
When they lead, my responsibility is to stay present enough to follow where they need to go.
Neither person is trying to control the dance.
Both are trying to stay connected.

Closing the business isn’t the end of the dance. It’s simply the end of the first song.

The partnership is just beginning.

E — Execution with Empathy

Execution doesn’t begin after a contract is signed.
It begins with the very first promise you make.
“I’ll send that article.”
“I’ll make that introduction.”
“I’ll follow up tomorrow.”

Every commitment is an opportunity to strengthen or weaken trust.
Execution is simply the repeated act of honoring those commitments.
But execution without empathy eventually becomes project management.
Execution with empathy becomes stewardship.

Customers aren’t simply implementing software.
They’re navigating change.
Managing competing priorities.
Working through procurement.
Negotiating legal requirements.
Introducing new workflows.
Supporting their own teams.
Answering to leadership.
Balancing risk while trying to improve outcomes.

Those realities deserve empathy.
The barriers that existed before the sale don’t disappear after signature.
In many cases they become even more visible.
Executing with empathy means remembering the vision that brought everyone together in the first place.

It means staying reliable.
Remaining present.
Remaining curious.
And continuing to advocate for the customer’s long-term success long after the contract is signed.

The goal was never simply getting to “yes.” The goal was helping someone create meaningful change.

Closing Thoughts

I don’t expect everyone to adopt the C.A.R.E. Framework.
That’s not really the point.
Every professional should develop a philosophy that guides how they show up in their work.
This one happens to be mine.

The frameworks I use will continue to evolve.
Technology will continue to evolve.
Artificial intelligence will continue changing how we research, communicate, and execute.
Sales methodologies will continue improving.

What I hope never changes is my belief that genuine care remains one of the greatest competitive advantages a professional can have.
If I can continue building relationships where people feel understood before they feel sold to…
If I can continue creating partnerships rooted in honesty, curiosity, and stewardship…
If I can continue helping organizations solve meaningful problems while remaining true to who I want to be…
Then I’ll consider that a career worth being proud of.

Customers may not remember every presentation I gave.
They won’t remember every pricing conversation.
They probably won’t remember every feature demonstration.
But they’ll remember how they were treated.
They’ll remember whether they felt understood.
That’s the standard I want to hold myself to.
That’s the professional I’m still trying to become.
And that’s the foundation beneath every framework I’ll ever use.
That’s C.A.R.E.