Signature request
One document, one or a few signers: contracts, NDAs, offers, authorizations.
Signing and verification
Sigil collects signatures on a PDF, seals the finished file, and leaves a path to verify that what you are holding is what was signed.
Most signing tools stop at “everyone clicked.” That is enough for an informal agreement. It is not enough when a client, an auditor, or your own team two years later needs to know whether the PDF in front of them is the one that was completed.
Sigil is built for that second moment. The signer does not need an account. You need, afterwards, not to argue about versions.
How it works
Upload a PDF, place fields — signature, date, text, completion stamp, verification code — and invite signers by email.
On completion, Sigil produces the document with signatures applied and a tamper-evident trail.
A verification link, or upload the PDF. The file is compared with the one kept at completion. No phone call required.
Send modes
One document, one or a few signers: contracts, NDAs, offers, authorizations.
The same PDF and field layout to many people. Each recipient gets their own link.
Many personalized PDFs signed by the organization. The holder receives a copy: certificates, credentials, reports.
The employer signs the batch. The employee records agreement or disagreement. Built for Argentine payroll practice, not a generic flow.
HR, law firms, commercial teams, and organizations that issue certificates and later have to prove the file was not altered. If the job ends at “sign and return,” Sigil is built so that is routine — and demonstrable.
There is an API and assistant integration (MCP) for teams that no longer want to live in the dashboard. The same scopes and the same sealed PDF as in the interface.
When the document is a step inside a case file, Praxis carries the procedure across departments and Sigil seals what must remain signed. You do not have to use both. They are designed not to overlap.