← Blog

How to Write a One-Page PRD and MVP Scope for Your First Student Project (2027)

By Build Theory team · November 4, 2026 · 10 min read

A PRD (product requirements document) is a short document that says who your product is for, what problem it solves, what version one will do and what it will not do. For a first student project, one page is enough, and it is the best thing to write before you open an AI tool.

This guide gives you a one-page template, an example and a way to decide what goes into version one.

What is a PRD, and why do students need one?

Product teams use a PRD to turn an idea into scope that can be built and tested. For a student project it does the same job in miniature: it makes you decide before you build.

That matters even more when you build with AI, because AI builds what you describe. A vague description gives you a vague product. Cohort 01 fellow Ch Sreemayee described what she learned like this: “I learned how to start with the problem, understand what’s needed, create the PRD and MVP, and then actually build it using AI.”

What goes in a one-page PRD?

  1. Header. Your name, the date and the status (draft, building, launched).

  2. Problem. One sentence on the problem, who has it and the evidence it is real, such as five conversations.

  3. Goal. What changes if this works, and how you will know.

  4. Users and user stories. Who uses it, and short lines such as “As a student I can rate today’s lunch in 10 seconds.”

  5. MVP scope. The few things version one must do.

  6. Out of scope. What version one will not do, so you do not drift.

  7. Risks and open questions. What could go wrong and what you still need to find out.

What does a good one-page PRD look like?

Example for illustration only. It is not a Build Theory product.

  • Title: Hostel mess feedback tracker

  • Problem: Students complain about mess food in chat groups, and the warden has no clear summary. Evidence: five students and the warden confirmed it.

  • Goal: The warden can see, every week, which meals get the lowest ratings.

  • User stories: As a student, I can rate today’s lunch in 10 seconds. As the warden, I can see this week’s lowest-rated dishes.

  • MVP scope: A rating form and a weekly summary page.

  • Out of scope: College ID login, push notifications, charts over time.

  • Risks: Students may not rate daily. Open question: how will the warden receive the summary?

How do you find the problem first?

Talk to five people who have the problem. Ask what takes their time, what goes wrong and what they do today. Listen more than you talk.

Cohort 01 fellow Ch Sreemayee, who built Tuition OS, said: “I, even growing up, did not really see this many problems in my own parents’ tuition institute until I started to see them as clients and did customer interviews.”

How do you decide what goes into the MVP?

MVP means minimum viable product: the smallest version that solves the problem for a real user. Product guides agree that the most important part of a PRD is the scope, and that version one should hold only the must-have items, often labelled P0. Everything else waits.

Ask three questions about every feature:

  • Can a user solve the main problem without it? If yes, it is not in version one.

  • Can you finish it in the time you have? If not, shrink it.

  • Is it written down in a “Later” list? Cut ideas are not lost. They just wait.

How do you use the PRD with an AI tool?

  1. Paste your PRD and ask the AI to propose small build steps.

  2. Build one step at a time.

  3. After each step, test it against your user stories.

  4. Update the PRD when users teach you something new.

  5. Keep the PRD in your project repository so anyone can read it.

For the full process, read our guide to vibe coding vs vibe developing.

What mistakes should you avoid?

  • Writing a ten-page document nobody reads.

  • Putting every feature into version one.

  • Describing a solution but no user.

  • Never updating the PRD after you talk to users.

Template you can copy

  • Title: …

  • Owner and date: …

  • Problem (one sentence, who has it, evidence): …

  • Goal and how I will know: …

  • Users: …

  • User stories (3 to 5): …

  • MVP scope (must-haves only): …

  • Out of scope (Later list): …

  • Risks and open questions: …

Next steps

Take the free readiness score to see which areas recruiters would flag first. To turn your PRD into a finished project, follow the 30-day plan in Build a Portfolio Project in 30 Days from our partner site Poditivity, or read about the Build Theory Fellowship, where each student works one-to-one with a mentor. It costs nothing to apply, and Build Theory does not guarantee placements.

Sources

  • #prd for students
  • #mvp scope
  • #one page prd template
  • #student project plan
  • #build with ai
  • #product requirements document
  • #build theory fellowship
  • #2027 batch