Senior Manager, Customer Success Enablement

We need to output HTML fragment with sections: About the role? The posting includes summary, what your team does, who you are, what you’ll work on, what you may have, serious bonus points if you have, what you will find here (compensation/benefits), diversity etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Learn more about our culture at clio.com/careers", "We're a Human and High Performing AI company..." etc. Also remove disclaimer about email. Also remove "Diversity, Inclusion, Belonging and Equity (DIBE) & Accessibility" maybe we keep? It's EEO boilerplate; we should remove. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So remove that section. We need sections only when posting has real specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. We have summary: "We are currently seeking a Senior Manager, Customer Success Enablement to lead our Customer Success Enablement function and join our Revenue Enablement team in the United States and Canada." That's about the role. What your team does: description of Revenue Enablement team. Could be part of About the role or Responsibilities? Probably "About the role" includes summary and team description. Who you are: description of leader role. Could be Responsibilities? Actually "Who you are" describes expectations. Could be "Responsibilities" or "Requirements". We'll decide. What you’ll work on: list of duties. That's responsibilities. What you may have: qualifications/experience. That's Requirements/Qualifications. Serious bonus points if you have: additional preferred qualifications. What you will find here: compensation and benefits. So we need Pay and Benefits sections. Schedule: not mentioned; we should not create Schedule section unless present. So omit. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list, we need bullet list. For qualifications list, bullet list. For benefits list, bullet list. We need

  for prose. We must not repeat job title as heading. So no

  Senior Manager... We'll just have sections. We need to output only HTML fragment. Let's craft:

  About the role

  Clio is the global leader in legal AI technology, empowering legal professionals and law firms of every size to work smarter, faster, and more securely. We are transforming the legal experience for all by bettering the lives of legal professionals while increasing access to justice. We are currently seeking a Senior Manager, Customer Success Enablement to lead our Customer Success Enablement function and join our Revenue Enablement team in the United States and Canada.

  The Revenue Enablement team at Clio equips our sales and customer success organizations with the knowledge, skills, tools, and processes they need to drive revenue growth and deliver exceptional client experiences. We design and deliver onboarding and ongoing programs, run a center of excellence operating model, and partner closely with Sales, Customer Success, Marketing, Product Marketing, and Revenue Operations to turn product launches and go-to-market priorities into field-ready execution. We are a team that runs on curiosity, data, and a genuine commitment to helping people do their best work.

  Then Responsibilities (

  Responsibilities

  ) with bullet list from "What you’ll work on". Also maybe include "Who you are" as part of responsibilities? But we can incorporate "Who you are" as part of Responsibilities or maybe as a separate section like "Expectations". But we only have allowed headings; we could put "Who you are" under Responsibilities as prose then list duties. Better: Under Responsibilities, include a paragraph describing the leader role then bullet list of work. Let's extract "Who you are" content: "You are the leader of our Customer Success Enablement function. You manage a team of enablers who support the full customer lifecycle, from onboarding and launch through adoption, expansion, and retention. You understand how a product story becomes the conversation that grows an account, and you build programs that change what CSMs and support teams do in front of customers. You are a strong people leader who coaches enablers and CS managers alike, you make decisions from call data and usage data, and you are comfortable owning outcomes in front of senior stakeholders. You thrive in a fast-paced, high-growth environment and are ready to run CS Enablement like your own business. Every people manager at Clio is expected to lead with context, set the pace, and own the outcome — giving their team the clarity to move fast, the authority to decide, and the accountability to deliver." We can put that as prose under Responsibilities. Then bullet list of "What you’ll work on": - Build and develop a high-performing team of Field Enablement partners who operate as trusted advisors to our Customer Success, Support, and Launch teams. - Own measurable CS outcomes across the customer success organization, including expansion ARR, multi-product attach, retention, and time to ramp for new CSMs across Success and Support - Build and run a manager coaching enablement program so CS managers reinforce trained behaviors and enablement lands in customer conversations - Establish a consistent Gong review rhythm on CS calls to surface coaching themes, objection patterns, and content gaps - Set and report on OKR-tied performance work that connects enablement investment to retention, expansion, and productivity - Direct the development of AI-assisted content and role-play certification grounded in real expansion and retention conversations - Ensure lifecycle and product enablement is tailored by segment and motion rather than delivered one size fits all - Partner with CS leadership, Product Marketing, Product, Revenue Operations, and the Enablement Operations function to align priorities and protect launch-critical work - Translate launch playbooks into CS-specific talk tracks for onboarding, adoption, upsell, cross-sell, and multi-product attach - Establish and regularly measure KPIs to assess the value of CS enablement programs, and recommend innovative solutions as the business evolves Now Requirements/Qualifications: "What you may have" list. We need to decide whether to split into Requirements and Qualifications and Skills. The instruction says use headings for those categories if content exists. We have a list of qualifications/experience. Could put under Requirements. Could also separate Skills (like proficiency with generative AI tools). But we can combine. We'll create

  Requirements

  with bullet list: - 5+ years of customer success, CS enablement, or related enablement experience, including experience leading or managing a team - Experience working with enterprise or high-growth SaaS organizations - Deep understanding of customer success motions such as onboarding, adoption, expansion, and retention - A track record of tying enablement programs to measurable retention and expansion outcomes - Strong people leadership skills, with the ability to coach and grow enablers - Excellent analytical, organizational, and communication skills - Ability to manage projects from conception to completion and to lead through ambiguity and change - Excellent strategic, conceptual, and decision-making skills - Proficiency with generative AI tools (Claude, ChatGPT, or similar) for content development and coaching Then maybe

  Preferred Qualifications

  but not in allowed headings; we could put under Skills? The allowed headings include Skills. So we can put bonus points under Skills. Thus

  Skills

  bullet list: - Experience in legal tech or a comparable regulated industry - Experience enabling expansion, cross-sell, or multi-product attach motions - Familiarity with Gong, LetterAI, and Salesforce - Relevant customer success or enablement certifications Now Benefits and Pay. What you will find here: includes compensation description and benefits list. We need Pay section: include salary range and description. We need Benefits section: list benefits. Let's extract: "What you will find here: Compensation is one of the main components of Clio’s Total Rewards Program. We have developed a series of programs and processes to ensure we are creating fair and competitive pay practices that form the foundation of our human and high-performing culture. Some highlights of our Total Rewards program include: Competitive, equitable salary with top-tier health benefits, dental, and vision insurance Hybrid work environment, with expectation for local Clions (Vancouver, Calgary, Toronto, Dublin and Sydney) to be in office minimum twice per week. Flexible time off policy, with an encouraged 20 days off per year.EAP benefits for you and household members, including counseling and online resources401k matching and Child Education SavingsClioversary recognition program with special acknowledgement at 3, 5, 7, and 10 years The expected salary range for this role is $165,600 to $248,400 USD. Initial placement within the range is informed by geographic region, experience, and skillset, with room to progress as impact and tenure grow. Final offer amounts will vary based on candidate profile." We need to separate Pay and Benefits. Pay: salary range description. Benefits: list of benefits: competitive equitable salary (but that's pay), top-tier health benefits, dental, vision insurance, hybrid work environment, flexible time off policy (encouraged 20 days off per year), EAP benefits (counseling and online resources), 401k matching, Child Education Savings, Clioversary recognition program (special acknowledgement at 3,5,7,10 years). Also maybe mention "Hybrid work environment, with expectation for local Clions (Vancouver, Calgary, Toronto, Dublin and Sydney) to be in office minimum twice per week." That's a work arrangement, could be under Benefits or maybe Schedule? Not schedule. We'll include under Benefits. We must not create Schedule section. Thus:

  Pay

  The expected salary range for this role is $165,600 to $248,400 USD. Initial placement within the range is informed by geographic region, experience, and skillset, with room to progress as impact and tenure grow. Final offer amounts will vary based on candidate profile.

  Benefits

  • Competitive, equitable salary with top-tier health benefits, dental, and vision insurance
  • Hybrid work environment, with expectation for local Clions (Vancouver, Calgary, Toronto, Dublin and Sydney) to be in office minimum twice per week
  • Flexible time off policy, with an encouraged 20 days off per year
  • EAP benefits for you and household members, including counseling and online resources
  • 401k matching
  • Child Education Savings
  • Clioversary recognition program with special acknowledgement at 3, 5, 7, and 10 years
  We should avoid duplicating salary in benefits list; but we already have salary in Pay; we could keep it there only. In benefits list we might omit salary line to avoid duplication. However the benefits list originally includes "Competitive, equitable salary with top-tier health benefits, dental, and vision insurance". That's mixing salary and health. Since we have Pay separate, we could keep benefits list as health benefits etc. But we need to preserve all substantive info; we can't omit salary mention entirely because it's in benefits list but we have Pay section covering salary. It's okay to not duplicate. We'll keep benefits list focusing on non-salary benefits. Thus benefits list: - Top-tier health benefits, dental, and vision insurance - Hybrid work environment, with expectation for local Clions (Vancouver, Calgary, Toronto, Dublin and Sydney) to be in office minimum twice per week - Flexible time off policy, with an encouraged 20 days off per year - EAP benefits for you and household members