4h
4h Loop
Participants
8 - 30 participants
Facilitators
1 facilitator
Outputs
§ Field Manual · Run Your First Loop
Run your first Loop in one day.
A practical guide to launching evidence-based venture challenges with small groups, simple tools and rapid learning cycles.
§ 01 - Choose your format
Four operational intensities.
Pick the smallest format that produces a real signal.
1 day
Buildathlon (8h)
Participants
12 - 40 participants
Facilitators
1 - 2 facilitators
Outputs
5 days
5-Day Challenge
Participants
20 - 60 participants
Facilitators
2 - 4 facilitators · mentors
Outputs
12w
12-Week Program
Participants
20 - 50 builders
Facilitators
Operator + mentor pool
Outputs
§ 02 - Required materials
What you actually need.
No platform. No login. No onboarding call.
- Printed or digital canvases (Problem, RAT, First Euro)
- Visible timers - one per team
- Interview templates and verbatim sheets
- Access to general AI tools (chat, image, transcription)
- Breakout spaces - even small corners count
- An evidence board - wall, table, or shared doc
§ 03 - Facilitator principles
Facilitators guide evidence. They do not give answers.
Four mentor postures. One discipline: protect the loop, not the idea.
The Operator
Holds the rhythm. Enforces timeboxes. Defends the protocol from drift.
The Capital
Asks the venture-grade questions. Pushes on viability without picking winners.
The Conscience
Protects participants. Watches for ethical drift, exhaustion, exclusion.
The Field
Brings real-world context. Sources users. Connects teams to reality.
§ 04 - The Loop flow
Signal → Frame → Build → Test → Learn → Decide.
Indicative timing for a Buildathlon (8h). Compress for 4h, expand for 5d / 12w.
- S1 · Signal
Talk to users. Capture verbatims. Detect real pain.
- S2 · Frame
Sharpen the problem. Pick one user, one moment, one job.
- S3 · Build
Ship the smallest evidence-bearing artefact. AI-native.
- S4 · Test
Confront the artefact with reality. Real users. Real money.
- S5 · Learn
Convert outcome into a decision-grade insight.
- S6 · Decide
Persevere, pivot, or stop - with evidence.
§ Canvas system · Printable
Three canvases. One operational discipline.
Run them in order. Print them. Stick them on a wall. Evidence first, ideas second.
C.01 · Problem Signal Canvas
Observe pain before building solutions.
- Observed problem
What did you see, hear, or measure - not what you assume.
- Affected users
Who lives this problem. Be specific. Avoid 'everyone'.
- Frequency
How often does it occur. Daily, weekly, edge case.
- Emotional intensity
Hair-on-fire, annoying, tolerable. Quote the user.
- Existing workaround
What people do today to cope. Tools, hacks, silence.
- Evidence source
Interview, observation, dataset, ticket. Cite it.
- Contradictions
What did NOT match the assumed narrative.
- Signal confidence
Low / Medium / High. With one sentence of justification.
C.02 · RAT Canvas
Identify and test the most dangerous assumption first.
- Key assumption
The single belief that, if false, makes the venture collapse.
- Why it matters
Consequence of being wrong. Be honest about kill-risk.
- Test design
Smallest experiment that produces a real signal. No demo theatre.
- Expected signal
What would 'true' look like. What would 'false' look like.
- Success threshold
Numeric or behavioural bar. Defined BEFORE running the test.
- Actual outcome
Raw result. Verbatims, numbers, screenshots.
- Decision
Persevere · Pivot · Stop. With one sentence of reasoning.
C.03 · First Euro Canvas
Design the fastest path to real economic validation.
- Customer profile
Specific person who could pay this week. Name them.
- Value trigger
The moment the customer feels the pain sharply.
- Acquisition channel
Where you will physically reach them. Not 'social media'.
- Offer
What exactly is being sold. One sentence.
- Pricing
Number, currency, structure. Even if symbolic.
- Payment mechanism
Stripe link, invoice, cash. Operational, not theoretical.
- Proof collected
Receipt, screenshot, signed quote. Evidence of money moving.
- Next loop
What this first euro tells you to test next.
§ 05 - Common failure modes
What kills a Loop.
Six anti-patterns to call out the moment you see them.
Building too early - skipping signal and frame.
Fake validation - 'my mom said it's a great idea'.
Endless brainstorming with no field contact.
Pitch obsession - polishing decks instead of evidence.
Avoiding uncomfortable evidence that contradicts the thesis.
Testing only with friends, classmates, or insiders.
§ 06 - Launch
Launch your first founder emergence loop.
Download the kit. Pick a format. Run a Loop this month.