Project Requirements Extractor

Category: General Content Difficulty: Intermediate Estimated Tokens: 600-900 Version: 1.0.0

Description

Transform rambling client conversations into organized project specifications. This prompt helps freelancers convert unstructured client discussions into professional project briefs with clear requirements, timelines, and deliverables.

The Prompt

Please analyze this client call transcript and extract the project requirements in a professional, organized format.

TRANSCRIPT: [Paste your client call transcript here]

Please organize the requirements into these sections:

## PROJECT OVERVIEW
- Brief project summary in 1-2 sentences
- Primary business objective or goal

## FUNCTIONAL REQUIREMENTS
- Core features and capabilities needed
- Technical specifications mentioned
- Integration requirements with existing systems

## DESIGN REQUIREMENTS
- Visual style preferences or brand guidelines
- User experience expectations
- Reference examples or inspirations mentioned

## TIMELINE AND MILESTONES
- Project deadline or launch date
- Key milestones or review points
- Dependencies or blocking factors mentioned

## BUDGET AND RESOURCES
- Budget range or constraints discussed
- Resource requirements (content, images, access)
- Third-party tools or services needed

## ASSUMPTIONS AND CLARIFICATIONS NEEDED
- Items that need follow-up or confirmation
- Assumptions made during the conversation
- Questions for next discussion

Format this as a professional project brief that both client and freelancer can reference throughout the project. Use clear, specific language and note any ambiguous requirements that need clarification.

---
Prompt by BrassTranscripts (brasstranscripts.com) – Professional AI transcription with high-quality results.
---

Best Practices

Documentation clarity: Extract exact quotes for critical requirements to avoid miscommunication.

Timeline tracking: Note any dependencies or external factors that could impact the project schedule.

Scope definition: Clearly separate what’s included versus what might be additional work.

Follow-up management: Always include a section for items that need clarification.

Use Cases

• Discovery call documentation - Convert initial client discussions into structured briefs
• Scope clarification - Organize scattered requirements into clear project definitions
• Project onboarding - Create comprehensive briefs for team members or contractors
• Client approval - Generate documentation that clients can review and approve
• Change management - Track how requirements evolve from initial conversations
• Proposal preparation - Use extracted requirements as foundation for project proposals

Example Output

Project Requirements: E-commerce Website Redesign

PROJECT OVERVIEW

• Redesign existing Shopify store to improve conversion rates and mobile experience
• Primary objective: Increase online sales by improving user experience and checkout flow

FUNCTIONAL REQUIREMENTS

• Mobile-responsive design optimized for tablets and smartphones
• Streamlined checkout process with guest purchase option
• Product filtering by category, price range, and customer ratings
• Integration with existing inventory management system
• Email capture for abandoned cart recovery

TIMELINE AND MILESTONES

• Project launch: 8 weeks from project start
• Design mockups: Week 2
• Development completion: Week 6
• Testing and launch: Week 8
• Dependency: Product photos from client by Week 3

ASSUMPTIONS AND CLARIFICATIONS NEEDED

• Confirm if current hosting plan supports new design requirements
• Verify which payment gateways client wants to maintain
• Clarify if blog integration is included in scope
• Determine if customer account system needs enhancement

Advanced Techniques

Priority ranking: Add priority levels to requirements:

Additionally, rank each requirement as:
- Must-have (project fails without this)
- Should-have (important but not critical)
- Could-have (nice to have if time/budget allows)

Risk identification: Include risk assessment:

Also identify potential project risks based on the conversation:
- Technical risks or challenges mentioned
- Timeline concerns or tight deadlines
- Budget constraints that might impact scope
- External dependencies that could cause delays

Integration Tips

CRM integration: Copy the output directly into your project management system or CRM for tracking and reference.

Client approval process: Send the extracted requirements to clients for confirmation before beginning work.

Team communication: Share requirements briefs with subcontractors or team members to ensure alignment.

Resources

• 📖 Detailed Guide: Freelancer Productivity Hack: Transcribing Client Calls for Better Project Management
• 🎯 All Prompts: BrassTranscripts AI Prompt Guide
• 🎤 Get Transcripts: Upload Your Audio

---

Created by BrassTranscripts - Professional AI transcription with high-quality results