AI Sales Companion

6 Interactive Sessions

Short, interactive sessions — watch it work, steer it, then build it yourself. Go deeper anytime with the full code walkthrough.

1. 1

   The Scattered Truth — five systems, one briefing

   Everything you need before the Acme call already exists — the open deal, the objection, the ticket, the competitor — but it's scattered across five systems in five formats. The companion's first job is to pull it all into ONE searchable store where every fact still remembers where it came from.

2. 2

   Meaning, Not Keywords — encode so search understands

   You search “pricing pushback”; the transcript says “worried the ROI won't justify the spend.” Zero words in common, same meaning. Keyword search misses it entirely. To find it, you chunk each Document and embed the text into vectors where meaning is a location — then a query for the concept lands right next to the objection.

3. 3

   Find the Right Passage — the five chunks that matter

   “What should I know before Acme?” could pull a hundred vaguely-related chunks and bury you. Retrieval's job is to surface the FIVE that matter — the open deal, the objection, the open ticket, the Clari threat — and skip the fifty that don't. Pure meaning-search isn't enough; hybrid search + RRF fusion + reranking on recency and source authority is what makes the shortlist right.

4. 4

   An Answer You Can Trust — ground it or don't say it

   The companion says “Acme's budget is $200K.” Real from the CRM, or made up? A rep who repeats a hallucinated number to the customer has done real damage — and there's no unsend on a sales call. The AI gateway is the line that makes the answer safe: every claim must be grounded in a retrieved, cited source, cross-account data can't leak into Acme's briefing, and PII is handled. Ground it and cite it, or refuse.

5. 5

   The Companion — a briefing you can click into

   The rep types “What should I know before Acme?” and gets a streamed briefing: the open $450K deal, the ROI objection to expect, the Clari threat — each claim linked to the exact source it came from. The app is where grounding stops being a backend idea and becomes a thing the rep can SEE: click a citation, land on the transcript or the CRM record. Citations are the interface of trust.

6. 6

   Ship It Where They Work — Slack, MCP, and eyes on it

   A companion in a browser tab is a companion reps forget. They live in Slack — so ship it there: “@companion prep me for Acme” in the channel they're already in. Expose it over MCP so other AI tools can call it too. Then watch it in production: is it fast, is it used, and — the one that guards the whole course — is it still citing its sources? Deploy is where the companion meets real reps and real calls.

What you walk away with