Brainforge Knowledge

SALES-GTM-CORPUS

3 min read

GTM sales corpus — where “sales calls” and commercial work live

Last updated: 2026-04-29

This is the correct place to look for sales (GTM, pursuits, partners, proposals, SOW work) in the monorepo. It is not about vault/clients/.../transcripts, which is mostly delivery (standups, weeklies, build syncs).

Golden rule

You wantSearch hereDo not use as the default “sales” index
GTM, pursuits, sales calls (as filed), SOWs, partner syncs, decksbrainforge-platform/vault/gtm/sales/** and knowledge/sales/**vault/clients/**/transcripts (thousands of delivery touchpoints)

A blind search of vault/**/transcripts is the wrong index for “how we handle a buyer objection” — you will drown in CTA/ABC/Eden project calls.

1) Canonical tree: vault/gtm/sales (entire subtree)

Path: brainforge-platform/vault/gtm/sales/**/*.md
Size (as scanned): 117 markdown files — this is the full GTM sales corpus in git (SOW framework, lead proposals, partner transcripts, breezy, plan-medicare, enablement, etc.).

Bucket (heuristic)CountWhat it is
sow-framework/**~42Templates & examples — many say “Prepared by: Robert Tseng” as format samples, not a meeting recording
leads/** (proposals, etc.)~24+Account SOWs, proposals, lead notes (Sunstone, YouVersion, …) — often the paper trail of a deal even when no transcripts/ file exists
**/transcripts/**18 (includes breezy/.../README.md) / 17 call bodiesActual exported call notes in this tree
breezy/meeting-notes, agendas, sows~4+Meeting artifacts
Other (e.g. root deck, enablement)restGTM material

Transcript bodies only (sales calls as text in repo), excluding README:

find brainforge-platform/vault/gtm/sales -path '*/transcripts/*.md' ! -name README.md
→ 17 files (listed in BACKFILL-LOG.md §A).

Important: A proposal or SOW under leads/<account>/ often is the durable record of what was said commercially — mine those for pricing, scope, and objection handling when there is no separate transcript.

2) knowledge/sales (pursuit copies + negotiation library)

Path: knowledge/sales/**/*.md
Size: ~18 files (lead spines, SOW drafts, negotiation-precedents, TSIB / All Dunkin transcripts, etc.).

Use this for portable pursuit docs that may not exist under vault/gtm/sales or are duplicated here for Cursor access.

3) “Robert Tseng” in vault/gtm/sales — read carefully

~15 files under vault/gtm/sales mention Robert Tseng in the first ~150k characters. Only part of those are calls:

KindExample paths
Transcripts (calls)partners/snowflake/.../2026-02-16_..._strategy_....md, partners/vixul/.../2026-02-17_..._sync_....md
SOW examples (author line)sow-framework/examples/sow-forecast-urban-stems.md, .../upwork-proposal-ilmor-GA4.md — not a live transcript
Proposals (author)leads/sunstone/PROPOSAL_..., leads/youversion/sow-... — commercial text, often as good as a call for precedents
Decklaralens-ai-sales-automation-deck.md

For negotiation precedents, treat SOWs and proposals in leads/ as first-class sources, not only transcripts/.

4) Glob patterns for AI and skills (sales, not client delivery)

  1. Full GTM sales corpus (recommended default):
    brainforge-platform/vault/gtm/sales/**/*.md

  2. Call notes only (small):
    brainforge-platform/vault/gtm/sales/**/transcripts/**/*.md

  3. Lead + partner commercial text:
    brainforge-platform/vault/gtm/sales/leads/**/*.md
    brainforge-platform/vault/gtm/sales/partners/**/*.md

  4. Knowledge mirror:
    knowledge/sales/**/*.md

  5. Exclude (unless you know you need delivery):
    brainforge-platform/vault/clients/**

  • BACKFILL-LOG.md — Robert+Uttam in transcripts only + wider vault stats (for debugging search noise)
  • FRAMEWORK.md — Getting to Yes alignment

Graph View

Backlinks