Most need one that survives a customer forgetting they agreed. Treating every document at the same assurance level either overspends on the ones that do not need it or underspends on the one that does.
Not "can you collect an electronic signature". It is what assurance level does this particular document need, and does your flow let you choose it per document rather than per contract.
Envelopes for multi-party, multi-document flows.
Composer to build a signing document from a template rather than a one-off PDF.
Dashboard for status across every signature in flight.
Hash signing where the source document has to stay on your infrastructure and only its hash crosses the wire.
Simple and advanced assurance levels here, alongside qualified signatures for the documents that need the highest standard the law recognises.
An assurance level lower than the document warrants is a signature you have to defend later rather than one that defends itself.
Assurance level set by document type and by rule, the same mechanism the QES page describes.
The right assurance level per document avoids overpaying for signatures nobody will challenge and underdefending the one that gets challenged.
A trail of who signed, when, and at what level.
The same identity that establishes assurance for one document reuses for the next. Assurance level becomes a choice per document, not a re-registration every time.