- Decision
- Focus the pilot on 12 sari-sari store owners in one barangay instead of the whole town.
- Adaptation
- Switched from an online sign-up form to in-person demos after only 2 of 30 replies came back.
- Outcome
- 9 owners now log daily sales. 3 have asked for credit tracking, which is next week’s test.
Ledger 02The proving-ground model
How It Works
Follow a student from a first Build to a growing 100X CV + Transcript. They solve problems with real users and markets, keep a weekly execution rhythm, and use the shared 100X operating system with Yodaman.AI support, all held to one evidence standard.
On this page
- 01Builds with real users and markets
- 02Weekly execution
- 03100X operating system
- 04Yodaman.AI support
- 05100X CV + Transcript
01Builds
Builds with real users and markets
A Build is not a case study or a simulated brief. It is a real problem that involves real users, customers, markets or communities. Students commit to it, act on it and live with the results.
This is what makes the work consequential. When a decision lands with someone outside the classroom, students get honest feedback. They learn to adapt. What they produce can be checked, not just graded.
Real people on the other side
Every Build answers to someone it actually affects. That could be a user testing a tool, a customer deciding whether to pay, a market that responds or a community whose problem is being addressed.
The same ecosystem as professionals
Students are not placed in a separate student track. They join the same Expedition ecosystem as entrepreneurs and professionals. They work to the same expectations and alongside people who build for a living.
Consequence over participation
Attendance and effort alone do not count. A Build is measured by the value it creates and the decisions behind it. This gives students proof of capability that grades and internship hours cannot show on their own.
02Weekly execution
One week at a time, on the record.
Students do not wait for a final submission to show what they can do. Every Build moves in weekly cycles. They commit to a move, do the work with real users, look honestly at what happened and decide what changes next. Each cycle leaves a trace.
Commit
Students name the week’s goal and the decision behind it: who they are serving, what they will test and what would count as progress.
Execute
They do the work where it matters. That means talking to users, shipping a version, running the offer or showing up for the community.
Evidence
They capture what actually happened, such as replies, numbers and artefacts, rather than what was planned.
Adapt
They review the results and keep, change or drop the approach before the next week begins.
What accumulates
- Decisions
- The choices made and the reasoning behind them.
- Adaptations
- What changed when reality pushed back.
- Outcomes
- What the work produced for real people.
Week after week, this record becomes the student’s 100X CV + Transcript. It is proof of capability built from evidence rather than hours logged.
The system
One shared system. Support built in.
Every student on the Expedition plans, executes and records their Build in the same place. AI support is on hand when the next step isn’t obvious. For your school, that means one standard to adopt rather than a new toolkit to invent, and it holds from the first cohort onward.
01Product
100X operating system
The shared operating system students use to plan, execute and record their Builds each week. It is the same system used across the Expedition, so students work to the same rhythm as the entrepreneurs and professionals around them.
- PlanSet the week’s goal and the assumption worth testing.
- ExecuteDo the work with real users, customers or communities.
- RecordCapture decisions, adaptations and outcomes as they happen.
02AI support
Yodaman.AI
AI support that helps students think through next steps on their Build. It helps them ask sharper questions, weigh their options and turn a stalled week into a plan. The decisions, and the evidence, stay with the student.
Student
I interviewed 14 sari-sari store owners about restocking. Only 3 said they’d pay for a delivery service. Do I drop the idea?
Yodaman.AI
Before deciding, look at those 3. What do they share — location, store size, how far they travel to restock? If there’s a pattern, a narrower test this week could tell you more than the other 11 answers.
03For school leaders
Shared standard
Every cohort works in the same system, so evidence stays comparable across sections, programmes and school years. Your faculty review work against one consistent record instead of reconciling different formats.
04For school leaders
Built to scale
From one cohort to thousands without diluting the standard. Start with a focused group and expand on the same footing, with no change to how Builds are run or recorded.
See how schools grow from pilot to scaleWant to see the system working with your own students?
See it in your school
Ready to see Builds in your programs?
Start with one focused pilot cohort, then expand on the same evidence standard. To decide where it fits first, see the integration pathways.
Request a pilot
Or email iggy@ignitehouse.vc