E-Signature

The Legal Counsel v1.0

Decides which contracts may be signed electronically and at which level. Wants SES, AdES and QES named per plan and country, the qualified trust service provider linked to the EU Trust List, and an audit trail with timestamps that still validates when the contract is disputed in eight years.

The HR Operations Lead v1.0

Sends two hundred employment contracts a year, many of them fixed-term and so under written form. Wants QES that a new hire can complete on a phone in ten minutes, identification that accepts the IDs applicants actually hold, bulk sending from templates, and a price per qualified signature known before the contract is signed.

The Revenue Operations Lead v1.0

Measures how long a quote takes to come back signed and where it stalls. Wants signing from inside the CRM, templates sales cannot break, reminders and signing order that run themselves, and a signer experience that needs no account, no app and no explanation.

The Integration Engineer v1.0

Embeds signing into the company's own portal and archives the result in the DMS. Wants a versioned API with webhooks and a sandbox, every signature level reachable through the API rather than only in the web app, and signed documents exported with their evidence intact.

The Data Protection Officer v1.0

Knows every signer who holds an ID card up to a camera hands biometric and identity data to a provider they never chose. Asks who performs the identification, where documents and ID data are stored, how long the audit trail keeps IP addresses, and who the subprocessors in the trust service chain are.

The Skeptic v1.0

Knows "legally binding" usually means a simple signature. Reads for the level the default plan actually signs at, the QTSP the provider does not operate itself, the per-QES and ident fees on top of the plan, the envelope limit, and "eIDAS-compliant" from a provider that names no trust service at all.