# Sales contracts that send themselves

The gap between a verbal yes and a signed order form is where deals cool off. Automation can close it, as long as a rep still sees the exact draft before the customer does.

## Why speed and review pull apart

Sales teams want the contract out in minutes. Legal wants nobody improvising on terms. Usually one side wins. A draft made by software and approved by a person gets you both, because the rep isn't typing and the rep still looks.

## The flow

1. A deal moves to closed-won in your CRM, or a row turns ready in [Clay](/integrations/clay).
2. A workflow fills the order form as a PDF, with tags for the buyer and your signer.
3. It calls `create_document` with both signers, `ordered` set to true, and the deal ID in `metadata`.
4. The rep gets an `approval_url`, reads the draft and approves.
5. The buyer signs, then your signer. Each is emailed in turn.
6. `document.completed` updates the CRM and files the sealed PDF.

## Where it pays off

Keep a person in the loop for non-standard deals. For a low-value self-serve plan with fixed terms, a direct key can send with no approval. You can run both from one account with two keys.

Reminders are a call away too. `remind_signers` emails anyone who hasn't signed, up to three times a day per document, so no rep has to write the nudge.

## Common questions

### Can the buyer sign without an account?

Yes. They open the link in their email, read the document and sign. There is nothing to install or sign up for.

### What if the buyer's legal team wants changes?

Void the document and create a new one. A sent document can't be edited, and that protects both sides. The record shows the old one was voided.

### Can our side countersign automatically?

No. Every signer signs for themselves, including your own. A person on your team gets a link just like the buyer, and with `ordered` they get it second.