Stop selling features. Start solving business problems.

Hi there,

One of the biggest shifts I’ve made since moving into Strategic Customer Success is changing how I talk about our products.

I spend less time describing what a feature does and more time thinking about the business problem it can help solve.

Over the past few months, I’ve been building ROI guides for some of the products I support. And the exercise has forced me to ask the same question over and over:

What business problem does this product actually solve?

Because your customer probably doesn’t care that you released a new dashboard, API, integration, or module.

They care about reducing costs, saving time, improving productivity, reducing risk, or making better decisions.

And as CSMs, we need to connect those dots.

Start with the business problem

Take meeting room analytics as an example.

I can show a customer a dashboard with room utilization, booking patterns, capacity, and occupancy.

But what can they actually do with that information?

If a real estate leader sees that their 12-person conference rooms are consistently being used by three or four people, they can start asking better questions:

• Do we have the right mix of meeting spaces?

• Could some larger rooms be converted into smaller collaboration spaces?

• Could we accommodate more employees without adding square footage?

• Could this data inform future real estate decisions and reduce costs?

The analytics become valuable when they help the customer make better decisions about their real estate portfolio.

Keep asking: “So what?”

This is one of the simplest exercises I use when trying to articulate value.

Take automation:

We automated a process.

So what?

The customer no longer has to complete it manually.

So what?

Their team saves hours every week and reduces errors.

So what?

They can spend that time on higher-value work.

Now we’re talking about productivity and operational efficiency.

A simple framework I use is:

Feature → Capability → Change in process or behavior → Measurable result → Business impact

The further you can move to the right, the stronger your value story becomes.

Here’s what this looks like with a real customer

One of my customers needed better visibility into who was actually coming into their offices after introducing a new return-to-office policy.

We could have approached the conversation as an integration project.

Instead, we focused on the question they were trying to answer.

Are employees actually coming into the office, and how are they using the space when they do?

Reservation data showed planned attendance. Badge data showed actual attendance.

Bringing those datasets together gave their real estate team a much better picture of attendance patterns and space utilization, which they could use to make workplace decisions.

Same technology. Much stronger business conversation.

Another example: automated check-ins

This same customer had another problem.

Employees would reserve desks and never show up. Those desks remained unavailable for other employees, creating frustration and making the workplace feel more constrained than it actually was.

We implemented automated desk check-ins.

The result?

Their desk “bumping” rate dropped from roughly 33% to less than 6%.

When I talk about that success, I focus on the impact: employees had more reliable access to desks when they came into the office.

That’s a much more meaningful story than saying, “We enabled automated check-in.”

This changes how I approach expansion, too

Recently, I was talking with another customer about a new module we’re developing.

Before showing them what it could do, we spent time understanding how they manage the process today.

• What information are you tracking?

• Where does it live?

• What requires manual work?

• What information is difficult to access?

• What would you like to do that you can’t do today?

Those questions gave us a much better way to evaluate whether the module could actually solve their problems.

And when there’s a strong connection, the expansion conversation becomes much easier.

Bring this into your Success Plans

This is also one of the concepts I spend a lot of time on in my Success Plan Playbook: learning to separate product outcomes from business outcomes.

A product outcome might be launching a module, increasing adoption, enabling an integration, or automating a workflow.

I always want to take the conversation one step further:

What does achieving this allow the customer to do better?

For example:

Enable an integration → combine reservation and attendance data → understand how employees are actually using the office → make better space planning decisions → optimize real estate investments.

That final connection is what I want reflected in my Success Plans because it gives me a much stronger way to talk about value with executive stakeholders.

Try this with one of your customers

Pick one feature your customer uses today.

Then ask yourself:

So what?

Keep asking until you reach something the business actually cares about.

• Reduced cost.

• Time saved.

• Increased revenue.

• Improved productivity.

• Reduced risk.

• Better decisions.

If you’re still talking about adoption, features, integrations, or configuration, keep going.

Strong product knowledge matters most when you can connect what your product does to a problem your customer needs to solve.

And that’s a skill I’m continuing to work on every day.

Best,

Erika