PRD Writer: Email Guide
The 'PRD Writer: Email Guide' prompt generates a comprehensive Product Requirements Document for new email-based features or optimizations, covering technical architecture, user experience, and success metrics, designed for Senior Product Managers and Technical Writers.
What is the PRD Writer: Email Guide prompt?
Copy the prompt below into ChatGPT, Gemini, Claude or any capable LLM, replace the bracketed variables with your own values, and run it.
ROLE: You are an expert Senior Product Manager and Technical Writer specializing in the development of communication infrastructure and email systems. Your expertise lies in translating complex business requirements into clear, actionable Product Requirements Documents (PRDs) that bridge the gap between stakeholders and engineering teams. GOAL: Your objective is to generate a comprehensive Product Requirements Document for a new email-based feature or optimization. The documentation must cover the technical architecture, user experience, and success metrics required to implement the initiative described in the provided context. CONTEXT: Use the following details to structure the PRD: - FEATURE NAME: [FEATURE NAME] - TARGET AUDIENCE: [TARGET AUDIENCE] - CORE PROBLEM STATEMENT: [PROBLEM STATEMENT] - KEY CONSTRAINTS (Technical/Legal): [CONSTRAINTS] - SUCCESS METRICS (KPIs): [SUCCESS METRICS] INSTRUCTIONS: 1. EXECUTIVE SUMMARY: Briefly describe what we are building and why it matters to the [TARGET AUDIENCE]. 2. USER STORIES: Draft 3-5 user stories in the "As a [User], I want to [Action], so that [Value]" format. 3. FUNCTIONAL REQUIREMENTS: List specific features including template management, trigger logic, personalization tokens, and delivery scheduling. 4. NON-FUNCTIONAL REQUIREMENTS: Detail requirements for scalability, deliverability (SPF/DKIM/DMARC), latency, and security as per [CONSTRAINTS]. 5. USER FLOW: Describe the customer journey from the trigger event to the email open/click. 6. TECHNICAL SPECIFICATIONS: Outline the data requirements (e.g., UserID, EmailMetadata) and API interactions needed to send the emails. 7. ANALYTICS & TRACKING: Define how we will measure [SUCCESS METRICS], including open rates, CTR, and conversion tracking. OUTPUT FORMAT: The output must be a professional, structured document using the following sections in order: - TITLE & VERSIONING - PROBLEM & OPPORTUNITY - TARGET AUDIENCE & USER STORIES - FUNCTIONAL SPECIFICATIONS - TECHNICAL CONSTRAINTS & COMPLIANCE - SUCCESS CRITERIA - APPENDIX: OPEN QUESTIONS / FUTURE PHASES QUALITY BAR: The PRD must be devoid of fluff. It must be specific enough for an engineer to understand the logic and a designer to understand the flow. Ensure that [CONSTRAINTS] are addressed directly in the technical section and that [SUCCESS METRICS] are quantifiable. Avoid generic descriptions; focus on the specific nuances of [FEATURE NAME].
What variables does the PRD Writer: Email Guide prompt use?
| Variable | What to put | Example |
|---|---|---|
| [FEATURE NAME] | The specific name of the email-based feature or optimization being documented. | Personalized Welcome Email Series |
| [TARGET AUDIENCE] | The primary user group for whom the email feature is intended. | New Users (e.g., of a SaaS platform) |
| [PROBLEM STATEMENT] | A concise description of the core problem this email feature aims to solve. | Low user activation rates due to lack of immediate engagement. |
| [CONSTRAINTS] | Any technical limitations, legal requirements (e.g., GDPR, CAN-SPAM), or policy restrictions affecting the feature. | Must comply with GDPR and CCPA; integration with legacy CRM. |
| [SUCCESS METRICS] | Key Performance Indicators (KPIs) that will be used to measure the success of the feature. | 5% increase in activation rate within 7 days, 25% open rate, 5% CTR. |
How do I use the PRD Writer: Email Guide prompt?
- 1Step 1: Copy the entire prompt body into your AI chatbot.
- 2Step 2: Replace each bracketed placeholder (e.g., [FEATURE NAME], [TARGET AUDIENCE]) with your specific details.
- 3Step 3: Ensure all your details are clear, concise, and specific, especially for constraints and success metrics.
- 4Step 4: Run the prompt and review the generated PRD. Edit or refine as needed.
When should you use the PRD Writer: Email Guide prompt?
Developing new email communication features
Use this prompt when starting a new project involving email features like personalized notifications or automated campaigns. It guides the creation of a detailed PRD.
Optimizing existing email systems
Apply this prompt to document improvements or changes to current email infrastructure, ensuring all technical and user experience aspects are covered.
Aligning cross-functional teams for email projects
Generate a common understanding across product, engineering, design, and marketing teams by using this prompt to produce a single source of truth for email initiatives.
Onboarding new team members to email platform projects
Provide new hires with a clear, structured document outlining the scope, requirements, and goals of email-related projects for quicker ramp-up.
Estimating effort for email system development
The detailed functional and non-functional requirements help engineering teams accurately estimate development time and resources for email features.
What does the PRD Writer: Email Guide prompt output look like?
TITLE & VERSIONING Personalized Welcome Email Series v1.0 PROBLEM & OPPORTUNITY The current user onboarding process lacks personalized engagement, leading to a significant drop-off in user activation within the first week. This feature aims to provide a tailored welcome experience, guiding new users to key product benefits and improving initial engagement, thereby increasing activation rates. TARGET AUDIENCE & USER STORIES Target Audience: New Users of our SaaS platform. User Story 1: As a new user, I want to receive a personalized welcome email, so that I feel acknowledged and understand the next steps. User Story 2: As a new user, I want to get relevant tips based on my initial setup, so that I can quickly realize the product's value. User Story 3: As a new user, I want to easily access support resources if I have questions, so that I don't get stuck early on. FUNCTIONAL SPECIFICATIONS - Automated trigger upon successful account creation. - Template management system for dynamic content insertion. - Personalization tokens for user name, company, and initial product settings. - Conditional logic for email content based on user segment. - Email scheduling for a drip series over 7 days. TECHNICAL CONSTRAINTS & COMPLIANCE - Integration with existing CRM (HubSpot) for user data. - Adherence to GDPR and CCPA for data privacy and consent. - Email sending via SendGrid API, requiring SPF/DKIM/DMARC configuration. - Maximum email size of 2MB. SUCCESS CRITERIA - 7-day user activation rate increases by 5%. - Average open rate for the welcome series is above 25%. - Click-through rate (CTR) to key features reaches 5%. - User churn rate within the first month decreases by 3%. APPENDIX: OPEN QUESTIONS / FUTURE PHASES - Explore A/B testing variations for subject lines and CTA placement. - Consider integrating in-app messaging alongside emails for a holistic onboarding experience. - Evaluate multi-language support for international users.
Which AI model works best with the PRD Writer: Email Guide prompt?
Excellent for generating detailed, structured technical documents, maintaining a professional tone, and understanding complex requirements (like NFRs for email systems).
Strong in handling specific structural instructions and integrating various data points seamlessly into a coherent document, ideal for PRD generation.
Good at producing clear, well-articulated user stories and executive summaries, and maintaining consistency across different sections of a professional document.
What are the pros and cons of the PRD Writer: Email Guide prompt?
Pros
- Generates comprehensive and structured PRDs
- Translates complex requirements into actionable items
- Ensures coverage of technical, UX, and metric aspects
- Facilitates alignment between stakeholders and engineering
- Addresses specific constraints and success metrics
- Output is professional and ready for immediate use
Cons
- Requires detailed context inputs to be most effective
- May require minor human editing for nuanced domain specifics
- Relies on user's ability to define exact KPIs and constraints
- Cannot autonomously identify missing key requirements
How can you get better results from the PRD Writer: Email Guide prompt?
- Be as specific as possible with your [CONSTRAINTS] to ensure they are adequately addressed.
- Clearly define quantifiable [SUCCESS METRICS] for robust tracking sections.
- If possible, provide examples of existing email designs or flows for inspiration on user flows.
- For complex features, break them down into smaller components and generate separate PRDs for each.
- Review the generated PRD for any ambiguities and refine the input context for clarity.
- Use real user feedback or market research to inform your [PROBLEM STATEMENT] and [TARGET AUDIENCE].
Frequently asked questions about the PRD Writer: Email Guide prompt
What is the PRD Writer: Email Guide prompt?
This prompt helps Senior Product Managers and Technical Writers create detailed Product Requirements Documents (PRDs) for new or optimized email features. It covers everything from executive summaries to technical specifications and success metrics.
Who is this prompt best for?
It's ideal for product managers, technical writers, and anyone involved in defining or developing email communication systems. It helps bridge the gap between business goals and technical execution.
What kind of email features can I define with this prompt?
You can define any email-related feature, such as welcome email series, transactional notifications, marketing campaigns, or re-engagement flows. The prompt is flexible enough for various use cases.
How detailed do my inputs need to be?
The more specific and detailed your inputs for brackets like [FEATURE NAME], [CONSTRAINTS], and [SUCCESS METRICS], the more accurate and useful the generated PRD will be. Avoid vague descriptions.
Can I use this prompt for non-email related features?
While specifically tailored for email systems, the core structure of defining a PRD can be adapted. However, some sections like 'deliverability (SPF/DKIM/DMARC)' are very email-specific.
How do I measure the 'Quality Bar' mentioned in the prompt?
The 'Quality Bar' implies the output PRD should be specific, action-oriented, and directly address all inputs without fluff. Engineers should understand logic, and designers should understand flow.
Which AI model works best with this prompt?
GPT-4o, Gemini 2.5 Pro, and Claude Sonnet are recommended for their ability to handle structured outputs, maintain professional tone, and integrate complex technical details effectively.