Zunou
Japan-Led GTM Strategy
Pilots · the per-partner workshop Internal prep + customer-facing deck per partner. Threaded into GTM Phase 1A.
GTM Phase 1A Foundation Tier-1
Pilots index Marco Avila · v1 · per-partner workshop

One page per pilot.
Prep doc inside. Deck for the partner.

Each pilot is its own folder under /pilots/<name>/ with two surfaces: an internal prep doc (what Marco + Malek read together) and a customer-facing deck (what we actually screen-share). Index sorts by status — active first, future last.

Active prep
1
Indelible Ventures · Beachhead 0
Queued
2
Wave 2 fallbacks awaiting gate
Planned
1
Beachhead 1 · TAI Tokyo
Future
2
Beachhead 2 layered communities
Executive summary 5 bullets · 30 seconds
  1. One pilot, two surfaces. Each /pilots/<partner> has an internal prep doc and a separate customer-facing deck at /pilots/<partner>/deck. Same content, different audiences and registers.
  2. Active right now: Indelible (Kevin Brockland). Our first portfolio rollout — Zunou is already in their portfolio. Three sequenced use cases. Pre-flight bug list visible.
  3. Two queued (Beachhead 0 wave 2): North Base Media + Headline. Fire only if Indelible's signal is mixed or if we want a parallel SEA read.
  4. One planned (Beachhead 1): TAI Tokyo, late July / early August 2026, conditional on Indelible UC1 clearing its gate.
  5. Two future (Beachhead 2): AI Tinkerers Ginza + Venture Café Toranomon. Layered post-TAI.
01 Active prep · 1

Indelible Ventures · Portfolio rollout

Beachhead 0 Wave 1

Kevin Brockland · indelible.vc · Kuala Lumpur · SEA

Zunou is already in their portfolio (per Tracxn). First confirmed external pilot — three sequenced use cases mapped from the meeting: portfolio knowledge hub → AI Salon Bangkok → FI Thailand alumni.

Next action: Clear iOS pre-flight blockers, build portfolio-pulse template, book follow-up meeting on his Android.

Internal prep Customer deck
02 Queued · awaiting gate · 2

North Base Media

Beachhead 0/2 Wave 2

TBD contact · northbasemedia.com · TBD

Beachhead 0 wave 2 — fires only if Indelible signal is mixed (≤60% activation in 14d) or if we want a parallel SEA-anchored read before opening TAI.

Next action: Identify warm-intro path. Confirm thesis fit. Defer until UC1 (Indelible) hits its gate.

— prep TBD — deck TBD

Headline Ventures

Beachhead 0/2 Wave 2 (alt)

TBD contact · headline.com · TBD

Alternative to North Base for the second Beachhead 0 wave. Larger fund, potentially faster portfolio coverage but lower per-founder trust density.

Next action: Hold until Indelible gate. North Base is the preferred wave 2 unless intro paths shift.

— prep TBD — deck TBD
03 Planned · Phase 1B+ · 1

TAI · Tokyo AI

Beachhead 1 Beachhead 1

Ilya Kulyatin (warm intro) · Tokyo · Japan

Tokyo community pilot launches end July / early August 2026. ~4,000-person WhatsApp group + monthly meetup. Spaces (Event-Spaces) is the natural surface; the muted-WhatsApp-triage wedge is the activation play.

Next action: Gate-conditional on Indelible UC1. Run Spaces flow QA in parallel with Beachhead 0.

— prep TBD — deck TBD
04 Future · Beachhead 2 · 2

AI Tinkerers Ginza

Beachhead 2 Beachhead 2

TBD chapter lead · Ginza · Tokyo

First of the layered Beachhead 2 communities. Dense AI builder audience overlaps with TAI; recurring monthly meetup format ideal for Spaces.

Next action: Defer. Layer in after Beachhead 1 establishes operational pattern.

— prep TBD — deck TBD

Venture Café Toranomon

Beachhead 2 Beachhead 2

TBD chapter lead · Toranomon · Tokyo

Weekly Thursday Gathering format (50–200 attendees per event). High recurrence = high cumulative installs. Spaces-as-event-OS positioning lands cleanly here.

Next action: Defer. Layer in alongside AI Tinkerers post-Beachhead 1.

— prep TBD — deck TBD
05 How to use these pages

Two URLs per partner, two registers.

Internal prep · /pilots/<partner>

What Marco + Malek read together before the meeting. Honest, action-oriented, with file:line cross-refs into Foundation Tier-1 and Journeys.

  • Research on the partner (CFA, fund firmography, sister portfolio)
  • Pain points captured from the meeting (in their words)
  • Pre-flight bug list — what blocks the pilot
  • Next-meeting agenda + open questions
Customer deck · /pilots/<partner>/deck

What we screen-share with the partner. Visual-first, less internal jargon, designed to be walked through in 15–20 minutes. Includes screenshot zones for live product captures.

  • Hero framing: their pain in their words
  • Three sequenced use cases — visual narrative
  • Product-in-action screenshot zones
  • What "success in 14 days" looks like — magic-number framed for them
  • What we're asking from them next
When you create a new pilot
  1. Drop a row in the array at the top of /src/pages/pilots/index.astro
  2. Create /src/pages/pilots/<partner>.astro from the Indelible prep template
  3. Create /src/pages/pilots/<partner>/deck.astro from the Indelible deck template
  4. Cross-link from GTM Phase 1A so the partner shows up where the strategy lives
  5. Update the partner row's prepUrl + deckUrl here

Where this fits

Pilots is the workshop floor. GTM is the blueprint.

The strategy lives in GTM. The build plan lives in Foundation. The user-flow audits live in Journeys. Pilots is where each named partner gets the prep + the pitch. One folder per partner. Two URLs each. No mixing.

Indelible · internal prep Indelible · customer deck