Customer Success Manager Work in 2026: Evidence from 119 Current Vacancies

Author: MTF Institute Research Team
Publication date: 23 August 2026
Evidence cut-off: 23 August 2026
Corpus: 119 current public Customer Success Manager vacancy records

The complete research archive - searchable PDF, evidence workbook and accepted-vacancy dataset - is openly available at Zenodo DOI 10.5281/zenodo.22067737.

Executive summary

This report examines how employers described Customer Success Manager work in 119 public vacancies verified on 23 August 2026. The accepted corpus covers 107 employers and five source-platform categories. It was built from 120 candidate records gathered through three bounded reviews of public first-party employer or applicant-tracking-system pages. Manager-side normalization and deduplication removed one cross-source duplicate. Every accepted record retained a direct HTTPS vacancy URL, employer, title, location or jurisdiction, retrieval date, requisition identity, a short evidence anchor, two or more duty codes and a record-specific limitation. The corpus passed a mechanical gate requiring at least 100 suitable current vacancies. [1][2]

The clearest finding is that advertised Customer Success work is centred on adoption and connected post-sale outcomes. Adoption was coded in 93 vacancies (78.2%). Health or risk and expansion each appeared in 80 (67.2%), while renewal or retention appeared in 79 (66.4%). Business reviews appeared in 59 (49.6%), success planning in 54 (45.4%), onboarding in 46 (38.7%) and analytics in 40 (33.6%). Systems discipline appeared in 13 (10.9%), and explicit handoff wording in 6 (5.0%). [1][2]

These are overlapping codes, not mutually exclusive job categories. The 119 records contain 550 code assignments, or 4.62 per vacancy on average. Sixty-four vacancies (53.8%) combine renewal and expansion; 61 (51.3%) combine adoption and expansion; 60 (50.4%) combine adoption and health or risk; and 58 (48.7%) combine adoption and renewal. Co-occurrence indicates that employers often describe Customer Success as a linked operating system rather than a sequence of isolated tasks. It does not show how much time CSMs spend on each activity, who has final authority, or whether any activity causes retention or revenue. [1]

The evidence supports a disciplined, evidence-led conception of Customer Success Management: clarify the accepted outcome, establish an onboarding and adoption path, monitor value and risk evidence, conduct structured reviews, prepare renewal evidence, and transfer qualified expansion signals to the authorized commercial owner where required. It does not support a universal claim that every CSM owns implementation, support, contracts, pricing, renewals or sales. Public employer handbooks and company filings reinforce this boundary: operating models vary, and implementation, Support, Professional Services, Renewals, Sales and operations can be separate owners. [4][5]

The report therefore recommends capability language, local responsibility mapping, traceable evidence and causal humility. Retention, renewal, expansion and revenue are multi-causal business outcomes. No vacancy count, health score, AI prediction or training intervention guarantees them.

Research questions

  1. Which post-sale responsibilities appear most often in the accepted 2026 Customer Success Manager vacancy corpus?
  2. Which responsibilities most often appear together?
  3. What operating model can be inferred cautiously from those patterns?
  4. Where does the evidence require role, legal, data and intellectual-property boundaries?
  5. What do the findings imply for employers, practitioners and professional learning design?

Method

Corpus construction

The unit of analysis is one public vacancy record, not one employer. Three independent bounded specialist reviews examined public first-party employer and ATS pages. The collection covered Greenhouse, Ashby, Lever, Workday, SmartRecruiters, UKG and employer-direct career pages. The manager then normalized the three inputs, reconciled fields, deduplicated across sources and ran mechanical validation. Collection and verification occurred on 23 August 2026 in the Europe/Lisbon time zone. [1][3]

The process began with 120 records. One cross-source duplicate was rejected, leaving 119 accepted vacancies from 107 employers. The largest employer contribution was three vacancies, limiting the ability of a single employer to dominate the corpus. All accepted URLs were HTTPS; canonical URLs, platform requisition identities, and normalized employer-title-location keys were unique. The accepted TSV contains 15 columns and has SHA-256 0c711d481d545723f019045ffc547592a2689a26e7aec86a7bc24196ca00730b. [1]

“Current” has a precise and limited meaning in this report: the public first-party employer or ATS page was directly opened and treated as live by the bounded review on the retrieval date. A vacancy may have changed or closed after that date.

Coding

Each accepted vacancy received at least two of ten overlapping operational labels. For readability, this draft renders the label names in plain English as follows; these glosses do not introduce a new codebook or change the accepted coding:

  • ONBOARD: onboarding or launch activity;
  • ADOPT: product or service adoption and value use;
  • PLAN: success, account or outcome planning;
  • HEALTH: account health, risk sensing or risk response;
  • REVIEW: periodic, business or executive review activity;
  • RENEW: renewal or retention work;
  • EXPAND: growth, upsell or expansion opportunity work;
  • HANDOFF: explicit transfer or coordination across ownership boundaries;
  • SYSTEM: record, workflow or operating-system discipline;
  • ANALYTICS: analysis, metrics or data-informed account work.

The labels are analytic categories, not a proprietary framework, occupational standard or universal responsibility model. A code indicates that the responsibility was evidenced in the vacancy record. It does not measure task intensity, seniority, decision authority, competence or business impact.

Calculations

Counts in the accepted analysis were independently recalculated from the immutable TSV. Percentages equal coded vacancies / 119 × 100 and are rounded to one decimal place. Pair counts were calculated by testing whether both labels occurred in the same duty_codes field. Because codes overlap, percentages must not be summed to estimate a share of jobs or workload. [1][2]

Corroborating and boundary evidence

The vacancy corpus is the primary empirical base. A specialist professional-practice ledger supplied bounded contextual evidence from public 2025–2026 industry research, employer handbooks, company filings, professional-association pages and public authorities. A separate source-rights register defined permissible use and exclusions. A learning-intent ledger was used only to understand the professional-learning context; marketplace enrolment, rating and provider figures are not treated as evidence of role prevalence, learning efficacy or MTF conversion. [5][6][7]

No protected framework, certification blueprint, proprietary template, paywalled research or bulk vacancy text was used. The few vacancy quotations in the references are 8–20-word evidence anchors already retained in the accepted corpus.

Findings

1. Adoption is the strongest advertised centre of gravity

Operational label Vacancies Share of 119
Adoption 93 78.2%
Health or risk 80 67.2%
Expansion 80 67.2%
Renewal or retention 79 66.4%
Business or executive review 59 49.6%
Success or outcome planning 54 45.4%
Onboarding 46 38.7%
Analytics 40 33.6%
Systems discipline 13 10.9%
Explicit handoff 6 5.0%

Adoption is the only code present in more than three quarters of the sample. This supports an operating view in which the CSM helps customers move from access or launch toward useful, outcome-aligned use. It does not establish a single adoption method, benchmark or causal pathway. Nor does it imply that adoption is controlled by the CSM alone; product quality, implementation, customer capacity, technical fit and commercial conditions can all affect the result.

Health or risk, expansion and renewal or retention form a second high-frequency group, each appearing in roughly two thirds of records. The proximity of these counts should not be read as equality of responsibility. Some employers assign direct commercial ownership; others expect the CSM to surface evidence, prepare readiness and coordinate with a separate Sales, account-management or Renewals owner. The accepted portfolio and legal review therefore requires local authority to be made explicit. [3][5]

2. The advertised role links adoption, risk, renewal and expansion

Pair of overlapping labels Vacancies with both Share of 119
Expansion + renewal 64 53.8%
Adoption + expansion 61 51.3%
Adoption + health/risk 60 50.4%
Adoption + renewal 58 48.7%
Health/risk + renewal 54 45.4%
Expansion + health/risk 54 45.4%

The dominant pairs connect value use with risk and commercial continuity. This pattern supports a practical evidence chain: observed use and outcome evidence inform account-health judgments; those judgments inform conversations about obstacles and readiness; renewal and expansion decisions then occur within the organization’s assigned authority.

This is an interpretation of coded co-occurrence, not proof of sequence or causation. The advertisements do not provide process timestamps, effort allocation, controlled outcomes or a consistent responsibility matrix. “Health” can also mean different things across employers. A health indicator should therefore be treated as a contestable decision aid whose inputs, missing data, assumptions and owner are visible—not as an objective churn verdict.

3. Planning and reviews make the role managerial without making it universally executive

Success or outcome planning appears in 54 vacancies (45.4%), and business or executive reviews in 59 (49.6%). Together, these frequencies suggest that many CSM positions require a repeatable management cadence: agreeing outcomes, organizing stakeholders, reviewing evidence, documenting changes and deciding next actions.

That cadence is not the same as enterprise-wide customer-experience ownership. The professional-practice sources describe broader Customer Experience work as including cross-journey strategy, voice-of-customer research, design, measurement, culture and accountability. The accepted course boundary therefore keeps this report at the account or portfolio-level post-sale operating layer. It does not transfer CX strategy, Product, CRM architecture, Support, RevOps, pricing or legal authority to the CSM. [3][5]

4. Analytics is material, but advertised evidence does not justify automated judgment

Analytics appears in 40 vacancies (33.6%). This is sufficient to make data interpretation a material role capability, but not to prescribe a universal metric or score. Public filings in the practice ledger show why caution matters: issuer retention measures can combine adoption, expansion, contraction and attrition, and their definitions may not be comparable across firms. Company-reported retention cannot be attributed to CSM action or training without a suitable causal design. [5]

For practice, the evidence supports transparent inputs, explicit assumptions, missing-data checks and decision records. For AI-supported work, customer messages, call notes and account records require data-minimization and privacy review. Generated summaries, risk hypotheses and suggested actions require human verification. AI must not autonomously label customers for consequential treatment, contact them, change a system of record, interpret contracts, make offers or authorize renewal or expansion. These controls reflect the jurisdiction-labelled public-authority sources and the accepted legal prequalification; they are risk controls, not legal advice. [3][5][6]

5. Onboarding is important but not universally explicit in vacancy wording

Onboarding appears in 46 vacancies (38.7%). Adoption and onboarding occur together in 43 vacancies (36.1%). The result supports teaching the transition from accepted commercial handoff through launch and early value, while avoiding the claim that every CSM owns technical implementation.

Public employer sources reinforce the distinction. GitLab’s public role materials separate advisory CSM work from hands-on Professional Services, technical roles, Support and commercial Renewals. Company filings likewise describe cases in which Professional Services owns lengthy implementation before subscription value can be realized. These are examples of operating design, not universal responsibility matrices. [5][8][9]

6. Explicit handoff and systems language is infrequent, but cannot be treated as unimportant

Only 6 vacancies (5.0%) carry the explicit handoff code, and 13 (10.9%) carry the systems-discipline code. These low frequencies mean only that such wording was explicitly evidenced and coded in this sample. They do not show that handoffs or records are absent in the actual job.

Indeed, the higher co-occurrence of adoption, health, renewal and expansion makes ownership clarity more important. Where several functions touch the same account outcome, an implicit transition creates risk: duplicate customer contact, missing decisions, unsupported commercial claims or unclear accountability. The defensible implication is to teach explicit owner, evidence, timing and acceptance criteria at boundaries—not to infer that the CSM owns every adjacent task.

7. The sample is diverse in employer count but uneven in geography and source infrastructure

Region label Vacancies Share of 119
Global or remote 46 38.7%
North America 42 35.3%
Europe or EMEA 14 11.8%
APAC 9 7.6%
Unspecified 7 5.9%
LATAM 1 0.8%

The GLOBAL_REMOTE category and North America together account for 88 vacancies (73.9%). Europe/EMEA, APAC and LATAM are much less represented. A “global or remote” label may still contain country, language, time-zone or work-authorization restrictions; it should not be interpreted as unrestricted global employment.

The source-platform distribution is Greenhouse 40 (33.6%), Ashby 35 (29.4%), employer-direct 26 (21.8%), SmartRecruiters 13 (10.9%) and Lever 5 (4.2%). Greenhouse and Ashby together provide 75 records (63.0%). The sample therefore reflects which public employer and ATS pages were findable, readable and verifiable within the bounded review, not the full distribution of Customer Success employment.

Implications

For employers and role designers

  • Define whether the CSM owns, coordinates, contributes to or merely informs onboarding, renewal and expansion.
  • Connect adoption and health indicators to customer outcomes, data provenance and an explicit review cadence.
  • Separate evidence preparation from legal, pricing, contracting and final commercial authority.
  • Make implementation, Support, Product, Sales, Renewals, Professional Services and operations handoffs observable.
  • Avoid performance claims that attribute multi-causal retention or revenue outcomes to one role without suitable evidence.

For practitioners

  • Treat the job as evidence stewardship across a post-sale lifecycle, not as possession of every customer-related decision.
  • Maintain an explicit outcome, adoption evidence, risk hypothesis, next action, owner and review date.
  • Read health scores and AI outputs as hypotheses requiring verification, not facts.
  • Escalate contract, privacy, direct-marketing, regulated-sector and authority questions to the appropriate specialist.
  • Qualify expansion fit and transfer it to the authorized owner when commercial authority sits elsewhere.

For professional learning design

The vacancy evidence supports learning centred on onboarding coordination, adoption, success planning, health and risk reasoning, business reviews, renewal readiness, responsible expansion handoff, analytics and record quality. Assessment should require original artifacts and explicit ownership decisions, not memorization of a vendor model.

External learning signals in the accepted ledger show visible marketplace participation, paid professional offers, team-training supply and recent learner questions. They support the existence of professional learning intent, but not a market-size estimate, course-sales forecast, employer recognition claim or learning-efficacy claim. Certificate-only positioning also faces practitioner skepticism. [7]

Rights, legal and ethical boundaries

The source-rights review permits factual summary, attribution and original synthesis. It prohibits reproducing or adapting protected frameworks, certification blueprints, branded diagrams, courseware, full vacancies, proprietary templates or licensed research without permission. In particular, this report does not teach or claim alignment with SPICED/Bowtie, DEAR/Elements, LAER/DARE, NPS-related systems, Gartner research, ISO material, Cisco certification content or other vendor credentials and methodologies. [3][6]

The generic occupational title “Customer Success Manager” is usable for this research context, but the bounded title screen is not a multi-jurisdiction trademark opinion. Credential acronyms and badges belonging to other organizations must not be used to imply equivalence, accreditation, endorsement or exam preparation. [3][6]

Vacancy evidence is retained as URLs, derived coding, limitations and short necessary anchors—not as full job descriptions. Customer, candidate and recruiter personal data, employer logos, authenticated pages and paywalled material are outside the evidence set. Legal, privacy, direct-marketing, contract and regulated-sector questions remain jurisdiction-specific and require qualified review. Nothing in this report is legal advice.

Limitations

  1. Point-in-time sample. The vacancies were verified on one date and may subsequently change or close.
  2. Purposive, not probabilistic. The corpus is not a census or representative probability sample of the global labour market.
  3. Platform and geographic skew. Greenhouse and Ashby provide 63.0% of records; GLOBAL_REMOTE and North America provide 73.9%.
  4. Advertised work, not observed work. Vacancies express intended hiring requirements. They do not prove day-to-day activity, authority, workload or effectiveness.
  5. Overlapping codes. A vacancy can carry several codes. Counts and percentages cannot be summed as shares of jobs or time.
  6. Coding judgment. The source bundle does not report an inter-coder reliability statistic. Short evidence anchors support traceability but do not replace the full context of a vacancy.
  7. Absence is not proof of irrelevance. Low counts for handoff or systems discipline may reflect wording or coding, not operational importance.
  8. Heterogeneous roles. The corpus includes software, services and vendor-success contexts, different seniority levels, portfolio sizes and commercial-accountability models.
  9. No causal claims. Counts do not establish that a practice improves adoption, retention, renewal, expansion, revenue, employment or learning outcomes.
  10. Context sources are bounded. Much professional-practice research is vendor-led, voluntary, self-reported or SaaS-heavy. Employer handbooks and filings describe particular organizations.
  11. Learning signals are directional. Marketplace counts can be cumulative and non-deduplicated; provider figures may be self-reported; search visibility is not demand volume.
  12. Legal and rights review is bounded. The prequalification is an operational screen, not worldwide clearance or legal advice. Rights must be rechecked for every final publication asset.

Conclusion

Across 119 current public vacancies, the operating shape of Customer Success Management is most consistently defined by adoption, health or risk, renewal or retention, and expansion. Planning, reviews, onboarding and analytics provide the mechanisms through which that work becomes manageable and reviewable. The pattern is multi-functional: codes overlap heavily, and the most common pairs join value use to risk and commercial continuity.

The evidence supports a CSM as a disciplined post-sale evidence operator and coordinator. It does not support a universal owner of implementation, Support, Product, CRM, Customer Experience, RevOps, contracts, pricing or Sales. The practical standard is therefore not a branded playbook or guaranteed result. It is a traceable chain of outcomes, evidence, assumptions, responsibilities, cadences and handoffs—adapted to the organization’s actual authority model and kept within legal, privacy and intellectual-property boundaries.

References

Immutable evidence artifacts

  1. MTF Institute. Accepted Customer Success Manager vacancies, 23 August 2026. accepted-vacancies-2026-08-23.tsv. 119 records; SHA-256 0c711d481d545723f019045ffc547592a2689a26e7aec86a7bc24196ca00730b.
  2. MTF Institute. Customer Success Manager vacancy corpus validation, 23 August 2026. vacancy-corpus-validation-2026-08-23.json.
  3. MTF Institute. Customer Success Manager portfolio, evidence and legal prequalification. portfolio-legal-prequalification-v1.md, 23 August 2026.
  4. MTF Institute. Derived Customer Success Manager vacancy evidence analysis. vacancy-analysis-v1.json, 23 August 2026.
  5. MTF Institute. Professional practice source ledger: Customer Success Manager. professional-practice-source-ledger-specialist-2026-08-23-v1.yaml.
  6. MTF Institute. Source rights register: Customer Success Manager. source-rights-register-specialist-2026-08-23-v1.yaml.
  7. MTF Institute. Professional learning-intent source ledger: Customer Success Manager. professional-learning-intent-source-ledger-2026-08-23-v1.yaml.

Selected public context sources recorded in the ledgers

  1. GitLab. CS & SA Roles Overview. Public employer handbook; retrieved 23 August 2026.
  2. GitLab. Customer Success Management Handbook. Public employer handbook; retrieved 23 August 2026.
  3. ChurnZero with 6sense and named partners. 2025 Customer Revenue Leadership Study. Vendor-led, voluntary research; factual summary only.
  4. Upland Software, Inc. Form 10-K for the year ended 31 December 2025. Company filing; company-specific evidence.
  5. nCino, Inc. Fiscal Year 2026 Annual Report. Company filing; company-specific evidence.
  6. European Commission. AI talent, skills and literacy. EU-specific and time-sensitive; not legal advice.
  7. European Data Protection Board. AI Privacy Risks & Mitigations: Large Language Models. EU data-protection context; not a complete global privacy guide.
  8. Customer Experience Professionals Association. CXPA CX Framework. Used only for anti-collision scope; no framework structure reproduced.

Short vacancy evidence anchors

The following anchors illustrate coding traceability. They are not a representative subsample and do not replace the aggregate analysis.

  • Apollo GraphQL, Senior Customer Success Manager, CSM-VAC-0007: “Manage the customer adoption lifecycle, including onboarding, value realization, expansion, and advocacy.” (12 words). Public vacancy.
  • Checkr, Staff Customer Success Manager, CSM-VAC-0021: “Own strategic post-sale accounts across adoption, expansion, renewals, and quarterly reviews.” (11 words). Public vacancy.
  • Common Room, Enterprise Customer Success Manager, CSM-VAC-0027: “Own a portfolio of Enterprise accounts, serving as their primary strategic partner post-sale.” (13 words). Public vacancy.
  • SPARETECH, Senior Customer Success Manager, CSM-VAC-0095: “Own post-sales journeys from handover through onboarding, usage, renewals, and upsells.” (11 words). Public vacancy.

Interpretation guard: This report describes coded advertised responsibilities in a point-in-time purposive sample. It does not establish universal duties, effectiveness, legal requirements, hiring outcomes, course demand causality or guaranteed business results.