SILICON VALLEY RANGSIT / CLASSROOM LAB

Startup Rangsit Quest

Build a venture around a customer problem

90 minutes6 teams × 5 learners7 missions300 credits / team

A classroom prototype for the facilitator’s screen. Learners work in teams using worksheets. Progress is stored only in this browser; separate learner devices do not share class state.

Thai guide + cards + worksheet PDF Read the background and research ↗

Form a team, take a problem and experiment

Make six teams of five and give each team one worksheet.
Each team gets one fictional scenario and 300 simulated credits.
Play seven ten-minute missions. The facilitator records choices; teams keep worksheet evidence.
Draw one challenge per team during mission 4 and reconsider the plan.
Finish with a 45-second pitch per team and a ten-minute debrief.

Six-team overview

Team	Credits left	Choices made	Reviewed	Teacher score
Team 1	300	0/7	0/7	—
Team 2	300	0/7	0/7	—
Team 3	300	0/7	0/7	—
Team 4	300	0/7	0/7	—
Team 5	300	0/7	0/7	—
Team 6	300	0/7	0/7	—

Autosaved in this browser · Download a backup to move devices

Startup Rangsit Quest learning report

Team 1 · 300 credits left · — / 100

A shop loses track of orders

1. Find a problem

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

2. Choose users and payers

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

3. Assign roles and owners

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

4. Prototype and test

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

5. Understand costs and cash

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

6. Test repeat use and delivery

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

7. Choose the next move

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

Team 2 · 300 credits left · — / 100

Students waiting for lunch

1. Find a problem

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

2. Choose users and payers

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

3. Assign roles and owners

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

4. Prototype and test

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

5. Understand costs and cash

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

6. Test repeat use and delivery

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

7. Choose the next move

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

Team 3 · 300 credits left · — / 100

Reporting repairs in a residence

1. Find a problem

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

2. Choose users and payers

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

3. Assign roles and owners

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

4. Prototype and test

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

5. Understand costs and cash

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

6. Test repeat use and delivery

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

7. Choose the next move

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

Team 4 · 300 credits left · — / 100

Reusable community packaging

1. Find a problem

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

2. Choose users and payers

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

3. Assign roles and owners

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

4. Prototype and test

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

5. Understand costs and cash

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

6. Test repeat use and delivery

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

7. Choose the next move

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

Team 5 · 300 credits left · — / 100

A small seller’s end-of-day surplus

1. Find a problem

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

2. Choose users and payers

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

3. Assign roles and owners

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

4. Prototype and test

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

5. Understand costs and cash

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

6. Test repeat use and delivery

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

7. Choose the next move

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

Team 6 · 300 credits left · — / 100

Accessible community services

1. Find a problem

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

2. Choose users and payers

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

3. Assign roles and owners

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

4. Prototype and test

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

5. Understand costs and cash

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

6. Test repeat use and delivery

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

7. Choose the next move

Plan: — (0)

Reason: —

Evidence: — · roleplay

Next: —

Scenarios, customers, events and credits are fictional learning devices. Scores reflect facilitator assessment of the activity. Real customer validation requires additional evidence.