Skip to content

Creating a Website PRD

Why PRDs Matter: Transform vague project ideas into actionable development guidance for AI assistants

A great PRD serves three audiences:

  1. You - Clarifies vision and requirements
  2. Your Team - Aligns everyone on goals and scope
  3. AI Assistants - Provides context for intelligent recommendations
  • Specific: “Generate 50 qualified B2B leads monthly” vs “get more customers”
  • Outcome-Focused: What success looks like, not just features to build
  • Constraint-Aware: Budget, timeline, and technical limitations
  • Audience-Centered: Based on real user needs, not assumptions
  • What is the single most important outcome this website must achieve?
  • Who specifically are you trying to reach? (Be narrow, not broad)
  • How will you measure success? (Specific numbers)
  • What are 3 competitor websites you respect/fear?
  • What do they do well that you want to match/beat?
  • What gaps can you capitalize on?
  • Realistic timeline and budget range
  • Who provides content/assets?
  • What existing materials do you have?
  • List must-have pages (usually 4-7 for most sites)
  • Define primary call-to-action journey
  • Map secondary actions users might take
  • What content exists vs. needs creation?
  • Who creates it and approval process?
  • Content creation timeline

Phase 3: Technical Requirements (20 minutes)

Section titled “Phase 3: Technical Requirements (20 minutes)”
  • Forms and lead capture requirements
  • Third-party integrations (CRM, email, analytics)
  • Performance or security needs

Implementation Track Selection (10 minutes)

Section titled “Implementation Track Selection (10 minutes)”
  • MVP Track: Launch quickly with basics (2-3 weeks)
  • Showcase Track: Full features and polish (4-6 weeks)
  1. Download the Website PRD Template
  2. Save As PRD-[project-name].md in your project’s docs/ folder
  3. Block 90 minutes for initial completion
  • Project Overview: Vision statement guides everything else
  • Target Audience: Be specific, base on research not assumptions
  • Site Architecture: Limit core pages to essentials
  • Content Strategy: Key messages should differentiate clearly
  • Technical Requirements: Stick to starter defaults unless specific needs

For Windsurf/Cursor:

Terminal window
# Add to .windsurfrules or .cursorrules
contextFiles: [
"docs/PRD-*.md",
"docs/ai-context/INDEX.md"
]

For VS Code + Copilot:

.vscode/settings.json
{
"github.copilot.advanced": {
"contextFiles": ["docs/PRD-*.md"]
}
}

Instead of: “Create a homepage for my business”

Try: “Based on the PRD, create a homepage targeting [specific audience] with our primary value prop of [specific benefit]. Focus on [primary CTA] conversion.”

  • “Increase engagement” → ✅ “Increase newsletter signups by 25%”
  • “Modern design” → ✅ “Clean, minimal design like Stripe’s homepage”
  • “Better UX” → ✅ “Reduce form abandonment to under 15%”
  • “We need a blog” → ✅ “Establish thought leadership to increase leads”
  • “Add testimonials” → ✅ “Convert visitors with credibility indicators”
  • “Users want detailed specs” → ✅ “Customer interviews show they need ROI calculators”
  • “Everyone uses desktop” → ✅ “Analytics show 78% mobile traffic”
  • Weekly: During active development
  • Monthly: During maintenance phases
  • Quarterly: Strategic reviews and updates
  • Success metrics based on performance
  • Content priorities from analytics
  • Technical requirements as you scale
  • Audience insights from feedback
  • Keep PRD in version control with code
  • Tag major revisions
  • Link updates to feature releases

Focus: Trial conversion, enterprise trust signals, technical credibility

Focus: Expertise demonstration, case studies, consultation booking

Focus: Product discovery, conversion optimization, retention

Focus: Work showcase, style demonstration, client acquisition

Focus: Content engagement, subscriber growth, monetization

  1. Create Your PRD: Use template, spend 90 minutes on first draft
  2. Configure AI Context: Set up IDE to reference PRD
  3. Test with AI: Try development prompts referencing your PRD
  4. Iterate: Refine based on results
  5. Share: Get team feedback and alignment

Remember: Start with 80% complete and refine as you learn more about your users and market.


See AI Context Index and Website PRD Template for implementation guidance.