← Part 05: Plan the architecture PART 05 · PLAN · 25 MINUTES

Plan the architecture

Present slides Full screen, one slide at a time · 4 slides
MASTERCLASS · PART 05 · PLAN 01

What is behind the screen?

  1. FRONTENDWhat people see and tap. TutorDesk: the booking page on a parent’s phone
  2. BACKENDThe rules and the work. TutorDesk: checks a slot is free, moves the lesson
  3. DATABASEWhat must be remembered. TutorDesk: tutors, students, lessons, availability
  4. 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.

MASTERCLASS · PART 05 · PLAN 02

Ten capabilities to consider

  1. AUTHENTICATIONProving who someone is: sign-up, log-in, password reset
  2. PERMISSIONSWhat each person may see and do: a parent sees only their own child’s lessons
  3. DATA MANAGEMENTStoring, editing and deleting records safely
  4. WORKFLOWSThe steps and rules: request, check, confirm
  5. NOTIFICATIONSEmails or messages: “Your lesson has moved to Thursday”
  6. PAYMENTSTaking money, refunds and invoices
  7. INTEGRATIONSTalking to other tools, such as calendars
  8. ANALYTICSMeasuring what people actually do
  9. SECURITYProtecting data, accounts and the system
  10. 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.

MASTERCLASS · PART 05 · PLAN 03

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.

MASTERCLASS · PART 05 · EXERCISE 4 04

Exercise 4: sketch your architecture

Draw the boxes behind your product and tick the capabilities your MVP really needs.

  1. Sketch four boxes: frontend, backend, database, external services; write what each does for your idea
  2. Ask your assistant: “What would a real version of this need that I have missed?” and add anything sensible
  3. Tick the ten capabilities: needed for the MVP, needed later, or not needed
  4. Turn to your neighbour: explain your diagram in 60 seconds
Deliverable

Architecture Diagram v1 and Capabilities Checklist in Blueprint section 9