Clay Product Requirements Documents

This repository houses exploratory PRDs and product ideas for Clay features and improvements. These documents help us think through potential backlog items, validate concepts, and align on implementation approaches before committing to development.

Purpose

• Explore ideas - Document and refine product concepts before they enter the roadmap
• Backlog management - Evaluate potential features with detailed technical and user research
• Alignment - Create shared understanding across product, engineering, and design
• Reference - Maintain living documents that evolve as we learn more

PRD Status Levels

PRDs in this repo may be at different stages of maturity:

• 🔵 Draft - Initial exploration, seeking feedback
• 🟡 In Review - Actively being discussed and refined
• 🟢 Approved - Ready for implementation planning
• ⚪ Archived - Deprioritized or superseded by other work

Current PRDs

🔵 Just-In-Time Sequencing

Status: Draft v0.1 Problem: Campaign leads are static snapshots that can't adapt to changing signals or eligibility Proposal: Move from bulk copy-by-value to dynamic references (table or audience segments) Key Use Cases: Intent-based prospecting, job change monitoring, re-engagement campaigns, paced outreach

---

Contributing

PRDs should follow this general structure:

1. Executive Summary - One paragraph capturing the core idea
2. Current State - How things work today (with code references if applicable)
3. Problem Statement - User pain points and business impact
4. Proposed Solution - Design options with pros/cons
5. Customer Use Cases - Concrete scenarios showing value
6. Technical Considerations - Implementation complexity, risks, dependencies
7. Success Metrics - How we'll measure impact
8. Next Steps - Phased rollout plan

Naming Convention

PRD-kebab-case-feature-name.md

Examples:

• PRD-just-in-time-sequencing.md
• PRD-workflow-versioning.md
• PRD-bulk-credit-estimation.md

---

Questions or Feedback?

These are living documents meant to spark discussion. Feel free to:

• Open issues for questions or alternative approaches
• Comment directly on PRDs via GitHub line comments
• Suggest edits via pull requests

Note: Not all PRDs will be implemented. The goal is thoughtful exploration, not commitment to build everything documented here.