When Sales and CS share the same customer: the commercial ownership problem

There's a meeting that happens in most SaaS companies at some point, usually when revenue is starting to get complicated. Someone in finance or leadership asks: "Whose number is the expansion revenue on this account?" And the answer is either immediately obvious, or a room-full of silence that confirms the problem.

The commercial ownership question (who owns the customer relationship when both Sales and CS are involved) is one that organisations delay answering for longer than they should. Partly because it feels like a nice problem to have (you have expansion opportunities!), and partly because the answer invariably requires someone to give something up.

---

How the overlap usually develops

In the early days, the picture is simple. Sales wins the deal, hands it to CS, and the relationship is clear. CS owns the customer. Sales moves on to the next deal.

Then a few things happen that complicate it:

The customer grows. An expansion opportunity appears: a new division, a new use case, more seats. Is that a CS conversation or a Sales conversation? In most organisations without a clear model, it becomes both, which usually means neither happens well, or they step on each other, or the customer is approached by two people on the same team with different messages and different agendas.

Sales introduces an Account Executive model. Now an AE owns a portfolio of existing accounts for expansion. They are measured on expansion ARR. CS is measured on retention. The customer has two named contacts at your company who are technically on the same side but have structurally different incentives.

Compensation gets entangled. CS leaders start advocating for CSMs to have expansion targets. Sales leadership pushes back. Everyone disagrees about where the boundary should be, and the customer (who just wants a coherent relationship) ends up in the middle.

---

The three models (and what each costs)

There's no universal right answer here. But there are three archetypal models, each with a clear set of trade-offs.

Model 1: CS owns expansion. CSMs are responsible for identifying and closing expansion opportunities. They have expansion targets. Sales is involved only for net-new logos. This keeps the customer relationship coherent: one primary contact, one commercial narrative. The cost is that you're asking CSMs to develop sales skills that aren't always natural to the role, and you need to comp them for commercial outcomes alongside retention outcomes. It can also mean slower expansion cycles if your expansion deals are complex.

Model 2: Sales owns expansion. An AE or account manager owns the commercial relationship for the existing base. CS is a retention and adoption function with no commercial targets. The advantage is commercial focus and specialised selling skills. The cost is relationship complexity: the customer gets two contacts with different agendas, and the AE may not have the product depth or relationship history to run a persuasive expansion conversation. Handovers between CS and Sales on expansion opportunities are notoriously fraught.

Model 3: Shared model with clear swim lanes. CS identifies expansion signals and surfaces them to Sales. Sales runs the commercial motion. CS facilitates from a relationship perspective. This sounds collaborative, but in practice it lives or dies on whether the compensation model aligns with the collaboration. If CS is rewarded for identifying expansion but not for closing it, the incentive to surface signals is weak. If Sales gets full credit for expansion that CS surfaced and facilitated, resentment builds quickly.

The honest answer is that most companies are running an accidental version of one of these models, not a designed version.

---

What the customer experiences

Underneath the internal politics is a customer experience question that tends to get overlooked.

Customers don't think about your org chart. They think about their relationship with your company. When that relationship has two primary contacts (one who talks about outcomes and adoption, one who shows up when it's time to talk about money), the seams show.

The best expansion conversations I've been close to happened when the customer didn't notice the commercial moment because it felt like a natural extension of the existing relationship. The CSM, or the AE-plus-CSM pairing, had built enough context and trust that a conversation about new budget felt like a logical next step, not a sales call.

The worst ones happened when a sales contact appeared from nowhere, three months before renewal, with a deck about an expansion product that the customer's CSM had apparently never mentioned. The customer felt sold at, not partnered with. They ended up feeling like two different departments were talking to them.

---

Where CS Ops sits in this

Whichever model you run, CS Ops is what makes it legible.

If CS owns expansion: you need systems that track expansion signals (product usage, stakeholder feedback, contract limits approaching, new use case conversations) and surface them to the right CSM at the right time. You need compensation reporting that can split retention and expansion outcomes. You need playbooks for how a CSM-led expansion conversation should run.

If Sales owns expansion: you need a clean mechanism for CS to pass expansion signals to Sales without it feeling like a one-way information feed. You need clarity on what information Sales needs from CS before running an expansion conversation. You need to avoid the situation where Sales runs an expansion motion without CS input and damages a relationship CS has spent a year building.

If you're running a shared model: you need the compensation model to actively incentivise the collaboration rather than just describing it. And you need clear ownership of the decision: if CS and Sales both think they should be running a given commercial conversation, someone senior needs to be able to adjudicate that quickly.

The common failure mode is designing the model at the strategic level and then leaving the operational details to sort themselves out. They don't.

---

The question worth answering first

Before building the compensation model or the swim lanes or the playbooks, it's worth answering one question clearly: what relationship model does the customer need from us?

For high-touch enterprise accounts, they often want a single point of accountability: one person who owns the commercial and success relationship, supported by a team behind them. For scaled or tech-touch accounts, the relationship model is lower-stakes and the handover risk is lower.

The answer to the ownership question is usually customer-segment-specific, not universal. Which means the right answer for your enterprise segment may be different from the right answer for your mid-market segment, and designing one model for both is where the complexity usually bites.

---

The short version: The commercial ownership problem (who owns the customer when Sales and CS are both involved) usually gets resolved by accident rather than design. The three models (CS owns expansion, Sales owns expansion, shared model) each have clear trade-offs. Whichever you pick, CS Ops is what makes it operational rather than theoretical: the systems for surfacing signals, the compensation structure that matches the intent, and the playbooks for the moments when it gets complicated. The customer experience question (do they feel partnered with or sold at?) is worth running as a gut-check on whatever model you land on.