Product Summary
The MVP is a guided interview and profile generation product that produces a Career Profile Pack for students and recent graduates. The MVP should validate willingness to pay and profile usefulness before investment in a full platform.
MVP Scope
| Feature | MVP Requirement |
|---|
| Landing Page | Explains product, shows sample output, captures purchase. |
| Payment Flow | Supports one-time payment for Career Profile Pack. |
| Intake Form | Collects student background and goals. |
| Guided Interview | Collects qualitative answers across required domains. |
| Profile Generator | Produces structured profile sections using evidence-based schema. |
| Manual QA Interface | Allows review before delivery. |
| Export | HTML, PDF-ready page, Markdown/aboutme.md. |
| Feedback Survey | Captures recognition, usefulness, and referral scores. |
Non-Goals
- No full university admin portal in MVP.
- No social network.
- No automated employer matching.
- No diagnosis or psychological testing.
- No subscription-first architecture.
- No public profile sharing by default.
User Stories
- As a student, I want to answer guided questions so I do not have to know how to describe myself upfront.
- As a student, I want a profile that sounds specific to me.
- As a student, I want language I can use in interviews and LinkedIn.
- As a parent, I want to buy a useful transition tool for my student.
- As an operator, I want to review outputs before delivery during the pilot.
Functional Requirements
| Requirement | Priority |
|---|
| User can purchase product. | P0 |
| User can complete intake. | P0 |
| User can complete interview. | P0 |
| System generates all required profile sections. | P0 |
| Profile includes evidence map. | P0 |
| User can receive HTML/PDF-ready output. | P0 |
| User can request deletion. | P0 |
| Operator can view completion and feedback metrics. | P1 |
| User can edit profile sections. | P1 |
| Automated profile revision workflow. | P2 |
Quality Requirements
- No condensation of user-provided material without explicit instruction.
- Profile claims must be evidence-supported or labeled as inference.
- Output must include risks and unknowns.
- Final profile must be professional enough to share with a coach, parent, or advisor.
- HTML output must be print-friendly and mobile-readable.
Technical Notes
- Use a structured profile schema rather than freeform generation only.
- Store generated profile versions with timestamps.
- Separate raw intake data from final profile outputs.
- Implement deletion logic before institutional pilots.
- Maintain prompt versioning for reproducibility.