CRM Operations Lead

We need to output HTML fragment with sections: About the role? The posting includes "Position Overview: CRM Operations Lead". That could be "About the role". Also "Responsibilities" with bullet list. "Core Outcomes" maybe "Qualifications"? Actually "Core Outcomes" could be "Requirements" or "Qualifications". The posting includes "You SHOULD apply to this role if:" and "You SHOULD NOT apply to this role if:" which are qualifications/requirements. Also "Compensation & Logistics" includes Pay and Schedule. So schedule. We need sections: About the role (position overview), Responsibilities, Requirements (maybe combine qualifications), Benefits? Not given. Pay and Schedule: we have OTE and schedule. So we can have Pay section and Schedule section. Benefits not mentioned, so omit. Also maybe "Qualifications" could be the SHOULD apply/not apply lists. We'll create sections: About the role (position overview paragraph), Responsibilities (ul), Requirements (ul combining should/should not? Might be better to split into Qualifications and maybe "Ideal Candidate"? But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include only those with real content. We have About the role, Responsibilities, Requirements (maybe the SHOULD apply list), Qualifications (maybe the SHOULD NOT list? but that's not qualifications). Could combine both into Requirements. Or we could have Requirements (should apply) and Qualifications (should not apply) but that seems odd. Better to have Requirements (should apply) and maybe Skills (should not apply?) Not ideal. Perhaps we treat SHOULD apply as Requirements, and SHOULD NOT apply as "Skills"? Not correct. Could instead have Requirements (should apply) and Qualifications (should not apply) but that is weird. Maybe we can omit Qualifications and Skills sections if not clearly defined. The instruction: "Prefer a few substantive sections over many thin ones." So we can include About the role, Responsibilities, Requirements (combining should/should not), Pay, Schedule. That's five sections. Benefits omitted. We'll not include Qualifications or Skills. We need to preserve all substantive information. Must not repeat job title as heading. Use

for section headings. Use

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

  for prose. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to include all substantive info: position overview paragraph, responsibilities bullet list, core outcomes maybe part of responsibilities? Actually core outcomes are separate but could be part of responsibilities or qualifications. We'll include them under Responsibilities? Might be better to include them as part of Responsibilities? But they are outcomes. Could be under Requirements? Not sure. We could create a section "Core Outcomes" but not in allowed headings list. The allowed headings list includes specific ones; we should not create other headings. So we need to map core outcomes to one of the allowed headings. Perhaps they belong under Responsibilities (as expected outcomes) or under Requirements (as success metrics). I'd put them under Responsibilities as they describe what success looks like. But we already have responsibilities list; we could add them as part of responsibilities prose. However we must not invent or summarize away detail. We need to preserve all substantive information; we can include them as a

  under Responsibilities heading before the

  . That's fine. Similarly, the "You SHOULD apply..." and "You SHOULD NOT apply..." lists are qualifications/requirements. We'll put them under Requirements heading as two lists? Could be separate
  for should and should not. We'll preserve both. Compensation & Logistics: includes Job Type, OTE, Additional Compensation, Schedule, Location, Compensation Range. We need Pay section (include OTE and bonus opportunities). Schedule section (Monday-Friday 9-6). Location maybe not a heading; we could include location in About the role paragraph or as a short

  under Pay? But location is not Pay or Schedule. Could include in About the role paragraph as extra info. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." Location is minor metadata; we can fold into a short

  under About the role or maybe under Pay? Probably under About the role. We must not include boilerplate like "Job Type: Full-time, W-2". That's minor metadata; we could include in About the role paragraph or maybe under Pay? But Pay section should contain compensation details. Job type could be placed in About the role paragraph. We need to output only HTML fragment. Let's craft:

  About the role

  Curvion Blue is a high‑performance RevOps & sales augmentation agency that installs and deploys enterprise‑grade, AI‑driven revenue engines and selling systems for growing companies. The CRM Operations Lead is a critical role responsible for strengthening and scaling the CRM infrastructure that powers Curvion Blue's sales delivery. This role is laser‑focused on HubSpot configuration, data integrity, system optimization, and operational enablement. You'll help ensure that the CRM environments supporting our sales organizations are clean, reliable, scalable, and built to support high‑performance selling. You'll play a key role across the CRM lifecycle, from system design and documentation to new account deployment, ongoing optimization, auditing, and maintenance. You'll work closely with RevOps, sales leadership, data, and other operational stakeholders to improve the systems and processes behind pipeline management, reporting accuracy, sales productivity, and revenue visibility. This role is ideal for a hands‑on CRM operator who enjoys working inside complex systems, improving what already exists, and building infrastructure that allows sales teams to move faster without sacrificing visibility or control. Location: Remote. Job Type: Full‑time, W‑2.

  Responsibilities

  Success in this role means:

  • HubSpot workflows, pipelines, automations, and configurations are continuously improved for scalability, reliability, and performance
  • CRM data is clean, accurate, structured, and trustworthy
  • Reporting and data pipelines receive the information they need to function properly
  • CRM inefficiencies and system gaps are identified and addressed proactively
  • New client accounts can be onboarded with consistent, scalable CRM infrastructure
  • Integrations between HubSpot and the broader sales technology stack function reliably
  • CRM documentation, SOPs, and playbooks remain current, actionable, and easy to follow
  • CRM standards and governance are consistently applied across teams
  • Sales teams have the systems and infrastructure they need to operate effectively
  • CRM initiatives move from idea → implementation without getting stuck in operational limbo

  Key duties include:

  • Configure, maintain, and continuously optimize HubSpot workflows, pipelines, properties, automations, views, and other CRM functionality
  • Audit existing CRM environments and identify opportunities to improve structure, usability, efficiency, and performance
  • Troubleshoot CRM issues and identify root causes rather than relying on temporary fixes
  • Evaluate existing processes and recommend opportunities for automation and system improvement
  • Support CRM setup and deployment for new Curvion Blue client accounts
  • Help configure CRM environments to support each client's sales motion and operational requirements
  • Coordinate CRM integrations with dialers, scheduling platforms, reporting tools, and other sales technology
  • Ensure new environments follow established configuration and data standards
  • Maintain strong CRM data integrity and establish standards for accurate, consistent data entry
  • Audit CRM data and system usage to identify gaps, inconsistencies, and process breakdowns
  • Partner with the data team to ensure CRM configuration supports reporting, analytics, and downstream data pipelines
  • Help establish and maintain CRM governance standards as the organization scales
  • Create and maintain CRM documentation, SOPs, workflows, playbooks, and process guides
  • Help translate complex CRM processes into clear, usable resources for sales and operations teams
  • Support onboarding for new sales hires and account teams to ensure CRM adoption and process alignment
  • Provide guidance on CRM best practices and help teams troubleshoot system challenges
  • Partner with RevOps and sales leadership on forecasting, reporting, pipeline management, and operational initiatives
  • Identify CRM-related bottlenecks that impact sales productivity or revenue visibility
  • Support CRM projects tied to quarterly priorities and broader company initiatives
  • Contribute ideas and recommendations that improve the scalability and effectiveness of Curvion Blue's revenue infrastructure

  Requirements

  • You've designed, configured, optimized, or administered HubSpot or another CRM at a meaningful level
  • You've worked with CRM environments supporting multiple teams, business units, or organizations
  • You enjoy improving and scaling existing systems, not just building from scratch
  • You've supported CRM deployments, migrations, or implementations, including integrations with dialers, schedulers, reporting tools, or other sales technology
  • You naturally look for ways to automate repetitive processes and eliminate operational friction
  • You care deeply about data integrity, reporting accuracy, and system governance
  • You're comfortable auditing CRM environments and identifying gaps in structure, usage, configuration, or performance
  • You can translate business requirements into practical CRM solutions
  • You can balance strategic thinking with hands‑on execution
  • You enjoy creating documentation, SOPs, playbooks, and processes that make systems easier to use and scale
  • You enjoy working cross‑functionally with RevOps, sales, data, and leadership
  • You're energized by scalability, standardization, and continuous improvement

  Requirements (cont.)

  You should NOT apply if:

  • You've primarily used a CRM but haven't configured, optimized, or managed one
  • You prefer simply completing tickets over identifying and solving systemic problems
  • You'd rather build something new than improve a system that's already in motion
  • Auditing data, workflows, and system architecture sounds painfully boring
  • You avoid documentation, process standardization, or governance
  • You need complete ownership before you're comfortable making an impact
  • You're uncomfortable working across multiple teams and stakeholders
  • You rely primarily on certifications or theory without meaningful hands‑on CRM experience
  • You're looking for a role where the system stays the same once you've built it
  • You aren't interested in thinking about how the CRM can make the sales organization better
  But we have duplicated heading "Requirements". Better to combine should and should not under same heading with two lists, maybe with a heading "You should apply if:" and "You should NOT apply if:" as

  then lists. But we must not create new headings beyond allowed list. We can keep a single Requirements heading and include both lists with introductory paragraphs. Let's do:

  Requirements

  You should apply if:

  ...

  You should NOT apply if:

  ...
  That preserves content. Now Pay and Schedule sections.

  Pay

  OTE: $72,000 - $100,000 annually. Additional compensation: bonus opportunities.

  Schedule

  Monday‑Friday, 9:00 AM‑6:00 PM.

  We