Signed, and able to prove it

An e-signature product is only worth anything at the moment it is questioned. So the parts that matter are the boring ones: who signed, when, from where, and whether the file you are holding is genuinely the signed one. All three are built in, and the third is enforced rather than trusted.

Templates with real fields

A template carries the fields to fill and the roles that must sign, so the same agreement is not rebuilt by hand each time.

  • Signature, initial, date, text and checkbox fields
  • Required signer roles per template, each field bound to one of them
  • Send now, or keep a reviewable draft first

The signer needs no account

Signing happens at a token link. Making a customer create an account before they can sign is how deals stall on a Friday afternoon.

  • A public signing link per signer, no login
  • Sign or decline, with the decline reason kept
  • Status per signer — pending, viewed, signed, declined — not one flat state

Proof, enforced rather than promised

The signed document and the audit certificate are separate artefacts, and the signed copy is not downloadable until it is actually signed.

  • The signed-copy download refuses until the document is signed
  • An audit certificate: who signed, when, and from which IP, in order
  • The certificate is the artefact that makes a signature defensible in a dispute

What Documents & e-signature runs on

Hold this on its own, or add the modules beside it when you want them — they share one login and one set of records. See the module library and pricing.

  • Documents & E-Signature
  • CRM
  • Field Service
  • Property
  • Finance

Questions buyers ask

Do the people signing need an account?

No. Each signer gets their own token link and can sign or decline without logging in. The signed copy lands back on the record the document belongs to rather than in someone's inbox.

Can we prove who signed if it is challenged?

There is an audit certificate recording who signed, when, and from which IP, in order — a separate artefact from the signed document itself. That is deliberately not optional, because a signature is otherwise only as good as somebody's word for it.

Can someone download a document before it is signed and pass it off as signed?

No — the signed-copy download refuses until the document is actually signed. It is a server rule, not a hidden button, which is the difference between a safeguard and a convention.

Is this legally binding?

We describe what the artefacts are — the signed document, the per-signer status, and an audit trail with time and IP — and let your counsel judge them against your jurisdiction. We deliberately do not claim qualified or eIDAS-advanced signatures, or notarisation, because we have not built those.

See it running

Create an account, or tell us how you work today and we'll show you what Documents & e-signature looks like on your data.