Skip to content
THE LOOP
Pilots

Launch a founder emergence pilot.

The Loop pilots help ecosystems test evidence-based entrepreneurial activation through lightweight venture challenge formats and operator-led deployment.

§ Pilot architecture · Operator-led · Free protocol core
§ 01 - Why pilots matter

Ecosystems need practical experimentation, not another framework.

Founder potential is mostly invisible upstream of the deck. Lightweight pilots reduce institutional friction and produce evidence ecosystems can actually act on.

  • Reduce friction

    A 2-hour Loop or a 5-day challenge needs no curriculum overhaul. Operators run inside existing structures.

  • Surface the invisible

    Pilots reveal founder behavior that no application form can capture: framing, listening, decision velocity.

  • Evidence over theory

    Every pilot ships artefacts. The ecosystem learns from real signals, not from satisfaction surveys.

  • Test before scale

    A pilot tells you whether your context, partners and operators are ready - before you commit to a program.

§ 02 - Pilot formats

Six contexts. One protocol. Multiple intensities.

Pick the operational complexity that fits your context. Every format runs the same protocol and produces the same evidence types.

  • School pilot

    Duration
    4h to 1 day
    Audience
    Pre-graduate students 16-22
    Complexity
    Low
    Outputs
    First Loop, customer interviews, learning logs
    Evidence
    Curiosity, listening quality, first framing

  • University pilot

    Duration
    5 days to 4 weeks
    Audience
    Graduate and entrepreneurship tracks
    Complexity
    Medium
    Outputs
    Multiple loops, prototype, sales attempts
    Evidence
    Learning velocity, evidence discipline, commercial courage

  • Incubator pilot

    Duration
    5 to 12 weeks
    Audience
    Early-stage builder cohorts
    Complexity
    Medium
    Outputs
    Build Passport, RAT canvas, first revenue attempts
    Evidence
    Resilience, customer proximity, decision quality

  • Community pilot

    Duration
    1 day to 4 weeks
    Audience
    Open builder communities
    Complexity
    Low to medium
    Outputs
    Loop sprints, public learning logs
    Evidence
    Founder maturity, peer dynamics, ethical awareness

  • Corporate innovation pilot

    Duration
    5 days to 12 weeks
    Audience
    Intrapreneurs and innovation teams
    Complexity
    High
    Outputs
    Validated assumptions, decision logs, executive memos
    Evidence
    Strategic discipline, evidence over narrative, judgment

  • Impact ecosystem pilot

    Duration
    4 to 12 weeks
    Audience
    Mission-driven founders, often non-Western contexts
    Complexity
    Variable
    Outputs
    Local loops, impact signals, founder evidence
    Evidence
    Customer proximity, resilience, founder maturity
§ 03 - What a pilot produces

Every Loop produces observable evidence.

Evidence belongs to the participants. Operators capture it. The ecosystem learns from it. Nothing is hidden.

  • 01Customer interviews
  • 02Prototypes and MVDs
  • 03Founder signals
  • 04Team dynamics observations
  • 05First revenue attempts
  • 06Learning loops and decision logs
  • 07Operator field observations
  • 08Pivot and stop decisions
§ 04 - Active pilot regions

Three contexts. Three founder emergence laboratories.

  • Institutional pilot

    Belgium

    Schools, universities and innovation hubs. Operators trained inside existing institutional structures.

  • Impact pilot

    Africa - with Ovation.eco

    Founder emergence in high-impact contexts. Local operators, evidence-driven, ecosystem-first.

  • Startup pilot

    Madrid - with Pitchless / Beta Dash

    Anti-pitch venture format. Builders ship evidence to investors instead of decks.

→ Field Notes
CLOSING SESSION

How the Loop ends matters.

The closing session transforms a sprint into a learning artifact. Operators choose their format - teams execute in 5 minutes.

5 min per team · Included in every Loop format
CHOOSE YOUR FORMAT
  • 01

    Signal Card

    2 minCanvas · Shareable

    Teams fill a structured card: Starting point → Hypothesis → Test → Signal → Decision → Next RAT. Exported as PNG, published on the pilot page.

    Best for: all formats

  • 02

    2-Minute Loom

    2 minAsync video · AI-transcribed

    Each team records a 2-min video guided by 5 questions. Auto-transcribed, summarized by AI, archived in the Loop Evidence Library.

    Best for: remote or hybrid

  • 03

    Signal Sprint Board

    5 minPhysical + Digital · Miro

    A shared board with 3 post-its per team: confirmed signal, invalidated hypothesis, decision taken. Photo = the closing artifact.

    Best for: in-person Buildathlon (8h)

  • 04

    Founder Moment

    60 secVertical video · Social-first

    60-second phone video: We came with [X] → We discovered [Y] → We decided [Z]. Filmed, edited in 5 min, shared on LinkedIn + community.

    Best for: public pilots

  • 05

    AI Readout

    5 minLooping-generated · Auto-published

    Teams submit raw notes to Looping via theloop.vc/mycofounder. Looping generates a Signal Card, 3 learning bullets, and a next-step recommendation. Validated in 30 seconds, published automatically.

    Best for: Buildathlon (8h)

The operator chooses the format during pilot setup. Templates and guides are sent automatically.

OPERATOR DEBRIEF

After each pilot, operators complete a short debrief: NPS, blockers, improvements, readiness to run again. Feeds the Loop Evidence Library and counts toward Operator certification.

Start small. Observe deeply. Scale what works.

Phase 1 pilots are intentionally small. We optimize for signal quality, not headcount. Conversation first, contract later.