Exercise 1 · CTO priorities: from product vision to five technical priorities
| Time | 7 minutes, after the Module 1 slides |
|---|---|
| Blueprint sections | 1 Product context and business objectives, 2 Functional and non-functional requirements |
| You need | Your AI assistant (ChatGPT, Claude or Gemini); the Architecture Blueprint open in another tab |
| You leave with | Your product context, business objectives and five ranked technical priorities |
| Safety tip | Describe your product and customers in general terms. Never paste customer data, passwords, keys or confidential contracts |
Where you are
You have seen what a CTO balances: business objectives, engineering quality, speed, cost, technical risk and future growth. Now you set up your Virtual CTO, the AI adviser you'll use all afternoon, and turn your product's business goals into the technical priorities that will drive every later decision.
What you will make
Technical priorities are quality requirements in business language: how secure, how reliable, how fast, how cheap to run and how ready for growth your product must be. Five is enough. The order matters more than the list, because every later trade-off asks "which priority wins?"
For TutorDesk, the booking tool for independent tutors: 1 protect children's lesson data; 2 never lose a booking or payment; 3 calendar sync within a minute; 4 available 99.5% of the time in UK evenings; 5 running costs under £1 per tutor per month. Deliberately not optimised yet: a mobile app, because the phone browser works for parents.
© 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