D

Docusign Agreement Manager

Agreement Manager's AI drives a core feature on a product that would still work without it. Docusign Iris extracts data from agreements, including fields the customer defines, builds AI worksheets for portfolio analysis, and runs agents that analyze agreements, follow the customer's policies and work across connected tools. Without the models, the product is still a repository. It stores signed agreements in one searchable place, controls access, keeps an audit trail, tracks renewals and obligations, and reports.

Extraction makes that faster than manual entry, but the repository is the reason the product exists. Docusign sells it as the manage step of its agreement lifecycle and includes it in IAM plans rather than selling it as an AI product. The capability came from the May 2024 Lexion acquisition, and the product was called Docusign Navigator before the rename.

Agreement Manager grounds its AI in the customer's own agreements, but publishes no accuracy measure. The AI reads executed agreements rather than a body of law. Agent answers are described as traceable to cited sources, so a user can follow an extracted term or an answer back to its agreement. The AI Trust page says diverse datasets and checks are used to correct skewed outputs before release, and that harmful outputs are filtered.

The subprocessor list names Google's Model Armor as an AI security and content moderation service in the IAM stack, which backs part of that claim. What is missing is measurement. The page says AI outputs have been tested for accuracy, but no figure, error rate, test set, evaluation or third party validation is published for extraction, agent answers or worksheets. Third party articles cite a 15 percent precision advantage over general purpose models on extraction.

Docusign does not publish that figure, so it is not relied on. Checks on legal authority do not apply, because the product cites the customer's contracts, not law.

Customer review of AI output is a written commitment from Docusign, and the product gives administrators tools to see what was done. The AI Trust page says the customer has the final say to approve outputs. Agents are described as following the customer's policies and returning answers traceable to cited sources. Access controls and built in activity tracking let an administrator see what happened. What is not published: no line between what an agent may do alone and what needs approval, no confidence threshold, no rule for when an agent stops or escalates, and nothing on what happens when it is wrong.

That gap matters because Docusign is moving toward autonomy. It markets agents that take action rather than only find data, and that handle delegated tasks across the customer's other tools. It launched an agent layer at its 2026 user conference. The final say statement is a general promise of human review. No published limit says what a given agent's output may not be used for.

Named customers come with real figures, but without dates or method. Four customer stories sit on the product page, each naming the organization, giving figures and quoting a named person by title. Catchafire reports about 77 percent less time processing agreements and double the contracting capacity across sales and legal, quoted by its Deputy Director of Revenue Operations. Greater Philadelphia YMCA reports 99 percent of agreement requests coming through one digital intake process and 50 percent less time on first reviews, quoted by its Senior Vice President of Information Technology.

Kindsight reports a sales cycle one week shorter and two to three days saved by IT, quoted by its Director of IT. The Law Offices of Mark T. Hurt, a law firm, is quoted by its Chief of Staff. Two things are missing. No story says when the deployment happened or over what period the figures were measured. No story says how a figure was measured, so a buyer cannot tell what 77 percent less time is compared against. The individual story pages were not opened. Docusign reports 1.9 million customers.

Confidentiality carries contract commitments, but training is permitted by default and privilege goes unmentioned. The Terms treat data uploaded to the services as the customer's Confidential Information. Docusign must use it only for the purpose provided, disclose it only to people who need it and are bound by equal duties, and protect it with at least reasonable care. If disclosure is compelled by law, Docusign must give prompt written notice first unless the law forbids it, and help obtain a protective order where reasonably available.

The subprocessor list names each model provider against the feature it powers: Microsoft Azure OpenAI Service, Azure AI Document Intelligence, Google Gemini, Model Armor and DocuSmart. Encryption in transit and at rest is stated on the AI Trust page. Two gaps remain. Training on customer data is not excluded, and the Terms present consent to it as something to opt out of. Privilege and work product are not addressed, on a repository that holds signed agreements and, in one published customer story, a law firm's matter workflow. Retention and deletion of AI inputs were not established, and the AI Attachment that governs them was not opened.

Where AI output ends and legal advice begins goes unaddressed, for a product that does legal work and is sold to people who are not lawyers. IAM is marketed by department, with pages for Sales, Customer Experience, Human Resources, Procurement and Legal. The published customer stories are led by revenue operations and IT, not counsel. For those buyers the AI extracts governing law, indemnities and liability caps, and flags high risk clauses against a company standard.

Through agents and AI-Assisted Review, it redlines and reviews contracts. Nothing says what the product is and is not, or whether its output is legal advice. Nothing says whether a lawyer should review an agent's redline before it goes to a counterparty, or who in the customer is accountable for it. No competence or supervision statement was found and no jurisdiction limit is named for the AI. Three things that might look relevant answer other questions.

The as is warranty disclaimer is a liability term. The Legality Guide covers whether electronic signatures are valid by jurisdiction, not AI output. The bar on using outputs to train competing systems protects Docusign, not the customer.

A governance framework is in place, without test results or a named owner. Iris has its own AI Innovation Principles and AI Trust pages. The AI Trust page describes four mechanisms. Data is encrypted in transit and at rest. Customers control whether their data is used for AI training, and data used with consent is aggregated and anonymized first. Diverse datasets and checks are used to correct skewed outputs before release, and content filtering screens harmful outputs.

A storage and compute platform supports labeling and training, and the page names the NIST AI framework. Two things are missing. No person, committee or team is named as accountable for model behavior. No test results are published, so the claim that skewed outputs are corrected has no results behind it, including whether output differs across agreement types, languages or regions. The page says broader AI Trust capabilities require contacting sales, so the public set is a summary. The AI Innovation Principles page was not opened.

Docusign publishes policy on most of the ground, but not on retention. Its subprocessor list is detailed. It is dated 11 August 2026, published as a web page and a download, and split by Docusign service so a buyer can read the IAM section alone. Each entry names the entity, country, the feature it powers and a contact address, and the list covers eighteen Docusign group entities and their locations. Updates go to an RSS feed customers can subscribe to, the Data Protection Attachment commits to that feed, and customers may object to a new subprocessor by email on stated grounds.

The Terms promise prompt written notice before compelled disclosure and notice of suspension. The Trust Center has incident reporting, security alert and system status pages, and encryption in transit and at rest is stated for Iris. No retention period or deletion commitment was found for prompts, extracted provisions or agent outputs, and the AI Attachment that would cover them was not opened. Buyers should also note that the Terms reserve usage data, including insights from operating the services, to Docusign for benchmarking, analytics and product development. Any disclosure of it is deidentified and aggregated.

Liability terms appear in full and favor the vendor. The service is provided as is and as available. All implied warranties are excluded, including merchantability, fitness for purpose, accuracy and title, and there is no promise that the service will be error free. Total liability is capped at the fees paid for the service in the twelve months before the first event, or 100 dollars if greater, and at 100 dollars during a free trial.

Direct and consequential damages are both disclaimed. The customer indemnifies Docusign for its use of the service, breach of the Terms and the content of uploaded documents. Nothing runs the other way on the AI. These Terms carry no vendor indemnity for AI output. The only vendor indemnity found covers intellectual property, in supplemental terms for Australian consumers and small businesses. Insurance, service levels and who bears the loss when an extraction is wrong or an agent acts on a misread obligation are not addressed. Enterprise customers sign a separate Master Services Agreement, published in archive form, which was not opened.

Many integrations are documented by Docusign, but not how they work. It runs an App Center for partner apps, advertises more than 1,000 prebuilt integrations, has a public Developer Center, and lists prebuilt MCP connections as an integration category. The product page names integrations and data sharing as a feature, connecting agreement data to existing tools through integrations, APIs and connectors. Another feature extends agreement data across vetted tools and AI ecosystems while enforcing governance and security controls.

Docusign Connect sends webhook events when an envelope changes state. What is missing is depth. The product page names no practice management, document management or matter management system. It does not say which way data flows for any connection or what a firm must configure. The Developer Center and App Center listings were not opened.

Where data is held is answered, but tenancy goes undescribed. The subprocessor list gives regions by supplier and service. Azure hosting for IAM runs in the United States, Australia, Canada, the European Union and Japan. Azure AI Services for IAM runs in the United States, Canada, the European Union, Australia and Japan. Google Cloud Vertex AI for IAM runs in those regions plus Switzerland. The list says accounts provisioned in the EU use EU infrastructure subprocessors, and the trust pages say documents are encrypted and stored in the data center region of the sending account.

A data residency page exists. Binding Corporate Rules approved by EU data protection authorities, as processor and controller, and the EU Standard Contractual Clauses at Modules 2 and 3 give cross border transfers a contractual basis. Nothing describes tenancy. No shared or isolated environment, separation model, or single tenant, private or on premises option is described or refused. Nothing says where AI processing runs relative to where documents are stored, even though AI services are provisioned region by region, apart from hosting.

Docusign holds current independent certifications with stated scope, and buyers can check them without a sales call. Its Trust Center has sections for Legal, Alerts, Compliance, Privacy, Security and System Status, plus a Trust Portal for certifications and assessments. Standards are listed with versions and years. They include ISO 27001:2022, ISO 27017:2015 and ISO 27018:2019, and PCI DSS 4.0, with Docusign on the Visa Global Registry as a service provider.

SOC 1 Type II and SOC 2 Type II audits run annually across production operations, including data centers. Docusign also holds C5 Type II, IRAP at PROTECTED level, DoD IL4 provisional authorization, APEC Privacy Recognition for Processor, Binding Corporate Rules as processor and controller, and Government of Canada Protected B. Scope is stated for each. FedRAMP Agency and GovRAMP authorizations name Docusign Federal covering eSignature and IAM, so this product is inside them.

C5 covers eSignature only and DoD IL4 covers eSignature and CLM, so this product is outside those. Buyers can verify through public registries: the FedRAMP marketplace, the Visa registry, the EU Trusted List via ANSSI, the APEC directory and the CSA STAR registry, where the annual CAIQ is public. Third party risk assessments are done each year under S&P Global KY3P, ProcessUnity and the Shared Assessments SIG.

Models and providers are named, with where they run and a commitment to tell customers when that changes. The disclosure is in the subprocessor list dated 11 August 2026, which is split by Docusign service and has a heading for AI suppliers. Each entry is tied to the feature it powers. Microsoft's Azure OpenAI Service runs AI extractions in Agreement Manager, AI agents and AI-Assisted Review for IAM. Azure AI Document Intelligence runs extractions in Agreement Manager and Agreement Desk agents.

Google's Gemini on Vertex AI runs extractions in Agreement Manager, Model Armor provides AI security and content moderation, and Gemini global endpoints power AI assisted web form creation. DocuSmart Inc., trading as Lexion and wholly owned by Docusign, runs extractions in Agreement Manager and has its own subprocessor page. Each entry states the countries where it is provisioned and a contact address. Updates go to an RSS feed customers can subscribe to, clause 7.2 of the Data Protection Attachment records that, and customers may object to a new subprocessor on stated grounds. Two gaps remain. No model version is given for any provider, and nothing says what any provider may retain.

Docusign publishes pricing for part of its range and withholds the enterprise tiers. The Terms set out the commercial mechanics in detail. Plans are sold in entitlement units and renew automatically unless canceled at least five business days before the term ends. Overage is billed monthly in arrears at the plan's per unit rate. Promotional codes apply to the first term only, and renewals are at the full price. Payments are not refundable, though Docusign will consider in good faith a refund request made in the first thirty days of an annual term.

Fee changes need thirty days' notice, late payment carries interest at 1.5 percent a month, and taxes are extra. The Terms say plans may be published on the website, and self serve plan and pricing pages exist for eSignature and IAM. Agreement Manager is not sold alone. It is included in select IAM plans, and the product page offers Explore IAM Plans next to Contact Sales, so its price depends on which plan carries it.

Which plans include it was not established, and the IAM plans and pricing page was not opened. That is a gap in what was checked, not a finding that Docusign hides its prices, and nothing suggests the page is gated.

Who the product serves is described in detail by Docusign, but not where its limits are. It has a page for each buyer department: Legal, Sales, Customer Experience, Human Resources and Procurement, plus IAM Core and enterprise pages. It has industry pages for financial services, insurance, real estate, government, healthcare and life sciences. Several rest on evidence. FedRAMP and GovRAMP authorizations name IAM for government, 21 CFR Part 11 with an annual independent USDM assessment supports life sciences, and HIPAA support is stated.

Docusign reports 1.9 million customers. For legal buyers it publishes material on agentic contract workflows for in house legal teams, and a law firm is among its named customer stories. The limits are not stated. Nothing says which agreement types or practice areas the extraction handles well or poorly. Some extraction paths are documented elsewhere as English first, but the product pages do not say so. No minimum customer size or excluded segment is named. Legal is one of five buyer groups here, not the only buyer.