GTM Operations Analyst

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if content present. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invented details. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove "How To Be a Medisolver — Our Values" maybe not needed? It's values but not a required section; we could include maybe under a generic section? The instruction: include a section ONLY when posting has real, specific content for it. Values could be considered but not one of the listed headings. We should not create a section for values unless we map to one of allowed headings. The allowed headings are limited: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit content into those. We have description: "Who We Are" paragraph about company. Could go under About the role? Actually About the role is separate. "Who We Are" could be part of About the role? Probably we can put company overview under About the role? But the instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). So we should put the "Who We Are" under About the role? Might be okay. But we also have "About The Role" section later. So we could combine. We need to extract responsibilities: bullet list under "What You'll Do". That's responsibilities. Requirements: "Required Who We're Looking For — The Competencies That Matter" list. Qualifications: maybe "Preferred" list? Could treat as Qualifications? Or Skills? The instruction: Use sections as appropriate. We have Required (competencies) and Preferred (exposure). Could map Required to Requirements, Preferred to Qualifications or Skills. Also we have "How To Be a Medisolver — Our Values" maybe could be Skills? Not exactly. Better to omit values if not fitting. We have no explicit Pay, Benefits, Schedule info. So we should not include those sections. Thus output sections: About the role (company overview + role description), Responsibilities, Requirements, Qualifications (maybe Preferred), Skills (maybe from Required like attention to detail, analytical mindset, etc). But we need to avoid duplication. Let's parse content: Who We Are: paragraph about Medisolv. About The Role: description of GTM Operations Analyst role. What You'll Do: list of duties. Required: bullet list of competencies. Preferred: bullet list. We could map: - About the role: combine Who We Are + About The Role paragraph. - Responsibilities: What You'll Do list. - Requirements: Required list. - Qualifications: Preferred list (or maybe Skills). But we also have skills like "Strong attention to detail", "Basic reporting and analytics skills", "Strong bias for action", etc. Those are in Required list as competencies. Could treat them as Skills section. However Required list already includes those. Might be better to put Required as Requirements, and Preferred as Qualifications. Then Skills could be omitted or we could extract specific skills from Required (like attention to detail, analytical mindset, bias for action, collaboration). But to avoid duplication, maybe we just have Requirements and Qualifications. But instruction: Use sections only when posting has real, specific content for it. It's okay to have only About the role, Responsibilities, Requirements, Qualifications. We must not invent content. So we will output:

About the role

...combined paragraphs...

Responsibilities

• ... each duty...

Requirements

• ... each required competency...

Qualifications

• ... each preferred qualification...

We must preserve all substantive information. Ensure we don't miss any details from Required and Preferred. Let's extract exact text. From posting: Required Who We're Looking For — The Competencies That Matter - 5 plus years of experience in marketing operations, sales operations, revenue operations, or CRM administration - Familiarity with HubSpot (preferred) or comparable CRM/marketing automation tools - Strong attention to detail and a commitment to data accuracy - Basic reporting and analytics skills in HubSpot, Excel, or Google Sheets - Strong bias for action, with the initiative to drive tasks from inception to completion - Ability to collaborate cross-functionally and build relationships, even when priorities or personalities compete - Analytical mindset, with the ability to dissect problems and tell a clear story using data - Eagerness to learn Revenue Operations concepts and grow within the function Preferred Exposure to complementary GTM tools such as Gong, ZoomInfo, or Definitive - Experience supporting deal desk, quoting, or contracting workflows - A track record of spotting and implementing process or automation improvements - Prior experience in a SaaS or B2B environment Also there is "How To Be a Medisolver — Our Values" list but we can omit. Now About the role: combine Who We Are paragraph and About The Role paragraph. Who We Are paragraph: "Healthcare quality is complex. Medisolv helps make it manageable — and actionable. We partner with hospitals, health systems, ACOs, and payers to bring clarity to quality data, connecting clinical and claims information into a single, reliable view. More than 1,800 organizations and 130M+ patient records rely on Medisolv to measure, report, and improve performance across 500+ measures tied to CMS, The Joint Commission, and other programs. With support from Bessemer Venture Partners Forge, we're continuing to grow our platform and expand our impact — investing in advanced analytics, AI, and new capabilities that help healthcare organizations stay ahead of change and improve outcomes with confidence." About The Role paragraph: "Reporting to the GTM Operations Manager, we are looking for a GTM Operations Analyst to join our team. About The Role The GTM Operations Analyst is the tactical backbone of Medisolv's go-to-market engine. You'll manage the day-to-day execution, data integrity, and reporting that keep Sales, Marketing, Customer Success, and Services running smoothly — from HubSpot administration and CRM hygiene to dashboarding and lifecycle reporting. This role sits close to the systems and the data. You will maintain workflows and automations, keep the CRM clean and trustworthy, and build the dashboards and reports that give GTM teams visibility into pipeline health and performance. You'll partner closely with the GTM Operations Manager, translating day-to-day operational work into the visibility and process improvements the broader team relies on. As Medisolv continues to grow, you'll have the chance to build real depth across HubSpot and the wider GTM tech stack — and to grow into broader Revenue Operations responsibility over time." We need to avoid repeating "About The Role" heading inside paragraph; but we can just include the text. Now Responsibilities: list from "What You'll Do". Let's extract each bullet: - Manage day-to-day HubSpot administration, including user setup, permissions, workflows, and automation updates across Sales, Marketing, and Service Hubs - Maintain CRM data hygiene through deduplication, standardization, and ongoing quality checks - Build and maintain dashboards, lists, and reports that give GTM teams visibility into pipeline health, deal velocity, and conversion across the lead-to-customer lifecycle - Support campaign tracking, lead routing, and lifecycle process execution - Assist with day-to-day support of GTM system integrations, including HubSpot, Gong, ZoomInfo, and Definitive - Support quoting, contracting, and deal desk workflows, helping ensure deals move smoothly through approvals prior to close - Document GTM processes and provide end-user support and training across Sales, Marketing, and Service teams - Partner with the GTM Operations Manager on analytics, pipeline reporting, forecasting support, and process improvement initiatives Also there are performance objectives (first 30/60/90 days). Those could be considered responsibilities? They are more like expectations. Could include under Responsibilities as well. The instruction: preserve ALL substantive information. So we should include those as part of Responsibilities maybe as sub-bullets? But we can just add them as additional list items under Responsibilities. Let's extract: In your first 30 days, you will: Onboard and get to know the people, products, and departments that make Medisolv run. You'll build immersion in HubSpot, the GTM tech stack, and the lead-to-customer lifecycle, and begin shadowing existing workflows and reporting. In Your First 60 Days, You Will Begin independently managing day-to-day HubSpot administration, data hygiene checks, and recurring reporting, with support from the GTM Operations Manager as you take on more ownership. In Your First 90 Days, You Will Fully own your recurring GTM reporting, dashboards, and HubSpot administration responsibilities — contributing process documentation and partnering closely with the GTM Operations Manager on pipeline visibility and improvement initiatives. We can include these as list items. Now Requirements list as above. Qualifications list as preferred. Now ensure we don't include any boilerplate like "Medisolv is committed to creating a diverse and inclusive workplace..." etc. That's EEO boilerplate; we must remove. Also remove "How To Be a Medisolver — Our Values" etc. Now produce HTML. We must not include markdown fences. Just raw HTML. Let's craft.

About the role

Healthcare quality is complex. Medisolv helps make it manageable — and actionable. We partner with hospitals, health systems, ACOs, and payers to bring clarity to quality data, connecting clinical and claims information into a single, reliable view. More than 1,800 organizations and 130M+ patient records rely on Medisolv to measure, report, and improve performance across 500+ measures tied to CMS, The Joint Commission, and other programs. With support from Bessemer Venture Partners Forge, we're continuing to grow our platform and expand our impact — investing in advanced analytics, AI, and new capabilities that help healthcare organizations stay ahead of change and improve outcomes with confidence. Reporting to the GTM Operations Manager, we are looking for a GTM Operations Analyst to join our team. The GTM Operations Analyst is the tactical backbone of Medisolv's go-to-market engine. You'll manage the day-to-day execution, data integrity, and reporting that keep Sales, Marketing, Customer Success, and Services running smoothly — from HubSpot administration and CRM hygiene to dashboarding and lifecycle reporting. This role sits close to the systems and the data. You will maintain workflows and automations, keep the CRM clean and trustworthy, and build the dashboards and reports that give GTM teams visibility into pipeline health and performance. You'll partner closely with the GTM Operations Manager, translating day-to-day operational work into the visibility and process improvements the broader team relies on. As Medisolv continues to grow, you'll have the chance to build real depth across HubSpot and the wider GTM tech stack — and to grow into broader Revenue Operations responsibility over time.

Responsibilities

• Manage day-to-day HubSpot administration, including user setup, permissions, workflows, and automation updates across Sales, Marketing, and Service Hubs
• Maintain CRM data hygiene through deduplication, standardization, and ongoing quality checks
• Build and maintain dashboards, lists, and reports that give GTM teams visibility into pipeline health, deal velocity, and conversion across the lead-to-customer lifecycle
• Support campaign tracking, lead routing, and lifecycle process execution
• Assist with day-to-day support of GTM system integrations, including HubSpot, Gong, ZoomInfo, and Definitive
• Support quoting, contracting, and deal desk workflows, helping ensure deals move smoothly through approvals prior to close
• Document GTM processes and provide end-user support and training across Sales, Marketing, and Service teams
• Partner with the GTM Operations Manager on analytics, pipeline reporting