TL;DR: start with your real usage model. Count who sends, how they send, which workflows are automated, whether Web Forms or APIs trigger sends, how many agreements need to be stored in Agreement Manager, and which add-ons matter. Then match that to the order form.
The short version
Public Docusign IAM plans are priced per user, but that does not mean “one user = unlimited everything”. The plan also controls how many automated workflows you can publish, how many automation sends you can trigger, what happens with Agreement Manager documents, and which features move to “contact sales”.
That is why the right question is not “Which IAM plan is best?” It is: which counters will this use case consume?
The public IAM plan family
The public US pricing page lists three self-serve IAM plans plus an enhanced/enterprise option. Local pricing, taxes, negotiated enterprise terms and regional availability can differ, so treat this as a practical map, not a quote.
| Plan | Public positioning | Key allowance to check |
|---|---|---|
| IAM Starter | Individuals who need to manage agreements with AI | 100 envelope sends per user per year and 1 automated workflow |
| IAM Standard | Small teams with complex workflows and an AI repository | Unlimited web-app envelopes, 3 automated workflows and automation-send limits |
| IAM Professional | Larger teams scaling workflows with forms, automation and AI | Unlimited web-app envelopes, 10 automated workflows, Web Forms and Bulk Send included |
| Enhanced / Enterprise | Custom requirements, larger organisations and advanced controls | SSO, org management, document visibility, signing groups, AI-assisted review and support terms |
The six counters to understand
1. Users / seats
IAM plans are user-based. Before buying seats, separate your population into heavy senders, regular senders, occasional requesters, approvers, viewers and admins. Not every person who touches a process necessarily needs the same type of access.
2. Web-app envelopes
For IAM Standard and Professional, Docusign's public pricing page lists unlimited envelopes sent through the web app. Starter is different: the public annual plan lists 100 envelope sends per user per year.
3. Automation sends
This is the part most teams miss. Docusign's allowance page says automation sends can include sends triggered through APIs or integrations, Workflow Builder triggers through APIs or integrations, Bulk Send, and Web Forms or PowerForms that result in a signature send. For annual IAM Standard and Professional plans, the public FAQ describes 100 automation sends per user per year, pooled at account level.
4. Maestro / Workflow Builder workflows
Public IAM pricing lists 1 automated workflow for Starter, 3 for Standard and 10 for Professional. The design implication is simple: do not create one workflow per tiny variation. Build conditional workflows around contract type, entity, amount, region and approval path.
5. Agreement Manager / Navigator documents
Agreement Manager gives teams a searchable, AI-assisted agreement repository. But allowances can depend on plan, order start date and whether documents are new or historical. Docusign's allowance page specifically notes several changes across 2024, 2025 and 2026, so old proposals and new proposals can behave differently.
6. Add-ons and premium actions
Some actions are not just “a send”: multi-channel delivery, ID verification, premium data verification, SMS or phone authentication and some API/integration patterns can have separate allowances or add-on pricing. Put them in the business case before signature.
Implementation view: licensing should be designed with the workflow. A Web Form, a Bulk Send, a Salesforce-triggered send and a manual web-app send may all look like “sending a contract” to the business, but they can consume different allowances.
A practical sizing checklist
- Export 12 months of eSignature usage and group senders by volume.
- List each future IAM workflow and decide if it starts manually, through a Web Form, through Bulk Send, or through an integration/API.
- Count the expected yearly automation sends, not just total envelopes.
- Estimate the initial repository upload and the yearly new agreement volume.
- Identify which users need to build, publish, approve, request, send, view or administer.
- Flag premium needs: SSO, document visibility, signing groups, identity verification, data residency, support level, AI-assisted review and custom extractions.
Questions to ask before signing
- Which exact IAM plan and edition is on the order form?
- How many web-app envelopes are included, and for which sending methods?
- How many automation sends are included per user per year, and are they pooled?
- Do third-party integrations count against automation sends in this contract?
- How many automated workflows can be published?
- What happens if the team exceeds workflow, automation send or Agreement Manager allowances mid-term?
- Which Agreement Manager document ingestion and processing allowances apply to this order start date?
- Are sandbox, SSO, org management, document visibility, ID verification, SMS, data residency and support included or add-ons?
FAQ
Is Docusign IAM seat-based or envelope-based?
Public IAM plans are priced per user, but usage still depends on web-app envelope, automation send, workflow and Agreement Manager allowances. The order form is the source of truth.
What is an automation send?
Docusign describes automation sends as sends triggered by API or integrations, Workflow Builder triggers through API or integrations, Bulk Send, and Web Forms or PowerForms that result in an agreement being sent for signature.
Does IAM replace eSignature?
IAM includes eSignature capabilities inside a broader agreement platform. For pure signature use cases, standalone eSignature may still be enough.
Why does the order start date matter?
Because Docusign's allowance page lists several changes tied to order start dates, including changes to automation sends, Agreement Manager documents and processing. Two customers on “IAM Standard” may not have identical terms if their contracts were signed at different times.
Official sources
We keep this guide grounded in public Docusign material. Always verify against your current proposal and order form.
Licensing evolves quickly. This guide reflects public Docusign information reviewed on July 8, 2026. ContractFlow implements Docusign and does not resell licences, so the goal is fit, not commission.