.png)
Frameworks, core principles and top case studies for SaaS pricing, learnt and refined over 28+ years of SaaS-monetization experience.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Procurement Guide How Are E-Signature & Digital Agreement Platforms Priced for Enterprises
Enterprise buyers rarely get into trouble because they misunderstand what an electronic signature does. They get into trouble because they misunderstand what the vendor counts. A contract may be sold per user, per envelope, per transaction, per document, or through a mixture of licences and credits. The same agreement sent from a web interface may be included, while the same agreement triggered through an API may consume a separate allowance. Docusign’s current IAM plans make this distinction explicit: web-app envelopes are unlimited on IAM Standard and Professional, yet automated sends through web forms, bulk send and APIs are limited to 100 per user per year on annual plans.
That distinction matters more as signing moves beyond legal and sales teams. HR offer letters, procurement approvals, service agreements, onboarding forms and embedded customer journeys can turn a modest e-signature deployment into a high-volume workflow platform. Docusign itself reported more than 1.8 million customers as of 31 January 2026, including roughly 280,000 direct enterprise and commercial customers, with 1,205 customers above $300,000 in annualised contract value. Its move from historically envelope-led pricing towards user-based IAM subscriptions with transaction add-ons shows where the market is heading.
Monetizely’s position is that enterprises should make pooled transaction capacity the primary pricing meter for e-signature and digital agreement platforms in 2026. Broad sender access should sit around that meter, while API traffic, authentication and trust services need explicit unit prices. Per-seat pricing is a poor primary meter once signing becomes distributed, while uncapped pay-as-you-go usage creates too much budget risk.
The signature is free to the recipient, but almost every workflow has something billable behind it
The first procurement mistake is treating “e-signature pricing” as though vendors sell the same unit. They do not.
Docusign’s traditional eSignature Standard and Business Pro annual plans allow up to 100 envelopes per user per year, and an envelope counts when sent whether or not the recipient completes it. Adobe says a transaction occurs when an electronic document or related collection is sent to one or more recipients, with user-licensed Acrobat Sign plans including 150 transactions per user per year unless the contract states otherwise. OneSpan’s Professional plan takes another approach, listing $22 per user per month billed annually with up to 1,000 transactions per user per year.
Dropbox Sign and PandaDoc push further towards removing send limits from their seat plans. As of 13 August 2026, Dropbox Sign Standard lists $17.50 per user per month on annual billing and includes unlimited signature requests, although organisations with more than five users are directed to sales and Premium is custom quoted. PandaDoc Business lists $49 per seat per month billed annually, while Enterprise explicitly offers either per-seat or per-document pricing; its document-based package provides unlimited seats and charges around document creation instead.
The exhibit below normalises the public pricing structures. Enterprise negotiated prices will differ, but the underlying meters are already visible.
| Vendor | Dominant enterprise pricing meter | Public pricing evidence, dated 13 Aug 2026 | Where procurement risk moves |
|---|---|---|---|
| Docusign | User subscription plus send allowances and transaction-style add-ons | IAM Standard is $50/user/month on an annual commitment, with unlimited web-app envelopes but 100 automation sends/user/year. Traditional Standard and Business Pro allow 100 envelopes/user/year. | Automation, APIs, bulk send and premium capabilities can move usage outside the apparently unlimited web allowance. |
| Adobe Acrobat Sign | Transactions tied to user entitlement, subject to contract terms | User-licensed Acrobat Sign plans include 150 transactions/user/year unless the contract says otherwise. API and third-party integration sends consume transactions. | Transaction definitions cover more than simple person-to-person signature requests. |
| Dropbox Sign | Sender seats, with unlimited standard signature requests | Standard lists $17.50/user/month annually; unlimited signature requests are included, while teams above five users move to sales-led pricing. | Seat growth becomes the main expansion path, while large-team and API economics move into negotiated contracts. |
| PandaDoc | Seat or document, chosen by enterprise | Business is $49/seat/month annually; Enterprise explicitly offers per-seat or per-document pricing, and the document option comes with unlimited seats. | CPQ, workflow automation, API, notary and related capabilities can broaden the paid package beyond basic signing. |
| OneSpan Sign | Pooled transaction volume for Enterprise | Enterprise buyers can choose a specific transaction quantity or a usage band; Professional lists $22/user/month annually with up to 1,000 transactions/user/year. | Paid integrations, SMS, identity features and volume-band boundaries can raise TCO. |
| Zoho Sign | User licences plus credits for automated and API activity | Enterprise includes complimentary credits linked to user licences; API and third-party app envelopes consume credits. API-only has no recurring user fee, but each API envelope consumes five credits. | Credits create a second meter that grows with automation, SMS, authentication and trust services. |
The table makes the core procurement point clear: “price per user” is rarely enough information to compare enterprise e-signature platforms. The bill is shaped by how many agreements move through the system, which channel initiates them and what additional proof of identity the workflow requires.
A digital agreement system starts as a productivity tool when a salesperson manually sends an NDA. It becomes infrastructure when Workday generates thousands of employment documents, Salesforce triggers contracts, or a customer portal embeds signature requests. Pricing needs to survive that transition.
Adobe illustrates the issue particularly well. Its Acrobat Sign documentation, updated 8 July 2026, says a transaction can be consumed by a normal signature request, an in-person signing flow, each agreement in a bulk send, a submitted web form, a custom workflow, and some Fill & Sign activity. Agreements sent through Salesforce, Workday, Microsoft Teams, custom applications or the Acrobat Sign API count under the same transaction entitlement.
Docusign has moved in the opposite direction on the user experience while retaining a usage boundary around automation. IAM Standard, at $50/user/month on an annual commitment as of 13 August 2026, includes unlimited envelopes sent through the web application. Annual IAM Standard and Professional plans, however, include 100 automation sends per user per year across Web Forms, PowerForms, Bulk Send and custom or partner API integrations.
That is not an accidental detail. Docusign’s 2026 10-K says the company began offering IAM on a user-based subscription with transaction-based add-ons in the second quarter of fiscal 2025, then expanded IAM across major geographies during fiscal 2026. IAM represented 10.8% of ARR by 31 January 2026, up from 2.3% a year earlier.
Zoho makes the dual structure even more visible. Its API-only plan has no periodic subscription or per-user licensing cost, yet an envelope sent through the API consumes five Zoho Sign credits. SMS delivery, recipient authentication, timestamps and other trust services can also consume credits at their respective rates.
From a buyer’s perspective, the important distinction is therefore not “seat versus usage” in the abstract. Procurement needs to map human sends, automated sends, authentication events, embedded signing and high-volume forms separately, because vendors can meter each category differently.
Monetizely’s 5-Step Pricing Framework provides the right discipline for doing so. It begins with Goals & Segments, which asks who buys and what business result pricing should support; moves to Positioning & Packaging, where capabilities are grouped for those buyers; then selects the Price Metric, the unit that causes spend to rise; sets actual charges through Rate-Setting; and finally addresses Operationalization, including quoting, usage tracking, billing, overages and renewals. The same discipline is discussed in Monetizing Agentic AI, although the logic applies just as strongly to mature workflow software. For e-signature procurement, packaging, the price metric and operationalisation deserve unusual attention because an enterprise can buy the correct features and still sign the wrong commercial model.
Our scorecard grades the six vendors on those three steps from the enterprise buyer’s perspective, not on product quality.
| Vendor | Packaging | Pricing metric | Operationalisation | Monetizely diagnosis |
|---|---|---|---|---|
| Docusign | B+ | B- | C+ | IAM gives broader agreement-management value, but “unlimited” web envelopes sit beside capped automated sends, creating channel-specific cost exposure. |
| Adobe Acrobat Sign | B | B- | C+ | A transaction is defined consistently, but many workflow actions consume it and enterprise entitlement is contract-sensitive. |
| Dropbox Sign | B+ | A- | B | Unlimited signature requests make human-driven use easy to understand; enterprise scale moves beyond the public small-team price into custom terms. |
| PandaDoc | A- | A | B | Letting Enterprise choose per-seat or per-document pricing is unusually strong metric design because organisations can match price to adoption pattern. |
| OneSpan Sign | B+ | A | B | Enterprise transaction quantities or usage bands fit automated signing well, although paid integrations and add-ons need to be normalised in the quote. |
| Zoho Sign | B | B+ | B- | Credits line up with API and third-party costs, but buyers must govern both licences and credit consumption. |
PandaDoc and OneSpan get closest to the metric architecture we favour because both make volume-oriented enterprise pricing explicit. Docusign has improved packaging materially with IAM, but its split between unlimited manual sending and separately limited automation makes usage governance more important, not less.
Enterprise pricing controversies are unusually difficult to document from Tier A sources because negotiated SaaS contracts are normally private. Public-sector budgets, regulator actions and government contracts provide a more reliable window than anonymous anecdotes.
The evidence does not support claiming that every example below is an adjudicated “bill shock”. Only the Adobe case is a formal regulatory pricing controversy. The others show documented cost increases, pricing dispersion or contract mechanics that can produce the same procurement problem: the buyer discovers that the original headline price did not describe the future cost.
The strongest lesson comes from North Carolina. Usage commitment itself is not the problem. Capacity that expires, cannot be pooled, or must be repurchased before old capacity is exhausted is the problem. North Carolina’s negotiated rollover illustrates exactly the protection commercial buyers should seek.
Discount percentage also deserves scepticism. Docusign acknowledges in its 2026 10-K that mid-size and large enterprises may demand substantial price discounts during contract negotiations. The GSA agreement confirms how large those reductions can become for a buyer with concentrated bargaining power.
Three-year TCO changes sharply when the same usage is placed behind a different meter
Procurement teams often compare vendor proposals with a Year One licence total. We think that is the wrong denominator.
A more useful model starts with expected agreement volume and allows adoption to rise. Consider an enterprise with 500 employees who may send agreements, 120,000 transactions in Year One and 20% annual transaction growth. The model below holds the underlying business activity constant while changing only the contract structure.
The model exposes why our preferred architecture is not simply “usage-based pricing”. The primary meter should be pooled transactions, with predictable rate steps and enough sender access that adoption does not create a second tax. An annual volume commitment with punitive overages can be almost as expensive as broad seat licensing.
Vendor mechanics make this more than a spreadsheet exercise. Adobe counts API and integrated application sends against transaction consumption. Docusign IAM gives unlimited web envelopes but a separate automation allowance. Zoho consumes credits for API envelopes and other services involving third-party costs. OneSpan Enterprise explicitly offers transaction quantities or a usage band.
A procurement team forecasting only “documents sent by legal” will therefore miss the growth that matters. The real forecast should include CRM-triggered contracts, HR workflows, procurement forms, customer onboarding, bulk campaigns, web submissions and embedded signing.
Buyers should negotiate the meter before negotiating the discount
A 40% discount against the wrong meter is still a bad deal.
The contract should first establish a unit that both sides can measure and the buyer can forecast. For most large organisations, that means a pooled transaction or envelope quantity shared across departments, senders and automated workflows. Named-user licences can remain for administrators or advanced workflow builders, but they should not be the main source of expansion revenue when thousands of employees may send only a handful of agreements each year.
The negotiation checklist should therefore force every bidder into the same set of questions:
- Define the billable event. State whether a transaction is counted on send, completion, signature, web-form submission or API call. Docusign’s traditional envelope allowance counts once sent whether completed or not, while Adobe’s transaction definition also starts with the send event.
- Pool capacity across people and business units. Do not accept a large enterprise commitment that strands transactions against individual user entitlements.
- Put API and automation treatment in the order form. Docusign’s 100 annual automation sends per IAM Standard or Professional user and Zoho’s five-credit charge per API envelope show why “API included” does not necessarily mean “API usage included”.
- Secure rollover before discussing multi-year prepayment. North Carolina’s 2014 Docusign extension preserved unused purchased envelopes and delayed additional purchases until that supply was consumed.
- Fix every overage rate for the full term. The contract should show exactly what the next transaction costs after committed capacity is exhausted.
- Price authentication and trust services separately. OneSpan lists SMS notifications starting at $0.40 per transaction, while Zoho says SMS, recipient authentication and timestamping can consume additional credits.
- Require usage reporting before an overage occurs. A meter the customer cannot observe is not procurement-grade pricing.
- Cap renewal increases. Multi-year subscriptions are common in this category: Docusign reported on 31 January 2026 that subscriptions generally run one to three years and that substantially all multi-year customers pay annual instalments one year in advance.
These terms matter more than extracting another five points of discount. They determine whether a £300,000 or $300,000 agreement remains close to its business case after workflows spread across the company.
The same logic changes vendor selection. Dropbox Sign’s unlimited signature requests make its standard seat model attractive when a relatively concentrated group of employees does most of the sending. PandaDoc’s document option is structurally stronger when senders are numerous but agreement volume is measurable. OneSpan’s volume-led Enterprise structure fits high-volume automated workflows. Zoho’s API-only credit model can align well with embedded use when organisations are prepared to manage credits.
Docusign deserves special treatment because its pricing transition is strategically important. Historically, the company says it priced most products around functionality and the quantity of envelopes required. Beginning in fiscal 2025 it introduced user-based IAM subscriptions with transaction-based add-ons, and by 31 January 2026 more than 25,000 customers were on IAM. Buyers should therefore model Docusign as an agreement platform with several possible usage paths, not simply compare an IAM seat to an old eSignature seat.
The strongest 2026 contract pays for agreement volume without taxing adoption
E-signature procurement is becoming harder precisely because the products are becoming more useful. Basic signature collection is no longer the whole purchase. Digital agreement platforms increasingly sit inside CRM, HR, procurement and customer-facing processes, while APIs and automation move volumes far beyond what a legal team sends manually. Current vendor pricing already reflects that shift through transaction add-ons, credits, automation allowances and volume bands.
Monetizely’s position is therefore firm: enterprises should buy pooled transaction capacity as the primary meter, with broad sender access, explicit API treatment, a fixed overage schedule and separately priced trust services. Seats should govern access to specialised authoring or administration features, not serve as the main tax on company-wide adoption.
For procurement leaders making a platform decision in 2026, five actions follow.
Build the business case around agreement throughput, not the current number of e-signature users. Pull twelve months of CRM, HR, procurement and customer-workflow data to estimate how many agreements the organisation actually creates, then model automation growth for the next three years.
Split the requirements into human-led and machine-triggered workflows before vendors see the RFP. A supplier that looks inexpensive for 100 legal and sales users can behave very differently once tens of thousands of agreements originate through APIs, bulk sends or web forms, as the Docusign, Adobe and Zoho rules demonstrate.
Force every finalist into a common three-year unit-cost model. Compare total contract value divided by expected completed business agreements, then run the same calculation at 70%, 100% and 140% of forecast volume. The exercise removes much of the distortion created by different names for envelopes, documents, transactions and credits.
Give pricing architecture meaningful weight in vendor selection. An enterprise should be willing to prefer a slightly weaker headline discount when the alternative provides pooled capacity, cleaner automation economics and better usage visibility. The GSA’s 2025 Docusign agreement shows how large negotiated discounts can become, but discount depth alone says nothing about the eventual fit between price and consumption.
Treat pricing migration as part of platform risk. Docusign’s shift from historically envelope-oriented pricing towards user-based IAM subscriptions with transaction add-ons demonstrates that a strategic vendor can change its monetisation model as the product expands. Procurement should select platforms whose underlying value meter would remain defensible even if packaging is reset at renewal.
The best enterprise e-signature deal is therefore not the one with the cheapest seat. Nor is it the contract with the largest nominal discount. It is the one where the buyer can explain, before signing, what another 10,000 agreements will cost, what happens when those agreements become automated, and what the organisation will actually pay over three years.
Assumptions
The three-year TCO exhibit is a Monetizely model rather than a vendor quote. It assumes 500 eligible senders, 120,000 Year One transactions, 20% annual transaction growth, a modelled $25 monthly seat rate, a $40,000 annual transaction-platform charge, $0.55 committed transaction pricing and $1.10 overage pricing. Figures exclude tax, implementation, migration, premium support, identity verification, qualified digital signatures, notary, SMS and other trust-service charges. Public vendor prices and product rules were checked through 13 August 2026; enterprise quotes may differ by geography, volume and negotiated contract.
Footnotes
https://www.amazon.com/Monetizing-Agentic-AI-Handbook-Transformation/dp/B0H7Z13VKJ/
https://www.sec.gov/Archives/edgar/data/1261333/000126133326000021/docu-20260131.htm
https://ecom.docusign.com/plans-and-pricing/iam
https://ecom.docusign.com/plans-and-pricing/esignature
https://www.gsa.gov/about-gsa/newsroom/news-releases/gsa-partners-with-docusign-to-deliver-price-reductions-for-docusign-government-07312025
https://helpx.adobe.com/in/sign/using/transaction-limits.html
https://helpx.adobe.com/sign/web/system-level-resources/adobesign-transaction-consumption.html
https://www.justice.gov/opa/pr/adobe-agrees-150-million-settlement-and-injunction-resolve-alleged-violations-restore-online
https://budget.hawaii.gov/wp-content/uploads/2022/12/08.-Department-of-Accounting-and-General-Services-FB23-25-PFP.Lk0_.pdf
https://sign.dropbox.com/products/dropbox-sign/pricing
https://www.pandadoc.com/pricing/
https://www.onespan.com/digital-agreements/esignature/plans-pricing
https://www.zoho.com/sign/pricing.html
https://www.zoho.com/sign/pricing-api.html
https://it.nc.gov/documents/files/electronic-forms-report-december-2014/open
https://publicdocuments.fortworthtexas.gov/CSODOCS/DocView.aspx?dbid=0&id=255870&repo=city-secretary