If you lead a CS team, there's a conversation you've probably had with yourself.

We're not talking to the right people. We're one level too low. We're having product conversations when we should be having business conversations. And I'm not sure how to fix it.

It's one of the most common problems in CS. And one of the least directly addressed.

Most of the advice you'll find is about skill. Train your team to ask better questions. Coach them on executive presence. Run discovery differently. All of that is real, but it takes time you don't have, and it misses the actual problem.

The problem isn't skill. It's positioning.

Your CSM isn't talking to the CFO because the CFO doesn't think the meeting is worth their time. That judgment was formed before your CSM said a word. Before they even got the invite accepted. And you can't coach your way out of a perception problem inside the meeting. You have to change the perception before it.

This is where most CS leaders get stuck. They diagnose the symptom correctly but reach for the wrong tool.

The right tool is social proof.

Robert Cialdini documented this in his work on influence. When people are uncertain, they look to others in similar situations to calibrate their own thinking. They don't want opinions. They want evidence. What did someone like me do? What happened?

Your customers are uncertain all the time. Are we using this the right way? Are we behind where we should be? Are we getting what other companies get from this?

Your CSM can answer that. And when they do, with specifics, with real examples, with outcomes that map to the decision-maker's world, something shifts. They stop being the person who manages the account. They become the person who knows things the decision-maker doesn't.

That's the conversation executives make time for.

Here's the practical version of this for a CS leader who wants to move fast.

Step one: Stop waiting for marketing to build the assets.

The case studies your marketing team produces are built for sales. Polished, generic, six months in the making. Your team needs something different. A simple internal document. Two to three sentences per customer. The situation they were in, what changed, what the result was. Your CSMs can build this themselves, from memory, from their own accounts. Start there. Done in a week.

Step two: Train one opening move.

Social proof lands hardest at the start of a conversation. Before the agenda. Before the update. Before anything else. Teach your team this move: open every decision-maker meeting with a reference to a similar company. "Before we get into today, I wanted to share something we saw with a company at your stage last quarter." Two sentences. Then the example. That one move reframes who your CSM is before the meeting properly begins.

Step three: Run one story session per month.

The CSMs with ten years of experience carry these stories naturally. They've lived them. Newer CSMs haven't, but they work at a company that has. Once a month, spend thirty minutes as a team. Each person shares one customer story. What happened, what they did, what the outcome was. Over time, every CSM on your team carries the collective experience of everyone in that room into every meeting they take.

You can't give someone a decade of experience overnight. But you can give them access to yours.

That's what repositioning actually looks like in practice. Not a training programme. Not a new meeting framework. A team that walks into every decision-maker conversation with evidence that they've seen this before and know what happens next.

Executives make time for that person.

Make sure that person is yours.

At Startdeliver we help CS teams build the kind of customer insight that makes these conversations possible. Join us live at startdeliver.com/webinars