Client Success Specialist, Insurance Partnerships

We need to output HTML fragment with sections: About Us? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include based on content. The posting includes: - About Us (company description) - About The Role (overview) - What You'll Own (list of responsibilities) - How We'll Measure Success (metrics) - What This Role Is (description of role nature) - Requirements (travel, preferred qualifications) - Benefits (compensation, health, etc.) - Base Salary: $70-80,000 per year (Pay) - No explicit schedule. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine some. We should not repeat job title. We can have sections: About Us? Not in list but maybe we can include as a paragraph before sections? The instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but we should stick to those. Probably we should include About the role (which covers About Us and About The Role). Could also have Responsibilities (What You'll Own). Requirements (travel + preferred qualifications). Qualifications maybe separate? But we can combine. We need Benefits section (they have benefits). Pay section (Base Salary). Schedule not present, so omit. We must not include filler like "commensurate with experience". Base Salary is specific: $70-80,000 per year, depending upon experience. That's okay. We need to preserve all substantive information. So we need to include details from About Us, About The Role, What You'll Own (list), How We'll Measure Success, What This Role Is, Requirements (travel, preferred qualifications), Benefits, Pay. We need to format lists with

• . Use

  for prose. We must not include boilerplate like equal opportunity employer etc. That's EEO boilerplate; remove. Also remove duplicated lines. Let's extract content. About Us paragraph: "Silvur is modernizing what retirement decision-making in America looks like. We partner with financial institutions to deliver world-class tools and educational resources to their account holders—including personalized content, calculators, and connections to healthcare and financial services—to support the critical decisions their members make in their 50s, 60s, and through retirement. Our tech powered insurance platform guides these members through the biggest health and wealth decisions of their life. Our white-labeled online platform is available to millions of credit union members and has been named to the Forbes Fintech 50 Most Innovative Companies. We've been featured in The New York Times, Fortune, CNBC, and Yahoo! Finance, and are backed by leading VCs like Anthemis and strategic investors including Curql, Reseda Group, Idaho Central Credit Union, Maps, WSECU, and Mission Federal Credit Union." About The Role: "We just doubled our partner network — from 8 credit unions to 17 — and we're heading into our biggest season pacing well ahead of last year. Now we need someone to help us own what comes next. As our Client Success Specialist, you'll be a key point of contact for our credit union partners — keeping them engaged, well-supported, and getting real value from the Silvur program. You'll manage day-to-day relationships, drive adoption, deliver training, and help build the playbooks that let us support a growing partner network with a lean team. It's a hands-on client success role with room to grow as you and the company do. Because we're supporting a large book with a lean team, your success depends not just on relationship quality but on your ability to build repeatable playbooks, scalable training, and data-informed engagement that work across a large portfolio — increasingly with AI doing the heavy lifting." What You'll Own: bullet list with subheadings? It has sections: Partner Relationship Management, Product Adoption & Enablement, Data, Reporting & Cross-Functional Collaboration, Onboarding & Implementation (growing over time). Each with description. We need to preserve all substantive info. So we can create a

  with each responsibility as
  • containing the description. How We'll Measure Success: paragraph: "This is a data-informed role focused on the health of our partnerships. Success is measured on how well our partners adopt and engage with the Silvur program, and on keeping those relationships strong and long-lasting. Partner satisfaction and retention — partners are engaged, well-supported, see clear value from the program, and renew their partnership with Silvur. Measured through business review outcomes, partner revenue trends, and direct feedbackProgram adoption and engagement — partner staff are trained and engaged, driving a set of KPIs critical to the success of the program" Note there is a missing space between feedbackProgram; but we keep as is. What This Role Is: paragraph: "We want to be transparent so you can self-select accurately: You'll build the plane while flying it. There will be lots of unknowns and processes to figure out. The ideal teammate thrives in ambiguity, builds process where none exists, and doesn't wait for executives to hand over the answersYou'll grow with the company. Start with a set of partners and a clear mandate, prove yourself, and grow into deeper ownership over time. This is a launchpad, not a holding patternYou'll help reinvent the work itself. We're building everything AI-native. You'll design AI-first workflows and automations that let one person do what used to take a team. We use Claude all day. You will too" Requirements: "Travel is expected. In-branch training, executive business reviews, and partner relationship-building mean regular time on-site across our credit union footprint. Preferred Qualifications 1-2+ years of experience in partner success, client onboarding, account management, marketing or product specialist roles Startup experience preferred; you're comfortable with ambiguity and building process where none existsExperience collecting and analyzing data to make informed decisionsComfort across a modern, AI first lightweight tech stack — Claude, Google Workspace (Docs, Sheets, Slides), HubSpot, Asana, Canva+. We use Claude all day!Excellent relationship-building, communication, and project-management skillsComfort leading cross-functional initiatives with internal and external stakeholders" We need to separate travel and preferred qualifications. Could have a

    for travel, then a

    for preferred qualifications. Benefits: "You will be an employee of Silvur Technology Services. Employees receive a total compensation package including salary, options, health benefits (healthcare, vision, and dental), paid time off + holidays, and 401k with employer contribution. You may choose the technology you need to help you excel in your role. You will work in a in-person environment with an impact-driven, high-growth team that is changing the future of retirement healthcare." Pay: "Base Salary: $70-80,000 per year, depending upon experience." We must not include EEO line. Now produce HTML fragment with

    headings for each section we include. Which sections? We could have: - About the role (combining About Us and About The Role) - Responsibilities (What You'll Own) - How We'll Measure Success (maybe could be part of Responsibilities? but it's distinct; we could include as a separate section maybe "Success Metrics" but not in allowed list. Allowed list includes Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No explicit "How We'll Measure Success". Could we fold into Responsibilities? It's about measurement; maybe we can include under Responsibilities as a bullet? But better to have a separate section maybe "Success Metrics" but not allowed. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies those are examples; we could still use other headings but they'd be non-standard. Safer to stick to those. So we need to map content to those headings. We have About Us and About The Role -> About the role. Responsibilities -> What You'll Own. Requirements -> Travel is expected (maybe also include preferred qualifications? but qualifications separate). Could have Requirements (travel) and Qualifications (preferred qualifications). Skills maybe from preferred qualifications (tech stack, relationship-building, etc.). Could combine. Benefits -> Benefits. Pay -> Base Salary. Schedule -> not present, omit. We need to ensure we don't create empty sections. Thus sections:

    About the role

    (contains About Us paragraph + About The Role paragraph)

    Responsibilities

    (list of responsibilities from What You'll Own)

    Requirements

    (travel expected)

    Qualifications

    (preferred qualifications list)

    Skills

    (maybe we can extract skills from qualifications: relationship-building, communication, project-management, cross-functional initiatives, data analysis, AI-first tech stack comfort). But we already have qualifications; maybe we can merge qualifications and skills. But we need to avoid thin sections. Could combine Qualifications and Skills into one section? But we need to follow instruction: use those headings for sections; we can decide to not include Skills if content overlaps with Qualifications. Better to have Qualifications include both experience and skills. So we can have Qualifications section containing the preferred qualifications bullet list (including experience, startup, data analysis, tech stack, relationship-building, communication, project-management, cross-functional). That covers skills. Thus we may not need separate Skills section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if any content left: What This Role Is and How We'll Measure Success not yet included. Need to incorporate somewhere. Could fold into About the role or Responsibilities? The "What This Role Is" describes nature of role (ambiguity, AI-native). Could be part of About the role. How We'll Measure Success could be part of Responsibilities (as a responsibility to track metrics) or maybe a separate section but we don't have heading. Could add as a paragraph under Responsibilities after list? Or we could create a section "Success Metrics" but not allowed. Better to incorporate into Responsibilities as a bullet: "Track referral activity, engagement, and product utilization across your partners, and use the data to guide where you focus; surface insights and trends to internal teams; translate partner feedback into actionable product and process recommendations; partner with operations, product, and marketing teams to improve client and member outcomes". That's already in Data, Reporting & Cross-Functional Collaboration bullet. So measurement is covered there. What This Role Is: talk about building plane while flying it, ambiguity, AI-native, etc. Could be added as a paragraph under About the role or Responsibilities. Probably under About the role as additional description. Thus we need to ensure we preserve all substantive info: include that paragraph. Let's craft. About the role section: combine About Us paragraph, About The Role paragraph, and What This Role Is paragraph. We must be careful