Engineering11Engineering11 rooms
Deal rooms

Deal rooms & e-signature

A deal room is a room per client or prospect where you generate contracts, SOWs and NDAs, send them for e-signature, and track who has signed — all in the browser, with no account for the other side. When everyone has signed, you get a signed PDF and a certificate of completion.

Turn it on (admins): create a room and choose the Deal room type — or tell Claude "make a deal room for Acme." A deal room is best kept per counterparty (one room = one client/prospect), since everyone you invite to sign can open that room.

What's in a deal room

Instead of ordinary documents, a deal room holds agreements — each one a contract typed as an NDA · MSA · SOW · Order form · Custom. You author the agreement the same way you author anything here (describe it to Claude), then add the parties who must sign.

Templates — write a contract once, reuse it

Author your standard contracts once and reuse them across every deal: Standard MSA, Standard MNDA, Standard License Agreement, and so on. Manage them in the app under Templates (or ask Claude), then start any new agreement from a template — it fills in the contract and type, and you just add the counterparty.

"Save this as our Standard MNDA template."
"In the Acme deal room, create an NDA from our Standard MNDA template for pat@acme.com."
No blanks in a contract. An agreement must be complete before it can be saved or sent — the system rejects any unfilled placeholder (a [TOTAL FEE]-style bracket) or open item (TODO, TBD). So when you ask Claude for a contract, it will ask you for the actual terms first — the fee, payment schedule, dates, and governing state — and fill them in, rather than handing you a document with holes. (Reusable templates may keep their fill-in blanks; the real agreement you create from one may not.)

The signing flow

  1. Draft — create the agreement (from a template or fresh). It's private — nobody can see it yet.
  2. Send for signature — this publishes it to the parties and sends each of them a link (a Slack DM for people in your workspace when Slack is connected, email otherwise — counterparties always get email). They open it and sign in with their work email + a one-time code — no account, no password.
  3. Sign — each party reviews the agreement, consents to sign electronically, types their name, and signs — right on the page. Signing is multi-party, any order; everyone listed must sign.
  4. Executed — the moment the last party signs, the agreement is fully executed. A signed PDF and a certificate of completion are generated and everyone is emailed.
"Send the Acme MSA for signature."
"Remind whoever hasn't signed the Acme MSA yet."

Track it all in the app: open the deal room to see each agreement's status (draft → sent → viewed → partially signed → executed), who has signed, and buttons to View, Send, Sign, Remind, or Void. Someone can also decline (with a reason) instead of signing.

Read it before you send it. A draft agreement is private — it isn't published anywhere yet — so use View on its row to read the full contract right in the console (or ask Claude to "show me the draft") and check every term before it goes out for signature.

The signed PDF & certificate of completion

On full execution you get two PDFs, downloadable from the agreement's Details:

  • The executed agreement — a clean PDF of exactly what was signed.
  • The certificate of completion — every party, their email, when they signed, the intent and consent they affirmed, their IP, and a SHA-256 hash of the signed document that proves it hasn't changed.

Need the full evidence file? Download the compliance record (a complete JSON of parties, signatures, consent, and the audit trail) from the agreement's Details, or ask Claude for it.

Why you can trust it — immutability, storage & audit

Everything about a signed agreement is built so you — and the other side, and an auditor later — can rely on it:

  • Tamper-evident by cryptographic hash. Each signature is bound to a SHA-256 fingerprint of the exact bytes the signer saw, and execution locks a final hash. If a single character of the signed document were ever changed, the fingerprint wouldn't match — so any alteration is provable, not hidden.
  • Immutable once signed. An executed agreement is locked: it can't be edited, re-sent, or voided, and the signed content is kept as a permanent, read-only snapshot. What was signed stays exactly as it was signed.
  • Verified signer identity. Every party confirms a one-time code sent to their work email before they can open or sign. Each signature is attributed to that verified identity, with a timestamp and IP address — you always know who signed, and when.
  • Affirmative consent & intent. Before signing, each person ticks a box consenting to sign electronically and confirms their intent to be bound. Both statements are captured on the certificate — the legal backbone of an ESIGN/UETA signature.
  • Complete audit trail. Sent, viewed, signed, declined, executed — every event is recorded with who and when, and appears on the certificate of completion and in the downloadable JSON record.
  • Secure, access-gated storage. The signed PDF, the certificate, and every version snapshot are stored in your company's own encrypted object storage behind the same sign-in wall as your rooms — only the agreement's parties and your room editors can open or download them. Nothing is public and nothing is shared with a third-party signing service.
  • Always retrievable. You can re-download the signed PDF, the certificate, and the full JSON evidence at any time from the agreement's Details — the record doesn't live on someone else's platform that could lock you out.

Is this a legally valid signature?

Deal rooms produce electronic signatures under the U.S. ESIGN Act and UETA: each signer affirmatively consents to sign electronically and intends to sign, their signature is attributed to their verified email, it's bound to the exact document by hash, and the whole event is recorded in an audit trail and certificate. This is not a "qualified" electronic signature under the EU's eIDAS (which needs a trust-service provider), and this isn't legal advice — if you operate somewhere with specific requirements, confirm it fits your needs.

The counterparty never installs anything or creates an account — they open a link and confirm their email with a one-time code. Everything they sign is gated by that verified identity, which is what makes the signature meaningful.