CAP · Prototype review
Help us define the MVP
Fifteen sections of the prototype. For each one, tell us if it's a Need, a Want, or something we Don't Need for launch. Your answers save automatically.
- —The purpose of this review is to define the MVP and refine the RFP for a web development agency.
- —Go through the prototype page by page. For each section below, mark it Need, Want or Don't Need, then add the classification and any notes.
- —Base your assessment on what is actually shown in the prototype. Do not assume functionality that is not represented.
- —Where something appears necessary but is not shown, log it as a gap, question or assumption rather than an existing requirement.
- —The prototype is a simulation: authentication is permissive, data is seeded, and payments, notifications and moderation are not real. Treat those as open scope questions.