Who Owns the Post-Sales Customer Journey, and Why It Matters

Every company eventually runs into the same question: once a deal closes, who is actually responsible for what happens to the customer next.

Not which team touches them, all of them do, but who is accountable when the handoffs between sales, onboarding, success and support start to fray. That is the real question behind who owns the post-sales customer journey, and it is one most companies answer by accident rather than on purpose.

Session 5 of the PSA Studio Lounge put that question to six practitioners, and the conversation moved quickly past org chart boxes into something more useful: what authority this role actually needs, and how it should be measured. You can watch the full discussion on the session page.

The short version is that the panel converged on customer experience, with customer success at the center, as the right home. But the more interesting part of the conversation was about what that role should and should not be allowed to do.

Who should own the post-sales customer journey?

Alison Bukowski was the clearest voice on this. She said she would not place post-sales ownership anywhere other than a customer experience function built around customer success. She has seen the model work reasonably well when it sits in enablement, struggle in marketing, and fail outright in sales, where the appetite and time simply are not there. Her proposal goes further: a chief customer officer overseeing customer success, customer advocacy and customer support as three connected arms of one function.

Diana Gabroveanu agreed, but added a caution. Even where a CX function exists on paper, it often has no operational power. It can define process and map the ideal journey, but it is the CSM who holds the actual relationship and the ability to execute. She described the CSM as a kind of family doctor who carries the full history of a customer, every engagement, every program, every prior conversation, which is what makes it possible to articulate renewal value without starting from scratch each time.

Diana also gave a concrete example: a 24-person company running four CSMs, where the model holds up because someone is intentionally given few enough accounts to sustain that continuity. Her point was that this works at small scale too, as long as a company is deliberate about who owns the relationship rather than letting it diffuse across whoever happens to be available.

Does it matter where this role sits on the org chart?

Erin Felton pushed back on the framing of the question itself. She argued that where this function reports matters less than what it is given the authority to do. Regardless of company size, she said the role needs three things: visibility into what happened presale, authority across functions when handoffs break down, and a shared view of growth metrics rather than metrics owned separately by each team.

This came up directly in the session: the panel's working word for the role, conductor, was questioned partway through. Erin reframed it as glue instead, something that holds functions together at the seams without taking over the work each function already does well. Kristine Kukich extended that image, noting that customers get pulled at from every direction, product, marketing, success, community, and someone needs to notice when a customer has been touched too many times in too short a window and call a pause.

Why does the first week matter so much?

Angela Sutton grounded the discussion in activation data. She pointed to research showing that most SaaS activation happens, or fails to happen, in the first seven days, and that a large share of churn risk concentrates in the first three months.

Her argument was that this is precisely why someone needs to actively shepherd a customer through that early window rather than leaving it to whichever team happens to be in contact. A silent customer in this period is not a safe customer. The practical implication, which Angela also raised, is that if a dedicated role cannot be hired, a product manager or similarly placed person can partially fill the gap by staying in close, frequent contact with sales and support and reviewing major accounts regularly.

How should this role be measured?

The panel was clear that no single metric does the job. Kristine Kukich argued that no one number holds up across the whole customer journey, because each stage is trying to deliver something different. A customer health score can work as an aggregating measure, she said, but only if it is built from the right signals, not treated as a shortcut.

Alison Bukowski pushed the group to interrogate every metric with a simple question: so what. She warned against vanity metrics that look good on a dashboard but do not tell anyone what to do next, and argued that most organizations never ask customers directly what success looks like to them, which means the metrics they do track are disconnected from what the customer actually wants.

Watch the full session to hear the panel in their own words.

Frequently asked questions

Should post-sales ownership sit in customer success or in revenue operations?

The panel's consensus was customer success, inside a broader customer experience function. Alison Bukowski argued this is the only place she has seen it work consistently well, and the group agreed CS should also be accountable for revenue outcomes like retention, since retention is one of the biggest revenue drivers available.

Does this role need formal authority over other teams?

Not in the sense of being a boss. Erin Felton's framing, which the panel adopted, is that the role is glue: it owns handoffs, shared signals and cross-functional trade-offs, and steps back once an issue falls clearly inside one function's territory.

What should a small team do if it cannot hire a dedicated person for this?

Diana Gabroveanu noted that small companies often have an advantage here, since one naturally customer-focused CSM with strong listening skills can run this model for a limited set of accounts. Angela Sutton suggested a product manager can partially cover the gap through frequent, direct contact with sales and support.