UNITED STATES EDITIONUS pricing. Source-backed comparisons.

US BUYER’S GUIDE Β· 5 PRODUCTS

Electronic Signature

Do you need occasional signatures, repeatable sales documents or a controlled agreement workflow?

Compare signature collection, reusable documents, approval workflows and agreement intelligence for US businesses.

Research desk Β· Oct 20, 2026 Β· Methodology

YOUR SHORTLIST STARTS HERE

Compare the options.

Highest documented score first. Fit adds up the 28 feature checks below, including AI, across documented plans. Entry price does not include every capability. Unknown evidence appears as a range.

Product / good fit forPricing contextDocumented fitNext step

Docusign

Teams needing repeatable signing workflows and a documented transaction record.

See pricingsender/montheSignature
84–100/100 documented fit
84% evidence coverage
Full research β†’

PandaDoc

Sales and service teams producing repeatable proposals and agreements.

$19.00seat/month Β· billed annuallyStarter
61–100/100 documented fit
61% evidence coverage
Full research β†’

Zoho Sign

Zoho-centered businesses that want signing, reusable workflows and document summaries.

See pricingsender/monthStandard / Professional / Enterprise
58–100/100 documented fit
58% evidence coverage
Full research β†’

Dropbox Sign

Individuals and teams prioritizing straightforward repeated signature collection.

$15.00month Β· billed annuallyEssentials
57–100/100 documented fit
57% evidence coverage
Full research β†’

Adobe Acrobat

Teams that prepare many PDFs and also collect routine signatures.

$16.99license/month Β· billed annuallyAcrobat Standard for teams
48–100/100 documented fit
48% evidence coverage
Full research β†’

BEYOND A FEATURE CHECKMARK

How deep does the capability go?

Choose up to 3 for a closer look β†’

28 weighted checks: core capabilities contribute 32 points and workflow depth contributes 68. AI is included at the weight shown for this category. Expand Evidence for scope and sources, or ask for the same demonstration from each supplier.

Showing fewer rows does not change the score.
Electronic Signature features for all 5 products
Feature / base weightDocusign
84–100/100 documented fit
Core capabilities32 / 32 pts10/10 checks with established status
Workflow depth52.3–68 / 68 pts12/18 checks with established status
PandaDoc
61–100/100 documented fit
Core capabilities32 / 32 pts10/10 checks with established status
Workflow depth28.8–68 / 68 pts6/18 checks with established status
Zoho Sign
58–100/100 documented fit
Core capabilities21.6–32 / 32 pts7/10 checks with established status
Workflow depth36–68 / 68 pts7/18 checks with established status
Dropbox Sign
57–100/100 documented fit
Core capabilities27.2–32 / 32 pts8/10 checks with established status
Workflow depth29.6–68 / 68 pts6/18 checks with established status
Adobe Acrobat
48–100/100 documented fit
Core capabilities23.2–32 / 32 pts7/10 checks with established status
Workflow depth24.8–68 / 68 pts5/18 checks with established status
Core capabilitySend electronic signature requests4.8 points Β· Prepare and send a document for electronic signing.Supported4.8 / 4.8 pts
Evidence

The eSignature product sends documents for electronic signing.

Official documentation Β· Oct 15, 2026Source
Supported4.8 / 4.8 pts
Evidence

Paid plans include document upload and electronic signature requests.

Official documentation Β· Oct 15, 2026Source
Supported4.8 / 4.8 pts
Evidence

The product supports sending documents for electronic signing.

Official documentation Β· Oct 15, 2026Source
Supported4.8 / 4.8 pts
Evidence

Paid plans advertise unlimited signature requests.

Official documentation Β· Oct 15, 2026Source
Supported4.8 / 4.8 pts
Evidence

Acrobat can request and receive electronic signatures.

Official documentation Β· Oct 15, 2026Source
Core capabilitySignature status tracking4.8 points Β· Track recipient activity or the completion status of a signature request.Supported4.8 / 4.8 pts
Evidence

The product manages signature-request status and progress.

Official documentation Β· Oct 15, 2026Source
Supported4.8 / 4.8 pts
Evidence

Recipient activity analytics and document tracking are listed.

Official documentation Β· Oct 15, 2026Source
Not verified0–4.8 / 4.8 pts
Evidence

Signature status tracking needs a feature-specific reference beyond generic sending.

Not verified Β· Oct 15, 2026Source
Supported4.8 / 4.8 pts
Evidence

Executed signature requests retain transaction status and event evidence.

Official documentation Β· Oct 15, 2026Source
Supported4.8 / 4.8 pts
Evidence

Signature tracking and completion notifications are documented.

Official documentation Β· Oct 15, 2026Source
Depth checkCorrect a pending signature request7.2 points Β· Correct a sent but incomplete request through a documented correction workflow.
Ask for a demonstration

Send a document with an error, correct it, and show what the recipient sees.

A scenario to run with the supplier; not a completed product test.
Supported7.2 / 7.2 pts
Evidence

Sent envelopes can be corrected through the web app or API.

Official documentation Β· Oct 15, 2026Source
Supported7.2 / 7.2 pts
Evidence

Editing a sent document resets it to draft and clears completed fields before resending.

Official documentation Β· Oct 15, 2026Source
Supported7.2 / 7.2 pts
Evidence

Sent requests can be corrected before the first recipient signs.

Official documentation Β· Oct 15, 2026Source
Supported7.2 / 7.2 pts
Evidence

Pending requests can be edited; changes are retained in the audit trail.

Official documentation Β· Oct 15, 2026Source
Supported7.2 / 7.2 pts
Evidence

Acrobat Sign Solutions can modify files and fields before the first recipient completes signing.

Official documentation Β· Oct 15, 2026Source
Depth checkCancel or decline a request7.2 points Β· Cancel an incomplete request or let a recipient decline it with recorded status.
Ask for a demonstration

Cancel or decline a request and show the final status and recipient notification.

A scenario to run with the supplier; not a completed product test.
Supported7.2 / 7.2 pts
Evidence

Voiding an incomplete envelope notifies its recipients.

Official documentation Β· Oct 15, 2026Source
Not verified0–7.2 / 7.2 pts
Evidence

The reviewed documentation does not establish this specific workflow: cancel or decline a request.

Not verified Β· Oct 15, 2026Source
Supported7.2 / 7.2 pts
Evidence

A sent request can be recalled with a recorded status change.

Official documentation Β· Oct 15, 2026Source
Supported7.2 / 7.2 pts
Evidence

API cancellation is supported before any signer signs; later cancellation has restrictions.

Official documentation Β· Oct 15, 2026Source
Not verified0–7.2 / 7.2 pts
Evidence

The reviewed documentation does not establish this specific workflow: cancel or decline a request.

Not verified Β· Oct 15, 2026Source
Core capabilitySigning audit record4 points Β· Retain a timestamped audit trail or certificate associated with the signing transaction.Supported4 / 4 pts
Evidence

Certificate of Completion and transaction data provide an audit record.

Official documentation Β· Oct 15, 2026Source
Supported4 / 4 pts
Evidence

Plans include signing audit trails.

Official documentation Β· Oct 15, 2026Source
Supported4 / 4 pts
Evidence

Senders or administrators can export an audit trail and completion certificate.

Official documentation Β· Oct 15, 2026Source
Supported4 / 4 pts
Evidence

A timestamped audit record is provided for requests; Just Me self-signing is excluded.

Official documentation Β· Oct 15, 2026Source
Supported4 / 4 pts
Evidence

The signing workflow records an audit trail.

Official documentation Β· Oct 15, 2026Source
Core capabilityAdditional signer authentication4 points Β· Offer an additional signer check such as an access code, SMS or identity verification.Supported4 / 4 pts
Evidence

Signers can be required to verify themselves through phone, SMS or knowledge-based checks.

Official documentation Β· Oct 15, 2026Source
Supported4 / 4 pts
Evidence

Recipient verification is an additional paid capability in eligible plans.

Official documentation Β· Oct 15, 2026Source
Supported4 / 4 pts
Evidence

Recipient authentication includes OTP options and US knowledge-based authentication.

Official documentation Β· Oct 15, 2026Source
Supported4 / 4 pts
Evidence

The help page documents password and SMS signer-authentication options.

Official documentation Β· Oct 15, 2026Source
Not verified0–4 / 4 pts
Evidence

Additional signer-authentication scope needs verification for the specific Acrobat offering.

Not verified Β· Oct 15, 2026Source
Depth checkExport document and audit evidence5.6 points Β· Download the signed document and its audit record or completion certificate.
Ask for a demonstration

Download a completed document and the evidence needed to review its signing history.

A scenario to run with the supplier; not a completed product test.
Supported5.6 / 5.6 pts
Evidence

Envelope audit events can be retrieved and reviewed through the API.

Official documentation Β· Oct 15, 2026Source
Supported5.6 / 5.6 pts
Evidence

Completed documents include a Certificate of Completion and signing audit trail.

Official documentation Β· Oct 15, 2026Source
Supported5.6 / 5.6 pts
Evidence

Completed documents and their completion certificates can be downloaded.

Official documentation Β· Oct 15, 2026Source
Supported5.6 / 5.6 pts
Evidence

The signed document and audit trail can be downloaded together or separately.

Official documentation Β· Oct 15, 2026Source
Supported5.6 / 5.6 pts
Evidence

Acrobat Sign can attach audit reports to downloaded agreements.

Official documentation Β· Oct 15, 2026Source
Depth checkAuthentication in the audit record6.4 points Β· Record the result or method of an additional signer-authentication step in the audit evidence.
Ask for a demonstration

Require an additional identity check and locate its result in the audit evidence.

A scenario to run with the supplier; not a completed product test.
Supported6.4 / 6.4 pts
Evidence

Envelope History records password-authentication events during signing.

Official documentation Β· Oct 15, 2026Source
Supported6.4 / 6.4 pts
Evidence

KBA verification information appears in the completed document signature certificate.

Official documentation Β· Oct 15, 2026Source
Not verified0–6.4 / 6.4 pts
Evidence

The reviewed documentation does not establish this specific workflow: authentication in the audit record.

Not verified Β· Oct 15, 2026Source
Not verified0–6.4 / 6.4 pts
Evidence

The reviewed documentation does not establish this specific workflow: authentication in the audit record.

Not verified Β· Oct 15, 2026Source
Not verified0–6.4 / 6.4 pts
Evidence

The reviewed documentation does not establish this specific workflow: authentication in the audit record.

Not verified Β· Oct 15, 2026Source
Core capabilityReusable document templates3.2 points Β· Reuse prepared documents or fields for repeated signature requests.Supported3.2 / 3.2 pts
Evidence

Reusable signature templates are documented.

Official documentation Β· Oct 15, 2026Source
Supported3.2 / 3.2 pts
Evidence

Templates and reusable proposal content support repeatable documents.

Official documentation Β· Oct 15, 2026Source
Supported3.2 / 3.2 pts
Evidence

Reusable templates are documented in the plan record.

Official documentation Β· Oct 15, 2026Source
Supported3.2 / 3.2 pts
Evidence

Template allowances vary by edition.

Official documentation Β· Oct 15, 2026Source
Supported3.2 / 3.2 pts
Evidence

Reusable forms and templates depend on the Acrobat plan.

Official documentation Β· Oct 15, 2026Source
Core capabilitySigning order or approval routing3.2 points Β· Route documents through a configured signing order or approval step.Supported3.2 / 3.2 pts
Evidence

The signature API supports recipient routing order; advanced conditional workflows require their corresponding package.

Official documentation Β· Oct 15, 2026Source
Supported3.2 / 3.2 pts
Evidence

The current feature comparison lists signing order across plans.

Official documentation Β· Oct 15, 2026Source
Not verified0–3.2 / 3.2 pts
Evidence

Bulk sending does not establish a signing-order or approval-routing feature.

Not verified Β· Oct 15, 2026Source
Supported3.2 / 3.2 pts
Evidence

The signature-request API defines a signing order so later signers wait for earlier signers.

Official documentation Β· Oct 15, 2026Source
Not verified0–3.2 / 3.2 pts
Evidence

Signing-order or approval routing needs feature-specific verification for the offered edition.

Not verified Β· Oct 15, 2026Source
Depth checkReminders and expiration4.8 points Β· Configure reminders or expiration for outstanding signature requests.
Ask for a demonstration

Set a reminder and deadline and show the pending-request behavior.

A scenario to run with the supplier; not a completed product test.
Supported4.8 / 4.8 pts
Evidence

Reminder and expiration settings apply per account or envelope.

Official documentation Β· Oct 15, 2026Source
Not verified0–4.8 / 4.8 pts
Evidence

The reviewed documentation does not establish this specific workflow: reminders and expiration.

Not verified Β· Oct 15, 2026Source
Supported4.8 / 4.8 pts
Evidence

Senders can remind recipients and extend a document expiration date.

Official documentation Β· Oct 15, 2026Source
Supported4.8 / 4.8 pts
Evidence

Signature requests support expiration dates and reminder delivery.

Official documentation Β· Oct 15, 2026Source
Supported4.8 / 4.8 pts
Evidence

Acrobat Sign Solutions offers configurable reminders and records reminder activity.

Official documentation Β· Oct 15, 2026Source
Depth checkTransfer request ownership or responsibility4.8 points Β· Transfer management of a signature request to another authorized user.
Ask for a demonstration

Have the sender leave the team and show how another user manages the request.

A scenario to run with the supplier; not a completed product test.
Supported4.8 / 4.8 pts
Evidence

Administration supports individual envelope ownership transfers and automatic custody rules.

Official documentation Β· Oct 15, 2026Source
Supported4.8 / 4.8 pts
Evidence

Document ownership can transfer to another member of the same workspace.

Official documentation Β· Oct 15, 2026Source
Supported4.8 / 4.8 pts
Evidence

The document list supports changing request ownership between authorized users.

Official documentation Β· Oct 15, 2026Source
Not verified0–4.8 / 4.8 pts
Evidence

The reviewed documentation does not establish this specific workflow: transfer request ownership or responsibility.

Not verified Β· Oct 15, 2026Source
Not verified0–4.8 / 4.8 pts
Evidence

Individual sharing permits viewing but not management; a management handover was not established.

Not verified Β· Oct 15, 2026Source
Core capabilitySignature workflow API1.6 points Β· Create or manage signature transactions through a documented API.Supported1.6 / 1.6 pts
Evidence

The official developer guide documents recipient authentication and routing through the signing API; entitlement is separately scoped.

Official documentation Β· Oct 15, 2026Source
Supported1.6 / 1.6 pts
Evidence

API and automated generation require matching tiers or usage credits.

Official documentation Β· Oct 15, 2026Source
Supported1.6 / 1.6 pts
Evidence

API and automated transactions use separate allowances.

Official documentation Β· Oct 15, 2026Source
Supported1.6 / 1.6 pts
Evidence

The official embedded-signing guide documents creating signature requests through the API; production app approval is required.

Official documentation Β· Oct 15, 2026Source
Not verified0–1.6 / 1.6 pts
Evidence

An enterprise Sign API should not be assumed to be included in ordinary Acrobat.

Not verified Β· Oct 15, 2026Source
Core capabilityStorage or business-system connectors1.6 points Β· Connect signature workflows to storage, CRM or other business applications.Supported1.6 / 1.6 pts
Evidence

CRM document generation and enterprise connectors require the appropriate offering.

Official documentation Β· Oct 15, 2026Source
Supported1.6 / 1.6 pts
Evidence

CRM connections require the corresponding plan.

Official documentation Β· Oct 15, 2026Source
Supported1.6 / 1.6 pts
Evidence

Third-party workflow transactions are available with their own allowances.

Official documentation Β· Oct 15, 2026Source
Supported1.6 / 1.6 pts
Evidence

Document and CRM connections are available with tier-dependent scope.

Official documentation Β· Oct 15, 2026Source
Supported1.6 / 1.6 pts
Evidence

Document-storage connections are documented; enterprise connectors are separate.

Official documentation Β· Oct 15, 2026Source
Depth checkSignature event notifications2.4 points Β· Send signature status changes to an integration through documented webhooks or callbacks.
Ask for a demonstration

Complete a signature and show the event delivered to an integration.

A scenario to run with the supplier; not a completed product test.
Supported2.4 / 2.4 pts
Evidence

Connect webhooks report envelope lifecycle events to integrations.

Official documentation Β· Oct 15, 2026Source
Supported2.4 / 2.4 pts
Evidence

Webhooks report document-state changes and completed PDF availability.

Official documentation Β· Oct 15, 2026Source
Not verified0–2.4 / 2.4 pts
Evidence

The reviewed documentation does not establish this specific workflow: signature event notifications.

Not verified Β· Oct 15, 2026Source
Supported2.4 / 2.4 pts
Evidence

Signature callbacks report signing progress and downloadable-document availability.

Official documentation Β· Oct 15, 2026Source
Not verified0–2.4 / 2.4 pts
Evidence

Reminder webhooks are documented; signature-status callbacks were not established by the reviewed source.

Not verified Β· Oct 15, 2026Source
Depth checkRetrieve signed documents by API2.4 points Β· Download completed documents or audit evidence through a documented API.
Ask for a demonstration

Use the API to retrieve a completed signed document.

A scenario to run with the supplier; not a completed product test.
Supported2.4 / 2.4 pts
Evidence

The official developer examples include downloading signed documents from completed envelopes.

Official documentation Β· Oct 15, 2026Source
Supported2.4 / 2.4 pts
Evidence

The completed-document API provides a downloadable protected PDF.

Official documentation Β· Oct 15, 2026Source
Supported2.4 / 2.4 pts
Evidence

The PDF download API optionally includes the completion certificate.

Official documentation Β· Oct 15, 2026Source
Supported2.4 / 2.4 pts
Evidence

The Get Files endpoint downloads the document and audit evidence.

Official documentation Β· Oct 15, 2026Source
Not verified0–2.4 / 2.4 pts
Evidence

The reviewed documentation does not establish this specific workflow: retrieve signed documents by api.

Not verified Β· Oct 15, 2026Source
Core capabilityAI agreement summaries or questions2.4 points Β· Summarize agreement content or answer questions about it using AI.Supported2.4 / 2.4 pts
Evidence

AI agreement summaries and questions are explicitly documented; package details should be confirmed.

Official documentation Β· Oct 15, 2026Source
Supported2.4 / 2.4 pts
Evidence

The official AI record documents finding and summarizing document information.

Official documentation Β· Oct 15, 2026Source
Supported2.4 / 2.4 pts
Evidence

Zia summarizes eligible PDFs after administrator enablement, within document and monthly credit limits.

Official documentation Β· Oct 15, 2026Source
Not verified0–2.4 / 2.4 pts
Evidence

Native AI agreement summaries or questions were not established for Sign.

Not verified Β· Oct 15, 2026Source
Supported2.4 / 2.4 pts
Evidence

AI Assistant or Studio packaging provides document summaries and questions.

Official documentation Β· Oct 15, 2026Source
Core capabilityAI document preparation2.4 points Β· Use AI to draft or refine document content, detect fields or assist preparation.Supported2.4 / 2.4 pts
Evidence

Agreement detection and suggested signing fields are documented.

Official documentation Β· Oct 15, 2026Source
Supported2.4 / 2.4 pts
Evidence

Writing assistance can draft or refine document content.

Official documentation Β· Oct 15, 2026Source
Not verified0–2.4 / 2.4 pts
Evidence

The reviewed Zia source establishes summaries, not AI drafting or field preparation.

Not verified Β· Oct 15, 2026Source
Not verified0–2.4 / 2.4 pts
Evidence

AI document preparation was not verified for Sign; other Dropbox products are not assumed included.

Not verified Β· Oct 15, 2026Source
Supported2.4 / 2.4 pts
Evidence

Drafting and preparation assistance require the corresponding AI package.

Official documentation Β· Oct 15, 2026Source
Depth checkAI source references in agreements3.2 points Β· Link AI answers or summaries to passages in the underlying agreement.
Ask for a demonstration

Ask about a clause and open the exact passage supporting the answer.

A scenario to run with the supplier; not a completed product test.
Not verified0–3.2 / 3.2 pts
Evidence

Grounded agreement Q&A is documented, but passage-level clickable references need verification.

Not verified Β· Oct 15, 2026Source
Not verified0–3.2 / 3.2 pts
Evidence

AI document assistance is documented, but passage-linked citations were not established.

Not verified Β· Oct 15, 2026Source
Not verified0–3.2 / 3.2 pts
Evidence

Zia summarizes selected document pages; passage-level supporting citations were not established.

Not verified Β· Oct 15, 2026Source
Not verified0–3.2 / 3.2 pts
Evidence

Native agreement-AI citations were not established for Dropbox Sign.

Not verified Β· Oct 15, 2026Source
Supported3.2 / 3.2 pts
Evidence

Acrobat AI Assistant provides citations linking answers to supporting document sections.

Official documentation Β· Oct 15, 2026Source
Depth checkControl agreement AI availability4 points Β· An account, admin or user control enables or disables the relevant agreement AI feature.
Ask for a demonstration

Show where AI agreement analysis can be enabled or disabled.

A scenario to run with the supplier; not a completed product test.
Supported4 / 4 pts
Evidence

Sender-account admin settings control AI-assisted signing; embedded-session API disabling is unavailable.

Official documentation Β· Oct 15, 2026Source
Not verified0–4 / 4 pts
Evidence

The reviewed AI information did not establish a feature-specific enable or disable control.

Not verified Β· Oct 15, 2026Source
Supported4 / 4 pts
Evidence

Administrators enable the Zia summarization integration and configure its use.

Official documentation Β· Oct 15, 2026Source
Not verified0–4 / 4 pts
Evidence

A Dropbox Sign agreement-AI availability control was not established.

Not verified Β· Oct 15, 2026Source
Supported4 / 4 pts
Evidence

Acrobat preferences include controls to turn off generative AI features.

Official documentation Β· Oct 15, 2026Source
Depth checkAdd a witness to a signing transaction2.5 points Β· Demonstrate: Add a witness to a signing transaction. State the plan, limits and behaviour on failure. Use a test envelope with two recipients.
Ask for a demonstration

Demonstrate: Add a witness to a signing transaction. State the plan, limits and behaviour on failure. Use a test envelope with two recipients.

A scenario to run with the supplier; not a completed product test.
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Depth checkCollect supporting files from signers2.5 points Β· Demonstrate: Collect supporting files from signers. State the plan, limits and behaviour on failure. Use a test envelope with two recipients.
Ask for a demonstration

Demonstrate: Collect supporting files from signers. State the plan, limits and behaviour on failure. Use a test envelope with two recipients.

A scenario to run with the supplier; not a completed product test.
Supported2.5 / 2.5 pts
Evidence

Signers can return requested supporting attachments. Sender must enable signer attachments; documented 25 MB/file and 50 MB/recipient limits. Global capability evidence; local plan availability and interface language are not inferred.

Official documentation Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Depth checkCollect payment in the signing flow2.5 points Β· Demonstrate: Collect payment in the signing flow. State the plan, limits and behaviour on failure. Use a test envelope with two recipients.
Ask for a demonstration

Demonstrate: Collect payment in the signing flow. State the plan, limits and behaviour on failure. Use a test envelope with two recipients.

A scenario to run with the supplier; not a completed product test.
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Depth checkEmbed signing inside a customer application2.5 points Β· Demonstrate: Embed signing inside a customer application. State the plan, limits and behaviour on failure. Use a test envelope with two recipients.
Ask for a demonstration

Demonstrate: Embed signing inside a customer application. State the plan, limits and behaviour on failure. Use a test envelope with two recipients.

A scenario to run with the supplier; not a completed product test.
Supported2.5 / 2.5 pts
Evidence

Signing can be embedded inside the customer's application. eSignature API Embedded Recipient View; production API entitlement and OAuth implementation required. Global capability evidence; local plan availability and interface language are not inferred.

Official documentation Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Depth checkCapture signatures offline and synchronise later2.5 points Β· Demonstrate: Capture signatures offline and synchronise later. State the plan, limits and behaviour on failure. Use a test envelope with two recipients.
Ask for a demonstration

Demonstrate: Capture signatures offline and synchronise later. State the plan, limits and behaviour on failure. Use a test envelope with two recipients.

A scenario to run with the supplier; not a completed product test.
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Depth checkChoose each recipient's signing language2.5 points Β· Demonstrate: Choose each recipient's signing language. State the plan, limits and behaviour on failure. Use a test envelope with two recipients.
Ask for a demonstration

Demonstrate: Choose each recipient's signing language. State the plan, limits and behaviour on failure. Use a test envelope with two recipients.

A scenario to run with the supplier; not a completed product test.
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Depth checkComplete signing using keyboard and assistive technology2.5 points Β· Demonstrate: Complete signing using keyboard and assistive technology. State the plan, limits and behaviour on failure. Use a test envelope with two recipients.
Ask for a demonstration

Demonstrate: Complete signing using keyboard and assistive technology. State the plan, limits and behaviour on failure. Use a test envelope with two recipients.

A scenario to run with the supplier; not a completed product test.
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Depth checkSelect recipients from document-field conditions2.5 points Β· Demonstrate: Select recipients from document-field conditions. State the plan, limits and behaviour on failure. Use a test envelope with two recipients.
Ask for a demonstration

Demonstrate: Select recipients from document-field conditions. State the plan, limits and behaviour on failure. Use a test envelope with two recipients.

A scenario to run with the supplier; not a completed product test.
Supported2.5 / 2.5 pts
Evidence

Document fields determine the conditional recipient route. Conditional routing must be enabled for the account; 200 rules and 20 criteria per rule documented. Global capability evidence; local plan availability and interface language are not inferred.

Official documentation Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source
Not verified0–2.5 / 2.5 pts
Evidence

This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan.

Not verified Β· Oct 21, 2026Source

WHAT WE MEASURE

The criteria behind the score.

The established 20 checks contribute 80 points. Eight new operational checks contribute 20 points. AI checks are included in their own group and are excluded when AI priority is set to zero. These assess documented capability scope, not measured performance. Adjust group priorities in the comparison tool.

See the complete calculation β†’
  1. Send, sign & track 24%

    The core signing experience must work for recipients and senders.

  2. Audit trail & verification options 20%

    Completion records, authentication and export support a controlled workflow.

  3. Templates & approvals 16%

    Repeatable documents and routing reduce preparation effort.

  4. Business-system integration 8%

    CRM, storage and API connections reduce duplicate data entry.

  5. AI document assistance 12%

    Differentiate summarization, drafting and agreement-management actions.

  6. Operational detail 20%

    Specific workflow, integration and control checks beyond the established rubric.

THE PRACTICAL BUYER’S GUIDE

How to choose electronic signature.

Electronic signature purchasing starts with the document workflow, not a claim that every product makes every agreement legally sufficient. A freelancer sending a few agreements needs different capabilities from a team generating proposals from CRM or managing approvals before signature. Compare sender seats, envelopes or documents, templates, authentication options, audit evidence and export. AI summaries can speed orientation, but should not replace reading important terms or professional review. Keep contract drafting, signature collection and post-signature management separate in your requirements so the quoted plan covers the tasks you actually need.

Count transactions using the vendor's unit

Write down how many documents, recipients and signing requests you send in an ordinary month and in a busy month. Then translate that usage into each vendor's definition of an envelope, document or transaction. A package containing several files may count differently from several separate requests. Confirm what happens when a request is voided, resent, sent in bulk or generated through an API. Compare annual allowances with monthly limits, and include the cost of adding senders. A generous headline allowance is less useful if the specific workflow uses a separately metered automation or integration.

Demo the full approval and evidence chain

Start with a document generated from a template, send it for internal approval, request a recipient correction and complete the signature. Export the signed file and the completion evidence to the repository where your team will keep them. Check who can alter templates, view agreements, resend a request or change the recipient. Ask which identity checks are available and which cost extra. Do not infer suitability for a regulated or unusual transaction from a general e-signature statement. Have your own legal or compliance owner decide the required process, then use the demo to verify the software can implement it.

Separate document AI from agreement execution

Ask the assistant to summarize a sample agreement and identify where each answer came from. Then test a changed date, an inconsistent price and a clause it cannot confidently interpret. If the product can create or send documents through an AI integration, inspect the permissions and confirmation step before a real recipient receives anything. Keep AI drafting, field detection, document search and post-signature obligation extraction as separate checklist items. Verify whether the feature belongs to the e-signature plan, a broader agreement-management product or an external AI subscription. Human approval remains essential for commitments.

What changes the total cost?

  • Sender licenses, envelope or document allowances and annual commitment.
  • Bulk sending, API transactions, identity verification, SMS and workflow automation.
  • Document-generation, CRM, agreement repository and AI product tiers.

Where purchases go wrong

  • Equating unlimited manual signatures with unlimited API or automated transactions.
  • Assuming an AI summary is a complete or authoritative interpretation of an agreement.
  • Purchasing a basic signature plan while expecting a full contract-management platform.

Bring these questions to the demo

  • What counts as one billable transaction in our actual workflow?
  • Can we export both the completed document and its audit evidence?
  • Which approvals, identity checks and integrations need an upgrade or credit?
  • What can the AI read or send, and where does a person confirm the action?

Questions buyers ask

Is an e-signature tool the same as contract management?

No. Signature collection is one stage. Drafting, negotiation, internal approval, searchable repositories and obligation tracking may belong to separate products or higher plans. Write down the complete lifecycle and compare the relevant modules rather than the vendor name alone.

Are AI summaries safe to rely on for a contract decision?

Use them to navigate the document, then verify the underlying language. A summary can omit context or misinterpret a term. The comparison evaluates documented assistance, not legal judgment, and important commitments still require appropriate human review.

How do I compare a cheap plan with an unlimited plan?

Calculate the cost for your real senders and workflows. Check annual versus monthly limits, bulk and API rules, templates, authentication and export. An unlimited manual workflow may still have separate charges for automation or recipient verification.

Research sources

  1. Docusign eSignature allowances
  2. PandaDoc pricing and automation
  3. Dropbox Sign plans
  4. Zoho Sign features and credits
  5. Adobe business plans

Your privacy choices

Optional Google Analytics runs only with your permission. Your saved shortlist stays in this browser.

Read the privacy policy