← From Idea to Product: the MVPAI Masterclass The workbook · My First Product Blueprint

One plan for your idea, built as you go.

Twelve sections, each with a short explanation, a worked TutorDesk example and space for your own idea. Your answers are saved in this browser as you type: nothing is sent to us. Export it as a PDF whenever you like.

0 of 12 sections started

My First Product Blueprint · From Idea to Product: the MVPAI Masterclass · MVP Studios Academy

M 01 · Exercise 1

My idea

Start with the idea as you would explain it to a friend. It will change, and that's the point.

See the TutorDesk example

TutorDesk: a simple way for independent tutors to manage lesson bookings.

Working name The idea in one or two sentences

Ready? I can say the idea in one sentence I haven't named a technology yet

M 02 · Exercise 1

Problem statement

A product starts with someone's problem: who has it, when, what goes wrong and what it costs them.

See the TutorDesk example

Independent tutors, on Sunday evenings when they plan the week, lose track of which parents have confirmed and rescheduled, and spend about an hour chasing messages. Evidence: assumed.

Who has the problem? When does it happen? What goes wrong? What does it cost them? How do you know?

Ready? The user is narrow, not everyone No product or technology is named The evidence is labelled honestly

M 03 · Exercise 1

Product vision

A clear problem leads to a vision: the change you want for the customer, and how you'd measure it.

See the TutorDesk example

Vision: tutors spend Sunday evenings planning lessons, not chasing bookings. Value: one link that keeps every booking in one place. Outcome: hours saved per week.

Vision Value proposition Measurable outcome

Ready? The vision is about the customer, not the product The outcome can be measured

M 04 · Exercise 1 or 2

Customer profile

Who exactly is it for, and what do they use today instead? 'Doing nothing' counts as an alternative.

See the TutorDesk example

Early adopters: tutors with 10 or more regular students who already use a spreadsheet. Alternatives: WhatsApp, spreadsheets, paper diaries, booking platforms that take a fee.

First customers What they use today

Ready? I've named at least three alternatives I know who I'd talk to first

V 05 · Exercise 2

Assumptions

Every idea rests on beliefs that might be wrong. Write them down across the four risks, then find the riskiest.

See the TutorDesk example

Desirability: tutors want one booking link. Viability: they'll pay £8 a month. Feasibility: calendar sync is simple. Usability: parents can book without help.

Desirability: will they want it? Viability: will it pay its way? Feasibility: can it be built and run? Usability: can they use it? The riskiest assumption

Ready? I've covered all four risks I've picked one riskiest assumption

V 06 · Exercise 2

MVP validation

Design the cheapest test that could prove your riskiest assumption wrong, and set the bar before you see results.

See the TutorDesk example

Hypothesis: we believe a booking link for tutors will cut rescheduling messages, shown by 50% of reschedules going through the link. Test: 8 tutors for 2 weeks. Threshold: 50% or more.

Hypothesis The test Metric and threshold

Ready? The metric has a denominator The threshold was set before testing The test is cheap and quick

P 07 · Exercise 3

AI prompt log

Keep the prompts that worked and the decisions you made, so you, a colleague or an AI can pick up where you left off.

See the TutorDesk example

Prompt: 'Act as a product manager… ask me five questions first.' Decision: drop payments from the first version; keep reminders.

Prompts that worked Decisions you made

Ready? I reviewed the AI's output rather than accepting it No personal or confidential data went in

P 08 · Exercise 3

Product requirements

Decide what the first version must do, and just as importantly what it won't.

See the TutorDesk example

Must have: tutor shares a link; parent picks a slot; tutor sees bookings. Not now: payments, reminders by text, a mobile app.

Must have (at most three) Not now

Ready? At most three must-haves Exclusions are written down

P 09 · Exercise 4

Architecture

Sketch the parts a real version would need. You don't need to code; you need to know what each part is for.

See the TutorDesk example

Frontend: booking page. Backend: checks slot clashes. Database: tutors, slots, bookings. External: email. Around it: security, hosting, monitoring.

Frontend: what people see Backend: what happens behind the scenes Data: what must be stored External services Security, privacy and running risks

Ready? Each part has a job I've flagged personal data and security

A 10 · Exercise 5

Prototype review

Your first screen is a question, not an answer. Record what works, what is simulated and what a partner did.

See the TutorDesk example

Works: the booking form. Simulated: availability and confirmation emails. Peer test: my partner found the slot but missed the confirm button.

Prototype link or screenshot note What works What is simulated What your partner did What still needs building

Ready? I've said what is simulated I watched someone use it

I 11 · At home

Launch readiness

Before real users rely on it, a prototype needs to become a product: secure, private, tested and supported.

See the TutorDesk example

Before launch: real sign-in, data backed up, privacy notice, errors monitored, a way to get help.

Security and sign-in Privacy and data Hosting, backups and monitoring

Ready? I know what changes between prototype and production

I 12 · Exercise 6 and at home

Action plan

The next 30 days decide whether this idea grows. Plan conversations, a test and a decision.

See the TutorDesk example

Week 1: five tutor conversations. Week 2: run the booking-link test. Week 3: change one thing. Week 4: persevere, iterate, pivot or stop.

Week 1 Week 2 Week 3 Week 4: the decision

Ready? There's a real conversation in week 1 Week 4 ends in a decision

Your answers are stored only in this browser on this device. Don't enter personal details about other people. To move to another device, export a PDF.