Exercise 3 · Technology selection: a decision matrix and build versus buy
| Time | 13 minutes, after the Module 3 slides, then a 10-minute break |
|---|---|
| Blueprint sections | 5 Technology stack and build-versus-buy decisions |
| You need | Your Virtual CTO conversation; your five priorities (section 2) and architecture (section 4) |
| You leave with | A weighted decision matrix, a chosen stack, build-versus-buy for each capability, and the lock-in and debt you accept |
| Safety tip | AI knowledge of prices and products can be out of date. Check anything that decides the outcome on the provider's own website |
Where you are
You have an architecture shape. Now you choose what to build it with: framework, database and hosting, and which capabilities to build yourself and which to buy. A CTO decides against criteria, not fashion, and knows the exit cost of everything bought.
What you will make
A decision matrix: three realistic options per choice, scored against weighted criteria that come from your priorities. A build-versus-buy list: for each capability, build, buy or rent, and why. And a short note of the lock-in and technical debt you accept knowingly.
For TutorDesk: Python/Django, PostgreSQL, a managed hosting platform. Buy payments, email/SMS, sign-in with Google and error monitoring. Build the booking rules and tutor dashboard. Accepted lock-in: the payment provider holds card details, so moving would take about a month.
© 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