Director of Customer Success: What the Job Owns (2026)

A Director of Customer Success runs the customer success function at the layer between the managers who run teams and the executive who owns the number. In practice the job is three things: hiring and keeping the people, setting what the team is accountable for, and being the person senior leadership asks when retention moves.

What it owns beyond that is genuinely unsettled, and not in a vague way. Two companies hiring for this exact title this week describe opposite mandates.

One posting says the Director's team will "partner closely with Business Development, who owns NRR, GRR, and expansion, by providing account health, risk signal, and expansion readiness." In that company, customer success supplies the evidence and another function owns the revenue.

Another says the Director will "own our entire book of business" across a geography, managing multiple teams and taking "ultimate responsibility" for it.

Same title. One feeds the number, one carries it. If you are weighing this job, or writing the role, that is the first thing to settle and the thing most people never ask.

What the job owns, consistently

Across the Director postings live at the time of writing, three things appear in every single one.

Hiring and building the team. Every posting, without exception, and the same is true one level down at manager. This is the part of the job people underestimate when they take it. Whatever else is on the scorecard, a Director who cannot recruit, retain and promote will fail at everything downstream of that.

Expansion. Every Director posting names expansion, upsell or account growth as an outcome the team is accountable for. Not one of them attaches a quota to it, which is the tension this whole role runs on and which we come back to below.

Cross-functional work and strategy. Almost universal, and worth reading carefully because the phrasing varies in a way that matters. Some postings mean "align with product and sales". Others mean "shape the strategy for how we engage customers at scale". Those are different jobs with the same words.

Below that, the picture splits. Renewals appear in most but not all. Coaching appears in roughly half, which is lower than most people would guess for a leadership role, and notably lower than at manager level. Executive or board reporting appears in under half, and when it does it is usually the clearest signal that the role is genuinely senior rather than a retitled manager.

What the job does not own

This is the more useful half, because absence is easier to trust than proportion in a small sample, and because it contradicts how the role is usually described.

No quota. Not one Director of Customer Success posting uses the word quota, and none names a revenue target. One level down, at manager, the word quota is equally absent and a single posting names a revenue target. For a field that has spent five years arguing that customer success is a revenue function, the way it actually hires its leaders barely reflects that at all.

Not the playbook. No Director posting mentions designing playbooks or owning the operating process. At manager level, both appear repeatedly. The person who decides how the team works day to day is the manager, not the Director.

Not the forecast. Forecasting appears in one Director posting and in roughly a third of manager postings. If you are expecting the Director role to be where renewal forecasting lives, it generally is not.

Put together, these absences describe something specific. The Director is accountable for outcomes they do not have a number for, using a process they do not design, based on a forecast they do not own.

That is not a criticism of the role. It is the actual shape of it, and knowing the shape before you accept it is the difference between a good two years and a frustrating one.

The expansion trap

Every Director posting names expansion. None attaches a quota. Those two facts together are the single most important thing on this page.

It means the Director is answerable for growth without the instruments that normally come with being answerable for growth: no number of their own, no pipeline they control, and frequently no say in pricing or packaging.

There are two honest ways this resolves, and both are visible in live postings.

In the first, another function owns the number and customer success supplies the signal, which is the arrangement the first posting quoted above describes. This works when the handoff is documented and the CS team gets credit for influenced expansion. It fails when "partner closely" is the only mechanism, because an expansion signal with no owner is a note in a tool.

In the second, the Director owns the book outright, as the second posting describes. This is cleaner and considerably harder. It means the Director is running a revenue function and should be resourced, compensated and measured like one.

The underlying argument, about whether customer success should carry revenue accountability at all, is one we have taken apart separately in should CSMs be accountable for revenue.

The failure mode is the third version, where nobody says which of these is true. The Director is told they own expansion, discovers the quota lives in sales, and spends a year producing readiness reports nobody acts on.

The question to ask in the interview: when my team finds a clear expansion opportunity, who closes it, and what shows up on my scorecard when they do?

Accountable for retention you can’t see in one place?

Director of Customer Success vs Manager of Customer Success

This is the promotion most people in the field are actually weighing, and the data says the two roles differ less than the titles suggest, but differ sharply on three specific things.

Counts below are postings, not percentages, because the two groups have different sizes and the sample is small. The number in each column header is the group size.

Hiring is the only row that is unanimous in both columns. Executive reporting is the only row that rises with the title.

The manager owns the machine. Playbook design, operating process and forecasting all appear far more often at manager level than at Director. Coaching appears in the clear majority of manager postings and only about half of Director ones.

The Director owns the room. Executive and board reporting is rare at manager level and common at Director. That is the real promotion: from running the team to representing the team where decisions about it get made.

Both are measured on expansion, renewal and adoption. Both are expected to hire. Neither carries a quota.

So the honest version of the step up is this: you give away the operating detail, you coach less than you expect to, and in exchange you get a seat where headcount, priorities and the team's remit are decided. If what you enjoy is building the system and developing people, the manager seat is where more of that work actually lives, which is not what the org chart implies.

For the broader version of this decision, including the paths that do not involve managing people, see our guide to becoming more strategic as a CSM.

Director vs Head of Customer Success vs VP of Customer Success

These three titles are not a reliable hierarchy, and treating them as one is how people end up disappointed by a promotion.

Most career guides state it as a clean rule: a Director manages managers, a VP manages Directors. In the live postings that is mostly true and worth knowing, but it is a tendency rather than a rule. Several describe managing managers outright, and one describes overseeing a team of regional Directors and managers, which is a VP's job carrying a Director's title. Against that, one describes leading "a team of 5 experienced Customer Success Managers", which is individual contributors.

So the title does not tell you. One in seven of these roles is running a small team directly, and that is a materially different job from running a function through other leaders. Account-facing titles do this constantly, and we have mapped the same problem for the technical account manager and client relationship partner roles. It is the first thing to ask and it takes one question.

"Head of Customer Success" is the least standardised of the three. In a company under about fifty people it is usually the first and only CS leader, reporting to the CEO, doing everything from the operating cadence to the executive relationships. In a larger company it can sit below a VP.

The reliable tests, in order of usefulness: who do you manage, who do you report to, and do you have headcount and budget authority. The title answers none of those, and all three are askable in a first conversation.

Do Directors of Customer Success still carry accounts?

Some do, and it is worth knowing before you accept the job.

Two of the seven Director postings in this sample describe owning a book of business directly, one of them specifying ownership "of a CS book of business or post-sale P&L of meaningful scale". No manager-level posting in the sample does.

That is counterintuitive, and the explanation is usually that these are the roles where the Director genuinely is the revenue owner rather than the signal provider, which is the cleaner arrangement described above.

The version to be careful about is the unstated one: a Director expected to coach a team while personally holding the hardest accounts. That arrangement keeps rewarding exactly the behaviour the promotion was supposed to change, because the accounts are urgent and the coaching is not. If a posting is quiet about whether you keep accounts, assume you do and ask directly.

Director of Customer Success salary

Four of the seven postings published a pay range, and they are high.

Across those, base ranges run from roughly $168,000 at the floor to $300,000 at the ceiling, with three of the four publishing an unambiguous base range and one publishing a figure labelled as either on-target earnings or base. One of the four also published an on-target earnings band above its base range, which is the clearest signal in the data that some of these roles carry variable pay even though none names a quota.

Two honest caveats. This is a small number of roles, all at US software companies that publish ranges because state law requires it, so it skews high relative to the global market. And a range that spans $130,000 from floor to ceiling is describing a ladder, not an offer.

The useful read is not the midpoint. It is that this role is paid like a senior function leader, which tells you what is expected of it regardless of what the posting says.

It is also worth knowing why the published averages for this role are so much lower, and how little they agree with each other.

Two of the pages currently ranking for this title state an average. One says $156,985. The other says around $102,000. That is a 54% spread between two sources describing the same job, which is not regional variation, it is methodology.

More to the point, both sit below the floor of every live base range we could read, the lowest of which starts at $168,000. A figure beneath what companies are currently advertising as the bottom of the band is not describing the market you would be hired into.

Pooled averages of self-reported data age badly and drift down. A posted range is what a named company was publicly offering on a stated date. When the two disagree, the posting is the better evidence.

What a Director of Customer Success should actually be measured on

Given there is no quota in these roles, the scorecard has to be built rather than inherited. Four things, in order of how defensible they are.

Retention, split. Gross retention tells you whether the product and the team are holding the base. Net retention tells you whether the account is growing. Reporting one without the other hides the thing you need to see. Our free calculators will do both from the same inputs.

Coverage, not activity. The share of the book that has a current owner, a current health read and a documented next action. This is the measure a Director can genuinely move, because it is about the system rather than individual outcomes, and we have written up how to define it as a health score coverage KPI.

Risk caught early enough to act. Not how many accounts were flagged, but how many were flagged while there was still time to do something. A risk register full of accounts in their final month is a reporting function, not a retention function.

Team retention and ramp. Given hiring is in every single posting, it belongs on the scorecard. How long a new CSM takes to reach full productivity, which our guide to ramping new customer success hires breaks into stages, and how many of your people are still there in two years.

For eight worked examples of quarterly objectives with named owners, including the retention objective usually assigned to this role, see our customer success OKRs guide.

What skills a Director of Customer Success actually needs

Ranked by how consistently the live postings ask for them, rather than by how they are usually listed.

Hiring. In every posting, at both Director and manager level. It is the most consistent requirement in the entire dataset and the least discussed in career guides. A Director who cannot fill a req, assess a candidate properly or keep a good CSM for three years will not get to the rest of the job.

Cross-functional influence. In almost every posting, and the phrasing is the tell. Where a posting says "align with" it means attending other people's meetings. Where it says "shape" or "partner closely with the team that owns X" it means genuine negotiating power. Read that line carefully before accepting.

Strategy, specifically written strategy. Almost universal, and in practice it means being able to put the state of the customer base into a document a CEO will read, with a recommendation attached. Not a dashboard.

Coaching. In roughly half the Director postings, against the clear majority of manager postings. Lower than most people expect, and worth sitting with if coaching is the part of leadership you actually want.

Executive communication. Named in under half the postings explicitly, but it is the capability that separates the role from the one below it, because the Director is the person asked why retention moved. The specific skill is giving three numbers and the bad one first.

Notably absent from the requirement lists: health scoring, forecasting methodology, and any named platform. The tools are assumed, not tested.

How big a team does a Director of Customer Success run?

There is no standard span, and the range in live postings is wide enough that the title tells you nothing.

At one end, a Director leading "a team of 5 experienced Customer Success Managers": five direct reports, all individual contributors, a hands-on job close to the accounts. At the other, a Director overseeing a team of regional Directors and managers who in turn lead teams of CSMs, which is three layers of distance from a customer.

Both are called Director of Customer Success. Both were hiring in the same week.

Our coverage model guide sets out how to size it. The practical consequence is that the two roles need different people and reward different strengths, and the interview process frequently does not distinguish between them. If the span is not in the posting, it is the question to open with.

What the week actually consists of

Derived from what the postings say the job is accountable for, rather than from a schedule, the work falls into four buckets that compete for the same hours.

People. Hiring, one-to-ones, performance, promotion cases, and the two or three difficult conversations that are always open. Given hiring appears in every posting, this is not a background task.

The base. Reviewing accounts at risk, agreeing which ones get intervention, and deciding what the team stops doing in order to make room.

The room. Preparing for and attending the meetings where the function is discussed, and answering the retention question when it arrives unscheduled.

Other functions. Product, sales and support, where the Director is usually negotiating for something they cannot build themselves.

If you are designing that week rather than surviving it, the CSM weekly operating rhythm is the layer underneath it.

What is not on that list is the operating detail. Playbook design and process do not appear in these postings, which means in a well-structured org they are genuinely delegated, and in a badly structured one they quietly become the Director's weekend.

How to become a Director of Customer Success

Experience asks cluster at ten years, which appears in five of the seven postings, with five years the next most common. Note that most postings name more than one figure, because they ask for a total and then a narrower requirement for people leadership specifically. This is not a fast progression and the postings are honest about it, which is worth weighing against the career guides that put this role at six to eight years.

The route that actually works runs through managing a team and surviving a hard year with it: a reorganisation, a flat quarter, a product problem you had to hold the line on. Interviews for these roles probe that, because the thing being tested is judgement under pressure rather than CS craft, which is assumed.

Two things to build deliberately on the way, because they are the two the manager seat does not develop. The first is executive communication, meaning the ability to put the state of the base in front of a CEO in three numbers without hiding the bad one. The second is hiring, because every posting asks for it and almost nobody arrives having done enough of it.

What the hiring process actually tests

Worth knowing from both sides of the table, because the posted requirements and the real assessment are not the same thing.

The requirements lists are about scope: years, team size, segment, industry. The assessment is almost entirely about judgement under pressure, because customer success craft is assumed by this level and nobody re-tests it.

Three things get probed in practice. A hard year, meaning a reorganisation, a flat quarter or a product problem you had to hold a line on, and specifically what you decided rather than what happened. A hiring record, because the requirement appears in every single posting and most candidates arrive having done far less of it than the role needs. The expansion answer, because the interviewer usually knows the quota question is unresolved in their own org and wants to hear whether you have thought about it.

The question worth asking back, given everything above: who owns the number my team influences, and what appears on my scorecard when they close it. A candidate who asks that is demonstrating the judgement being tested, and the answer tells you which of the two versions of this job you are being offered.

Where GainTrace fits

The specific problem this role has is that the things it is accountable for sit in different systems from the things it can see. Retention is in billing, risk is in someone's notes, ownership is in a spreadsheet, and the executive question arrives on a Tuesday.

GainTrace is the account health layer under that. It puts owner, health, renewal date and next action on one record, which is what makes coverage measurable rather than anecdotal, and it flags at-risk accounts about 45 days before renewal so the risk arrives while there is still something to do about it. It is free forever on your first 25 companies.

The method matters more than the tool here. A Director who can state what share of the book has a current owner and a documented next action is already doing the job, whatever they track it in.

Want coverage you can measure, not just report? Start GainTrace free.