Overview
Strategy
Product Phases
Signal (v1)
Architecture
Delivery
Dev
Ops & Next
Stakeholders
GitHub LLM Wiki
Organized AI · MatchBox

MatchBox — strike the match between founders and VCs

A matching layer that sits on top of a partner fund's existing deal flow. Listens to VC-founder calls, scores sentiment + fit, surfaces coaching notes for the founder and ratings for the VC, and turns high-confidence pairings into portable signal. Not another CRM — the engine that makes the next-best founder obvious.

v1 Signal · shipping
v2 Matching · planned
v3 Founder Prep · planned
Forked from ClawBox (Tauri + Bun + React 18)
Forbes-first rollout
Revenue model in negotiation

Product thesis

The best founder–VC matches are obvious in the first 20 minutes of a call. MatchBox makes that signal legible, portable, and actionable.

Four moves per call

listens

Transcribes every VC-founder call and scores sentiment, fit, and red flags. Captures training data for v2 matching.

matches

Pairs founders with the right fund based on call signal plus intake data, not just thesis keywords. (v2 deliverable.)

coaches

Returns founder-ready coaching notes and VC-ready call ratings after each conversation. Closes the feedback loop.

connects

High-confidence deals get shared across a trusted VC network as the subscriber base grows. Network depth compounds.

Seed node
Crowley Capital is the seed node for the curated VC network. Partner contact: Jon Forbes.

At a glance

KeyValue
RepoOrganized-AI/MatchBox (private · MIT)
Default branchclaude/founder-fund-matching-urzts
Base projectForked from ClawBox (still reports clawbox in package.json)
Shipping surfaceSignal · src/components/SignalView.tsx
Founder intakeAirtable form
Strategy callGranola notes
Phase 01 · Strategy

Strategy

Upgrade a working 7/10 VC workflow into the 10/10 industry benchmark by wiring MatchBox into a partner fund's existing process. No forced platform migration.

Forbes-first rollout

Primary · Jon ForbesProven software funding pipeline · wants ambiguous-industry expansion
Non-exclusiveForbes is the case study; same system offered to other funds once proven

Why Forbes first

  • MatchBox slots in as the matching + signal layer on top of existing deal flow — no CRM migration.
  • Forbes's proven pipeline + infrastructure means integration is additive, not invasive.
  • Ambiguous-industry expansion is the explicit thesis he wants — matches MatchBox's core capability.
  • A reference customer earlier means the subscription tier is easier to price on real outcomes.

Revenue model — in negotiation

Jake meets Jon Forbes this Friday to lock compensation terms before broader rollout. Options on the table:

  • Revenue share on existing portfolio companies uplifted by MatchBox.
  • Deal participation in successful post-implementation investments.
  • Subscription for other funds accessing the MatchBox network.
Open question
  • Terms are not locked yet. All downstream rollout plans depend on the Friday meeting landing.
Phase 02 · Roadmap

Product Phases

Three product versions, compounding value — signal captures the training data for matching, matching's ranking signals feed founder prep.

v1 · Signal · shipping

Turns each VC-founder call into structured signal. Transcribe → sentiment + fit + red flags → coaching notes for the founder + ratings for the VC. Captures training data for v2.

v2 · Matching · next

High-confidence founder ↔ fund pairings. Cross-network deal sharing between subscribed funds. Match quality improves fund-over-fund as the data pool grows.

v3 · Founder Prep · later

AI avatar conducts the initial founder interview. Automated screening before the VC meeting. Due-diligence layer that cuts fraudulent claims and wasted partner time.

v1 surface (today)

  • src/components/SignalView.tsx — the operator UI.
  • src/types/signal.tsFundProfile · CallSignal · SentimentScores · RedFlagHit · AirtableConfigView · AnalyzeCallInput.
  • src/services/signal.ts — fetch client against the local backend at http://127.0.0.1:13000.
  • src/store/signal.ts — Zustand state: funds, calls, Airtable config, loading/syncing/analyzing flags.
  • internal/routes/signal.ts — Hono routes (Airtable config, sync, funds CRUD, analyzer).
  • internal/signal/{index,airtable,analyzer}.ts — store + Airtable sync + LLM analyzer.

What Signal is not

  • Not a recording tool — works off transcripts you already have.
  • Not a standalone SaaS — it's an internal operator surface plus agent delivery into the VC's existing tools.
  • Not yet the matching engine — v1 captures the training signal for v2.
Phase 03 · Signal

Signal — the v1 shipping surface

Signal turns a call into a structured CallSignal: rating, sentiment scores, red flags with quoted evidence, fact-finding prompts, and coaching notes for the VC.

Data model

interface FundProfile { id, name, thesis, stage, checkSize, sectors[], redFlags, notes source: 'manual' | 'airtable' airtableRecordId?, createdAtMs, updatedAtMs } interface CallSignal { id, fundId, fundName, founderName, callDate transcriptExcerpt, rating (0-10) sentiment: { enthusiasm, thesisAlignment, concern } // each 0-10 redFlags: [{ quote, reason }] factFindingPrompts: string[] coachingForVc, summary model?, createdAtMs } interface AirtableConfigView { apiKey (masked), hasApiKey, baseId, tableName, viewName }

Backend routes — internal/routes/signal.ts

Method + pathRole
GET /api/signal/airtableCurrent Airtable config (API key masked to last 4)
PUT /api/signal/airtablePatch config · supports clearApiKey
POST /api/signal/airtable/syncPull FundProfile rows from Airtable
GET · POST · PUT · DELETE /api/signal/fundsManual fund CRUD (coexists with Airtable-sourced rows)
GET · POST · DELETE /api/signal/callsCall list + analyze + delete

Analyzer — internal/signal/analyzer.ts

Builds the prompt from the FundProfile + transcript (truncated to MAX_EXCERPT_CHARS = 20_000), calls callOpenclawDefaultModelChatCompletion, validates the JSON response, and produces an AnalyzeResult that gets wrapped into a persisted CallSignal.

  • Score clamping — each numeric score rounded to 0.1 and bounded to [0, 10].
  • Red flags cap — max 8 per call, each carrying a literal quote + reason.
  • Fact-finding prompts — max 8; the next-call follow-up questions the VC should ask.
  • Transcript truncation is explicit — appends …[truncated N chars] so the model knows.
Why Airtable
The founder intake form is already on Airtable — Jake runs the top of funnel there. Signal syncs fund profiles from Airtable rather than inventing a new schema. Base id + table name + view are all config.
Phase 04 · System

Architecture

MatchBox inherits the ClawBox three-process split: Tauri shell · React 18 SPA · Bun/Hono backend. Signal adds one route module, one store, and one analyzer over that base.

Processes [Tauri v2 shell · Rust] src-tauri/ OS integration · autoupdate [React 18 + Vite SPA] src/ Zustand · Tailwind · en / zh i18n fetch http://127.0.0.1:13000 [Bun / Hono backend] internal/ routes incl. signal.ts ├──▶ Airtable fund intake sync WebSocket RPC [OpenClaw Gateway] http://127.0.0.1:18789/v1 [LLM provider] via callOpenclawDefaultModelChatCompletion

Repo layout

. ├── src/ │ ├── components/ │ │ ├── SignalView.tsx # v1 operator UI │ │ ├── ChatView · OnboardView · SettingsView · … # inherited from ClawBox │ │ └── chat/ · layout/ · plugins/ · sidebar/ · skills/ · soul/ · ui/ │ ├── services/signal.ts # fetch client │ ├── store/signal.ts # zustand │ └── types/signal.ts # shared TS types ├── internal/ │ ├── routes/signal.ts # Hono routes │ ├── signal/ │ │ ├── index.ts # store (funds + calls + airtable cfg) │ │ ├── airtable.ts # syncFundsFromAirtable │ │ └── analyzer.ts # analyzeTranscript via OpenClaw default model │ ├── providers/openclaw-completions.ts # model bridge │ ├── channels · onboard · skills · titles · tool-call-summaries │ └── routes/{agents,channels,chat,config,cron,models,onboard,sessions,skills,soul,titles,tools}.ts ├── src-tauri/ # Tauri v2 Rust shell ├── scripts/ # mock-gateway · sync-version · sign-win · … ├── docs/ # dependency-policy · openclaw-compatibility · releases · releasing ├── public/ · test/ · index.html └── package.json (still named "clawbox" · v2026.3.17)

Inherited from ClawBox

  • All 12 backend routes (agents · channels · chat · config · cron · models · onboard · sessions · skills · soul · titles · tools).
  • All non-Signal frontend views (Chat · Cron · Onboard · Plugins · Settings · Skills · Soul · Startup · etc.).
  • Onboarding wizard, Gateway-restart banner, language toggle, theme toggle, i18n en/zh.
  • Scripts: mock-gateway.mjs, smoke-backend, sync-version, Windows signing chain, macOS .dmg build.
  • See the ClawBox guide and ClawBox wiki for the base surface.

What's new versus ClawBox

  • SignalView.tsx, signal.ts type/service/store trio, routes/signal.ts, internal/signal/*.
  • MatchBox branding (README, banner.png, logo SVG), founder-intake Airtable hookup.
Phase 05 · Delivery model

Agent, not platform

MatchBox ships as an agent. Each VC gets a custom GPT trained on their own process, reachable where they already work — not as a forced migration to a new app.

Surfaces

Slack

Coaching notes + call ratings posted directly into the fund's working channel.

WhatsApp

Same signal, delivered where the partner already texts with founders.

Email

Follow-up + next-call prompts surfaced alongside the VC's existing thread.

Airtable form

Founder intake — the signup link. Rows sync into MatchBox's fund store.

Desktop shell is optional
The Tauri desktop app in this repo is the internal operator surface. Partner funds don't have to adopt it to get value — the agent can run headlessly and reach them through the channels above.

Network effects

  • A curated VC network grows as more funds subscribe.
  • Cross-fund deal sharing for premium members (v2).
  • Crowley Capital seeds network depth.
  • Closes the industry due-diligence gap: fewer fraudulent claims, better fit, less wasted time on poor matches.
Phase 06 · Running from source

Dev

Engine-identical to ClawBox. Same npm ci → npm run dev loop.

Install + run

npm ci npm run dev # frontend (Vite :14200) + backend (Bun :13000) npm run tauri:dev # desktop shell

OpenClaw for the analyzer

npm install -g openclaw@latest openclaw gateway run --dev --auth none --bind loopback --port 18789

Build + verify

npm run build:frontend npm run build:backend cargo check --manifest-path src-tauri/Cargo.toml

Repo hygiene

npm run scan:repo npm run audit:licenses npm run audit:deps npm run smoke:backend # against mock-gateway.mjs

Branch note

Default branch today: claude/founder-fund-matching-urzts. No main at repo root yet — signal + matching work land on topic branches.

Phase 07 · Ops

Next steps

What's on the calendar, and what needs to land before Forbes rollout broadens.

Open commitments

OwnerItem
JakeMeet Jon Forbes Friday — define compensation structure
JordanCreate technical guides and development assets (this guide + wiki are the first two)
TeamFollow-up meeting scheduled for Wednesday or sooner
FocusFinalize the Forbes partnership terms before broader rollout

Strategy artefacts

Follow-ups

  • Clean up the package.json name + repo URL (still inherited from ClawBox fork).
  • Rename default branch to something durable once Forbes terms are locked.
  • Promote Signal from operator-only to Slack delivery once the analyzer output stabilises.
  • Draft the v2 Matching spec after the v1 corpus has enough calls to validate the prompt.
Phase 08 · People

Stakeholders

Who's involved and what they own.

Jake

Business lead. Owns the Forbes relationship and the Friday compensation meeting. Runs founder intake through Airtable.

Jordan

Technical lead. Owns technical guides, development assets, and the Signal / Matching delivery surface.

Jon Forbes (Crowley Capital)

Primary partner. Proven software funding pipeline; wants expansion into ambiguous industries. MatchBox plugs into his existing deal flow.

Crowley Capital

Seed node for network depth. Anchor fund for the case study.

Organized AI

Parent org. Ships MatchBox alongside ClawBox, OpenClaw, and the broader market projects.

matchbox-guide
Organized-AI/MatchBox · private
Tauri v2 · Bun · React 18
matchbox-guide.pages.dev/#home