Business Operations Manager

We need to output HTML fragment with sections: About the role, Responsibilities? Actually the posting includes sections: About The Role, What You'll Own, What You'll Work Across, What We Look For, What we offer, Compensation, About Pathpoint (maybe not needed?), but we need to include only sections with real content. Also we must not repeat job title as heading. Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove Notes about visa sponsorship? That's legal/EEO? Probably remove. Also remove "Compensation Range: $115K - $140K" duplicate? We'll keep compensation section with base salary range. We need to preserve all substantive information. Let's extract content. Original posting: Business Operations Manager - Communications & AI Systems About The Role Pathpoint's Business Operations team builds and runs the production systems behind how we quote, bind, and service E&S insurance for 25,000+ agencies nationwide. This role exists to make our customer communications best in class: everything an agent or insured hears from us, across email, campaigns, and telephony, and the AI systems that increasingly draft and drive it. In parallel, you'll build the automations that keep agents and insureds informed without anyone having to reach out in the first place. You will take end-to-end ownership of our communications domain: lifecycle and campaign messaging, our shared email operations layer, our telephony and conversation-intelligence surface, the reporting across all of it, and a growing set of production AI agents that draft, triage, and respond to customer communications. We are looking for someone who thrives on problem-solving and is unfazed by ambiguity. You will own the systems, the processes around them, and the outcomes they produce. Some of this is live and needs to be improved upon. Some parts do not exist yet and we are looking for someone with the design prowess to build them. This ownership extends past the current infrastructure: we expect you to proactively find problems worth solving, including ones that don't fit neatly inside today's workflows, and to bring teams along as you change how things work. What You'll Own The communications layer stack end to end, currently running on::Customer.io: segmentation, Liquid templating, lifecycle and transactional campaigns, and the data pipeline that feeds them. Front: shared inbox administration and operations. Routing, triage, rules and automation, assignment, permissions, and workload distribution across the teams working in it, plus turning high-volume inbound into signal. Dialpad and Attention: telephony administration, conversation intelligence, insight generation, and making our call data as useful as our written channels. Reporting across the domain. Some of these systems are new and do not have reporting developed yet. You will write the SQL, build the reporting, and be the person who can say whether what you shipped worked. Production AI systems in this domain: extending and operating our existing AI email agents, monitoring them, catching regressions, and tuning them. You will not need to architect new agents from scratch, but you will be the person who knows when one is behaving badly and why. Quality and rollout for customer-facing communications: evaluation approaches, guardrails, staged releases, and the judgment to know when a system is ready for production and when it isn't. What You'll Work Across You'll operate in a business operations team, which means domain ownership comes with range. You won't be the deepest person in these on day one, but you'll be expected to work in them as needed with support from the team: Salesforce, as a reader: your systems read CRM data by way of our warehouse, so understanding an unfamiliar enterprise data model matters. Administering it does not; others cover that. The n8n automation layer where workflows that integrate Salesforce, our communications platforms, and LLM APIs live. What We Look For 3-6 years in marketing operations, revenue operations, business operations, or a similar systems-heavy role. We care more about what you've shipped than how long you've been shipping. If your experience is unusually deep for its length, we want to hear from you. Ability to write SQL against a production warehouse independently. You will own reporting for your domain. You should be able to reason about joins across several tables and know why a plausible-looking number is wrong before you send it to anyone. Platform skill in at least one communications system, either a lifecycle and campaign platform (Customer.io, Braze, Iterable, Marketo) or a shared inbox and support platform (Front, Zendesk, Intercom, Gmail or Outlook shared mailboxes at volume), including templating or routing logic and data integration, not just campaign building. Comfort with APIs, webhooks, and data syncs, including systems with poor documentation or none. Everything in this stack is joined together by them and there is no engineer to hand that work to. Evidence you have designed a system other people work inside: queues, routing, escalation, SLAs, or anything where a human operator's day depends on your design being right. Hands-on experience operating AI in production, not just using it. You've extended and run LLM-powered workflows or agents that real users depend on, you've dealt with prompt regressions, evaluation, and failure modes, and you have opinions about what makes AI systems reliable versus demo-ware. Strong communication judgment. This role will own domains where language is going out under our name, written or spoken through our systems, and you can tell the difference between a message that's fine and one that's right. An owner's disposition. You debug your own work, you fix root causes rather than filing tickets, and when something breaks near your domain, your first move is to pick it up, not to ask whose it is. Nice to have n8n, Zapier, or similar workflow-automation depth Salesforce administration at the object and automation level Insurance or fintech operations exposure Experience being the sole or founding owner of a system surface Experience building system integrations Prior roles in Sales Operations, Marketing Operations, or Revenue Operations What we offer Insurance coverage fit for an insurance company – with some plans at no cost to you Competitive compensation, equity, and total rewards 401(k) with a 2% bi-weekly employer match 20-days of PTO (increased to 25-days after 2-years) Professional development opportunities Remote-first working environment with investments in in-person collaboration Annual $500 home office stipend Monthly $75 internet stipend Generous paid parental leave An insurance partner offering unique opportunities for professional growth Compensation The expected base salary for the position at the start of employment is $115,000–140,000. Actual compensation is based on factors such as, but not limited to, applicable job experience, skills, and qualifications. Base salary is just one component of Pathpoint's Total Rewards package, which includes equity grants and generous employee benefits fitting of an insurance company. About Pathpoint Pathpoint's Values: Hard Problems Drive Us: We believe the insurance industry hasn’t kept up with changing times and fixing that is a hard problem worth solving. We Start with Why: Seek to understand what customers care about. Use data to challenge assumptions and figure out the problem. We Take Ownership and Accountability: We think people are their happiest when they have high ownership and accountability over the problems confronting them and are empowered to move decisively to work on them. We Work Together: Nothing happens without the individual efforts of our team members, but effective teamwork is how we build and maintain customer value. We Move Forward: We value the ability to persist through adversity to achieve goals and believe speed plays an important role. Notes: We are unable to provide visa sponsorship for this position at this time. By applying to this job, you confirm that you are eligible to work in the U.S. without requiring visa sponsorship now or in the future. Thank you for your understanding. Pathpoint is an equal opportunity employer that values diversity, inclusion, and belonging. We do not discriminate on the basis of race, religion, color, national origin, gender, sexual orientation, age, marital status, veteran status, or disability status. Compensation Range: $115K - $140K We need to remove boilerplate: Notes about visa sponsorship, EEO statement, etc. Also remove duplicate compensation line at end. We need to keep sections: About The Role, What You'll Own, What You'll Work Across, What We Look For, What we offer, Compensation, About Pathpoint (maybe keep values? It's substantive but not boilerplate; it's company values. Could keep as section "About Pathpoint". The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The About Pathpoint section has values, which is specific content. So we can keep. We need to format with

  headings. Use

  • for any list of duties/requirements/benefits. For prose use

    . We need to decide what constitutes a list. In sections like "What You'll Own" there are bullet-like sentences separated by periods but not explicit list. Could treat as prose. However there are enumerated items like "Customer.io: segmentation, Liquid templating, lifecycle and transactional campaigns, and the data pipeline that feeds them." Not a list. Might be okay as prose. But "What we offer" includes bullet-like lines each starting with a benefit. Those could be turned into

    • . Similarly "What We Look For" includes many bullet-like requirements. Could turn into list. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep each requirement as separate list item. Let's parse each section. About The Role: multiple sentences. We'll put in

      . What You'll Own: sentences describing ownership. Could be

      with maybe sub-bullets? The text includes colon-separated items: Customer.io: ..., Front: ..., Dialpad and Attention: ..., Reporting across the domain..., Production AI systems..., Quality and rollout... Could treat as

      but maybe better to break into

      • for each major component. However the instruction: Use
        • for any list of duties/requirements/benefits. This is a list of duties (what you'll own). So we can make list. What You'll Work Across: also list of items (Salesforce, n8n). Could be list. What We Look For: list of requirements; also Nice to have sublist. What we offer: list of benefits. Compensation: prose. About Pathpoint: values; could be list of values or prose. We'll need to ensure we don't include boilerplate like "Notes:" etc. Let's craft HTML. Structure:

          About the Role

          ...

          What You'll Own

          • Customer.io: segmentation, Liquid templating, lifecycle and transactional campaigns, and the data pipeline that feeds them.
          • Front: shared inbox administration and operations, routing, triage, rules and automation, assignment, permissions, workload distribution across teams, and turning high-volume inbound into signal.
          • Dialpad and Attention: telephony administration, conversation intelligence, insight generation, and making call data as useful as written channels.
          • Reporting across the domain: writing SQL, building reporting, and assessing whether shipped work succeeded.
          • Production AI systems: extending and operating existing AI email agents, monitoring, catching regressions, and tuning them.
          • Quality and rollout for customer-facing communications: evaluation approaches, guardrails, staged releases, and judgment to know when a system is ready for production.
          But need to preserve exact wording? We must not invent or summarize away detail. We can keep the substance but rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So