CRM Operations Lead

We need to output HTML fragment with sections: About the role? Actually the posting includes "Position Overview: CRM Operations Lead". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only when there is real specific content. We have content: Position Overview (description). Could map to "About the role". Responsibilities: list of responsibilities. Requirements/Qualifications: the "You SHOULD apply to this role if:" list and "You SHOULD NOT apply..." maybe treat as Requirements? Could combine. Also "Core Outcomes Success in this role means:" maybe part of responsibilities or qualifications. We'll treat as part of Responsibilities or maybe "Key Outcomes". But we only allowed headings from list. Could put under Responsibilities. Compensation & Logistics: includes Job Type, OTE, Additional Compensation, Schedule, Location, Compensation Range. So we can have Pay section (OTE range) and Schedule section (Monday-Friday 9-6). Benefits? Not mentioned besides bonus opportunities. Could include Benefits? Not explicit. We'll include Pay and Schedule. Location maybe not needed as heading; could be in a short p. We must not include boilerplate like EEO etc. Not present. We must not include application instructions. We need to preserve all substantive info. Let's craft:

About the role

A Snapshot of Curvion Blue ... (the introductory paragraph about company) ... Position Overview: CRM Operations Lead ... (the paragraph describing role).

But we need to avoid repeating job title as heading; okay. We need to include the company description maybe as part of About the role. Then Responsibilities: list bullet points from Responsibilities section. Then Requirements/Qualifications: combine the "You SHOULD apply..." and "You SHOULD NOT apply..." plus maybe Core Outcomes. We could split into Requirements and Qualifications but we can just have one Requirements section. But we need to follow instruction: use headings for those categories if content exists. We'll include Requirements and maybe Qualifications if distinct. However we have both "You SHOULD apply..." (qualifications) and "Core Outcomes" (success metrics). Could treat Core Outcomes as part of Responsibilities or Qualifications. Let's put Core Outcomes under Responsibilities as they describe success. Thus we have sections: About the role, Responsibilities, Requirements, Pay, Schedule. We must not create Benefits unless stated; we have bonus opportunities mentioned under Additional Compensation; could be part of Pay. Pay section: include OTE $72,000 - $100,000 annually, Additional Compensation: Bonus opportunities. Schedule: Monday-Friday, 9:00 AM-6:00 PM. Location: Remote maybe in a p under About the role or separate short p. We must not include Job Type etc as headings; we can embed in Pay or Schedule. Let's craft HTML. We need to ensure we use

• for any list of duties/requirements/benefits. Thus Responsibilities: list items. Requirements: list items from the SHOULD apply and SHOULD NOT apply? Could combine but we need to keep all info. We'll make two lists: "You should apply if:" and "You should NOT apply if:" maybe as separate
  under Requirements. We also need to include the Core Outcomes list maybe as part of Responsibilities. Let's extract details. Company description paragraph: "A Snapshot of Curvion Blue 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. Think of a lead generation-based marketing agency... but focused on sales. 🤪 Our clients bring us in when they need to build, optimize, or scale their revenue engine without having to build the entire infrastructure themselves. We architect end-to-end sales solutions by designing custom sales motions, implementing GTM strategies, configuring CRM and sales infrastructure, deploying AI-enabled tools, and providing highly trained sales talent to execute the system. Our approach combines technology, strategy, systems, and people. We use battle-tested playbooks and proprietary processes to help our clients generate revenue faster, more efficiently, and with greater consistency, visibility, and control. Our experience spans the alternative education space, including business consulting, real estate investing, mergers and acquisitions, sales training, and other transformative programs, as well as the SaaS industry, where we help innovative technology companies bring their products to market. In short, we build and deploy revenue engines. And CRM is a major part of that engine." Position Overview paragraph: "CRM Operations Lead 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. But this isn't a "keep the CRM running" role. We're looking for someone who naturally sees the next level of the system. Where are we creating unnecessary friction? Where is data breaking down? What should be automated? Where are teams working around the CRM instead of through it? What needs to be standardized before we scale it? You'll help identify those opportunities and turn them into better systems, cleaner data, stronger processes, and more scalable revenue operations. 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." We'll combine those into About the role. Responsibilities list: from "Responsibilities" section: - CRM Configuration & Optimization - 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 - Client & Account Deployment - 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 - Data Integrity & Governance - 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 - Documentation & Enablement - 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 - Revenue Operations - 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 We could flatten but keep hierarchy? Use
  • and maybe nested lists? Probably okay to have nested
    . We'll keep simple: each bullet as
    • with sub-bullets as nested
      . Core Outcomes list: "Success in this role means:" items: - 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 We could add these under Responsibilities as additional bullet list maybe separate heading? But we only allowed certain headings; we could incorporate them under Responsibilities as part of responsibilities. Requirements list: "You SHOULD apply to this role if:" items: - 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 "You SHOULD NOT apply to this role if:" items: - 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 We'll put these under Requirements maybe split into "Qualifications" and "Disqualifiers"? But we only have allowed headings; we could have Requirements and maybe "Qualifications". We could put the SHOULD apply list under Requirements, and the SHOULD NOT apply list under a separate heading like "Disqualifiers" but not allowed. Could combine both into one Requirements section with two subheadings? Not allowed to create extra headings beyond the list? The instruction: "Use

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

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should stick to those. So we can have Requirements and Qualifications separate. We'll put the SHOULD apply list under Requirements, and the SHOULD NOT apply list under Qual