EverPro - Lead Product Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section only when posting has real, specific content. So we need sections: About the role (the paragraph after "About The Role"), Responsibilities (list), Skills and Experience needed for success in this role (list), Benefits and Perks (list), Pay (compensation). Also maybe "Where" could be considered Schedule? Not exactly schedule; but they ask to include Schedule only if posting states schedule. There's no explicit schedule info besides remote/hybrid etc. Could treat as "Work Location" but not requested. Probably we omit Schedule. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, equal-opportunity, scam-warning, application instructions, cookie/navigation/legal. Also remove duplicated lines. We need to preserve all substantive information. So we need to include the description of EverCommerce, EverPro, ZyraTalk etc? That's part of "About the role"? Actually the initial paragraphs about EverCommerce and EverPro are company overview, not role-specific. Should we include them? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company overview is substantive but not part of role. However the instruction about sections: use headings for sections like About the role, Responsibilities etc. The company overview could be placed before any heading as prose (
) because it's not a section heading. The instruction says: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other prose before headings. So we can include a
with company overview. We also need to include "About The Role" heading with its content. Responsibilities: list items from "Responsibilities:" and also "What You’ll Do" maybe considered part of responsibilities? The posting has "Responsibilities:" then bullet list, then "What You’ll Do" with more bullet-like sentences. We should combine them into a single
- list? The instruction: Use
- for any list of duties/requirements/benefits. So we should treat both sections as list items. We'll combine. Skills and Experience needed for success in this role: there is a heading "Skills and Experience needed for success in this role:" then a numbered list (1-10). Then "Nice To Have" list. We should include both as list items under Skills section? Could separate into Required and Nice-to-have but both are skills. We'll just list all items as
- . We'll preserve the numbering? Not needed; just content.
Benefits and Perks: list after "Benefits and Perks:" with bullet points starting with dash. We'll list each.
Compensation: after "Compensation:" paragraph. We'll put as
maybe but it's a single paragraph. Could also be
- but it's not list. We'll use
- Lead the product strategy, roadmap, and execution for ZyraTalk as part of the EverPro product portfolio.
- Define and drive the EverPro Voice product line, including how AI voice capabilities integrate into and enhance EverPro’s vertical SaaS products.
- Identify and prioritize integration opportunities across EverPro products, with a focus on customer communication, scheduling, lead capture, missed-call handling, support workflows, and revenue conversion.
- Partner with engineering, design, AI/platform teams, customer success, sales, and business unit leaders to deliver high-impact voice and AI-powered workflows.
- Build a deep understanding of home services SMB customers and how voice automation can reduce administrative burden, improve responsiveness, and drive business outcomes.
- Translate customer needs, product usage, and business priorities into clear requirements, product briefs, launch plans, and success metrics.
- Own product discovery, customer feedback loops, competitive analysis, and market insights for AI voice and receptionist capabilities.
- Drive adoption and commercialization of voice offerings across EverPro, including packaging, positioning, enablement, and expansion opportunities.
- Establish product KPIs and operating rhythms to measure usage, quality, retention, revenue impact, customer satisfaction, and operational effectiveness.
- Help lead the transition from founder-led product intuition to a scalable product management discipline for the ZyraTalk product area.
- Create a compelling product vision for AI voice within EverPro and turn that vision into an actionable roadmap.
- Work closely with engineering to continue developing ZyraTalk’s core capabilities, including call handling, conversational flows, integrations, routing, summaries, handoffs, analytics, and customer-specific configuration.
- Partner with EverPro product teams to determine where voice should be embedded directly into existing workflows and where it should operate as a standalone or cross-product offering.
- Prioritize product investments across core ZyraTalk enhancements, platform integrations, customer-specific needs, and scalable shared capabilities.
- Collaborate with go-to-market teams to define target customers, packaging, pricing inputs, sales enablement, launch sequencing, and expansion motions.
- Partner with AI and platform leaders to ensure voice capabilities align with EverPro’s broader agentic platform strategy, including shared tooling, data access, observability, security, and reusable agent patterns.
- Develop a strong point of view on the AI voice market, including competitive offerings, customer expectations, technical constraints, and emerging opportunities.
- Bring clarity and momentum to a product area with high strategic importance and significant cross-portfolio potential.
- 10+ years of product management experience, including experience owning complex SaaS products or platform capabilities.
- Experience with AI, voice, conversational products, communications platforms, workflow automation, or customer engagement tools strongly preferred.
- Proven ability to lead product strategy and execution in a cross-functional environment.
- Strong customer discovery skills and ability to translate qualitative and quantitative insights into product decisions.
- Experience working with engineering teams on technically complex products, integrations, APIs, data workflows, or platform capabilities.
- Ability to balance near-term customer and business needs with longer-term platform and product strategy.
- Strong analytical skills, including comfort defining success metrics, evaluating adoption, and making prioritization decisions based on data.
- Excellent communication skills, with the ability to align executives, product teams, engineering, sales, customer success, and other stakeholders.
- Comfort operating
. We must not include sections like "Requirements", "Qualifications" unless present. Not needed. We must not include placeholder text like "commensurate with experience". Not present. We must not include boilerplate like EEO etc. Remove the equal opportunity paragraph and AI use policy etc. Also remove "Learn more at EverCommerce.com." maybe part of company overview? It's substantive? It's a link; but it's not essential? It's part of company overview. Might keep but it's a link; but we can keep as plain text without link? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The link is substantive; we could keep as plain text "Learn more at EverCommerce.com." but we should not include actual HTML anchor? Probably just text. Also remove "Please note that you must be eligible to work without sponsorship to qualify for this position, and this role may require travel to our Corporate Headquarters in Denver, Colorado, or to other office locations around North America." That's substantive about location/eligibility; maybe we should include under a section? Not specified heading. Could be part of "About the role" or separate? It's not a list; we could add a
after About the role? But we already have About the role heading with its content. Could add a separate paragraph after that heading about location/eligibility. However the instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we could add a
after About the role heading for location/eligibility. But we already have About the role heading with its content; we could append that location info as part of About the role paragraph. That seems okay. Also "Where: The EverCommerce team is distributed globally..." That's location info; we can incorporate. Thus About the role section will include the paragraph(s) describing role plus location/eligibility. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:
EverCommerce (Nasdaq: EVCM) is a leading service commerce platform, providing vertically-tailored, integrated SaaS solutions that help more than 745,000 global service-based businesses accelerate growth, streamline operations, and increase retention. Its modern digital and mobile applications create predictable, informed, and convenient experiences between customers and their service professionals. With its EverPro, EverHealth, and EverWell brands specializing in Home, Health, and Wellness service industries, EverCommerce provides end-to-end business management software, embedded payment acceptance, marketing technology, and customer experience applications. Learn more at EverCommerce.com. We are building an extraordinary company and looking for talented, energetic, and motivated people to join our team. You can learn more about our Company, Culture and Values here: https://www.evercommerce.com/about-us/careers/ EverPro, a business within EverCommerce, provides software and solutions designed to help home and field service businesses run and grow their companies with greater efficiency and confidence. EverPro brings together purpose-built tools across key trades—including field service, remodeling and roofing, landscaping, and pest and lawn—so service professionals can manage operations, engage customers, and drive long-term growth. Our solutions support the full lifecycle of running a service business, from scheduling and dispatching work, to estimating, invoicing, and payments, to customer communication, reputation management, and business insights. Together, these connected solutions help service pros win more jobs, save time, and build stronger, more resilient businesses.
About The Role
EverPro is hiring a Senior Product Manager to lead the next chapter of ZyraTalk, our AI-powered voice and receptionist product line. ZyraTalk was recently acquired by EverCommerce and is now becoming a core part of EverPro’s AI and customer engagement strategy across our portfolio of home services software products. This role will own the product direction for ZyraTalk while also driving the broader EverPro Voice product line: deepening integrations into EverPro Product Suite; expanding the value of AI voice across customer communication workflows; and helping shape how voice agents become an embedded, revenue-driving capability across the EverPro suite. The ideal candidate is a senior product leader who is comfortable operating at the intersection of AI, voice, SaaS workflow automation, customer experience, and platform integration. They should be able to translate market opportunity and customer pain into clear product strategy, partner closely with engineering and go-to-market teams, and bring structure to a product area entering its next phase of scale. Where: The EverCommerce team is distributed globally, with teams in the U.S., Canada, the U.K., New Zealand, and Australia. With a widely distributed team, we are used to working remotely across different time zones. This role can be based anywhere in the United States or Canada – if you’re close to one of our offices, we can set you up in-office or you can work 100% remotely. Please note that you must be eligible to work without sponsorship to qualify for this position, and this role may require travel to our Corporate Headquarters in Denver, Colorado, or to other office locations around North America.
Responsibilities
Skills and Experience needed for success in this role