Documents & e-signature
Tenacap generates the paperwork your equity records imply — grant notices, SAFE agreements, RSPAs, and board consents — and signs them natively. You can also upload any PDF and send it for signature the same way. The signer gets a private link, no account needed, and you get back a sealed PDF with a completion certificate that records exactly who signed, when, and how.
A cap table is full of agreements waiting to happen: every option grant has a notice, every SAFE has a contract, every founder’s restricted stock has a purchase agreement. Tenacap draws each of these straight from the records you already keep, sends them for signature in the same window, and stores the executed result with a durable evidence trail. There’s no separate e-signature account and no copy-paste between tools.
Documents you can generate
Tenacap produces these agreements today, each merged from the underlying record so the numbers always match your cap table:
- Notice of Stock Option Grant — a one-page summary of an option grant: grantee, plan, type, shares, strike, dates, and the vesting summary.
- YC post-money SAFE agreement — the official Y Combinator form with your terms filled in. Recording and generating SAFEs is covered in SAFEs & convertibles.
- Restricted Stock Purchase Agreement (RSPA) — the founder purchase agreement that accompanies a restricted stock issuance.
- Board consent — the written consent that records a board approval, sent to every director for signature in one request.
- Stock Repurchase Agreement — a short-form buy-back agreement generated straight from a recorded repurchase transaction (parties, share class, quantity, price, total, and governing law), sent to the selling stakeholder to sign. Record the repurchase in the cap-table manage panel, then Generate & send repurchase agreement.
Send any document
Not every signature comes from a record on the cap table. From a company’s Documents tab you can upload any PDF, add one or more signers, and send it through the very same engine — private signing links, ESIGN/UETA evidence, and a sealed PDF with its completion certificate at the end.
This is the path for agreements Tenacap doesn’t generate for you, such as:
- side letters, amendments, and consents not modeled on the cap table;
- an externally drafted version of any agreement your counsel prepared.
Send for signature
From the document, choose Request signature. Tenacap hashes the exact PDF being presented — that hash is the anchor that proves nothing changed afterward — creates a signature request, and emails the signer a single-use link. If no email is on file, you can copy the link and share it yourself. The request inside Tenacap is the system of record, so a delivery hiccup never loses it.
What the signer sees
The signer opens the link and lands on a clean public page — no Tenacap account, no password. They see the document itself in the page, can open it in a new tab, and then complete two small steps:
- Consent — they check a box agreeing to do business electronically (E-SIGN / UETA) and confirming they are the named signer.
- Sign — they type their full name and click Sign.
Once signed, the page confirms it and they can close the tab. Each link is single-use and expires, so a stale or already-signed link shows a friendly message instead of letting anyone sign twice.
A signer can also decline instead of signing — a first-class outcome (it matters for a shareholder consent, where a holder may not approve). Declining records the same evidence as a signature, plus an optional reason. A request resolves to Completed once everyone signs, or Declined once everyone has responded and at least one person declined; the Shareholders view shows the approved / declined / pending tally.
The evidence recorded
Signing isn’t just a typed name — it’s a record built for the E-SIGN and UETA standards. With each signature Tenacap captures:
- the typed signature and the signer’s name and email;
- the moment consent was given and the moment the document was signed;
- a privacy-preserving hash of the signer’s IP address, plus their browser details;
- the document hash, binding every event to the exact PDF that was presented.
Each of these events is appended to Tenacap’s tamper-evident audit chain, so the evidence holds together as a sequence that can’t be quietly edited after the fact.
Sealed PDF & certificate
When everyone has signed, Tenacap seals the result: the signed document and a completion certificate are merged into a single PDF. The certificate lists the signers, their timestamps, consent, typed signatures, IP hash, browser, and the document hash — the whole evidence trail on one page. From the cap table you can download the signed PDF and the certificate any time after completion. Your admins are also emailed the moment a document is fully signed.