Adobe Acrobat Sign

What it is

Adobe Acrobat Sign is Adobe’s e-signature service, formerly Adobe Sign and before that EchoSign. It ships two ways. Self-serve, signing is bundled into the Acrobat for teams plans: you buy a PDF editor and get send-for-signature with it. Sales-led, Adobe sells Acrobat Sign Solutions, the transaction-priced tier with the enterprise integrations, the API at volume, and the compliance configurations (Adobe lists HIPAA, FERPA, GLBA, eIDAS and FDA 21 CFR Part 11). DocuSign’s own FY2026 10-K names Adobe as its primary global eSignature competitor, which is the cleanest statement of where Acrobat Sign sits: the default second quote in every CLM signing step.

This entry covers Acrobat Sign as the signature layer under a contract process. It is not a CLM. There is no repository workflow, obligation tracking or intake engine here; for that, see what CLM actually covers.

What changed in 2026

Adobe ships Acrobat Sign on a numbered release train, and 2026 was a year of workflow plumbing rather than AI:

• v17.0 (production 2026-02-03). Dynamic Participation removes a recipient from an in-flight agreement without cancelling and resending; completed, cancelled or expired agreements can be copied into a new draft; checkbox groups get validation rules; and fields auto-fill from verified identity data after a signer authenticates through a supported digital identity provider.
• v17.1 (production 2026-05-05). In-Person Signing lets an internal host run a signing session in a browser, logged in the audit trail. Bulk digital signatures let a signer select several agreements in “Waiting for you” and apply certificate-based signatures under one signing authorization.
• v17.2 (production 2026-09-08). Agreements can pause, for 1 to 30 days, when a recipient fails authentication, instead of being cancelled. The sender switches the authentication method and resumes, and completed signers do not sign again.
• v17.2.1 (production 2026-10-06). Inline text editing while authoring library templates, without re-uploading the file.

New features ship disabled by default; an account or group admin has to switch each one on.

Pricing reality

Self-serve list prices, annual commitment billed monthly, per license:

• Acrobat Standard for teams — $16.99. Send, sign and track.
• Acrobat Pro for teams — $23.99. Adds bulk send, web forms, reusable templates and agreement branding.
• Acrobat Studio for teams — $29.99. Everything in Pro plus the Acrobat AI features.

The number that matters is not the seat price. Adobe’s transaction-limit page states that user-licensed plans include 150 transactions per user per year unless the contract says otherwise, and a transaction is each send to one or more recipients. Ten Pro seats is $2,879 a year at list and 1,500 sends. High-volume buyers move to Acrobat Sign Solutions, priced by transaction band (reseller SKUs run from 1–999 to 5,000–14,999 transactions a year) and quote-only. Vendr does not publish an Acrobat Sign-only benchmark; its Adobe-wide median of $63,796 a year across 731 purchases is mostly Creative Cloud and Acrobat, so do not use it to anchor a signature budget.

Against DocuSign, whose eSignature Business Pro is $45/user/month, Acrobat Pro for teams is roughly half the seat price and includes a PDF editor most legal teams already pay for separately.

Best for

A legal-ops or contracts manager at a 50–2,000 employee company that already licenses Acrobat, signing standard paper — NDAs, MSAs, order forms, offer letters — out of Microsoft 365, Salesforce or Workday, under about 150 sends per user per year. The scoped win: signature added to a license you already own, with no new vendor review.

Not for

Teams buying the signature layer for its AI. Acrobat Sign has no first-party agents and no official MCP server; agent access today runs through third-party bridges such as Zapier’s Acrobat Sign MCP. Also not for a company whose signature volume sits with a few senders — 150 transactions per seat punishes exactly that pattern.

Versus the alternatives

• DocuSign IAM — the share leader, and the pick when you want signature and post-signature repository from one vendor, a published path into agreement management, and an official MCP server. Pick Acrobat Sign when signature is the whole job and Acrobat is already on the desk.
• Dropbox Sign — the third incumbent. Pick it when the company’s files live in Dropbox and the requirement is a clean API for embedded signing in a product flow.
• PandaDoc — pick it when the document is a sales proposal or quote with pricing tables and payment collection; Acrobat Sign has no quoting layer.
• Native CLM signing — Ironclad and Juro both sign inside the contract platform. Pick native signing when the CLM is already the system of record and a separate signature vendor is one more integration to maintain.

Watch-outs

• The 150-transaction allowance is per user per year. A sales-ops team where three people send every order form burns through it in weeks. Guard: count last year’s envelopes by sender before buying seats, and if any sender exceeds 150, price Acrobat Sign Solutions on transaction volume instead.
• The embedded Power Automate experience leaves the Acrobat Sign web app with v18.0 in January 2027. Existing flows keep running and move to management in Microsoft Power Automate itself, where flows with premium connectors need Power Automate Premium at $15/user/month. Guard: before January 2027, inventory every Acrobat Sign flow, confirm owners can open it in Power Automate, and check each for premium connectors.
• Features ship switched off. A release note is not a capability in your tenant. Guard: have the account admin enable and test pause-on-authentication-failure, In-Person Signing and bulk digital signatures in sandbox before you promise them to the business.
• Legacy screens are being retired on a rolling schedule. Adobe’s notices put the legacy signature-request screen and legacy reports on a 2027 removal path. Guard: rebuild any SOP screenshots and report exports against the new experiences now, not in the release week.