diff --git a/README.md b/README.md
index 0d9a35f..5062050 100644
--- a/README.md
+++ b/README.md
@@ -2,12 +2,18 @@
 
 **Turn a discovery call into a complete, working Odoo demo — and the documents to sell it — with an AI agent doing the build.**
 
-A [Claude Code](https://claude.com/claude-code) skill. Point it at a discovery transcript and a reachable Odoo instance; it mines the client's pains, researches what Odoo does natively vs. what needs building, stands up a **live database** (modules + realistic data + the 1–2 "hero" features that win the deal), **tests** that those features actually fire, and generates three sales documents: a **run-of-show**, a **one-pager** for the decision-maker, and a **one-page step-by-step demo script**.
+> Powered by **[Claude Code](https://claude.com/claude-code)** (the agent) + **[Knowcap](https://knowcap.ai)** (the memory). Claude does the research, build, code, and testing; Knowcap — queried over its MCP — feeds the agent the *truth of what the client actually said* in the discovery call. The agent is only as good as its memory: Knowcap is the memory.
 
-Built from a real engagement where this produced a full Odoo 19 Enterprise demo — credit-limit hard-block with manager override, weight-based fleet load-building, EGP data, three sales docs — ready for a CEO meeting, with the founder barely touching the keyboard.
+A Claude Code skill. Point it at a discovery call (in Knowcap) and a reachable Odoo instance; it mines the client's pains, researches what Odoo does natively vs. what needs building, stands up a **live database** (modules + realistic data + the 1–2 "hero" features that win the deal), **tests** that those features actually fire, and generates three sales documents: a **run-of-show**, a **one-pager** for the decision-maker, and a **one-page step-by-step demo script**.
+
+Built from a real engagement where this produced a full Odoo 19 Enterprise demo — credit-limit hard-block with manager override, weight-based fleet load-building, localized data, three sales docs — ready for a CEO meeting, with the founder barely touching the keyboard.
 
 ---
 
+## The stack
+- **Claude Code** — the agent that reads the call, researches native-vs-custom, builds the database, writes + ships the custom code, and tests every hero feature.
+- **Knowcap** — the meeting-intelligence layer. The agent calls the **Knowcap MCP** (`get_source_transcriptions`, `search_memories`) to pull the discovery transcript and the client's pains in their own words. No transcript hunting, no "remind me what they said." → [knowcap.ai](https://knowcap.ai)
+
 ## What you get
 - A **live Odoo demo DB** tailored to the client (any Odoo: Online, self-hosted, or Odoo.sh).
 - **Working hero features**, no-code where possible, custom module only when necessary.
@@ -19,25 +25,26 @@ Built from a real engagement where this produced a full Odoo 19 Enterprise demo
 # clone into your Claude Code skills folder
 git clone https://github.com/Smetools/odoo-demo-architect ~/.claude/skills/odoo-demo-architect
 ```
-Or drop the folder anywhere Claude Code loads skills. Then just ask Claude: *"build an Odoo demo for <client> from this discovery call."*
+Or drop the folder anywhere Claude Code loads skills. Then just ask Claude: *"build an Odoo demo for <client> from our discovery call."*
 
 ## Prerequisites
-- Claude Code.
-- A reachable Odoo instance + an **API key** (Settings → My Profile → Account Security → New API Key).
-  - On **Odoo.sh**: create the project and enter any partner trial code first (web-only), then come back with the DB URL + API key.
-- Optional but recommended: the **Perplexity MCP** (for the native-vs-custom research step). Web search works too.
+- **Claude Code.**
+- **Knowcap** (recommended) with its **MCP** connected — so the agent can pull the discovery transcript + extracted pains directly. → [knowcap.ai](https://knowcap.ai). (No Knowcap? Paste a transcript or notes instead.)
+- A reachable **Odoo instance + API key** (Settings → My Profile → Account Security → New API Key).
+  - On **Odoo.sh**: create the project + enter any partner trial code first (web-only), then come back with the DB URL + API key.
+- Optional: the **Perplexity MCP** for the native-vs-custom research step (web search works too).
 
 ## Quickstart
 1. Put your Odoo creds in env vars (or `scripts/creds.json`):
    `ODOO_URL`, `ODOO_DB`, `ODOO_LOGIN`, `ODOO_KEY`.
 2. Verify the connection: `python scripts/odoo_connect.py` → prints `server_version`.
 3. Copy `demo_config.example.json` → `scripts/demo_config.json`, fill it from the discovery call.
-4. Ask Claude to run the pipeline (see `SKILL.md`), or run `python scripts/build_demo.py` for the data layer, then let the agent build + test the heroes and generate the docs.
+4. Ask Claude to run the pipeline (see `SKILL.md`).
 
 ## How it works (pipeline)
-1. **Mine the discovery** — pains in the client's words; the 1–2 heroes.
+1. **Mine the discovery — via Knowcap.** Pull the meeting transcript over the Knowcap MCP; extract pains in the client's words + the 1–2 heroes.
 2. **Research native-vs-custom** for each hero, for the client's exact Odoo version.
-3. **Connect** over XML-RPC; confirm the version.
+3. **Connect** to Odoo over XML-RPC; confirm the version.
 4. **Install** the scope's modules.
 5. **Load realistic data** (idempotent; currency before invoices; pre-stage so heroes fire live).
 6. **Build heroes** — no-code first, custom module as fallback.
@@ -64,4 +71,5 @@ templates/                      brand.css + the three doc templates
 MIT. Use it, fork it, sell with it.
 
 ## Credit
-Built by [SMEtools](https://www.smetools.io) — Odoo implementation + AI automation. Made with Claude Code.
+Built by **[SMEtools](https://www.smetools.io)** — Odoo implementation + AI automation.
+Runs on **[Claude Code](https://claude.com/claude-code)** + **[Knowcap](https://knowcap.ai)**.
diff --git a/SKILL.md b/SKILL.md
index 1217cec..30ea28f 100644
--- a/SKILL.md
+++ b/SKILL.md
@@ -7,21 +7,23 @@ description: Build a complete, client-tailored Odoo demo from a discovery call.
 
 Turn a discovery call into a polished, working Odoo demo + the documents to sell it — end to end, with minimal human steering. Built from a real engagement that won on first showing.
 
+> **Powered by Claude Code (the agent) + Knowcap (the memory).** The agent pulls the discovery call from **Knowcap** over its MCP — the client's pains in their own words — then researches, builds, writes + ships the custom code, and tests. The agent is only as good as its memory; Knowcap is the memory. → knowcap.ai
+
 ## What it produces
 1. A **live Odoo database** with the client's modules installed, realistic industry data, and the 1–2 "hero" features that map to their pain — actually working, not slideware.
 2. Three **sales documents** (brand-themed, self-contained HTML): a **run-of-show**, a **one-pager** for the decision-maker, and a **1-page step-by-step demo script**.
 3. A **verification log** proving each hero feature fired (e.g. "credit block raised at 56,379 > 50,000; override confirmed").
 
 ## Inputs you need before starting
-- **Discovery material** — a call transcript, recording, or notes describing the client's business + pains. (If using Knowcap, pull the transcript first.)
+- **Discovery material** — pull the meeting transcript from **Knowcap** via its MCP (`get_source_transcriptions`; locate it with `list_sources` / `search_memories`). This is the agent's memory of what the client actually said. (No Knowcap? A transcript or notes works too.)
 - **Agreed scope** — which Odoo areas are in Phase 1 (Sales, Inventory, Accounting, Fleet, etc.).
 - **A reachable Odoo instance + credentials** — `URL`, `DB`, `login`, and an **API key** (Settings → My Profile → Account Security → New API Key). Works on Odoo Online, self-hosted, or Odoo.sh.
   - *Odoo.sh note:* create the project + enter any partner trial code FIRST (web UI only — no API for project creation). Then proceed here once the DB is up and you have an API key.
 
 ## The pipeline (run in order)
 
-### 1. Mine the discovery
-From the transcript/notes, extract and write down:
+### 1. Mine the discovery — via Knowcap
+Pull the meeting transcript from **Knowcap** over the MCP (`get_source_transcriptions`, after locating the source with `list_sources` / `search_memories`). From it, extract and write down:
 - The **business shape** (entities, what they sell, who they sell to). Watch for "it's a group" that is really ONE company in Odoo — confirm chart-of-accounts/P&L/warehouse are shared.
 - The **top 3–5 pains in the client's own words** (quote them). These become the demo beats.
 - The **1–2 hero features** — the differentiators that justify the spend. Everything else is supporting flow.