← Part 05: Plan the architecture
PART 05 · PLAN · 25 MINUTES
Plan the architecture
Present slides ▶
Full screen, one slide at a time · 4 slides
What is behind the screen?
- FRONTENDWhat people see and tap. TutorDesk: the booking page on a parent’s phone
- BACKENDThe rules and the work. TutorDesk: checks a slot is free, moves the lesson
- DATABASEWhat must be remembered. TutorDesk: tutors, students, lessons, availability
- EXTERNAL SERVICESWhat you borrow. TutorDesk: calendar sync, email reminders, payments
Around all four sit security, hosting and monitoring: locks, a home and a smoke alarm.
Ten capabilities to consider
- AUTHENTICATIONProving who someone is: sign-up, log-in, password reset
- PERMISSIONSWhat each person may see and do: a parent sees only their own child’s lessons
- DATA MANAGEMENTStoring, editing and deleting records safely
- WORKFLOWSThe steps and rules: request, check, confirm
- NOTIFICATIONSEmails or messages: “Your lesson has moved to Thursday”
- PAYMENTSTaking money, refunds and invoices
- INTEGRATIONSTalking to other tools, such as calendars
- ANALYTICSMeasuring what people actually do
- SECURITYProtecting data, accounts and the system
- DEPLOYMENTPutting it online and updating it safely
Most products need most of these eventually. Your MVP needs only the few that test your riskiest assumption.
No-code, AI-generated or custom?
For a prototype (today)
- AI-generated screens in Claude Artifacts, ChatGPT Canvas or Gemini Canvas
- No-code tools: forms, spreadsheets, website builders
- Fake data, simulated steps, no real users’ details
For production (later)
- No-code platforms, if they cover your capabilities and can grow with you
- AI-assisted custom code in a coding environment, reviewed by someone who understands it
- Real logins, real data, security, backups and monitoring
Choose the cheapest approach that answers today’s question. You can change approach later.
Exercise 4: sketch your architecture
Draw the boxes behind your product and tick the capabilities your MVP really needs.
- Sketch four boxes: frontend, backend, database, external services; write what each does for your idea
- Ask your assistant: “What would a real version of this need that I have missed?” and add anything sensible
- Tick the ten capabilities: needed for the MVP, needed later, or not needed
- Turn to your neighbour: explain your diagram in 60 seconds
Deliverable
Architecture Diagram v1 and Capabilities Checklist in Blueprint section 9
© 2026 MVP Studios Ltd. MVPAI™ and the MVP Studios Academy course materials, including the MVP Founders Programme and MVPAI in a Week, are original works of MVP Studios Ltd. All rights reserved. No copying, redistribution or commercial use without written permission. Course terms