
How to evaluate eSignature providers without getting lost in feature lists
Every eSignature vendor publishes a feature page, but features are not the same as fit. The questions that decide a procurement outcome are structural: which compliance regimes actually apply to you, how the platform proves the integrity of a signed record, what happens to your data, and what the total cost looks like as volume grows. This guide gives you an 8-dimension scorecard — compliance, identity assurance, evidence and audit trail, API and integration, data residency, support and onboarding, pricing model, and migration — with key questions, red flags and suggested weights. Copy the table into your procurement doc, score shortlisted vendors 0–2 per item, and compare totals. No vendor wins every dimension; the goal is a defensible, documented decision.

The 8-dimension vendor scorecard
| 1. Compliance (20%) | Certifications and assessments (ISO 27001, SOC 2 Type II) plus evidence mapped to the regimes that apply to you — e.g. 21 CFR Part 11, HIPAA, eIDAS QES, GDPR | Which regimes are you assessed against? Can you share audit reports and the scope of each certification? How do you support QES where required? | Generic “fully compliant” claims with no named standard, no scope, and no evidence |
|---|---|---|---|
| 2. Identity assurance (15%) | Range of identity methods: SMS, knowledge-based, government ID, national eID, QES-grade identity | Which methods do you support and in which countries? Is identity verification included or an add-on, and at what cost per signer? | No published identity options, or identity priced as a surprise per-transaction fee |
| 3. Evidence & audit trail (15%) | Computer-generated, time-stamped audit trail of every action; tamper-evidence; exportable evidence package | How is the audit trail generated and stored? Who can modify it? Can we export a complete evidence file and verify it independently? | No audit trail, or trail that cannot be exported or verified |
| 4. API & integration (10%) | REST API, webhooks, SDKs, maintained connectors for CRM/ERP (Salesforce, SAP, etc.) | What are the API rate limits and sandbox terms? Which connectors are maintained by the vendor rather than the community? Is API access on the standard plan? | API on a separate negotiated plan, no public documentation, no sandbox |
| 5. Data residency (10%) | Where documents and metadata are stored and processed; region pinning; sub-processor transparency | Which regions can we choose? Can data be pinned to a specific region? Who are your sub-processors and where do they process data? | Single region only, no residency options, no sub-processor list |
| 6. Support & onboarding (10%) | Support SLA and channels, onboarding program, training, time-to-value | What is the support SLA? Who runs onboarding and how long does it take? Is training included? | No published SLA, self-serve only, no onboarding path |
| 7. Pricing model (10%) | How cost scales: per-user subscription, per-envelope, API volume, enterprise custom; identity and add-on fees | What drives cost as volume grows? Which fees are separate (identity, SMS, API)? Is annual billing required? What is the renewal increase policy? | Unpublished pricing, opaque per-transaction fees, long lock-in without price protection |
| 8. Migration & exit (10%) | Export of completed documents, templates, contacts and audit data; exit terms | How do we export all completed documents and evidence? Is there a documented exit process and data-deletion timeline? | No self-serve export, data hostage risk, punitive exit terms |
A five-step evaluation process
1. Fix the scorecard and weights before seeing demos. Agree the dimensions and weights with procurement, security and legal first. Weights above reflect a typical mid-to-large enterprise; regulated industries should shift weight from pricing toward compliance and audit trail. 2. Run security and legal review on evidence, not slides. Request audit reports (SOC 2 Type II, ISO 27001), the sub-processor list, DPA terms, and regime-specific evidence (e.g. Part 11 feature documentation, QTSP status for QES). A vendor that cannot share evidence fails regardless of demo quality. 3. Script a hands-on POC before signing. Give every shortlisted vendor the same scenarios: a multi-signer document, an approval chain, an identity-verified signature, a bulk send, and an audit-trail export. Score outcomes against the scorecard, not against the demo script the vendor chose. 4. Check support and reference accounts. Ask for 2–3 reference accounts in your industry or region and verify onboarding time, support responsiveness and renewal behavior. Support quality is the most common post-sale complaint in eSignature procurement. 5. Contract the exit before the entry. Put export commitments, data deletion timelines, renewal caps and migration assistance in the contract. The cheapest vendor is expensive if your signed records are locked in.
How providers handle audit trails
Audit trails are the core evidence of a valid eSignature. Under 21 CFR Part 11 (FDA), regulated electronic records require “secure, computer-generated, time-stamped audit trails” that independently record the date and time of operator entries and actions that create, modify or delete records. Outside regulated sectors, the same principle applies commercially: a defensible trail records who, when, what and in what order — and it must be tamper-evident and exportable. When comparing vendors, ask to see a real evidence package: the signer identity method used, the document hash or fingerprint, the timestamping mechanism, and the complete event log. If the vendor cannot show you the actual file format a court or auditor would receive, the trail is not yet a deliverable.
Pricing models compared
| Per-user subscription | Flat fee per seat per month/year | Predictable for small teams with steady volume | Pays for seats that never sign; scales poorly for high-volume automation |
|---|---|---|---|
| Per-envelope / per-transaction | Cost per sent envelope or per completed signature | Variable volumes, seasonal spikes, low seat counts | Identity and SMS fees stack on top; hard to budget at scale |
| API / volume pricing | Tiered pricing by API transactions or annual envelope volume | Embedded signing, high automation, batch operations | Volume cliffs can surprise; confirm overage and renewal terms |
| Enterprise custom | Negotiated contract with SSO, admin and custom terms | Large organizations with security and compliance needs | Opaque pricing; require price protection and clear add-on list |
Provider landscape: where the majors stand (2026)
| DocuSign | Certifications: SOC 2 Type II and ISO 27001 (trust center) | Regulated depth: Life Sciences Module + Part 11 Validator (official) | QES: offering with AI-driven identity proofing (official) | Fit: enterprise generalist; broad connectors; regulated add-ons sold separately |
|---|---|---|---|---|
| Adobe Acrobat Sign | Certifications: SOC 2 Type II and ISO 27001 (trust center) | Regulated depth: 21 CFR Part 11 Validation Package (official helpx) | QES: via approved digital-ID trust list; PAdES default on EU1 shard | Fit: PDF-native workflows; validation templates for life sciences |
| Dropbox Sign | Certifications: SOC 2 Type II and ISO 27001 (Dropbox trust center) | Regulated depth: no dedicated Part 11 program found in this review | QES: no offering found | Fit: value and API play; SharePoint integration discontinued Mar 2026 (third-party report); 2024 security incident reported (public sources) |
| PandaDoc | Certifications: SOC 2 Type II (official) | Regulated depth: no Part 11 validation package found | QES: eIDAS-compliant signing; no QES issuance found | Fit: sales and procurement documents; strong CRM workflows |
| eSign.AI | Certifications: SOC 2 Type II report available on request (official blog) | Regulated depth: confirm current Part 11 documentation before regulated use | QES: QES/QSeal documented in official trust resources | Fit: global-local hybrid; data residency and China PIPL focus |
Use the full scorecard when
- You are selecting an enterprise platform for multiple teams or regions
- Regulated records (FDA, HIPAA, eIDAS, financial services) are in scope
- You will integrate signing into CRM, ERP or your own product
- Documents contain personal data with residency or transfer constraints
- You need to defend the decision internally or to an auditor
A lighter process is fine when
- A single team signs a few document types with no integration
- You already know the shortlist and only need to confirm one dimension (e.g. price)
- You need a quick capability check, not a formal procurement — use the 22-point checklist instead
Frequently asked questions
It depends on security review, legal scope, integrations, procurement gates and POC complexity. A focused 2–4 week evaluation is realistic for most mid-market teams; regulated or multi-region procurement usually runs 6–12 weeks. Agree on evidence requirements and test scenarios first, then set milestones from that plan.
Information reflects publicly available sources as of 2026-08-18 and may change. Vendor certifications, features and pricing should be verified against current official documentation before procurement decisions. This content is informational and not legal advice.








