The Product Experience Document (PXD) is a specification artifact for agentic products, proposed by Rags Vadali (founder, Floto) as a replacement for the traditional PRD. It rests on a reframing: when the product you're building is an agent, the actual product to define is the experience layer built on top of the agent, not the UI.
Why → Success Criteria (quantitative + qualitative) → Experience Principles → Critical Moments → Conversation Closing → Success Metrics.
Unlike a PRD, a PXD is written after a working prototype already exists, not before: engineers build directly from a problem statement, and only once the PM has played with what got built does the PXD get authored. The 'Experience Principles' section is fed into Claude to generate the prompts engineers use to build and tune the agent — in practice the PXD ends up written for a coding agent as much as for a person.
Because the underlying system is a non-deterministic model rather than a person, the PXD specifies ranges of good/bad/explicitly-unwanted answers instead of a single fixed requirement, including real good/bad/ugly example transcripts pulled from usage. See Critical Moments & Breakpoints (Agent Conversation Design Pattern) for the runtime mechanism this enables.
Vadali is explicit that this only fits agentic products; for UI/interface-heavy products he still prefers a traditional designer+engineer close design process that produces a Figma reference first.
Reported firsthand by a single founder at a ~3–6 person team (Floto) as of 2026; not externally validated at time of filing.