Skip to content
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

    Duración
    4h to 1 day
    Audiencia
    Pre-graduate students 16-22
    Complejidad
    Low
    Resultados
    First Loop, customer interviews, learning logs
    Evidencia
    Curiosity, listening quality, first framing
  • University pilot

    Duración
    5 days to 4 weeks
    Audiencia
    Graduate and entrepreneurship tracks
    Complejidad
    Medium
    Resultados
    Multiple loops, prototype, sales attempts
    Evidencia
    Learning velocity, evidence discipline, commercial courage
  • Incubator pilot

    Duración
    5 to 12 weeks
    Audiencia
    Early-stage builder cohorts
    Complejidad
    Medium
    Resultados
    Build Passport, RAT canvas, first revenue attempts
    Evidencia
    Resilience, customer proximity, decision quality
  • Community pilot

    Duración
    1 day to 4 weeks
    Audiencia
    Open builder communities
    Complejidad
    Low to medium
    Resultados
    Loop sprints, public learning logs
    Evidencia
    Founder maturity, peer dynamics, ethical awareness
  • Corporate innovation pilot

    Duración
    5 days to 12 weeks
    Audiencia
    Intrapreneurs and innovation teams
    Complejidad
    High
    Resultados
    Validated assumptions, decision logs, executive memos
    Evidencia
    Strategic discipline, evidence over narrative, judgment
  • Impact ecosystem pilot

    Duración
    4 to 12 weeks
    Audiencia
    Mission-driven founders, often non-Western contexts
    Complejidad
    Variable
    Resultados
    Local loops, impact signals, founder evidence
    Evidencia
    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.

SESIÓN DE CIERRE

Cómo termina la Loop importa.

La sesión de cierre transforma un sprint en un artefacto de aprendizaje. Los operadores eligen el formato - los equipos lo ejecutan en 5 minutos.

5 min por equipo · Incluido en todos los formatos Loop
ELIGE TU FORMATO
  • 01

    Signal Card

    2 minCanvas · Compartible

    Los equipos rellenan una ficha estructurada: Punto de partida → Hipótesis → Test → Señal → Decisión → Próximo RAT. Exportada como PNG, publicada en la página del piloto.

    Para todos los formatos

  • 02

    Loom de 2 minutos

    2 minVídeo async · Transcrito por IA

    Cada equipo graba un vídeo de 2 min guiado por 5 preguntas. Auto-transcrito, resumido por IA, archivado en la Loop Evidence Library.

    Para formatos remotos o híbridos

  • 03

    Signal Sprint Board

    5 minFísico + Digital · Miro

    Un tablero compartido con 3 post-its por equipo: señal confirmada, hipótesis invalidada, decisión tomada. La foto = el artefacto de cierre.

    Para Buildathlons de 8h presenciales

  • 04

    Founder Moment

    60 segVídeo vertical · Social-first

    Vídeo de 60 seg con el móvil: Vinimos con [X] → Descubrimos [Y] → Decidimos [Z]. Filmado, montado en 5 min, compartido en LinkedIn + comunidad.

    Para pilotos públicos

  • 05

    AI Readout

    5 minGenerado por Looping · Auto-publicado

    Los equipos envían sus notas a Looping vía theloop.vc/mycofounder. Looping genera un Signal Card, 3 bullets de aprendizaje y una recomendación de próximo paso. Validado en 30 segundos, publicado automáticamente.

    Para Buildathlons de 8h

El operador elige el formato durante la configuración del piloto. Las plantillas y guías se envían automáticamente.

DEBRIEF DEL OPERADOR

Después de cada piloto, los operadores completan un breve debrief: NPS, bloqueos, mejoras, disposición para repetir. Alimenta la Loop Evidence Library y cuenta para la certificación de Operador.

Start small. Observe deeply. Scale what works.

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