Hammer
d390720986
- README.md: Project overview - requirements.md: Full feature specification - competitors.md: Market research (Wealthbox, Affinity, Clay, etc.) - feasibility.md: Technical assessment with Swift/Firebase/Claude architecture - blueprint.md: Architecture diagrams, screens, data models, API endpoints, dev phases Client: David DePoyster / NWM Tech: Swift/SwiftUI, Firebase, Claude AI
178 lines
4.5 KiB
Markdown
178 lines
4.5 KiB
Markdown
# The Network App - Requirements Specification
|
|
|
|
**Version:** 1.0
|
|
**Date:** 2025-06-26
|
|
**Client:** David DePoyster / NWM
|
|
|
|
---
|
|
|
|
## 1. Product Vision
|
|
|
|
An iPhone app for NWM wealth management firm that serves as an AI-powered CRM for managing relationships with high-net-worth clients. The app prioritizes relationship intelligence over traditional transaction tracking.
|
|
|
|
---
|
|
|
|
## 2. Core Features
|
|
|
|
### 2.1 Client Profiles
|
|
|
|
**Purpose:** Store comprehensive information about each client beyond basic contact details.
|
|
|
|
**Required Fields:**
|
|
- Basic contact information (name, phone, email, address)
|
|
- Professional information (company, role, industry)
|
|
- Personal interests and hobbies
|
|
- Family details (spouse name, children, pets)
|
|
- Important dates (birthday, anniversary, client since)
|
|
- Communication preferences
|
|
- Relationship notes and history
|
|
- Custom tags/categories
|
|
|
|
**Nice-to-Have:**
|
|
- Photo/avatar
|
|
- Social media links
|
|
- Net worth tier (for service level segmentation)
|
|
- Referral source tracking
|
|
|
|
### 2.2 Personalized Communications
|
|
|
|
**Purpose:** AI-generated emails and newsletters that feel authentic and personal.
|
|
|
|
**Functionality:**
|
|
- Generate personalized email drafts based on client profile
|
|
- Create customized newsletter content segments
|
|
- Suggest talking points before meetings
|
|
- Draft birthday/anniversary messages
|
|
- Write introduction emails when connecting clients
|
|
|
|
**AI Requirements:**
|
|
- Must feel human-written, not templated
|
|
- Incorporate specific details from client profile
|
|
- Match advisor's communication style/tone
|
|
- Support review/edit before sending
|
|
|
|
### 2.3 Network Matching
|
|
|
|
**Purpose:** Identify clients who would benefit from knowing each other.
|
|
|
|
**Matching Criteria:**
|
|
- Shared professional interests
|
|
- Complementary business needs (e.g., investor + entrepreneur)
|
|
- Common hobbies or passions
|
|
- Geographic proximity
|
|
- Similar life stages or family situations
|
|
|
|
**Functionality:**
|
|
- AI-suggested matches with explanation
|
|
- Advisor approval workflow before any introduction
|
|
- Track successful introductions and outcomes
|
|
- "Do not match" preferences
|
|
|
|
### 2.4 Event Tracking & Automation
|
|
|
|
**Purpose:** Never miss important dates or opportunities for meaningful touches.
|
|
|
|
**Tracked Events:**
|
|
- Birthdays
|
|
- Anniversaries (wedding, client relationship)
|
|
- Major life events (children graduating, retirement, etc.)
|
|
- Follow-up reminders from meetings
|
|
|
|
**Automation:**
|
|
- Push notification reminders
|
|
- Pre-drafted messages for events
|
|
- Calendar integration (optional)
|
|
- Bulk actions for seasonal greetings
|
|
|
|
### 2.5 Security & Compliance
|
|
|
|
**Purpose:** Meet regulatory requirements for financial services.
|
|
|
|
**Requirements:**
|
|
- GDPR compliance (data portability, right to deletion)
|
|
- HIPAA compliance (for any health-related notes)
|
|
- End-to-end encryption for sensitive data
|
|
- Secure authentication (biometric + PIN)
|
|
- Audit logging for compliance reviews
|
|
- Data residency options (US/EU)
|
|
- Role-based access (if multi-user)
|
|
|
|
---
|
|
|
|
## 3. User Roles
|
|
|
|
### 3.1 Primary User: Wealth Advisor
|
|
- Full access to all client data
|
|
- Can create, edit, delete clients
|
|
- Approves AI suggestions
|
|
- Sends communications
|
|
|
|
### 3.2 Future Consideration: Admin/Team Lead
|
|
- Manage multiple advisors
|
|
- View aggregate analytics
|
|
- Configure compliance settings
|
|
|
|
---
|
|
|
|
## 4. Non-Functional Requirements
|
|
|
|
### 4.1 Performance
|
|
- App launch: < 2 seconds
|
|
- Search results: < 500ms
|
|
- AI generation: < 5 seconds
|
|
|
|
### 4.2 Reliability
|
|
- 99.9% uptime for core features
|
|
- Offline access to client profiles
|
|
- Data sync on reconnection
|
|
|
|
### 4.3 Scalability
|
|
- Initial: 100+ clients per advisor
|
|
- Target: 500+ clients per advisor
|
|
- Future: Multi-advisor organizations
|
|
|
|
### 4.4 Platform
|
|
- iOS 16+ (iPhone)
|
|
- iPad support: Nice-to-have
|
|
- Android: Future consideration
|
|
|
|
---
|
|
|
|
## 5. Technical Constraints
|
|
|
|
- **Backend:** Firebase preferred (existing familiarity)
|
|
- **AI Provider:** Claude API (Anthropic)
|
|
- **Frontend:** Swift/SwiftUI (native iOS)
|
|
- **Budget:** TBD (affects feature prioritization)
|
|
|
|
---
|
|
|
|
## 6. Success Metrics
|
|
|
|
- Time saved per client interaction
|
|
- Quality of AI-generated content (approval rate)
|
|
- Successful client introductions made
|
|
- User engagement (daily active usage)
|
|
- Client satisfaction improvements
|
|
|
|
---
|
|
|
|
## 7. Out of Scope (v1)
|
|
|
|
- Portfolio management integration
|
|
- Financial data/account information
|
|
- Document storage
|
|
- Video calling
|
|
- Web application
|
|
- Android application
|
|
|
|
---
|
|
|
|
## 8. Open Questions
|
|
|
|
1. Budget range for development?
|
|
2. Timeline expectations?
|
|
3. Existing client data to import? Format?
|
|
4. Specific compliance certifications needed?
|
|
5. Multi-user from day one or single advisor MVP?
|