Contracts & e-signatures

Create reusable contract templates, draft client-specific contracts with AI help, and collect legally binding e-signatures through a secure link — no account needed on the signer's side.

Who this is for

Anyone who sends agreements to clients, buyers, or partners: service agreements, scopes of work, insertion orders, NDAs. You need the contracts: read permission to open the page; creating needs contracts: create, editing contracts: update, deleting contracts: delete.

Where to find it

Go to Payments → Contracts. The page lists your contract instances (one per client/situation). Templates live separately and are picked when you create a contract — see below.

The lifecycle at a glance

Every contract moves through the same states:

1. DRAFT — you're still editing. Only your team can see it.
2. SENT — you've sent it to the recipient. They get an email with a secure signing link.
3. COMPLETED — the recipient has signed. Values are frozen as a snapshot (see below).
4. ARCHIVED — kept for reference, out of the active list.

If a sent contract needs changes, revert it to DRAFT first — this invalidates the old signing link so nobody can sign the outdated version.

Creating a contract

Select Create Contract. A picker offers two paths:

• Start from a template — browse your saved templates and create a ready-structured instance from one.
• Start blank — an empty document.

Either way the new contract starts as a DRAFT in the same folder as the source template (or at root).

Duplicating

From a contract's ⋯ menu, Duplicate copies it as a new DRAFT with a "Copy of" prefix — handy for repeat clients with small tweaks.

The builder

The builder is a rich-text editor with contract-specific building blocks:

• Text with formatting — headings, lists, bold/italic, the usual.
• Variables — dynamic placeholders like the client name, dates, or prices. Type / to see the slash-command menu, or open the variables sidebar to browse every available variable (lead fields, organization details, dates). Variables auto-replace as you type once recognized, and each shows as a pill with its label.
• Signature blocks — drop in where the recipient must sign.
• Input fields — short text boxes the recipient fills in before signing (company name, title, etc.).
• AI drafting — describe what you need in the AI chat and the content streams directly into the editor with a live typewriter effect. The AI can also extract variables from your text automatically.

Moving between contracts

Move (in the ⋯ menu) files a contract into a different folder. Folders themselves can be created, renamed, color-coded, nested, and moved from the folder controls.

Templates

A template is a contract marked as reusable — same editor, same blocks, but it is never sent directly. Instead, Create from template stamps out a fresh DRAFT instance with the template's content. Edit the template once and every future instance picks up the change; already-created instances are unaffected.

Templates show an ACTIVE status when published and ready to use.

Sending for signature

Open the contract and select Send. Enter the recipient's name and email. The platform then:

1. Generates a unique, unguessable signing link (a 32-character token).
2. Emails it to the recipient from your workspace.
3. Flips the contract to SENT.

Anyone with the link can open it — that is by design, so forward it carefully. Each send generates a fresh token; re-sending after a revert invalidates earlier links.

What the recipient sees

The signer opens a clean, read-only page — no login, no account:

1. The contract text with your variables already filled in (their name, your company, today's date, etc.).
2. Input fields rendered as real text boxes to complete.
3. Signature blocks they click to sign (typed name captured as the signature).
4. A signing toolbar that tracks what's left — signatures and required fields — and enables the final Sign button only when everything is complete.

After signing, the contract flips to COMPLETED and you are notified by email. Re-opening the link later shows the signed version with every dynamic value baked in — the numbers and dates are a frozen snapshot from signing time, so they can never drift afterward.

After completion

• Completed contracts are immutable. To amend terms, duplicate the contract and send the new version.
• Archive finished contracts you no longer need at hand; they stay retrievable.
• Signature notifications land in your inbox pipeline like any other outbound email, so replies and follow-ups stay threaded.

Troubleshooting

Problem	Likely cause and fix
Recipient says the link doesn't work	The contract was reverted to DRAFT (invalidates links) or archived. Re-send to generate a fresh link.
Variables show blank for the recipient	The variable has no value for that lead/organization. Fill a fallback value in the variables sidebar before sending.
Sign button stays disabled	A required input field or signature block is incomplete — the toolbar lists exactly what's missing.
Signed values changed later	They can't — COMPLETED contracts serve baked snapshots. If you see different numbers, you're looking at a different (duplicate) instance.

Related

• Payments — invoices, products, and orders that often accompany a contract.
• Plans, billing & wallet — how your own subscription and usage billing works.
• Automations — trigger follow-ups when contracts are sent or completed.