Senior Product Manager | Prism

Overview Prism runs on third-party AI models, RAG/hybrid search and a set of Prism's own core agents, all coordinated by an orchestrator that Epicor built and owns. That orchestrator decides which model or agent should handle a given request, the guardrails and security controls make sure whatever handles it stays inside the lines, and the usage tracking and monetization systems turn that activity into a billable, accountable event. You own how all of that evolves: which models and core agents are available, how a new model gets evaluated and rolled out, how usage is tracked and monetized, and how safety and security controls keep pace as more of Prism runs through this layer. This is a foundational product role. You will work with the product teams building on top of Prism Core to make sure these shared services give them what they need, and with the engineers building the services themselves to decide what gets prioritized next. Epicor Epicor is a technology leader in ERP software for manufacturing, distribution, and retail, with deep roots in both enterprise software and startup culture. Our product organization is in the middle of a deliberate move to a platform-first, AI-enabled delivery model: building shared capabilities that many teams can build on, broadening how roles work together, and removing the silos and friction. How This Team Works The biggest change versus a traditional PM job is how the work gets done. We expect this leader to operate fluently in the model below, and to help the rest of the org adopt it. - Built as a platform, not a feature. Prism Core exists to be depended on by every other part of Prism. Reliability, safety, and ease of adoption for the teams building on it are the real measures of success, not any single feature. - A small, senior team, not a feature factory. Delivery happens in a lean, senior, cross-functional team working closely together against a system with built-in human oversight. You are inside that loop as the product decision-maker, not reviewing status from the outside. - Roles blur on a team like this. The lines between product, engineering, design, and architecture blur on a team this size. You work directly in specs, cross-team sequencing decisions, and real usage data, not a backlog handed over a wall. You keep clear ownership of product scope and decisions while picking up adjacent work that a small team requires. - Evidence. Model and platform changes are only shipped once they've passed Epicor's own evaluation suite and produced real usage data, not because a new model looked good in a demo. You own the success criteria. - Trust is the differentiator. Every model call, every agent action, and every dollar billed runs through the guardrails, security, and audit controls you own. Getting that right, not simply adding the newest model first, is what lets customers trust the platform with real business data. - Share openly. Open questions, usage patterns, and outcomes are shared across the org so people can see clearly what the platform can and can't yet promise. What We'd Love to See Empathy for two different customers. Real understanding of the end customer whose data, actions, and billing run through these services, and of the engineering and product teams deciding whether to build on them or work around them. You validate both before committing to a build. A platform mindset. You think about ease of adoption, reusable building blocks, and how many teams choose to build on your system the way a good platform product manager thinks about retention, not the way a feature team thinks about a single roadmap. Working Backwards: Demonstrates mastery of customer empathy, working backwards from customer pain points to validate the customer problems, ideal customer profiles, and value propositions. <