Vice President of Growth, Payers & Health Systems

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if content exists. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, accommodations, application instructions. Also remove "About Us" maybe? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we need to map content to those headings. The posting includes "About Us" (company description) maybe not needed as a heading? Could be considered "About the role"? Actually "About Us" is company overview, not role. The instruction says 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. It doesn't say we cannot have an "About Us" section, but the list of allowed headings includes "About the role". Probably we should include an "About the role" heading summarizing the role description (What We're Looking For etc). The "About Us" could be omitted or placed under "About the role"? The instruction: "Prefer a few substantive sections over many thin ones." So we could combine company overview into "About the role" maybe. But we need to preserve ALL substantive information; we cannot drop company overview. So we need to include it somewhere. Perhaps we can have a heading "About the role" and include both company overview and role description. Or we could have separate headings: "About Us" is not in allowed list, but we could still include it? 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 suggests using those. Safer to stick to those headings. So we need to map content: - About the role: could include company overview (About Us) and the description of the role (What We're Looking For, How You'll Make An Impact). That seems appropriate. - Responsibilities: likely the bullet points under "How You'll Make An Impact" (Enterprise Sales & Growth, Commercial Strategy & Partnerships, Leadership & Commercial Excellence). Those are responsibilities. - Requirements: the list under "Requirements What You’ll Bring:" (the bullet list). That's requirements. - Qualifications: maybe separate? The posting doesn't have a separate qualifications section; the requirements list includes qualifications. Could combine? But we need to include a section only when posting has real specific content for it. If we don't have distinct qualifications, we could omit Qualifications heading. Similarly Skills maybe part of requirements. Benefits: we have Benefits section with compensation and benefits details. Pay: we have compensation details inside Benefits; but we could separate Pay as its own heading if we have specific pay info. The Benefits section includes "Compensation: The base salary for this role is up to $200,000 annually plus bonus..." and then list of benefits. So we could have Pay heading for salary info, Benefits heading for other benefits. Schedule: maybe remote-first flexibility etc. Could be considered Schedule. The posting mentions "Remote-first flexibility and work-from-home support". That's schedule info. So we can have Schedule heading. We must not include placeholder text like "commensurate with experience". Not present. We must remove boilerplate: EEO, Reasonable Accommodations, "Ready to Join Us?" etc. Also remove "Learn more at solunaapp.com/impact." That's part of About Us but maybe keep as it's substantive? It's a link; maybe keep as part of About Us. It's not boilerplate. Keep. We must not include application instructions: "apply today". Remove. We must not include duplicated lines. Now craft HTML. Structure:

About the role

... company overview + role description ...

Then maybe

Responsibilities

• ... each responsibility ...

Then

Requirements

• ... each requirement ...

Then

Benefits

• ... benefits list ...

Then

Pay

... compensation details ...

Then

Schedule

... remote-first flexibility etc ...

We need to ensure we preserve all substantive info. Let's extract content. About Us paragraph: "At Kooth, our mission is to create welcoming, accessible spaces for personalized digital mental health care that empowers young people to thrive. Grounded in an early-intervention model, we help youth aged 10–25 build resilience, access timely support, and lead fulfilling lives. We are more than a digital service — we are a movement for inclusive, evidence-informed mental health care. Our culture is rooted in our values: Alongside You, Flexible, Compassionate, Committed, and Safe. These guide everything we do - how we show up for young people, how we collaborate as a team, and how we build solutions that meet communities where they are. With Kooth, you’ll be part of something bigger than yourself: meaningful work with measurable impact. We bring this mission to life through Soluna, a digital behavioral health service for 13–25-year-olds. Soluna removes barriers to care by providing immediate access to 1:1 coaching, Care Navigation, and self-guided tools helping young people find real support, build resilience, and discover hope when they need it most. Together with state and local partners, we’re transforming access to mental health support for youth. Learn more at solunaapp.com/impact." What We're Looking For paragraph: "The Vice President of Growth, Payers & Health Systems will lead Kooth's commercial growth across health plans, payers, health systems, IDNs, and other strategic healthcare and technology partners. This is a hands-on commercial leadership role responsible for building pipeline, winning new enterprise customers, and delivering contracted revenue. The VP will own the full sales cycle while helping shape Kooth's payer and health system go-to-market strategy and building the function as the business grows." How You'll Make An Impact section includes three subsections with bullet-like sentences. We need to convert each sentence into

maybe. Enterprise Sales & Growth: - Own and deliver annual payer, and health system sales targets, focused on net-new business, pipeline development, conversion, and forecasting. - Build and advance a healthy pipeline of enterprise opportunities across targeted payers, health systems, and other strategic channel partners. - Lead complex sales cycles from prospecting and discovery through proposal, negotiation, contracting, and close. - Build trusted relationships with C-suite and senior healthcare leaders and translate Kooth's clinical and commercial value into compelling customer propositions. - In collaboration with Kooth’s sales operations team, oversee strategic RFPs, RFIs, presentations, business cases, pricing discussions, and commercial negotiations in partnership with Finance, Legal, Clinical, and Product. Commercial Strategy & Partnerships: - Partner with Commercial leadership to define and execute Kooth's U.S. private-sector go-to-market and target-account strategy. - Maintain strong knowledge of payer and health system priorities, healthcare economics, reimbursement models, competitive dynamics, and emerging market opportunities. - Bring customer and market insights into Kooth's Product, Clinical, Marketing, and Service Delivery strategies. - Partner across teams to identify contracting, clinical, regulatory, credentialing, data, and operational requirements early in the sales process. - Ensure a seamless transition of new customers into implementation and Account Management while supporting strategic expansion opportunities. Leadership & Commercial Excellence: - Operate as a player-coach, personally leading key strategic opportunities while building and developing the payer and health system sales function. - Establish clear sales goals, pipeline discipline, forecasting, account planning, and deal-review processes. - Provide executive leadership with clear reporting on pipeline, bookings, deal progression, risks, and market trends. - Represent Kooth at customer meetings, conferences, industry events, and other strategic opportunities. Now Requirements list: "What You’ll Bring:" then bullet points (some with (Preferred) after). We need to keep all. List: - 10+ years of enterprise sales and commercial growth experience, with demonstrated hunting and net new client generation focus, in healthcare, with proven experience selling into payers and health systems, or other complex healthcare organizations - Proven success sourcing, developing, negotiating, and closing complex enterprise partnerships while consistently achieving sales or revenue targets - Track record of delivering against near-term growth objectives while simultaneously building commercial infrastructure, processes, and organizational capabilities needed to support sustainable scale - Deep understanding of the U.S. payer and health system landscape, including procurement, contracting, healthcare economics, and commercial decision-making - Strong C-suite relationship-building skills and experience navigating long, multi-stakeholder enterprise sales cycles - Strong commercial and financial acumen, including business cases, pricing, negotiations, and healthcare payment models - Strong pipeline management and forecasting discipline, with experience using Salesforce or a comparable CRM - Exceptional executive presence, communication, presentation, negotiation, and storytelling skills - Bachelor’s degree or equivalent relevant professional experience - Experience selling digital health, behavioral health, virtual care, healthcare technology, or tech-enabled healthcare services - (Preferred) Existing executive relationships across U.S. health plans, payers, and/or health systems - (Preferred) Experience building or scaling a healthcare sales function or go-to-market strategy - (Preferred) Experience within mental health, behavioral health, pediatric/adolescent health, or population health We need to keep the (Preferred) notation. Now Benefits section: "Benefits What You’ll Get: Compensation: The base salary for this role is up to $200,000 annually plus bonus based on personal and company performance. We’re committed to transparency and value our candidates time, which is why we share salary ranges in all states—regardless of local requirements. Final compensation will be based on a variety of factors, including your education, experience, skills, and overall alignment with the role. Kooth offers a competitive base salary, employee equity program, and comprehensive benefits including: Excellent Medical, Dental, and Vision Coverage 401(K) Retirement Plan with company match Generous Paid Time Off Remote-first flexibility and work-from-home support Paid parental leave Learning & development opportunities 8 Paid Holidays, plus two half-day holidays (Christmas Eve and New Year’s Eve)" We need to separate Pay and Benefits. Pay: base salary up to $200k annually plus bonus based on personal and company performance. Also mention salary ranges transparency etc. Could include that. Benefits: list of benefits: Excellent Medical, Dental, and Vision Coverage; 401(K) Retirement Plan with company match; Generous Paid Time Off; Remote-first flexibility and work-from-home support; Paid parental leave; Learning & development opportunities; 8 Paid Holidays, plus two half-day holidays (Christmas Eve and New Year’s Eve); employee equity program (mentioned earlier). Also "competitive base salary" already in pay. We'll create Pay paragraph with compensation details. Benefits ul list. Schedule: Remote-first flexibility and work-from-home support is already in benefits but could be schedule. However we already used remote-first in benefits. Might duplicate. Better to keep schedule separate: maybe mention remote-first flexibility and work-from-home support as schedule. But we already have it in benefits list; we could keep it only under Schedule and not duplicate. However we need to preserve all info; we can mention it under Schedule and not duplicate in benefits. But benefits list also includes remote-first flexibility; we could keep it there and not have schedule. But schedule section is optional; we can omit if not distinct. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine remote-first into benefits and not have schedule. However we need to include schedule only if posting has real specific content for it. It does mention remote-first flexibility and work-from-home support, which is schedule-related. Could