Skip to main content

Using Your Own Contract in Common Paper

Three ways to use a contract you wrote elsewhere: keep your own wording as an editable Custom Agreement, rebuild it on the Common Paper Standard Terms with Claude, or upload a final file for signature.

Written by Mark Frantz

If you have a contract written somewhere else - a Google Doc, a Word file, a PDF from your lawyer - there are three ways to use it in Common Paper. Which one fits depends on whether you want to keep your own legal language, and whether you'll need to edit it.

Choose an approach

  • Keep your own wording and manage it in Common Paper: use a Custom Agreement. Your contract's legal language becomes your Terms, and the details that change from deal to deal become a Cover Page your team fills out. You can edit and version the Terms, and you send, negotiate and sign these agreements like any other Common Paper agreement.

  • Move to the Common Paper Standard Terms: convert it with Claude. Claude maps your business terms onto a Common Paper Standard Agreement, and the Standard Terms replace your legal language.

  • Send a finished document as-is: upload it. Common Paper collects signatures on the file, but you can't edit its text inside Common Paper.

Keeping your own wording with a Custom Agreement

A Custom Agreement has two parts: your Terms, which hold the legal language, and a Cover Page, which holds the details that vary from deal to deal, like the parties, fees and dates.

  1. On the Templates page, click Add new template and choose Set up a custom agreement under Write your own.

  2. Click Create new Terms below the Terms dropdown. Paste your contract's legal text into the Terms editor, so you can edit it in Common Paper later. If the language is final and you won't need to edit it, you can click Upload a set of terms and upload the file instead.

  3. Build the Cover Page with fields for the details that change from deal to deal, and save the template.

Then create agreements from it with Create or import an agreement, the same way as any other template. See Custom Agreements, Your Terms and Custom Cover Pages for the details.

If Claude is connected to Common Paper, it can set this up for you. Ask it to copy your legal language into the Terms exactly as written and to move only the deal-specific values onto the Cover Page.

Converting to the Common Paper Standard Terms with Claude

Claude can read your contract and build a matching Common Paper template. It pulls out the business terms and fills in the Cover Page fields for the agreement type you choose.

This is a starting point, not a conversion. Common Paper Standard Agreements use hosted Standard Terms written by a committee of attorneys. Your business terms carry over into the Cover Page, but your legal terms are replaced by the Common Paper Standard Terms. The result is a new agreement with similar commercial deal points, not a reproduction of your old contract. Read the whole thing before you send it.

If you need to keep your own legal language, use a Custom Agreement instead, as described above.

What you need

  • The Common Paper MCP server or Claude Skill connected to your account. See Common Paper and LLMs for setup.

  • Your existing contract as text, DOCX, or PDF. For a Google Doc, use File > Download > Microsoft Word (.docx), or just paste the text.

  • A sense of which Common Paper agreement type fits. If your contract covers ongoing access to a SaaS product, that's a Cloud Service Agreement. If it covers a short paid trial, you can either use a Pilot Agreement or use a CSA with a pilot (the Pilot row in CSA 3.0, or Pilot Period in CSA 2.x). See Agreement Types in Common Paper.

Building the template

Give Claude the contract and tell it what you want. A prompt like this works:

Read the attached contract. Build a Common Paper CSA template from it. Map the business terms - product description, fees, term, liability caps, governing law - to the Cover Page fields. Tell me which terms in my contract have no matching field, and don't guess at anything the contract doesn't say.

The last sentence matters. Without it, Claude will fill gaps with reasonable-sounding values you never agreed to.

Claude creates the template in your account and reports what it mapped. Anything in your contract that has no Cover Page field can go into Additional Changes, which is free text that appears in the agreement. Ask Claude to put your success metrics, custom obligations, and other bespoke terms there.

Reviewing the template

Open the new template in Common Paper and read every section before you use it. A generated template is fully populated, not sparse. Every field you didn't specify has a Common Paper default in it, and defaults are real terms once the agreement is signed.

NOTE: Liability and indemnification defaults are the highest-risk part of this workflow, because they are plausible, invisible, and legally significant. If your contract capped liability at a fixed dollar figure, verify that figure appears in the template rather than a multiplier.

Ask Claude to read the created template back to you and compare it against your original contract. That catches most gaps faster than reading the form yourself.

What doesn't carry over

  • The wording of your original contract. Standard Terms replace your legal language entirely. To keep it, use a Custom Agreement.

  • Terms with no Cover Page field. These are dropped unless you put them in Additional Changes.

  • Attachments and exhibits. Add them separately as attachments to the agreement.

  • Signatures on an already-signed contract. Converting produces a new, unsigned agreement. To change the terms of a contract that is already signed, issue an amendment instead.

Uploading a finished document

If the document is final and you only need signatures, or the agreement is already signed and you want to store it, upload the file:

An uploaded file can't be edited inside Common Paper. See Editing an Uploaded Agreement. If you'll need to change the text later, use a Custom Agreement instead.

Learn more

Did this answer your question?