Brainforge Knowledge

README

2 min read

Negotiation precedents (cross-deal)

Purpose: A searchable library of how Brainforge has handled common buyer questions in the past—pricing posture, scope boundaries, “ballpark” asks, risk/compliance framing—so people in active negotiations can reuse language and logic without starting from zero.

Framework (best-in-class): Precedents should align with principled negotiation (Getting to Yes — separate people from the problem, interests not positions, invent options, objective criteria, BATNA), with optional use of Getting Past No, Difficult Conversations, and (tactically) Never Split the Difference. See FRAMEWORK.md.

Who it’s for: Account leads, practice leads, and anyone drafting replies or SOWs during commercial or scope discussions.

GTM sales vs 5,000+ client “transcript” files: read SALES-GTM-CORPUS.md first — the 117-file vault/gtm/sales tree (proposals + SOWs + 17 call exports) is the right sales index; vault/clients/.../transcripts is not. Short alias: SALES-TRANSCRIPT-LOCATIONS.md. Backfill scan log: BACKFILL-LOG.md.

How to use with AI or skills

  • Path to search: knowledge/sales/negotiation-precedents/ (and entries/ if present).
  • Discovery: Grep or codebase search for topic: / tags: in frontmatter, or keywords in the Question / Response sections.
  • Prompting: “What precedents do we have on [topic]?” or “Read knowledge/sales/negotiation-precedents/ and summarize handling for production MVP pricing questions.”
  • Skills: Point read_file / glob to this folder; encourage one entry per file so chunks stay small.

Relationship to lead folders

  • knowledge/sales/leads/<slug>/ — Account-specific email log, deal timeline, and this lead’s table of objections (tied to one opportunity).
  • This folder — Reusable Q&A and posture that is safe to generalize (anonymize client names in context if needed; use source_lead for internal traceability only).

Conventions

ConventionWhy
One file per topic instance (or one markdown section per year if you merge—prefer one file per precedent for easier AI chunking)Clean retrieval
YAML frontmatter with title, date, tags, topicsFilter without reading full file
Question / How we handled / Principles / CaveatsConsistent skimmable shape; Principles may cite FRAMEWORK.md
source_lead optional (e.g. all-dunkin)Internal only; strip for external paste
Backfill from callsWhen mining transcripts, log the scan in BACKFILL-LOG.md so the next run can extend it

Add a new entry

  1. Copy _template.md into this folder (or a future entries/ subfolder) with a descriptive filename: YYYY-MM-DD-short-slug.md.
  2. Fill frontmatter; keep PII and confidential numbers out unless policy allows.
  3. Open a PR or commit with a normal message.

See _template.md and these examples:

Graph View