Compliance & Legal

How to send an nda from a template as Small Legal and Compliance Teams

Compliance & LegalFor Small Legal and Compliance Teams3 apps12 steps~24 min to set up

Your two-person legal team gets pulled into every NDA request from sales, BD, and partnerships — sometimes three in a single afternoon. The current process: someone emails you asking for an NDA, you dig through Google Drive to find the right template version, manually fill in the counterparty name and jurisdiction, attach it to a DocuSign envelope, chase the rep to confirm it went to the right signatory, then update a Notion tracker that's already three months stale. Each NDA takes 20-40 minutes of your time. Multiply that by the 8-12 NDAs your company sends per month and you're spending a full day every month on a document that shouldn't need you at all.

Build this on Starch → See the apps used

Compliance & LegalFor Small Legal and Compliance Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

A self-serve NDA workflow where sales fills out a short form, Starch populates the correct template, and the envelope goes out via DocuSign — without touching your inbox.

A live contract tracker that updates automatically when DocuSign envelopes are opened, signed, or declined, so your Notion tracker is never stale again.

An alert that flags NDAs that haven't been countersigned in 5 business days so you can chase without having to remember to check.

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Contract Lifecycle Management Email Agent Knowledge Management

Data sources & config

Starch syncs your Gmail data on a schedule (read and send), Starch syncs your Notion data on a schedule for the contracts tracker, Google Drive is connected from Starch's integration catalog and queried live when a template needs to be pulled, and DocuSign is connected from Starch's integration catalog so the agent can create and send envelopes live. Calendly is connected from Starch's integration catalog if you want signing-deadline scheduling. No browser automation required for this stack — everything runs through direct integrations.

Prompts to copy

Build me a form where sales reps submit counterparty name, signatory email, governing law (default: Delaware), and deal type. When submitted, pull the matching NDA template from Google Drive, fill in the counterparty fields, create a DocuSign envelope, send it to the signatory, and log the deal to my contracts tracker in Notion with status 'Sent.' Notify me on Gmail only if there's an error.

Every weekday at 9am, check my Notion contracts tracker for any NDA with status 'Sent' and a sent date more than 5 business days ago. Draft a follow-up email to the rep who initiated the request with the counterparty name and DocuSign link, and surface it to me in Gmail as a draft so I can send with one click.

Build me a dashboard that shows all NDAs sent in the last 90 days, their current DocuSign status, governing law, and counterparty — pulling from Notion. Flag any that are unsigned past the 5-day threshold in red.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect Google Drive from Starch's integration catalog and point it at your /Legal/Templates/NDA folder. Identify the 2-3 template variants you actually use (mutual, one-way, jurisdiction-specific) and confirm their naming convention.

2 Connect DocuSign from Starch's integration catalog. Confirm the sending account, default reminder schedule, and the envelope fields you need pre-populated (counterparty name, signatory name, effective date, governing law).

3 Starch syncs your Notion data on a schedule — connect your contracts database or let Starch create a new one with the fields you need: Counterparty, Type, Sent Date, Status, Signed Date, Governing Law, Initiated By.

4 Starch syncs your Gmail data on a schedule — connect Gmail so the agent can monitor for DocuSign webhook events and surface draft follow-ups to your inbox without you having to log into another tool.

5 Describe the intake form to Starch: counterparty name, signatory email, deal type, and governing law with a Delaware default. Starch builds the form your sales reps will use — shareable via a link, no login required from their side.

6 Describe the automation: 'When the intake form is submitted, match deal type to the correct template in Drive, fill in counterparty fields, create and send a DocuSign envelope to the signatory, log the record to Notion with status Sent and today's date, and email the submitting rep a confirmation with the DocuSign tracking link.'

7 Test with a real counterparty from a closed deal to confirm field mapping, template selection logic, and Notion logging are all working before you tell sales the form is live.

8 Describe the follow-up automation: 'Every weekday morning, query the Notion tracker for NDAs with status Sent and sent date more than 5 business days ago. For each one, draft a follow-up email to the initiating rep with the counterparty name and DocuSign link and put it in my Gmail drafts.' This keeps you in control of what goes out without requiring you to remember to check.

9 Describe the status-sync automation: 'When a DocuSign envelope status changes to Signed, Declined, or Voided, update the corresponding Notion record and change the status field accordingly. If Signed, populate the Signed Date field.' This replaces the manual Notion updates you're currently doing after the fact.

10 Build the NDA dashboard in Starch: 'Show me all NDAs from the last 90 days, their status, counterparty, governing law, who initiated the request, and how many days since sent. Highlight anything unsigned past 5 business days.' Use this as your weekly legal-ops view instead of opening Notion.

11 Share the intake form link with your sales and BD leads with a one-paragraph SOP: fill out the form, NDA goes out in under 2 minutes, you'll be CC'd only on errors. No more 'can you send an NDA?' Slack messages to you directly.

12 Once the workflow has run for a month, use the dashboard to identify which counterparty types have the slowest countersign times and whether certain governing-law choices are causing delays — this is the data your Notion tracker never gave you.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

BD NDA Backlog — April 2026 (8 NDAs in 5 days)

Sample numbers from a real run

Acme Corp — mutual NDA, Delaware, BD partnership	1
Globex Inc — one-way NDA, California, vendor onboarding	1
Initech Ltd — mutual NDA, Delaware, enterprise sales	1
Umbrella Ventures — mutual NDA, New York, investor conversation	1
Hooli Analytics — one-way NDA, Delaware, contractor	1
Pied Piper — mutual NDA, Delaware, BD partnership	1
Dunder Systems — one-way NDA, Texas, vendor onboarding	1
Vandelay Tech — mutual NDA, Delaware, enterprise sales	1

In the first week of April, BD closed three partnership conversations simultaneously and sales pushed two enterprise deals to contract stage. Eight NDA requests hit your inbox between Monday and Friday. Under the old process — template hunting, manual DocuSign setup, Notion logging — that's 4-6 hours of your time across a week when you were also reviewing a DPA for IT and finalizing a vendor-risk questionnaire. With the Starch workflow live, all eight reps submitted the intake form themselves. Starch matched each to the right template (5 mutual Delaware, 2 one-way Delaware, 1 California one-way), created and sent DocuSign envelopes within 2 minutes of form submission, and logged all eight to your Notion tracker automatically. By Wednesday morning, 5 were already countersigned. The 9am follow-up automation caught the 3 still unsigned and put draft follow-ups in your Gmail for the initiating reps. You spent 12 minutes reviewing and clicking send on those drafts. Total legal time on 8 NDAs: 12 minutes, versus an estimated 5+ hours. You spent the rest of the week on the DPA and the vendor questionnaire — the work that actually needs you.

Measurement

How you'll know it's working

NDA cycle time: days from request submitted to fully countersigned (target: under 3 business days)

Legal team hours per NDA sent (target: under 5 minutes of attorney time)

Percentage of NDAs with up-to-date status in the Notion tracker (target: 100% — this should be automatic now)

Follow-up rate on unsigned NDAs past 5 business days (should be 100% without manual intervention)

Number of NDA requests that hit your inbox directly vs. going through the intake form (target: zero inbox requests within 30 days of launch)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Ironclad

Purpose-built CLM with strong clause libraries and approval workflows, but starts at six figures annually and assumes a dedicated legal-ops person to configure and maintain it — not realistic for a 2-person team at a 150-person company.

DocuSign alone (current state)

Handles e-signature well but has no intake form, no template-selection logic, and no contract tracking — you're still doing all the coordination and Notion updates manually.

Google Drive + Notion + manual DocuSign

Free and already in place, but the coordination between them is entirely manual — no automation, no status sync, and the tracker is only as accurate as the last time someone remembered to update it.

PandaDoc

Good self-serve document workflows and cheaper than Ironclad, but it's another standalone tool with its own CRM and tracker that won't connect to your existing Notion setup without custom work.

Zapier + DocuSign + Google Drive

Can automate individual steps, but building the full intake-to-tracker-to-follow-up workflow requires stitching together multiple Zaps, and any change to your template structure or Notion schema breaks the automation without an obvious way to debug it.

On Starch RECOMMENDED

One platform — contract lifecycle management, email agent, knowledge management all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

We already have DocuSign. Does Starch replace it or work with it?

Starch works with it. DocuSign handles the e-signature — Starch handles everything around it: the intake form, the template selection, the envelope creation, the Notion logging, and the follow-up drafts. You keep your DocuSign account and audit trail exactly as they are.

What about our NDA templates in Google Drive — do we need to reformat them?

No. Starch connects to Google Drive from its integration catalog and queries your templates live. You tell Starch which folder to look in and which file name or prefix maps to which deal type. Your templates stay in Drive as they are.

Can sales reps use the intake form without a Starch login?

Yes. The intake form is shareable via a link. Reps don't need a Starch account. Only your legal team needs to be in Starch to build and monitor the workflow.

Is Starch SOC 2 Type II certified?

Not yet. Starch is not currently SOC 2 Type II certified. If your company or a counterparty requires SOC 2 Type II for any tool touching contract data, that's a real constraint you should weigh before using Starch for NDA workflows.

What happens if a rep selects the wrong template or governing law?

The intake form logic Starch builds will default based on deal type — mutual for partnerships, one-way for vendors, for example — but a rep can override it. You can also add a validation step where submissions above a certain deal size or with a non-standard jurisdiction flag to you before the envelope goes out, rather than going automatically.

We have a Notion contracts tracker but it's a mess. Do we need to clean it up first?

Not necessarily. Starch syncs your Notion data on a schedule, so it can read whatever schema you already have. If the existing tracker is too inconsistent, the easier path is often to describe a clean schema to Starch and have it build a new Notion database, then migrate the records you care about. Either way, you don't need to manually clean the existing tracker before you start.

What about the Contract Lifecycle Management app I saw mentioned on your site?

Contract Lifecycle Management is coming soon — it's currently in development and you can request beta access. The workflow described on this page is buildable today using Starch's composable app layer on top of your existing DocuSign, Google Drive, Gmail, and Notion connections. The CLM app will add a purpose-built interface for clause libraries and multi-party approval routing when it launches.

Can Starch handle NDAs that need to go through legal review before sending, not just auto-send?

Yes. Instead of describing the automation as 'send immediately on form submission,' you'd tell Starch: 'When the form is submitted, populate the template and create a DocuSign draft — do not send. Email me the draft link for review. If I reply approve, send the envelope and log to Notion. If I reply reject, notify the submitting rep.' The review step is just part of the prompt.