Client Success Manager

We need to output HTML fragment with sections: About the role? The posting includes Overview, Responsibilities, Qualifications, Travel Required, What It’s Like To Work At Rithum, At Rithum You Will, Benefits, Pay (base pay range), Bonus info, etc. We must not repeat job title as heading. Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Other Duties" note? It's generic; maybe keep? It says "Please note that this job description is not designed to cover..." That's boilerplate; we should drop it. We need to preserve all substantive information. So we need to include Overview (maybe as About the role?), Responsibilities (with subpoints), Qualifications (minimum and preferred), Travel Required, What It’s Like To Work At Rithum (maybe as Culture), At Rithum You Will (maybe as Benefits? Actually that's more about culture), Benefits, Pay, Bonus (discretionary bonus). Also maybe "Travel Required Up to 10%" as a section? Could be under Schedule? Not schedule. Travel is not schedule; but we could put under a section "Travel". However instructions say use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings if needed? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are typical but we can use others if appropriate? Probably we should stick to those headings where applicable. Travel could be under Schedule? Not exactly. Could be under "Schedule" if they mention remote work etc. Travel is separate. Could include as a

  under Overview. We need to avoid empty sections. So we need to decide which sections to include: About the role (overview), Responsibilities, Qualifications, Benefits, Pay, maybe Bonus as part of Pay? Could include Pay section with base pay and bonus. Benefits separate. We also have "What It’s Like To Work At Rithum" and "At Rithum You Will" which are culture/benefits; could merge into Benefits or a separate "Culture" but not in list. Might be okay to include as a section "Culture" but not in examples; risk of being considered filler? The instruction: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings beyond the examples; they just gave examples. So we can add a heading like "Culture and Work Environment". That's specific content. Thus sections: About the role (Overview), Responsibilities, Qualifications (maybe split into Minimum and Preferred but we can combine), Culture and Work Environment (What It’s Like To Work At Rithum + At Rithum You Will), Benefits, Pay (including base pay range and discretionary bonus), Travel (maybe under Schedule? but we can add Travel). However they said prefer a few substantive sections over many thin ones. So maybe combine Travel into About the role or Culture. Travel is just a line; could be a

  under About the role. We need to use

  • for any list of duties/requirements/benefits. So responsibilities list, qualifications list, benefits list. We must preserve all substantive information: need to include details like "Serve as the primary relationship owner for assigned enterprise accounts." etc. Let's extract content. Overview paragraph: "Rithum™ is the world’s most trusted commerce network, accelerating how brands, suppliers, and retailers work together to deliver seamless e-commerce experiences. We provide an unmatched platform for brands and retailers, enabling them to accelerate growth, optimize operations across channels, scale product offerings and enhance margins. Today, more than 40,000 companies trust Rithum to grow their business across hundreds of channels, representing over $50 billion in annual GMV. Using our commerce, marketing, and delivery solutions, our customers create optimized consumer shopping journeys from beginning to end. Overview As a Client Success Manager – Enterprise Accounts, you own a portfolio of enterprise clients across the client lifecycle. You build consultative relationships, drive adoption and value realization, manage client health and renewals, and identify growth opportunities. You work across Rithum to align client priorities with our capabilities and deliver measurable business outcomes. Rithum empowers employees across all roles to leverage AI and technology to work smarter, move faster, and create scalable ways of working. In this role, you will use AI and data-driven insights to improve preparation, identify risks and opportunities, and deliver more proactive client engagement." We can combine into About the role. Responsibilities: bullet points under headings: Client Outcomes & Value Realization - Serve as the primary relationship owner for assigned enterprise accounts. - Align Rithum’s capabilities to client goals and define measurable success outcomes. - Lead business reviews and success checkpoints to demonstrate value and align on priorities. - Monitor client health and proactively address risks and client needs. Retention & Growth - Own renewal planning and execution, including forecasting and risk mitigation. - Identify expansion opportunities aligned to client goals, usage, and business strategy. - Partner with Sales on account planning and expansion execution. - Support commercial discussions across pricing, packaging, and contract changes. Cross-Functional Partnership & Operational Excellence - Coordinate across Sales, Product, Support, Legal, Finance, and other teams to advance client priorities. - Maintain accurate client, renewal, and opportunity data. - Use AI, client data, and Client Success tools to improve insights, preparation, and productivity. - Apply AI to account research, business review preparation, and client health and usage analysis, and verify outputs for accuracy before they reach a client. - Share client feedback and emerging needs with relevant internal teams. Qualifications: Minimum Qualifications list: - 2+ years of experience in Client Success, account management, renewals, or related client-facing roles in B2B SaaS. - Experience supporting enterprise clients with multiple stakeholders and complex business requirements. - Experience with renewals, client health, value realization, and client risk management. - Strong communication and relationship-management skills with the ability to influence multiple stakeholder levels. - Experience using CRM or Client Success platforms to manage client workflows and data. - Experience using AI tools (e.g., ChatGPT, Microsoft Copilot, Claude) to improve productivity, insights, or client engagement. Preferred Qualifications: - 3+ years of progressive client-facing experience. - Experience in SaaS, e-commerce, marketplace, or related technology environments. - Familiarity with Salesforce, Gainsight, or similar Client Success platforms, and AI-enabled client or productivity tools. - Bachelor’s degree in Business, Marketing, Communications, or a related field preferred. Travel Required: Up to 10% (maybe as a note). What It’s Like To Work At Rithum: paragraph: "When you join Rithum, you can expect to work with smart risk-takers, courageous collaborators, and curious minds. As part of the Rithum team, you are valued, supported, and included. Guided by a transparent culture and accessible, approachable leadership, we offer career opportunities aligned to your ambitions and talents. To ensure work and life balance works for you, we also offer an array of resources to support you and your families, including comprehensive benefits and wellness plans." At Rithum You Will: bullet-ish list: - Partner with the leading brands and retailers. - Connect with passionate professionals who will help support your goals. - Participate in an inclusive, welcoming work atmosphere. - Achieve work-life balance through remote-first working conditions, generous time off, and wellness days. - Receive industry-competitive compensation and total rewards benefits. Benefits: list items: - Medical, dental and vision benefits: Affordable health care plans and company HSA contributions, starting on Day 1 - A 6% 401(k) match - Competitive time off package with 20 days of Paid Time Off, 9 Company-Paid holidays, 2 paid floating holidays, 7 paid sick days, 2 Wellness days, and 1 Paid Volunteer Day; at 3 years of service PTO increases to 22 days, and at 5 years it increases to 25 days - 12 weeks primary caregiver leave & 4 weeks secondary caregiver leave - Accident, critical illness, and hospital indemnity insurance - Pet insurance - Legal assistance and identity theft insurance plans - Life insurance 2x salary - Access to the Calm app and the Employee Assistance Program - $65/month Remote work stipend for internet - Culture and team-building activities - Tuition assistance - Career development opportunities - Charitable contribution match up to $250 per year Pay: base pay range $60,000-$93,000 per year. Also discretionary bonus 10% of annual base salary. We should not include boilerplate like EEO etc. Now produce HTML. Structure:

    About the role

    ... overview paragraph ...

    Responsibilities

    • ... maybe group subheadings? Could we include subheadings inside
      ? Probably not; we could have

      inside? But instruction only mentions

      for section headings. Could we still use

      for sub-sections? Not prohibited but might be okay. Safer to keep as plain list items with the subheading text as part of the item? Could do

      Client Outcomes & Value Realization: ...

      but that mixes. Better to keep subheadings as

      maybe. But instruction didn't forbid other headings; just said use

      for section headings (e.g. About the role...). It didn't say you cannot use other heading levels. I'd use

      for sub-sections inside Responsibilities. Thus:

      Responsibilities

      Client Outcomes & Value Realization

      • ...
      ...

      Retention & Growth

      ...

      Cross-Functional Partnership & Operational Excellence

      ...
      Similarly for Qualifications: maybe

      Minimum Qualifications

      and

      Preferred Qualifications

      . Benefits: just a list. Pay: maybe

      Pay

      with

      base pay range and bonus. Travel: maybe include as a

      under About the role or a separate

      Travel

      . Since they said prefer few sections, maybe incorporate Travel into About the role as a sentence. Culture: we can make a section "Culture and Work Environment" with two paragraphs: What It’s Like To Work At Rithum and At Rithum You Will (maybe as list). At Rithum You Will items could be list. Thus sections: About the role, Responsibilities, Qualifications, Culture and Work Environment, Benefits, Pay. Now produce HTML. Need to ensure no duplicate lines. Also remove "Other Duties" etc. Let's craft. About the role paragraph: combine overview and overview sentence. We'll write:

      Rithum™ is the world’s most trusted commerce network, accelerating how brands, suppliers, and retailers work together to deliver seamless e‑commerce experiences. We provide an unmatched platform for brands and retailers, enabling them to accelerate growth, optimize operations across channels, scale product offerings and enhance margins. Today, more than 40,000 companies trust Rithum to grow their business across hundreds of channels, representing over $50 billion in annual GMV. Using our commerce, marketing, and delivery solutions, our customers create optimized consumer shopping journeys from beginning to end