# From Conversation to Capability

> Turning discovery-call transcripts into a deployable AI roadmap. A four-stage pipeline that decomposes interviews into atoms, clusters tasks across people, and outputs an auditable hours build-up the CFO can sign. 24 slides, 30 minutes.

*WS·07 · Module WORKSHOPS — Workshops · The CEO AI Playbook by Stephen Forte*

Canonical: https://academy.buildclub.com/workshops/transcript-pipeline

## Thesis

The transcript is the raw ore. The pipeline is the refinery.

## Key Takeaways

- The transcript is the raw ore. The pipeline is the refinery.
- Pick one process and one person. Not 'do AI strategy.' Pick one workflow and one human who runs it. Record one 45-minute conversation. The pipeline starts with a single honest interview, not a roadmap.
- Turning discovery-call transcripts into a deployable AI roadmap. A four-stage pipeline that decomposes interviews into atoms, clusters tasks across people, and outputs an auditable hours build-up the CFO can sign. 24 slides, 30 minutes.

## The Playbook

1. **Ingest** — Fetch · dedupe · classify · resolve speakers · anchor in the system of record. Before any analysis runs, every transcript is attributed to named people in a named meeting.
2. **Analyze** — Seven sequential passes per interview, starting with PASS 0 — Resolve (the entity-resolution gate covered in WS-08 Company Brain). After that, six analytical passes ask one question each — process, friction, knowledge, opportunity, strategic, quantified. Shallow summaries are designed out of the system.
3. **Synthesize** — One overpass across all interviews. Cluster the atoms, corroborate the claims, rank the recoverable-hours catalog. Insight that lives between conversations becomes visible here, not before.
4. **Deploy** — Auditable hours build-up, ranked task-cluster catalog, candidate agents. The output is a roadmap a CFO can sign and an engineering lead can scope.
1. **Fetch** — A nightly cron pulls the latest transcribed calls from the recording service. No human in the loop; no missed days.
2. **Dedupe** — Cross-reference the index; skip already-processed calls and empty stubs from failed recordings. The dataset stays clean by construction.
3. **Classify** — Tag each transcript by meeting type, client, topics, phase. The classification decides which downstream analysis runs — and which prompt version is used.
4. **Resolve** — Map 'Speaker 1 / Speaker 2' to named individuals using attendees, self-intros, and a confidence floor. Anything below the floor is queued for human review, not silently guessed.
5. **Anchor** — Match or create the parent meeting row; build bidirectional relations that make every transcript, atom, and quote navigable from any direction.
1. **Decompose** — Break each job into atomic tasks. Stop thinking in job titles. Start thinking in repeatable units of work. 'AP Analyst' is not the unit; 'reconcile vendor file to GL on Monday morning' is.
2. **Cluster** — Group the same task_type across people, regardless of department. A cluster is where six different humans do the same kind of work. Departments hide clusters; the atom layer reveals them.
3. **Deploy** — Build one agent per high-value cluster. The cluster, not the role, is the unit of automation. An agent that does reconciliation for six people beats six pilots that each touch one person.
1. **Empty stubs** — Failed recordings poison the dataset. Detect zero-duration and null-host transcripts at ingest; skip them. One bad stub propagated downstream contaminates the cluster counts.
2. **Speaker drift** — Anonymous speaker labels destroy provenance. Enforce a confidence floor; route low-confidence calls for human review rather than silently guessing a name. 'Speaker 3' is never an answer.
3. **Prompt creep** — Analysts add fields; outputs balloon; the schema drifts. Version prompts in git with a change log and a kill switch to roll back. Prompts are code — treat them that way.
4. **Silent malformed atoms** — A bad analysis stored as if it were good is the worst possible outcome. Schema-validate atoms as a hard gate. Reject, do not store. Better an empty row than a corrupt one.
5. **Hours without provenance** — A headline number nobody can defend kills the roadmap. Tag every hour stated/derived/inferred and report them separately. Mixed buckets look impressive and fund nothing.
1. **Is the unit of analysis a task, not a department?** — If your roadmap is organized by team, you are still doing org-chart AI. Reorganize around task clusters. Departments are where AI dies.
2. **Is every hour traceable to a person and a quote?** — If the answer is 'the model said so,' reject the number. Demand atom-level provenance — name plus verbatim. No exceptions.
3. **Is judgment_level a column in the plan?** — If you cannot point to which tasks are rote, rules-based, or judgment-heavy, you have not done the work. That column gates every automation downstream.
4. **Is there a follow-up queue for unquantified work?** — A roadmap that hides its gaps is propaganda. A roadmap that names them is a plan. Honesty about what you don't know is the new differentiator.
5. **Is the build order ranked by hours × automatability?** — Without an explicit ranking rule, you will build agents for the loudest cluster, not the biggest one. Loud is not the same as large.

## What to Do Monday

- Pick one process and one person. Not 'do AI strategy.' Pick one workflow and one human who runs it. Record one 45-minute conversation. The pipeline starts with a single honest interview, not a roadmap.
- Capture the Triple in every interview. Frequency × volume × time-per-unit. Train your team on this one rule. It rescues most unquantified work and turns folklore into a fundable hour.
- Separate content, index, and logic. Decide where transcripts live, where metadata lives, where prompts live. Three locations, not one. The boring half of the architecture is the half that keeps it from drifting.
- Define your judgment_level vocabulary. Decide today what counts as rote, rules-based, and judgment-heavy in your business. Write it down. Without this, every automation decision becomes a debate.
- Demand provenance from any vendor. No hours figure without an atom ID, a speaker name, and a verbatim quote. That single rule filters 80% of vendor pitches before they get past the cover slide.

## FAQ

**What is the core idea of From Conversation to Capability?**

The transcript is the raw ore. The pipeline is the refinery.

**What should a CEO do Monday morning after reading From Conversation to Capability?**

Start here: Pick one process and one person. Not 'do AI strategy.' Pick one workflow and one human who runs it. Record one 45-minute conversation. The pipeline starts with a single honest interview, not a roadmap; Capture the Triple in every interview. Frequency × volume × time-per-unit. Train your team on this one rule. It rescues most unquantified work and turns folklore into a fundable hour; Separate content, index, and logic. Decide where transcripts live, where metadata lives, where prompts live. Three locations, not one. The boring half of the architecture is the half that keeps it from drifting.

**What are the steps in From Conversation to Capability?**

1) Ingest; 2) Analyze; 3) Synthesize; 4) Deploy; 1) Fetch.

**Where do the claims in From Conversation to Capability come from?**

The playbook cites Internal workshop source material; WS-08 Company Brain · The Resolution Layer.

## Sources

- [Internal workshop source material](https://buildclub.com)
- [WS-08 Company Brain · The Resolution Layer](https://buildclub.com)

---

Work with BuildClub: https://buildclub.com/engagements