Talk by Hiral Shah (Docusign) and Sean Sodha (NVIDIA) on agreement data as an unqueryable database. Covers the scale of locked-up negotiated value (~$2 trillion in agreements organizations never revisit), Docusign's processing scale (~1 million agreements/day), and why tables—pricing tiers, rate cards, SKUs, service levels—break generic document extraction. They describe a purpose-built vision language model (~900M parameters) designed as an extractor rather than a generator, replacing stacks of layout/table models with a single pass producing reading order, semantic structure, and preserved tables, with the lesson that the small specialized model ran table extraction roughly 20x faster than general alternatives. Includes a demo converting an order form into structured data and a Q&A on whether OCR is going away. # Video Identity Observation — Hiral Shah (Docusign) & Sean Sodha (NVIDIA) ## Session Format & Setting - **Conference-style breakout session** with a live audience: speakers ask for raised hands ("raise your hands how many of you have used Docusign"), take audience Q&A at the end, and close with "[applause]." - **Two-speaker partner presentation**: a Docusign senior director of products (Hiral Shah) paired with an NVIDIA product manager (Sean Sodha), each self-introducing at the start. - Includes a **live product demo** mid-session (Agreement Manager UI walkthrough) and a stated agenda: stakes → technical architecture → model evaluation learnings. ## Explicit Self-Descriptions (Creator Claims) - **Hiral**: "I'm a senior director of products at Docusign" — presenting Docusign's Intelligent Agreement Management (IAM) platform. - **Sean**: "I'm a product manager at NVIDIA" — presenting the **NeMo/Neotron Retriever initiative**: "building embedding models, reranking models, and document extraction models." - **NVIDIA team claim**: "our team is responsible for leading a lot of the leaderboards in the retrieval space… we've had a lot of leaderboard winnings in the last year or so." - **Docusign scale claims**: "we have 1.9 million customers who are paying us and a billion users… we process a million agreements a day," citing a study claiming "$2 trillion captured in this agreement negotiated value." > Note: These are creator-stated claims about their organizations, not independently verifiable from the material itself. ## Intended Audience - **Enterprise technical and product audiences** — evidenced by: - References to "paabytes scale data" enterprises deal with. - Mention of "claude… especially at your companies' organization" as a shared context. - Technical depth: FP16/FP8/NVFP4 quantization, multi-token generation, encoder–decoder VLM architecture, batch sizes and concurrency tradeoffs. - Relatability to practitioner pain points: "OCR is always a thorn in the whole process" (audience question), legal/procurement/sales team workflows. ## Claimed Scope of Content - **Problem domain**: large-scale unstructured **agreement data extraction** — pricing tables, SKUs, SLAs, rate cards — where "traditional document extraction tools or a generic VLM completely fail." - **Solution presented**: Docusign IAM + NVIDIA's NeMo/Neotron Parse model (described as an "850–900 million parameter" "tiny small model… It's not a generator. It's more of an extractor"), claimed to be "20x faster" than other open-source models on tables-per-second. - **Forward-looking claims**: partnership deepening, NeMo Retriever effort, NVIDIA agent toolkit, "production scale agents," FP8/NVFP4 paths — stated as future plans, not demonstrated. ## Observable Presentation Patterns (Demonstrated, Not Claimed) - **Vendor-collaboration framing**: content is structured around a joint Docusign–NVIDIA solution, with each speaker covering their company's component. - **Benchmark-driven argumentation**: cites "RD table bench" comparisons and leaderboard placements to justify model quality. - **Demo-driven proof**: shows upload → AI processing → structured metadata extraction → CSV export → API availability in a live walkthrough, framed as evidence the product works "in seconds." - **Audience-engagement style**: rhetorical hand-raising, "I'm sure you all are using a lot of right claude," offers to "chat offline" on architecture details, and a reference to a published blog ("we have a blog out there how we are really solving this at scale"). ## Notable Distinctions for Synthesis - **Claims vs. demonstration**: The 20x speed figure, leaderboard wins, and scale metrics are speaker assertions; only the demo of single-document extraction is directly shown. - **No channel-level self-description** appears — this is a one-off conference talk, not a video with explicit channel branding, subscriber appeals, or series identity. # Delivery Observation: Hiral Shah (Docusign) & Sean Sodha (NVIDIA) ## Format & Structure - **Two-speaker tag-team presentation** with explicit handoffs: - > "And to share more about how we're leveraging the Neotron, I'm going to hand it to Sean." - > "So I'll let Sean talk through those." - Hiral anchors the **problem framing and demo**; Sean handles the **model/technical details**. - A stated agenda up front: > "We'll start with just the stakes... then we'll dive deep into the technical architecture... and then finally, we'll cover what we have learned." ## Audience-Interaction Habits - Both speakers use **raise-your-hand prompts** as an engagement device: - > "raise your hands how many of you have used docuign" - > "So for those who here knows about Neotron, you raise your hand real quick. Awesome." - Ends with live Q&A: > "We have time for a couple questions." ## Recurring Verbal Patterns ### Hiral - **Filler-heavy, rapid delivery**: frequent "you know," "kind of," "like": - > "which is kind of what we're going to show" - > "So that's kind of why docysine built AM" - > "it's like we have a whole repository" - **Signposting phrases**: "So real quick" style transitions and repeated "So when you think about..." framing: - > "So when you think about the challenges involved right..." - > "when we think about what have we learned" - **Scale through numbers**: cites concrete figures repeatedly — "1.9 million customers," "a billion users," "a million agreements a day," "$2 trillion," "20x faster." - Relatable callback to the audience: > "I'm sure you all are using a lot of right claude and all especially at your company's organization." ### Sean - Also uses **"real quick"** as a recurring pivot: - > "Uh so real quick on uh the Neotron retriever initiative." - > "So real quick here we sort of our first initiative..." - > "Uh so real quick as well too..." - **Credential-by-leaderboard habit**: > "our team is responsible for uh leading a lot of the leaderboards in the retrieval space. So Vidori V1, V2, V3, MTB, MMT." - Uses the phrase **"whatever it may be"** multiple times: - > "merged rows whatever it may be" - > "top five quer documents whatever it may be" - > "page element extraction, whatever it may be" ## Teaching Habits - **Concrete-before-abstract**: abstract claims are grounded in named entities and specifics (Claude token contracts, Coupa, CSV downloads, YOLOX comparisons, FP16/FP8/NVFP4). - **Live product demo** as the centerpiece, narrated in second person: > "Let me show you how easy it is to turn any agreement into structured usable data... As you can see..." - **Recap habit in Q&A**: Hiral restates audience questions for the room: > "just to recap for everybody if you didn't hear it was the question is right like OCR is always a thorn..." - **"Lessons learned" framing** to close the teaching arc: purpose-built models, model efficiency, faster extraction — each with supporting evidence. ## Uncertainty Notes - Hiral's transcript shows heavy disfluency and possible transcription noise ("docysine," "neotron" variants), so exact-quote reliability at word level is moderate. - Audience questions are largely inaudible in the transcript; Q&A responses are observable but the questions themselves are not. - Patterns like "kind of" / "you know" are clearly repeated; finer-grained habits (e.g., pace shifts) cannot be verified from transcript alone. # Observation Record: "Your Agreements Are a Database You Can't Query" — Hiral Shah (Docusign) & Sean Sodha (NVIDIA) ## Speakers - **Hiral Shah** — Senior Director of Products, Docusign (introduced self; handles the Docusign-side framing, demo, and learnings) - **Sean Sodha** — Product Manager, NVIDIA (introduced self; handles the Neotron model discussion) > Attribution note: transcript alternates between speakers with `>` markers; first-person statements are attributed to the named speaker only where directly supported by the introduction flow. Where a marker cannot be tied to a specific name, statements are left unattributed by name. --- ## Claim 1: Agreement data is a massive, trapped enterprise resource **Speaker:** Hiral Shah - Agreements are central to every B2B relationship, and critical data (pricing tables, etc.) is captured in them — but in **unstructured formats** (PDFs, PNGs). - Scale claims: - **1.9 million paying customers**, **a billion users**. - Docusign processes **"a million agreements a day."** - Cites a **Deloitte study** (rendered in transcript as "Deote"): **$2 trillion** in negotiated value captured in agreements that "no one capitalizes on" because of human reading, disconnected systems, and manual workflows. ## Claim 2: Traditional extraction tools fail on tables in contracts **Speaker:** Hiral Shah - Enterprise contracts contain **"vital terms"** — pricing tiers, SKUs, SLAs, rate cards — almost always in **table format**. - Traditional document extraction tools and **generic VLMs "completely fail here"** because they read text line by line, which breaks table concepts; **merged cells** and missing boundaries compound the problem. - Consequence: major operational overhead for legal, procurement, and sales teams who "spend hours and hours" locating basic information. ## Claim 3: Neotron Parse is a small, purpose-built, single-shot extraction model **Speaker:** Sean Sodha - **Neotron** is an open-source model initiative: publishes model weights, datasets, techniques (quantization, distillation, pruning), and blueprints. - **Neotron Retriever** covers embedding models, reranking models, and document extraction models, targeting a two-stage pipeline: 1. Find the **right document** given an agent's query (petabyte-scale enterprises). 2. Find the **right information within the document** — the stage addressed in the Docusign partnership. - **Neotron Parse** characteristics as stated: - ~**850–900 million parameter** VLM — "very small tiny" compared to multi-billion-parameter VLMs, which he characterizes as heavy and high-latency. - **Single-shot**: document in → semantic formatting, layouts, text, reading order, preserved table structure out — replacing chains of smaller models (e.g., YOLO-X style) for page element/table detection. - "Not a generator. It's more of an **extractor**." - Served via **NVIDIA NIM** or "the LLM" (as transcribed). - Benchmark claim: compared against popular open-source models on table extraction (transcript renders "RD table bench"), claiming competitive/world-class results on the accuracy-vs-performance Pareto curve. ## Claim 4: Demo — Agreement Manager turns agreements into structured data in seconds **Speaker:** Speaker (Docusign-side; not explicitly named during demo narration) - **Agreement Manager** is described as a central repository of every signed agreement; supports upload, AI processing via a jobs engine, automatic metadata extraction (key terms, commercial details), highlighted jump-to-section navigation, and CSV download/API access of extracted table data. - Explicitly credits **"NVIDIA's Neotron model"** for breaking down dense pricing tables into order details. ## Claim 5: Learnings — purpose-built, small models win at enterprise scale **Speaker:** Hiral Shah - **Purpose-built models** for each job accelerated time-to-market. - **Model efficiency**: smaller context meant lower latency and lower cost at their scale. - **Speed claim**: Neotron was **"20x faster"** than other open-source models at tables extracted per second. - Docusign maintains its own **proprietary agreement data model** and a robust search layer on top; the pipeline uses a **hybrid approach** — Neotron handles layout/table extraction while OCR is still used for other fields and full text. ## Claim 6: Roadmap — from extraction to retrieval and agents **Speaker:** Sean Sodha - Partnership deepening over "the next few months": from page-level extraction to **finding the right page** (Neotron Retriever), then **NVIDIA agent toolkit**, then production-scale agents. --- ## Q&A Positions ### On whether OCR should be dropped in favor of agentic processing from the start - **Hiral Shah**: It depends on the use case. Reactive, single-document queries can work dynamically at small scale, **but** at the scale of thousands of queries, **pre-processing is required** to manage latency. Also, downstream automated workflows (e.g., procurement pushing pricing tables into **Coupa**, rendered "Koopa") can't be done document-by-document. - **Sean Sodha**: Agrees it's use-case dependent — petabyte-scale queriable corpora justify **heavy upfront compute (OCR)**; single-contract Q&A is a low-latency use case where throughput, batch sizes, and concurrency trade-offs differ. Where you spend compute "in that cycle will be changing between the different use cases." ### On quantization and performance - **Sean Sodha**: Model is currently **FP16**; paths to **FP8 and NVFP4** "in the next few months." Pushing toward **Blackwell**; sees potential in **multi-token generation** and encoder-decoder optimizations (currently generates one token at a time). Priority framing: "right now we're focusing on the accuracy side… then push out that Pareto curve on the performance." ### On serving/production use - **Docusign speaker**: They do use the discussed model plus "some of the older ones" — described as an ongoing journey of tweaking as customer load grows. A follow-up question about retrieval appears to be redirected: answers come from the **extracted and stored agreement data**; detailed architecture discussion deferred to offline conversation and a **published blog** on solving this at scale. --- ## Qualifications and Tensions Preserved - **OCR is not abandoned**: despite the AI-first framing, Docusign explicitly retains OCR in a two-route hybrid pipeline — a qualification to any "agentic from the get-go" implication. - **Neotron Parse is extraction-only**, not generative — a stated limit on what the model does. - **Benchmark name uncertain**: "RD table bench" is the transcript rendering; no verification available in-source. - **Performance claims (20x faster, benchmark leadership)** are speaker assertions from the presentation; no independent verification within the transcript. - **Unresolved items**: FP8/NVFP4 support and retrieval/agent integration are stated as **future** work, not current capability. # Speaker & Provenance Observation Record ## Video Identification - **Title:** Your Agreements Are a Database You Can't Query — Hiral Shah, Docusign & Sean Sodha, NVIDIA - **Video ID:** `01a15ca7-5e7e-7263-b415-6ad8ac1542b0` ## Speakers & Roles | Speaker | Role (self-identified) | Organization | |---|---|---| | **Hiral Shah** (transcribed as "Haral") | **Co-presenter**, Senior Director of Products | Docusign (transcribed as "DocYsine"/"docysine"/"docuign") | | **Sean Sodha** | **Co-presenter**, Product Manager | NVIDIA | ### Additional voice activity - **Audience Q&A participants** — unnamed; questions asked during the closing Q&A (on OCR/agentic processing, quantization/precision, and architecture). At least one question is only paraphrased by Hiral ("the question is right like OCR is always a thorn..."). ## Segment Attribution - **Opening & problem framing, Docusign scale claims, demo narration, lessons learned:** Hiral Shah - **NVIDIA Neotron Retriever / Neotron Parse model, benchmarks, quantization discussion, "what's next":** Sean Sodha - **Product demo (Agreement Manager walkthrough):** Presented within the session; speaker attribution between the two presenters is not explicitly marked in the transcript around the demo handoff. - **Q&A:** Both speakers respond; attribution of individual answers is explicit in most cases via alternating turns. ## Referenced Sources & Claims (Provenance) - **Third-party study claim:** Hiral cites a study done "in the past we've worked with Deote on a study" (name garbled in transcript) claiming **$2 trillion** of negotiated value in agreements goes uncaptured. Provenance: study partner named only as garbled "Deote"; no citation details provided. - **Docusign internal figures:** 1.9 million paying customers, 1 billion users, ~1 million agreements processed per day — attributed to Hiral (speaker claim; no cited source). - **Benchmark reference:** Sean references "RD table bench" (likely garbled table-extraction benchmark) comparing Neotron Parse against open-source models; chart shown, no external citation given. - **Named technologies/products discussed:** NVIDIA Neotron (Retriever, Parse), NVIDIA NIM, NVIDIA agent toolkit, Blackwell/NVFP4 quantization, Docusign IAM / Agreement Manager, Claude (mentioned by Hiral as an example in an audience-relatable aside), YOLOX, Vidori V1/V2/V3, MTB/MMT leaderboards (as stated by Sean), "Koopa" (garbled; likely Coupa, per Hiral's procurement example), FP16/FP8/NVFP4 precisions. - **Blog reference:** Hiral states "we have a blog out there how are we really solving this at scale" — no URL or title given. ## Promotional Segments (Flagged) - **Docusign Agreement Manager demo** — an explicit in-session product demonstration of Docusign's IAM platform, framed as "how easy it is to turn any agreement into structured usable data." - **NVIDIA Neotron model promotion** — presentation of Neotron Parse performance claims (e.g., "20x faster" table extraction vs. other open-source models, per Hiral) and leaderboard leadership claims. - **Partnership promotion** — the session as a whole promotes the Docusign–NVIDIA collaboration and upcoming roadmap ("we're going to continue to deepen that partnership"). ## Comment Availability - No metadata supplied; **comment availability is unknown/unrecorded**. ## Uncertainty Notes - Speaker names and company/product names appear garbled in the transcript (e.g., "Haral"/Hiral, "DocYsine"/Docusign, "Deote", "Koopa", "RD table bench", "Neimatron"). Title metadata confirms canonical spellings for speakers and companies only. - No timestamps are present in the supplied transcript; segment ordering is inferred from narrative flow. Uh, welcome everyone to our session. Um, I'm Haral. I'm a senior director of products um at DocYsine and I'm joined by Sean. \>\> Hello everyone. I'm a product manager at NVIDIA. So today Sean and I are going to talk about a massive problem that every enterprise faces which is agreement data largecale agreement data. Agreements are a big part of any relationship any B-2B organization kind of goes through day in day out and a lot of that data is captured inside that agreements and it's very critical whether it's pricing tables a lot of it and it's all in a lot of different unstructured format and that's kind of what we're going to show is how docysine partner with Nvidia are fixing that on making that data available readable usable for a lot of our kind of organizations. So here is kind of just a quick map of our talk today. We'll start with just the stakes. Why does this matter? Why the scale is so large? And then we'll dive deep into the technical architecture of how we are approaching it, how we have tackled this thing, especially this document processing at at scale. And then finally, we'll cover what we have learned from our evaluation of all of the different models we've tried for different purposes. and share our learnings with you. So why like you know just to understand why this is a big problem when you think about docysine raise your hands how many of you have used docuign anyone who's employed probably the HR docs right so it's a massive scale everyone uses docy for us it's a massive engineering problem as well because just look at the scale we have 1.9 million customers who are paying us and a billion users what does that imply we process us a million agreements a day that needs to now structurize make it readable make it querable usable and you know in the past we've worked with Deote on a study and it says that there's $2 trillion captured in this agreement negotiated value that no one capitalizes no one goes back and gets that um data back right and why it's because they have to do a lot of human reading human reviews there's disconnected systems lot of manual workflow flows that are there. So that's kind of why docysine built AM an intelligent agreement management platform that takes the entire like applying in an AI first way the entire agreement life cycle whether you are creating agreements genai helps a lot with that whether you're negotiating to understanding and redlinining all the way to after signing storing and making a lot of insights from this data. So when you think about the challenges involved right in an agreement there is the unstructured data it could be a PDF it could be a PNG and what are people wanting to do is simple questions they can't get that that is the data that is trapped inside one agreement but also the whole corpus of millions of agreement 10 years 20 years of business has kind of put into that. So for agreements aren't flat they're also hierarchical in nature they are like you know one agreement governs the other the other kind of does something else so you always are needing lot of things to answer this question simple thing I'm sure you all are using a lot of right claude and all especially at your company's organization simple thing what did we contract for the total tokens right with claude no one knows that's captured inside this agreement in different forms and fashion so you need to be extracting this data to find things but also insights and push it downstream where you're tracking doing more things and when you analyze an enterprise contract a big set of things are captured what I call vital terms like pricing tiers the skues the information SLAs's rate cards they're all in table format now traditional document extraction tools or a generic VM BLM completely fail here like you know we've tried we've definitely done this because they're reading text line by line which breaks a lot of that concept within the table. A merge sells some things are not boundaried. So this makes a massive operational overhead for the downstream legal teams, procurement team, sales teams to get that queries and get that answers done and they spend hours and hours digging through this um to even just locate a basic thing. And that's kind of where we partnered with Nvidia and leveraged a purpose-built model like you know tool which is literally like you know making our architecture for table extraction take us to make and solve these complex use cases. We're trying with this we're making things scalable. We can understand it with the layout but also deliver really accurate results. And to share more about how we're leveraging the Neotron, I'm going to hand it to Sean. All right. Hello everyone. Uh so real quick on uh the Neotron retriever initiative. So for those who here knows about Neotron, you raise your hand real quick. Awesome. Uh so Neimatron is all about building worldclass open-source models and publishing the data sets, the techniques, uh the quantization approaches, distillation approaches, pruning approaches, every technique possible, blueprints to go with that, you name it. Um throughout the Neimatron portfolio, we have specifically Neatron Retriever, which is building embedding models, reranking models, and document extraction models. Um so real quick here we sort of our first initiative is if you're a large scale enterprise that deals with pabytes scale data our first initiative is how do we make sure that you find the right document given a certain query your agent sends you know set of queries to the corpus afterwards. Once you find those top five quer documents whatever it may be then we say okay you found the right document now how do you then find the right information within the document and this is where the work with the docysteine team has gotten really great where we've uh worked with them to build the neatron parse model to focus specifically on table extraction which is a really complicated technique um if you think about it the number of permutations of tables are quite vast when you think about nested tables merged cells merged columns merged rows whatever it may be and that can get really really complex and really hairy of a Uh so real quick as I mentioned before right our team is responsible for uh leading a lot of the leaderboards in the retrieval space. So Vidori V1, V2, V3, MTB, MMT. Um so our team knows how to build world-class retrieval models given a lot of leadership uh given a lot of leaderboard winnings that we've had in the last year or so and then of course as I mentioned before we open source everything right so we share the open source model weights the techniques and then we release with those blueprints and skills that agents can use then afterwards um so to touch a little bit on the actual model that we are working with with docuign was the neatron parse model so when you think VLM you generally think a multi-billion parameter model it's very heavy It's high latency. Um, this is a very small tiny C radio VLM. It's about 850 900 million parameter model. Uh, designed to kind of be that all-in-one package sort of model where you deploy it and instead of having small, let's say, YOLO X models that do table extraction or page element extraction, whatever it may be. This is a singleshot model that you can feed a document in and out comes the semantic formatting layouts the text uh the reading order uh the the preserved structure of the table etc. Um this can be served via the NVIDIA NIM or via the LLM as well too. Um and so it's a tiny small model that you can use. It's not a generator. It's more of an extractor at the end of the day. Uh so real quick as well too um we always want to make sure that we're building towards benchmarks that matter most to the enterprise space. So we want to make sure that both on the paro curve of accuracy versus performance, we're make sure that we're going to be releasing a world-class models to the ecosystem too. So you'll see here generally is just a very standard benchmark of table extraction. I believe this one was RD table bench and we compare some popular open source models here and then we compare how our neatron parse model does compared to that industry and we continue to kind of strive to improve this as time goes on. \>\> So that I think we believe we have a demo as well. Yeah, \>\> just press one. Yeah. Okay, there we go. \>\> Let me show you how easy it is to turn any agreement into structured usable data with agreement manager, which is a central repository of every agreement an organization has ever signed. Let's look at this. So when we look at the agreement manager view here, you know, we have an ability to see the entire list of agreements, but also go and upload a new agreement. So I'm uploading a new order form into agreement manager. As you can see, I can select from my computer, import from other places. The moment I select the agreement, it starts uploading and starts processing with AI. And just like that, you can see that the jobs engine has processed it. Let's take a closer look at this agreement. So when you go into the action, you can go and browse the file. Within seconds, agreement manager has extracted a rich set of metadata. Everything from key terms to commercial details are automatically structured, highlighted, and immediately you can jump to that section where the details are found. Builtin goes deeper. This is where the Nvidia's model comes in that it's extracted all the structured pricing data around this agreement. It goes in breaks down these complex t tables into order details. And as you can see, we can break it down. We can download all of this data. This is powered by the advanced parsing leveraging Nvidia's Neotron model, turning every even dense tables into something that is instantly usable. And of course, you can take this data with you. You can see when we've downloaded into CSV how we've structured all of it for your finance team, procurement team, even further analysis. All of it is also available through API. And that's how agreement manager has transformed agreements into actionable insights in seconds leveraging Nvidia. So I think you know what you saw there from um a demo perspective we've tried to shortened it. It's like we have a whole repository what you see a list we get customers which has thousand agreements to all the way millions of agreements within but the big piece is how do we understand and get that data that makes it very valuable to an end business user right a legal person a procurement person a salesperson who's doing a lot of the deals or even a leader right like a business unit the CTO goes and asks what did we do this is how we have making each of the things a lot more structured so we have our own proprietary agreement data model which we are structurizing each agreement but also at a whole organization level and leveraging a lot of the NVIDIA things we've been able to do a really good job especially with all of those tables like pricing SLAs's and then make that available and then we also have a like robust kind of search that is um on top of it so when we think about what have we learned right when you think from a neotron plus docyign we one of the biggest things for us we definitely have done lot of different models mod for different purposes. So a purpose-built model for the job you're trying to do is a big big part of how we've been thinking about and that's kind of where we've been able to accelerate bring things to market much faster. The second big piece around like the model efficiency. So for you know as Sean was talking about the number of parameters yes context and stuff matters in the you know in a different environment for different things. For us the lower kind of context basically also meant lower latency lower cost to deliver the scale that we are talking about last around the faster extraction. So um we we ran this against a lot of the other open source models when we think about how many tables can it extract per second Neotron was 20x faster which helps us when we're talking about the millions and billions of scale that we're kind of serving for all of our customers. So a lot of it is like having that smaller purpose-built things is the way for an enterprise as an organization to go and leverage and then serve that from an enduser perspective. Um and then what's next? So I'll let Sean talk through those. \>\> Yeah. So working with the docuign team uh has been awesome so far. Uh and we're going to continue to deepen that partnership as well over the next few months. So uh with them we started with the how do I extract as much possible information from a page and now we'll scale to how do I now find that page to begin with. Um so we'll start a little bit with the neatron retriever uh effort and then of course we'll talk a little bit about the NVIDIA agent toolkit with them over the next few months um and then actually start scaling into into more production scale agents then. \>\> Perfect. I think that's what we had. We have time for a couple questions. I went in the room. Okay. Someone there. So just to recap for everybody if you didn't hear it was the question is right like OCR is always a thorn in the whole process so are we thinking about letting the go of that and starting from agentic from the get-go I can talk from my perspective but so I think for us right like there are different use cases at different points in time many times if you are reactive you have a question and you're coming some of that can can work dynamically at a smaller scale. The question is the latency when I am quering at that scale of thousands I do need to have pre-processed have identified. So that's one. I think the second big part of the use case for us a lot of times businesses want to use this data to do a lot of downstream work. So an example is a procurement team. This is my pricing table. I want to put it into Koopa to make sure when I'm paying that works at that time there like you know the agent is kind of helping but I can't do that on a one document by document. That said, there is ways that we are compressing. That's kind of why Neotron worked for us is like how do you do it from a layout understanding just for that purpose but I would like let you add. \>\> Yeah, I think it depends on the use case a little bit. Um I think for this specific instance, right, you have pabytes of documents that you want to be queriable at some point, right? So you are heavy on the compute at the upfront side with all the OCR so you don't have to worry about it later on, right? I think there's some instances where people may upload a contract to begin with for Q&A and that's a very high that's a very low latency use case, right? So you have a high throughput versus low latency use case and in that scenario your different batch sizes, your concurrencies, your different techniques on how you process the document will be different and where you spend that compute in that cycle will be changing between the different use cases. \>\> Okay, one more there. We we do a lot of like more of what I call hybrid approach and a purpose-built for like the needs and the use cases. So from a table piece it does kind of you know do the whole layout along with extracting we still do OCR from a lot of other fields and metadata and a closet like all of the text kind of thing. So that I think we had a architecture where we have our pipeline going through two different routes for that. Um as a follow we have a blog out there how are we really solving this at scale across and if you look at that there's a lot of different peacemail modules and stuff together. \>\> Yeah one moreization \>\> so we this model is currently on FP16 but there are paths towards going on to FP8 and VFP4 in the next few months as well too. What about center? Are you using the 16 or \>\> we do use that and then we're also kind of using some of the older ones and that's the journey as a partnership is to kind of go tweak as you get more of the customers. \>\> Yeah. So for this there are many techniques on how to improve the performance side right so quantization right so we're trying to move everyone to blackwell right so that's why NVFP4 is the big thing now um as well as multi-token generation for this it's a VLM architecture right so your encoder decoder techniques can definitely be further optimized so not right now this model just generates one token at a time you can do multi token generation of course too so there's plenty of performance things right now we're focusing on the accuracy side like are we adding value to the system and then from there we'll then push out that paro curve on the performance Are you guys using \>\> I believe they just deploy via directly recall when you do that. \>\> Oh, this is just an extraction. This is now a retrieval. \>\> Yeah. \>\> Yeah. Yeah, you're asking question. \>\> It's coming from that agreement data that we've kind of extracted and stored. \>\> So yeah, maybe I can chat with you offline and how like we our architecture kind of works fully as well. No, we're almost coming up on time there. Um, but I think that's kind of all we have. I'm happy to hang around uh in the back with more questions. Um, and good luck with a lot of your uh challenges with AI. So, thank you. \>\> Thank you. \>\> \[applause\]