Guide AI assistants in creating professional Business Requirement Documents for Web, Mobile, ERP, CRM, CDP, and E-commerce projects
This skill enables AI assistants to create comprehensive, professional Business Requirement Documents (BRDs) that clearly communicate business needs, objectives, and high-level requirements to stakeholders and development teams.
A Business Requirement Document (BRD) is a formal document that:
BRD vs. FRS:
Purpose: Provide a concise overview for busy executives
Contents:
Length: 1 page maximum
Writing Tips:
Example:
Project: Mobile App Development for Customer Self-Service
Business Problem: Customers currently must call our support center for account inquiries, order tracking, and returns, resulting in 15,000+ monthly support calls and $450K annual support costs. Customer satisfaction scores for support are 3.2/5.
Proposed Solution: Develop a mobile application (iOS and Android) enabling customers to self-serve for common inquiries, track orders in real-time, and initiate returns without agent assistance.
Expected Benefits: Reduce support call volume by 60% (9,000 calls/month), save $270K annually in support costs, improve customer satisfaction to 4.5/5, and increase customer retention by 15%.
Investment: $180K development cost, 4-month timeline
ROI: Payback in 8 months, $540K savings over 2 years
Purpose: Define what the business wants to achieve
Contents:
Format: Use SMART criteria (Specific, Measurable, Achievable, Relevant, Time-bound)
Example:
Primary Objective: Reduce customer support costs by 60% within 6 months of mobile app launch
Secondary Objectives:
- Improve customer satisfaction score from 3.2 to 4.5 within 3 months of launch
- Increase customer retention rate by 15% within 12 months
- Enable 24/7 customer self-service capabilities
Strategic Alignment: Supports company's digital transformation initiative and customer-first strategy
Success Criteria:
- 70% of customers download and activate the app within 6 months
- 60% reduction in support call volume
- 4.5+ app store rating
- 80% of users complete tasks without contacting support
Purpose: Provide context for why this project is needed
Contents:
Example:
Our customer support center currently handles 15,000 calls per month, with 70% being routine inquiries (order status, account balance, return requests) that don't require human expertise. Industry benchmarks show that companies with self-service mobile apps reduce support costs by 50-70% while improving customer satisfaction.
Our main competitors (CompanyX and CompanyY) launched mobile apps in 2024 and have seen significant improvements in customer satisfaction and retention. Customer surveys indicate that 65% of our customers prefer mobile self-service over calling support.
Previous attempts to address this through a web portal in 2023 achieved only 15% adoption due to poor mobile experience and lack of push notifications for order updates.
Purpose: Identify who is impacted and their needs
Format: Table with stakeholder roles, interests, and requirements
| Stakeholder Group | Key Representatives | Interest/Concern | Key Requirements |
|---|---|---|---|
| Customers | End users | Easy access to account info, order tracking | Intuitive UI, fast performance, offline access |
| Customer Support | Support Manager | Reduced call volume, better tools | Integration with support system, escalation path |
| IT Operations | IT Director | System stability, security | Secure authentication, API performance, monitoring |
| Marketing | Marketing VP | Customer engagement, retention | Push notifications, personalization, analytics |
| Executive Team | CEO, CFO | ROI, strategic alignment | Cost savings, customer satisfaction improvement |
Purpose: Clearly define what WILL be included
Format: Categorized list of features/capabilities
Example for E-commerce Mobile App:
Account Management:
Order Management:
Product Browsing:
Customer Support:
Notifications:
Purpose: Explicitly state what will NOT be included (manage expectations)
Example:
Format: Organized by category with clear, business-focused language
BR-001: User Authentication
BR-002: Order Tracking
BR-003: Push Notifications
BR-NFR-001: Performance
BR-NFR-002: Availability
BR-NFR-003: Security
BR-NFR-004: Usability
BR-NFR-005: Compliance
Purpose: Document what we're assuming to be true
Example:
Purpose: Document limitations and restrictions
Categories:
Purpose: Identify what this project depends on
Example:
| Dependency | Description | Owner | Status | Risk |
|---|---|---|---|---|
| Backend API Enhancement | Order tracking API needs real-time updates | IT Team | In Progress | Medium |
| Push Notification Service | Need to procure service (OneSignal or Firebase) | IT Team | Not Started | Low |
| App Store Accounts | Apple Developer and Google Play accounts | Marketing | Pending | Low |
| Customer Data Migration | Clean customer data for app migration | Data Team | Planned | Medium |
| Support System Integration | Integrate with Zendesk for ticket creation | IT Team | Not Started | High |
| Risk | Impact | Probability | Mitigation Strategy |
|---|---|---|---|
| Low app adoption rate | High | Medium | Comprehensive marketing campaign, in-app incentives, email promotion |
| Backend API performance issues | High | Medium | Load testing, performance optimization, caching strategy |
| App store rejection | Medium | Low | Early review of guidelines, compliance checklist, beta testing |
| Integration delays with legacy systems | High | High | Early technical spike, parallel development, fallback plan |
| Security vulnerabilities | Critical | Low | Security audit, penetration testing, code review |
Adoption Metrics:
Business Impact Metrics:
Technical Metrics:
Engagement Metrics:
| Phase | Milestone | Duration | Target Date |
|---|---|---|---|
| Planning | BRD Approval | 2 weeks | Feb 1, 2026 |
| Design | UX/UI Design Complete | 3 weeks | Feb 22, 2026 |
| Development | iOS App Development | 8 weeks | Apr 19, 2026 |
| Development | Android App Development | 8 weeks | Apr 19, 2026 |
| Testing | QA and UAT | 3 weeks | May 10, 2026 |
| Deployment | App Store Submission | 1 week | May 17, 2026 |
| Launch | Public Launch | - | May 24, 2026 |
| Category | Cost | Notes |
|---|---|---|
| Development (iOS & Android) | $120,000 | 2 developers x 3 months |
| UX/UI Design | $25,000 | Design agency |
| QA & Testing | $15,000 | QA engineer + device testing |
| Project Management | $10,000 | BA + PM time |
| Third-party Services (Year 1) | $5,000 | Push notifications, analytics |
| App Store Fees | $200 | Apple ($99) + Google ($25) + buffer |
| Contingency (10%) | $17,520 | Risk buffer |
| Total | $192,720 |
| Role | Name | Signature | Date |
|---|---|---|---|
| Business Sponsor | |||
| Product Owner | |||
| IT Director | |||
| Finance | |||
| Business Analyst |
Focus Areas:
Key Metrics: Conversion rate, cart abandonment, average order value, customer lifetime value
Focus Areas:
Key Metrics: Process efficiency, cost reduction, data accuracy, user adoption
Focus Areas:
Key Metrics: Lead conversion rate, sales cycle time, customer satisfaction, pipeline value
Focus Areas:
Key Metrics: Data completeness, segment accuracy, campaign performance, ROI
Focus Areas:
Key Metrics: User engagement, session duration, retention rate, app store rating
✅ Do:
❌ Don't:
frs-creation skilluse-case-documentation skilluser-story-writing skillprocess-mapping skilluat-planning skill