5-week evidence-building journey for pathfinders

Build for the edge.
Forge new frontiers.

Build for the edge.
Forge new frontiers.

Build for the edge.
Forge new frontiers.

Start the trailhead

Arc Frontier is a 5-week youth incubation sprint. Students move from problem discovery to a visible portfolio and a grounded venture decision through weekly artifacts, mentor gates, and customer evidence.

Arc Frontier is a 5-week youth incubation sprint. Students move from problem discovery to a visible portfolio and a grounded venture decision through weekly artifacts, mentor gates, and customer evidence.

Arc Frontier is a 5-week youth incubation sprint. Students move from problem discovery to a visible portfolio and a grounded venture decision through weekly artifacts, mentor gates, and customer evidence.

A five-week evidence pipeline, not a class schedule.

A five-week evidence pipeline, not a class schedule.

A five-week evidence pipeline, not a class schedule.

Each week has a focus, a core question, a working response, and proof points mentors can inspect. Customer evidence moves underneath the sprint from problem users to demand prospects.

Each week has a focus, a core question, a working response, and proof points mentors can inspect. Customer evidence moves underneath the sprint from problem users to demand prospects.

W1 / Discover

Problem + value

Students prove the problem before the solution through a Problem Brief, Value Proposition, Opportunity view, Product Box, and PRFAQ.

W2 / Define

Needs + scope

Customer-backed requirements define what the solution must do, for whom, and within what boundaries.

W3–W5 / Build, test, decide

Prototype to decision

Teams build v1, test with several users, improve based on evidence, then present an evidence-backed next step.

Admissions selects Pathfinders

Fit for ambiguity, action, reflection, and commitment.

Fit for ambiguity, action, reflection, and commitment.

Fit for ambiguity, action, reflection, and commitment.

We use tools that professionals use in the real life

The Pathfinder loop runs every week.

The Pathfinder loop runs every week.

The Pathfinder loop runs every week.

Students learn, contact, define, build, test, reflect, and commit. The loop repeats as customer evidence compounds from initial users to prototype testers and demand prospects.

Students learn, contact, define, build, test, reflect, and commit. The loop repeats as customer evidence compounds from initial users to prototype testers and demand prospects.

01

Discover: is the problem worth solving?

Problem evidence comes before solution. The gate asks whether the issue is specific, frequent, painful, and valuable.

02

Define: what must the solution do?

Students translate needs into a customer journey, stakeholder map, future customer list, PRD v1, and wireframe.

03

Build and test: what happens in reality?

Prototype v1, build logs, test scripts, field logs, evidence boards, iteration briefs, and prototype v2 make changes inspectable.

04

Launch and decide: what does the evidence support?

The final output is a portfolio, founder memo, demo deck, and decision to continue, pivot, pause, kill, or transfer.

Already on the path? Sign in. Not applied yet? Join the waitlist.

Already on the path? Sign in. Not applied yet? Join the waitlist.

Already on the path? Sign in. Not applied yet? Join the waitlist.

Existing students can sign in to continue their sprint. If you have not applied yet, complete the waitlist form and we will guide you through the next step.

Existing students can sign in to continue their sprint. If you have not applied yet, complete the waitlist form and we will guide you through the next step.

Sign in

Join the waitlist

The waitlist takes a few minutes. Returning students should use Sign in instead.