How to choose electronic signature software: a practical checklist
Every electronic signature product looks the same in a demo. Upload a PDF, drag a signature field, press send, watch the document come back signed. Seen from that surface, there is almost nothing to choose between a 9 € plan and a 456 € per-user-per-year contract. The real differences live in two places the demo never shows: the invoice after twelve months, and the evidence file you hand to a court when someone denies having signed.
This guide is the checklist we wish more buyers used. It works through documents, legal evidence, pricing mechanics, workflow features, hosting, integrations and a concrete evaluation process, naming the traps along the way. We build Signatuz, an e-signature platform, so we are not neutral — but every check below applies to any vendor, including us.
Map your documents before you look at tools
Start with an inventory, not a shortlist. Write down every document type your organisation signs — sales contracts, NDAs, employment contracts, service agreements, consent forms, mandates — and answer four questions for each:
- Volume: how many do you send per month, and how much does it swing with the season? Your choice of pricing model depends almost entirely on this number.
- Signers: employees, clients, suppliers or the general public? External signers need a flow that works without accounts or app installs.
- Identification: is an email link enough, do you want a one-time SMS code, or do you need identity documents verified?
- Assurance level: does the document need a simple, advanced or qualified electronic signature under eIDAS?
That last question does the most work. eIDAS defines three levels — simple (SES), advanced (AES) and qualified (QES) — with rising requirements for identity binding and tamper evidence. Most everyday business documents are perfectly served by SES or AES; QES, which is legally equivalent to a handwritten signature, is required only in specific cases. Our guide to the three signature types explains which documents typically need which level. Classify your inventory first and you will know immediately whether you are shopping for a simple tool or a qualified trust service.
Legal validity lives in the evidence, not the logo
Under eIDAS, an electronic signature cannot be denied legal effect solely because it is electronic — Article 25 says so in plain terms. What actually decides a dispute is the quality of the evidence: can you prove who signed, that the document has not changed since, and how the process ran? When you evaluate a vendor, ask to see the evidence package for a completed document and check it against this list:
- A sealed final PDF whose integrity can be verified — any change after signing must be detectable.
- Trusted timestamps, ideally RFC 3161 tokens from a time-stamping authority, proving when each event happened.
- A complete audit trail: every view, consent and signature, with IP address and device data.
- A record of the identification steps each signer passed — email access, one-time SMS code or identity document checks.
- A signature certificate that packages all of the above into something a lawyer can read.
The legal weight of that package is not academic. In Spain, for example, Ley 6/2020 and Article 326 of the civil procedure law govern what happens when an electronic document is challenged: where a non-qualified trust service was used, the burden of proving authenticity falls on the party relying on the document. A thorough audit trail is what turns that proof into a formality rather than a problem. We cover the mechanics in more depth in our guide to legal validity and in electronic vs digital signatures.
Pricing models decide your real cost, not headline prices
Two structural choices matter more than any listed price: whether you pay per user or per organisation, and whether sends are metered. Per-user pricing suits a small team of heavy senders; it punishes the far more common case where many people send occasionally, because every extra seat costs the full rate. Per-organisation pricing — one flat price for the whole company — favours exactly that occasional-sender pattern. Signatuz prices per organisation, which is worth knowing as you read this section, and worth comparing directly against per-seat quotes.
Then come the meters. DocuSign's Standard and Business Pro plans cost 23 € and 38 € per user per month billed annually and include 100 sent envelopes per user per year — an envelope counts once sent, signed or not (published pricing at the time of writing). SignNow's and Adobe's team plans carry similar annual send allowances, in some cases with per-envelope overage fees. One-time SMS codes are often metered separately or sold as add-ons. None of this is hidden, strictly speaking, but none of it appears in the headline price either.
| Pricing model | Scales with | Watch for | Typical fit |
|---|---|---|---|
| Per user | Number of seats | Envelope allowances per user; the cost of occasional senders | Small teams of heavy senders |
| Per organisation | Nothing — flat rate | Document or SMS quotas on lower tiers | Many occasional senders across a company |
| Per envelope or credits | Volume sent | Credits that expire; overage fees | Low or unpredictable volume |
| Enterprise quote | Negotiation | Renewal increases; opaque comparisons | Large, regulated deployments |
Run the arithmetic on your own numbers. Ten people who each send a handful of contracts a month cost 2,760 € a year on a 23 € per-seat plan, before any overages; on a flat per-organisation plan such as Signatuz Business — 25 € per organisation per month billed annually, with unlimited documents, users and SMS codes — the same team costs 300 €. The comparison will not always fall that way: a single heavy sender may do better per seat. That is precisely why you model it before signing, and why our comparison of DocuSign alternatives looks at total cost rather than sticker price.
Workflow features are where the daily time goes
Legal evidence decides the worst day; workflow features decide every other day. The gap between tools is wide here, and vendors gate these features across tiers very differently. Mark which of these your team actually needs, then confirm which plan carries them:
- Reusable templates with variables — prepare a contract once, then fill names, dates and amounts per send instead of editing PDFs.
- Bulk sending — one template to hundreds of recipients, each receiving their own document.
- Sequential and parallel routing — signer B after signer A where order matters, everyone at once where it does not, with approval steps before anything goes out.
- Reminders and expiry — automatic chasing and clean expiry dates, because without them the default fate of a document is to sit unsigned.
- Shareable form links — a public link where anyone can complete and sign, useful for consents and onboarding.
- Organisation and permissions — folders, team spaces and role-based access once more than three people use the tool.
Template limits deserve particular attention: several vendors cap their cheaper tiers at five or fifteen templates, which quietly breaks template-driven working. See how Signatuz templates handle variables and form links if you want a reference point for what to ask other vendors.
Security and hosting: ask where the documents actually live
For a European organisation the questions are concrete: where is customer data hosted at rest, is the vendor GDPR-ready with a proper data processing agreement, and is EU residency available on the plan you can afford — with some vendors an EU region exists but is reserved for top or enterprise tiers. Residency is also not the same as jurisdiction: a US-headquartered provider remains subject to US law wherever the servers sit, which some compliance teams care about and others accept.
Then look inward: role-based access so the sales team cannot open HR contracts, revocation for documents sent in error, and SSO if your organisation requires it. Signatuz hosts customer data on EU infrastructure and is built around the GDPR — the details are on our security page — but whichever vendor you choose, get the hosting answer in writing before procurement, not after.
Integration and API: check the tier, not the feature list
If signatures need to flow into a CRM, an ERP or your own product, the questions are: is there a REST API, are there webhooks for real-time status, and — critically — which plan includes them. Several major vendors sell API access as a separate product or reserve it for sales-led tiers, and third-party pricing trackers report four-figure annual prices for premium API access. A generous feature list means little if the API sits two tiers above your budget.
Ask for the API documentation before you buy and judge it as you would any dependency: authentication, sandbox availability, webhook reliability, rate limits. Signatuz includes the REST API and webhooks on the Business plan at 25 € per organisation per month; wherever you land, insist on knowing the all-in price of the integration you actually plan to build.
A concrete evaluation process
You can settle this in two weeks with a process instead of a feeling:
- Shortlist three vendors that match your assurance levels and pricing model — not ten; three you can genuinely test.
- Run a real document through each free plan or trial, with real fields and a real colleague as signer, not the vendor's demo PDF.
- Test the signer experience on a phone, because that is where many of your clients will sign. Count the taps, and watch for forced account creation or app installs.
- Download and inspect the evidence PDF: audit trail, timestamps, identification records — and whether any of it is gated behind a higher tier.
- Model the twelve-month cost at three times your current volume, including extra seats, envelope overages, SMS fees and API access — growth is exactly when metered pricing bites.
Red flags worth walking away from
Any one of these is a reason to look harder; two or more are usually a reason to leave:
- Prices only revealed on a sales call. If a vendor will not publish numbers, budget for the numbers to move at renewal.
- Per-user pricing for a team of occasional senders. You will pay the full rate for seats that send twice a month.
- Evidence or audit trails locked behind higher tiers. The proof of who signed is the product; it should never be an upsell.
- No straight answer on EU hosting. If two emails cannot establish where your documents rest, assume the answer is one you would not like.
Frequently asked questions
Do most business documents need a qualified signature (QES)?
No. Under eIDAS, simple and advanced signatures have legal effect and are admissible as evidence, and Article 25 forbids rejecting a signature solely for being electronic. QES is legally equivalent to a handwritten signature and is required only in specific cases — check which types of signature your documents actually need before paying for qualified infrastructure.
What is the difference between an electronic and a digital signature?
An electronic signature is the legal concept: data used with the intent to sign. A digital signature is the cryptographic technique, based on certificates and hashes, that many platforms use underneath to make tampering detectable. Our comparison explains how the two relate.
Is per-user pricing always the wrong choice?
No. A small team where every member sends heavily can do well per seat. It becomes expensive when many people send occasionally, because each seat costs the full rate whether it is used or not — that is the pattern where per-organisation pricing usually wins. Model both against your real volume before deciding.
What should the evidence file of a signed document include?
A sealed PDF whose integrity is verifiable, trusted timestamps, the full audit trail with IP and device data, a record of the identification steps each signer passed, and a readable signature certificate. Download one from every vendor you trial and compare them side by side.
Can I switch providers later without losing my signed contracts?
Completed documents remain valid: the sealed PDF and its evidence stand on their own once downloaded. Before switching, export all signed documents with their audit trails, and budget time to rebuild templates and workflows — that rebuild, not the legal side, is the real switching cost.
