Kevin's portfolio is the wedge.
The product has to be ready for it.
First external user. Three concrete pain points from the meeting. Three sequenced use cases. A short pre-flight list of bugs to clear (iOS auth, web DM, notification outbox) — most are already Foundation Tier-1. Kevin himself is on Android (PWA covers it for ~6 weeks), but his portfolio is mixed — iOS bugs block the pilot, not just his demo.
- Kevin Brockland (Indelible Ventures, KL) is our first portfolio rollout — and Zunou is already in his portfolio per Tracxn. Critical reframe: this isn't a cold sale, it's a portfolio company demoing back to its GP. The meeting surfaced three concrete pains; we sequence by activation likelihood, not by his preference — lead with the smallest, highest-trust use case.
- Lead with the portfolio knowledge hub. Smallest cohort (~20–40 founders), Kevin-curated trust, fastest read on whether the magic-number works on a friendly cohort. Don't open events or FI alumni until UC1 hits its gate.
- iOS bugs block this pilot, not just Kevin's demo. Kevin is Android (PWA fine for him), but his portfolio is mixed. The "sign in twice" + "iOS keeps kicking users out" bugs from the audit will burn ~30–50% of his portfolio before they ever activate. Foundation Tier-1 has these — they're now hard pre-flight blockers for this pilot.
- Native Android in 3–4 weeks. PWA on Android Chrome covers Kevin himself for the first 6 weeks of the pilot. Native build (Capacitor or Expo) ships to Google Play internal testing in ~3–4 weeks so he can dogfood while the rest of the portfolio runs PWA.
- The next meeting is a 35-minute structured agenda. Recap pains → live demo on his Android → show the magic-number instrumentation → pre-flight transparency → his next move (he curates the first 5 founders) → open questions. Outline below in §07.
Kevin Brockland · Indelible Ventures.
CFA, ex-impact-fund portfolio manager (SEAF ~$400M AUM, MDIF covering India / SEA / LatAm). Relocated to Malaysia, founded Indelible Ventures in 2021. VC Lab alumnus · Endeavor Malaysia mentor · organizes AI Salon Bangkok on Luma.
Zunou is already in Indelible's portfolio. This isn't a cold sale — Kevin is one of our investors. The pitch is "the portfolio knowledge hub you wished existed, that we just built and now want to roll out across your portfolio first." Earned trust, much warmer dynamic. (Source: Tracxn portfolio listing.)
Pre-seed / seed. First check $100K–$250K, average round $580K. ~10 portfolio companies as of early 2025. Thesis: B2B SaaS · fintech infra · AI-enabled tools · productivity · HR — for SEA's overlooked corners.
Sister portfolio (UC1 lookalikes): BetterClinic (ambient AI scribe) · Kimaru AI (supply chain) · Quotable AI (SME supply) · RunCloud · Vase AI · Zunou AI.
indelible.vc →Kevin organizes the SEA chapter of the global AI Salon network. Monthly invite-RSVP events on Luma. Audience: early-stage AI founders + investors. Recent confirmed editions: May 2025 · Sep 2025.
HQ-rolled-out platform is bad → migrated Eventbrite → Luma → WhatsApp group hit max. UC2 lives here.
Kevin is a FI-affiliated mentor (VC Lab alumnus). The FI Bangkok chapter was launched by Krating Poonpol (Disrupt) + Benjamin Ranck (Jetabroad) — Kevin is not the chapter director. He routes us to FI Thailand once UC2 lands.
Thailand cohort already used an auto-join-app pattern — exactly mirrors what Spaces does at graduation. UC3 lives here.
Indelible backs pre-seed/seed B2B SaaS and AI tools targeting SEA founders who are resource-constrained and need to punch above their weight operationally — that's the published thesis on indelible.vc. Zunou's Pulses + Spaces + Agent stack is directly additive for sister portfolio companies: BetterClinic (small clinical teams), Quotable / Kimaru (distributed supply-chain ops), Vase AI (async research workflows). Each one needs lightweight async collaboration without enterprise pricing — the agent layer addresses the exact "enterprise software infrastructure" gap their thesis names. UC1 isn't speculative; the lookalikes are sitting in the same fund.
From the meeting · in his words.
Each pain is real and current. We don't have to invent demand — we just have to be ready for it.
"How do I leverage the portfolio for extra value, downstream to the companies?"
Facilitate knowledge sharing · interactions amongst portfolio companies · shared learnings of GTMs and outbound · what's the latest and greatest of service providers. Kevin is sitting on dense tribal knowledge that never circulates.
"HQ rolled out a bad platform — Eventbrite to Luma, then WhatsApp hit max."
Easier way to attend events, come back to events. Free tools intentionally — they're not monetizing the AI Salon. The pain is community-organizational, not revenue. Spaces is the answer; Luma stays for registration.
"Built a portal — no interactions inside. Hard to keep alumni after they graduate."
Teaching startups bad at product design. Right now just an email list. Thailand cohort already had an app installed and auto-joined the group — that's the pattern we mirror with Spaces install at graduation.
Sequenced. UC1 lands first. UC2 unlocks. UC3 follows.
Activation must feel organic. Kevin will lead — try the portfolio pulse himself, then bring his team, then bring the portfolio. Members stick on the magic-moment landing in their first session, not on a pitch.
Indelible Portfolio Knowledge Hub
Pain: Portfolio founders don't share GTM learnings, outbound playbooks, or vetted service-provider intel. Tribal knowledge stays tribal — Indelible's value-add stops at the cap-table.
Play: Private portfolio pulse. Default channels: Intros · Playbooks · Service Providers · Asks · Wins. Agent ingests and surfaces what's relevant to each founder's stage and stack. Brain Dump captures learnings, Relays drives async intros, Voice Agent answers "latest playbook on cold-email in SEA right now."
Magic number: 60% of portfolio founders hit 5 events + 1 magic moment + 3 returns in 14 days. Magic moment = a relevant intro, playbook, or service-provider rec the agent surfaces unprompted.
Why this position: Smallest cohort (~20–40 portfolio companies), Kevin-curated trust, fastest activation read. Lowest pre-flight risk.
AI Salon Thailand · Events
Pain: HQ-rolled-out platform is bad. Eventbrite → migrated to Luma → hit WhatsApp group max → no continuity post-event. Free intentionally (no monetization), so the pain is community-organizational.
Play: Spaces (Event-Spaces): QR at the door → Nova installs → AI agent pre-loaded with attendee + event + speaker context → persistent post-event Pulse. Luma stays for registration; Zunou is the community-continuity layer.
Magic number: Attendee hits 5 interactions + 1 magic moment + 3 returns inside 14 days post-event. Magic moment = an intro the agent makes, or a question answered by another attendee's content.
Why this position: Needs Spaces flow end-to-end + a successful UC1 to point at as proof. Becomes the wedge for the broader Thailand AI community.
Founder Institute Thailand · Alumni
Pain: Built a portal — no interactions inside. Alumni become an email list after graduation. Thailand cohort already had an app install + auto-join group as the pattern that worked.
Play: Alumni Pulse with auto-join via Spaces install at the graduation event → ongoing agent-mediated re-engagement (curated learnings, fresh intros, hiring digests, service-provider rotations).
Magic number: Alumni stay engaged 30 / 60 / 90 days post-graduation, measured by 5+ interactions per month per alum.
Why this position: Needs the events flow from UC2 + a portfolio activation success story before we propose this to FI Thailand leadership.
What has to be true before the pilot opens.
Kevin is Android — PWA covers him for ~6 weeks. But his portfolio is mixed. iOS bugs we already documented in Foundation Tier-1 become hard pre-flight requirements for this pilot, not just future improvements. Burning a portfolio founder on day one because of a sign-in bug is the worst thing we can do — Kevin loses face with his founder, and the pilot's activation read collapses.
Blocking · must clear before pilot opens (4)
Fix native iOS auth — "keeps kicking users out"
Kevin uses Android (PWA fine for him), but his portfolio is mixed. iOS founders bouncing on cold-start kills the cohort activation read. PWA fallback isn't acceptable when the rest of TAI is on iOS.
Foundation Tier-1 #06 + Journeys §J1Drop `prompt: 'login'` — "sign in twice"
One-line fix. Returning iOS users see the login screen on every cold start; some give up before they sign in once.
Journeys §J1 → Drop prompt: 'login'Make `upsertNovaSettingMetadata` blocking before navigation
If the GQL save returns mid-background, iOS user re-onboards on next session — looks like "sign in twice" from their POV. Will hit Indelible founders the day after the pilot opens.
Journeys §J2 onboarding bugWeb DM flow restored
If anyone in Kevin's portfolio demos on a laptop (likely — investors check things on desktop), the missing /dashboard DM path looks like a half-built product.
Foundation Tier-1 #02 + Journeys §J4In flight · should clear in parallel with pilot prep (5)
Verify production onboarding end-to-end with a fresh pilot account
Onboarding rebuilt recently; production behavior hasn't been validated by a non-team user. A broken first session = magic-number activation reads as 0%, regardless of how good the rest of the pitch is.
Foundation Tier-1 #01Notification outbox + idempotency + DLQ
Indelible portfolio = 20–40 founders messaging each other in a private pulse. Every silently-dropped @mention is a broken trust moment. Outbox is the cheapest insurance.
Foundation Tier-1 #10Surface per-channel mute in conversation header
Volume in the portfolio pulse will spike. If they can't tame the noise per-channel without nuking everything, they'll mute the whole product. Already exists in backend — just expose it.
Foundation Tier-1 #03Confirm PWA on Android Chrome — install, push, badge
Kevin's primary device. PWA must support add-to-home-screen, push notifications via Web Push, and badge counts. Test on his exact device before the next meeting.
Journeys §J1 (web push path)Native Android build → Google Play internal testing
PWA is fine for the next 4–6 weeks but native unlocks better push reliability + background sync. Capacitor or Expo build (we have iOS already). Aim for internal testing track in 3–4 weeks so Kevin can dogfood the native app while his portfolio uses PWA.
Foundation Stage 4 (mobile parity)Ready or near-ready (1)
Pre-built portfolio pulse template
Kevin shouldn't have to configure pulse settings, default channels, agent prompts, or service-provider templates from scratch. Ship a one-click "VC portfolio" template (channels: Intros · Playbooks · Service Providers · Asks · Wins).
Kevin gets PWA on day one. Native Android in three to four weeks.
We don't want to delay the pilot waiting for native — and we don't want to leave Kevin on PWA forever either.
Add-to-home-screen, Web Push notifications, badge counts. Kevin installs from chrome://flags-free flow. Full functionality minus background sync edge cases.
- Verify install prompt fires in his Chrome version
- Verify Web Push notifications land + are tappable
- Verify the install icon stays on his home screen across Chrome updates
We have iOS Nova working (Expo / React Native). Android build is the same codebase + an Android signing key + Play Console internal-testing track.
- Set up Android signing key + Play Console
- Add Kevin to internal testers list
- First build via EAS Build (or Xcode-equivalent for Android)
- Tighten Beams / FCM push registration on Android
Internal-track build is the realistic 3–4 week target. Public Play Store comes after.
35 minutes. Six blocks. Demo on his Android.
Don't pitch — show. Magic-number-or-bust philosophy. He should leave the meeting with a clear picture of (a) what Zunou does for his portfolio, (b) what we're fixing first, and (c) what he does next.
Recap pain points + confirm sequencing
Recap Kevin's three pain points back to him; confirm we lead with the portfolio knowledge hub (not events, not FI alumni).
Live demo · UC1 portfolio pulse
On Kevin's device (Android PWA). Show: Brain Dump capturing a learning · Relays sending an async intro · Voice Agent answering a real portfolio-relevant question · Daily Debrief surfacing it.
Show the magic-number instrumentation
Walk the activation funnel we'll be reading. The number we'll send him at day 7 and day 14. Honest about what triggers the gate-up to UC2.
Pre-flight transparency
Show the bug list we're fixing before opening his portfolio (iOS auth, web DM, notifications). Set expectation: pilot opens after the blocking items clear.
His next move
Kevin curates the first 5 founders he'd want in the portfolio pulse. We hand-onboard each one alongside him.
Open questions + close
Pricing for after pilot? Spaces config for Thailand AI Salon (UC2 prep)? FI Thailand intro path (UC3)? Anything we missed?
Things to resolve before — or in — the next meeting.
Pricing post-pilot
What does Indelible pay (if anything) for the portfolio pulse + Spaces? Free for pilot is fine; the pricing conversation comes after activation lands.
Indelible thesis confirmation
Pull their thesis from indelibleventures.com + LinkedIn before the meeting. Quote it back to him. Show we did the homework.
First 5 founders
Kevin curates. We pre-prep the portfolio pulse with default channels and an agent-prompt template before he sends invites.
AI Salon Thailand timeline (UC2)
When's the next salon? Spaces flow needs to be production-ready by then — possibly sets a hard date for UC2 readiness.
FI Thailand intro path (UC3)
Who's the right FI Thailand contact when we're ready? Confirm Kevin's still close enough to make the warm intro.
Pre-flight transparency vs polish
Show him the bug list openly (engineering credibility) or wait until clean (product polish)? Recommend showing it openly — Kevin's a builder, he'll respect the honesty.
The bottom line
Land Kevin with one use case done well, not three half-shipped.
The portfolio knowledge hub is the wedge. Get the iOS bugs out of the way so his founders can actually activate. Hand-onboard the first five with him. Read the magic-number at day 14. If it lands, we earn the right to UC2 (events) and the TAI pitch. If it doesn't, the second Beachhead 0 wave (North Base Media or Headline) is next.
He'll try most himself. The product has to do the rest.