Videos u6jJcIFDLE4
Why We Killed Our Multi-Agent Pipeline — Subbiah Sethuraman and Abhilash Asokan, ZS Associates
Scene timeline
34 shot(s).
keyframes kept every frame deduplicated
What was stored
- cues
- 240
- whisperx 240
- chunks
- 27
- from 240 cues
- keyframes
- 22
- kept of 34 captured
- frames with text
- 22
- 330 lines read
- chapters
- 9
- from the source metadata
- keyframe bytes
- 3.3 MB
- word timings on 240 cues
Provenance
| stage | state | model | started | took |
|---|---|---|---|---|
fetch |
done | — | 2026-08-10 03:33 | 1m 50s |
stt |
done | — | 2026-08-10 03:35 | 19s |
chunk |
done | — | 2026-08-10 03:35 | 0s |
text_embed |
done | — | 2026-08-10 19:46 | 0s |
keyframe |
done | — | 2026-08-10 03:36 | 1m 23s |
ocr |
done | — | 2026-08-10 03:37 | 11s |
frame_embed |
done | — | 2026-08-10 19:46 | 4s |
Frames, and what the machine read
-
- AlEngineer0.96
- World's Fair1.00
-
- AlEngineer0.95
- World's Fair0.99
-
- LAB & PLATINUM SPONSORS0.99
- Amazon AGI Lab0.98
- ANTHROP\C1.00
- Google DeepMind1.00
- MINIMAX0.94
- OpenAl0.92
- Akamai1.00
- arize1.00
- aws1.00
- Braintrust bright data0.98
- B1.00
- Browserbase1.00
- docker1.00
- :neo4j0.93
- ORACLE1.00
- PayPal1.00
- qodo1.00
- reducto1.00
- Sonar1.00
- Makers of0.99
- togetherai1.00
- Unblocked1.00
- WorkOS1.00
- SonarQube1.00
-
- AlEngineer1.00
- World's Fair0.99
-
- AlEngineer0.98
- World'sFair1.00
- Why We Killed Our1.00
- PRESENTED BY1.00
- Multi-Agent Pipeline1.00
- Microsoft1.00
- Lessons from building Al for pharma commercial teams0.99
- Subbiah Sethuraman1.00
- Abhilash Asokan1.00
- ZS Associates0.97
- Al Engineer World's Fair 20261.00
- World'sFair0.88
- Engineering the future of Al0.98
-
- AlEngineer0.98
- World'sFair1.00
- Why We Killed Our1.00
- PRESENTED BY0.97
- Multi-Agent Pipeline1.00
- Microsoft1.00
- Lessons from building Al for pharma commercial teams0.99
- Subbiah Sethuraman1.00
- Abhilash Asokan1.00
- ZS Associates0.97
- Al Engineer World's Fair 20260.99
- Worid'sFair0.97
- TRACK 5· JULY 2,20260.96
- Graphs1.00
-
- AlEngineer0.99
- How an analyst works1.00
- World's Fair0.97
- Four questions, answered in order.0.99
- 21.00
- 31.00
- 41.00
- Signal1.00
- Why1.00
- Action1.00
- Outlook1.00
- Is the change real?0.99
- What's causing it?0.98
- What should we do?1.00
- What happens next?1.00
- World's Fair0.99
- TRACK 5• JULY 2, 20260.96
- Graphs1.00
-
- AlEngineer0.99
- We built an agentic system to mimic that1.00
- World's Fair0.98
- One agent per step, an orchestrator running the team.1.00
- Orchestrator1.00
- runs the team1.00
- SIGNAL1.00
- WHY IT'S HAPPENING0.99
- ACTION + OUTLOOK0.99
- Signal1.00
- Source1.00
- Driver1.00
- Detection1.00
- Localization1.00
- Attribution1.00
- Synthesis1.00
- two agents to answer one question1.00
- Worid's Fair0.93
- TRACK 5· JULY 2, 20260.95
- Graphs1.00
-
- AlEngineer0.96
- The packet it generated1.00
- World'sFair1.00
- SIGNAL1.00
- Brand A's new prescriptions dropped 18% in Territory X over four weeks.1.00
- WHY1.00
- Almost all of the drop is in one insurer, Payer Y. They moved Brand A to a worse coverage tier, so0.99
- patients now pay more — and many walk away at the pharmacy counter.1.00
- ACTION1.00
- Send sales reps to visit more doctors in Territory X to push prescriptions back up.1.00
- OUTLOOK0.96
- The overall outlook for the brand is healthy heading into next quarter.0.99
- World'sFair0.90
- TRACK 5· JULY 2, 20260.95
- Graphs1.00
-
- AlEngineer0.97
- It looks correct. Until you read it closely.1.00
- World'sFair1.00
- THE CAUSE1.00
- Patients can't afford the drug after an insurance change0.99
- THE ACTION1.00
- Reps should visit more doctors — which says nothing about insurance0.99
- THE OUTLOOK1.00
- "Recoverable if rep activity improves"0.97
- And here's the unsettling part1.00
- The action doesn't match the cause.0.99
- Nothing was made up. Every fact is real — but no single agent ever saw the whole0.98
- picture.1.00
- World'sFair0.89
- TRACK 5· JULY 2,20260.95
- Graphs1.00
-
- AlEngineer0.96
- Why it failed0.97
- World'sFair1.00
- Not the model. The way we split the work.0.99
- A language model was deciding the signal1.00
- We asked an LLM whether an 18% move was a real signal or normal noise — a question statistics should0.98
- answer, not a model.0.97
- 21.00
- Context was lost at every handoff0.99
- Each agent passed on its conclusion, not its reasoning. The clue that explained the drop never reached the0.99
- agent writing the advice.1.00
- No shared understanding of the business0.98
- Each agent inferred how pharma metrics relate from raw tables. Nothing told them what actually drives0.99
- prescriptions, or in which direction.1.00
- World'sFair0.85
- TRACK 5· JULY 2, 20260.95
- Graphs1.00
-
- AlEngineer0.97
- Why it failed0.96
- World'sFair0.93
- Not the model. The way we split the work.0.99
- A language model was deciding the signal1.00
- PRESENTED BY1.00
- We asked an LLM whether an 18% move was a real signal or normal noise — a question statistics should0.98
- answer, not a model.0.96
- Microsoft1.00
- Context was lost at every handoff0.99
- Each agent passed on its conclusion, not its reasoning. The clue that explained the drop never reached the0.99
- agent writing the advice.0.99
- No shared understanding of the business0.98
- Each agent inferred how pharma metrics relate from raw tables. Nothing told them what actually drives0.99
- prescriptions, or in which direction.1.00
- Word'sFair0.97
- TRACK 5· JULY 2,20260.95
- Graphs1.00
-
- AlEngineer0.97
- World'sFair1.00
- So we stoppeddesigningthe architecture — and0.99
- started deriving it.0.98
- PRESENTED BY0.96
- Microsoft1.00
- A bare agent.0.98
- Bash and the database1.00
- One real KPI decline.0.96
- Then we watched.0.99
- What the agent touches, we derived from traces. Where the math lives, we decided up front.1.00
- World'sFair0.95
- TRACK 5· JULY 2,20260.95
- Graphs1.00
-
- AlEngineer0.97
- World'sFair1.00
- So we stoppeddesigningthe architecture — and0.99
- started deriving it.0.98
- A bare agent.0.99
- Bash and the database1.00
- One real KPI decline.0.97
- Then we watched.0.99
- What the agent touches, we derived from traces. Where the math lives, we decided up front.1.00
- World'sFair0.92
- TRACK 5· JULY 2,20260.95
- Graphs1.00
-
- FIX 1 · Language model determined the signal0.97
- AlEngineer0.97
- World'sFair1.00
- Statistics finds the signal. The agent explains it.1.00
- STATISTICS1.00
- THEAGENT1.00
- Find the signal.1.00
- Explains it.0.99
- Is an 18% drop real, or just noise? Deterministic tests0.99
- Once the signal is real, the agent investigates, reasons1.00
- and guardrails decide — before the agent starts.1.00
- about cause, and writes the recommendation.1.00
- A language model is a reasoning engine, not a statistics engine.0.99
- TRACK 5· JULY 2,20260.95
- Graphs1.00
-
- FIX 2 · context was lost at every handoff0.98
- AlEngineer0.97
- What replaced the pipeline.1.00
- World'sFair1.00
- Knowledge graph1.00
- Sub-agent1.00
- Signal Detection1.00
- Analyst agent1.00
- Sub-agent1.00
- launched for one isolated task — e.g. verify a driver0.99
- branch: did rep activity really fall?1.00
- One agent owns the whole investigation. Sub-agents investigate. Knowledge Graph provides pharma context0.99
- World'sFair0.97
- TRACK 5· JULY 2,20260.95
- Graphs1.00
-
- FIX 3 · No shared understanding of the business0.98
- AlEngineer0.99
- We gave the agent the business domain — as a graph.0.99
- World'sFair1.00
- WHERE· localize first0.97
- WHY· only after WHERE0.99
- National1.00
- Brand A1.00
- Payer Y0.99
- CONTAINS1.00
- SETS1.00
- Region1.00
- OF1.00
- Coverage tier ↓0.99
- Territory X0.97
- measured af0.96
- NRx↓18%1.00
- Patient cost ↑1.00
- + raises0.98
- Account1.00
- + small0.95
- - suppresses0.97
- Abandoned fills ↑0.97
- HCP1.00
- Rep reach small0.96
- geography entity driver signal0.97
- The graph didn't just add context. It structured the investigation.1.00
- TRACK 5· JULY 2,20260.96
- Graphs1.00
-
- FIX 3 · No shared understanding of the business0.98
- AlEngineer0.99
- We gave the agent the business domain — as a graph.0.99
- World'sFair1.00
- WHERE·localize first0.99
- WHY· only after WHERE0.99
- National1.00
- Brand A1.00
- Payer Y1.00
- CONTAINS1.00
- SETS1.00
- Region1.00
- OF1.00
- PRESENTED BY1.00
- Coverage tier ↓0.99
- Microsoft1.00
- Territory X1.00
- measured at0.96
- NRx↓18%1.00
- Patient cost ↑0.99
- + raises0.97
- Account1.00
- + small0.94
- - suppresses0.98
- Abandoned fills ↑0.99
- HCP1.00
- Rep reach ↓ small0.93
- geography entity driver signal0.98
- The graph didn't just add context. It structured the investigation.1.00
- TRACK 5· JULY 2,20260.97
- Graphs1.00
Transcript
240 cues· 2,567 words· 13,967 chars
- 0:13 Okay, so I'm Subbaya.
- 0:14 I head AI engineering at ZS.
- 0:17 I'm Abhilash.
- 0:17 I'm director of AI engineering at ZS.
- 0:20 So ZS, we are a tech firm.
- 0:21 We work with many of the top companies in the world, including a lot of the top pharmas, actually.
- 0:26 So today's talk, I think we wanted to, as I think already introduced, right?
- 0:29 We wanted to talk from our experience, right?
- 0:31 Building multi-agent pipelines.
- 0:33 What are the mistakes we did, right?
- 0:35 And what did we learn and how did we fix them?
- 0:38 So I'm going to orient it more on pharma, commercial domain, and for people in the room probably who are not aware quickly, pharma has two main functions.
- 0:46 One is R&D, the drug discovery, and the clinical trials part.
- 0:50 And then there's the commercial.
- 0:51 How do you take a drug to a patient, basically?
- 0:55 And within commercial, there are different functions.
- 0:58 Like once you create a drug,
- 1:00 What is the performance of a brand?
- 1:01 How is the drug performing in different markets?
- 1:05 Then there are things like your field force, your reps. How effectively are they engaging with everyone?
- 1:10 There are things around patient journey, how patients are adopting a drug.
- 1:14 I think if there is any therapy switch which is happening.
- 1:16 So as you can think about, there is a lot of analytics which really happens in a commercial domain.
- 1:22 And how do typically analysts work?
- 1:25 So there are four steps, right, what analysts do, right?
- 1:28 So first, there is always something called a signal detection, right?
- 1:31 So signal can be something like, okay, the prescriptions what a doctor is writing, maybe is there a drop in the prescription?
- 1:37 So that's a signal.
- 1:39 So once you got a signal, the second thing what an analyst does is why is this signal really failing?
- 1:44 What is the reason for it?
- 1:45 So is it like there is a competitor drug which has come in?
- 1:48 Because of that, is it reducing?
- 1:50 Is it because maybe a payer coverage for the drug has reduced?
- 1:53 Or maybe the reps on the ground, there's no proper, they're actually not taking the benefits to the doctors.
- 2:01 And once you arrive at the reason, the next step becomes, okay, what is the action do you take?
- 2:05 So if reps, suppose if reps, the coverage is not good in a particular region, do we have to increase that?
- 2:12 And once you do that, what is the outlook?
- 2:15 Is my brand, is my sales performance, is it going to improve?
- 2:18 So these are the four things which happens.
- 2:21 Now, for some of the top farmers, what we have done is how do we, in an agentic way, right?
- 2:26 I think how do we actually mimic this analytics work?
- 2:29 So what we did, we built agents for every step, right?
- 2:33 Signal detection, we said, okay, we'll have an agent for signal detection.
- 2:36 It'll identify the signals for me.
- 2:39 Second, what are the root cause, right, for the signals, right?
- 2:42 So in this case, we have two agents.
- 2:43 One, we call it a source localization.
- 2:45 So for example, if my sales is dropping at a national level,
- 2:48 Is it because it's dropping at say a particular region or is it dropping for a payer?
- 2:53 So we need to understand that.
loading
Chapters
- 0:00 Pharma commercial analytics and the analyst's four steps
- 2:33 V1: an agent for every step
- 3:26 Why the output was incoherent
- 4:32 Why it failed: signals, handoffs, and missing domain
- 5:57 The rebuild: watching Claude Code in an empty directory
- 7:01 Deterministic signal detection before the agent
- 8:05 Consolidating to a single agent
- 9:22 The knowledge graph as a control plane
- 11:04 Every edge a hypothesis, and the result