Compliance & Legal

How to send an nda from a template as Small Investor Relations Teams

Compliance & LegalFor Small Investor Relations Teams3 apps11 steps~22 min to set up

Your two-person IR team sends NDAs constantly — before sharing data room credentials, before LP co-invest discussions, before onboarding new placement agents. Right now that means hunting for the right template in a Google Drive folder with six versions named 'NDA_final_v3_REVISED.docx', copy-pasting the LP's legal entity name and notice address, emailing a PDF, chasing a wet signature or a DocuSign you paid for separately, and then manually filing the countersigned copy somewhere your CFO can find it when they inevitably ask. Each NDA takes 20-40 minutes of actual time across two people. You're doing dozens per quarter.

Build this on Starch → See the apps used

Compliance & LegalFor Small Investor Relations Teams3 apps11 steps~22 min to set up

Outcome

What you'll set up

A living NDA template wired to your LP contact database so every send pre-fills the correct legal entity, jurisdiction, and notice details without copy-paste

An automated send-and-track workflow that logs outbound NDAs, pings you when one goes unsigned after 48 hours, and files countersigned copies back to your data room folder

A searchable record of every executed NDA — who signed, when, what version, and what data room access it covers — so you can answer LP questions in seconds instead of digging through email

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 CRM

Data sources & config

Wire your LP CRM (connect from Starch's integration catalog; the agent queries it live when drafting each NDA) and Gmail (Starch syncs your Gmail on a schedule — sent NDAs and inbound countersigned copies are tracked automatically). For data room platforms like DocSend or Intralinks that don't expose a public API, Starch automates them through your browser — no API needed. Contract Lifecycle Management is coming soon; in the meantime, the CRM app plus Email Triage app cover send-track-file today.

Prompts to copy

Build me an NDA workflow that pulls the LP's legal entity name, address, and primary contact from my CRM, merges them into our standard mutual NDA template, sends it for e-signature, and logs the executed copy with a timestamp and the LP name.

Create a follow-up automation: if an NDA I sent hasn't been countersigned in 48 hours, draft a short follow-up email to the LP contact and surface it in my inbox for one-click send.

Build a dashboard showing all open and executed NDAs from the last 12 months — LP name, send date, execution date, which data room tier they were granted access to, and whether the countersigned PDF is on file.

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

Walkthrough

Step-by-step

1 Connect your LP CRM from Starch's integration catalog. Starch queries it live each time you initiate an NDA so the legal entity name, address, and signatory details pre-fill from the source of record — no copy-paste.

2 Upload your standard mutual NDA template (and any fund-specific variants — co-invest NDA, placement agent NDA) into Starch. Tag each template by use case so the right one surfaces automatically based on who you're sending to.

3 Tell Starch: 'When I send an NDA to an LP, pull their legal entity and notice address from the CRM, merge it into the mutual NDA template, and create a signature-ready document.' Starch builds the merge workflow.

4 Configure e-signature delivery. Starch sends the prepared NDA via Gmail (synced on a schedule) and logs the send event — LP name, template version, timestamp — in your NDA tracker.

5 Set the 48-hour follow-up rule: 'If an outbound NDA hasn't been countersigned after 48 hours, draft a short follow-up to the LP contact and surface it in my Email Triage app for one-click send.'

6 When the countersigned copy comes back into your Gmail, Starch detects it (via scheduled Gmail sync), extracts the LP name and execution date, and appends the record in your NDA tracker.

7 For data rooms on DocSend or Intralinks, Starch automates access provisioning through your browser — no API needed. Once an NDA executes, the automation can log in and grant the appropriate data room tier to that LP.

8 Build the NDA status dashboard: 'Show me all NDAs sent in the last 12 months — LP name, send date, execution date, data room access tier, and whether the countersigned PDF is on file.' Starch assembles this from your Gmail sync and CRM data.

9 Add an expiration alert: 'Flag any executed NDAs that are more than 24 months old and haven't been renewed.' IR NDAs often have term limits that nobody tracks until a lawyer asks.

10 Publish the NDA tracker as a shared view so your CFO can pull executed NDA status themselves instead of asking you — one less recurring question in your week.

11 When Contract Lifecycle Management launches (coming soon), migrate your NDA workflow into it for full clause-library management, multi-party signing orchestration, and audit trail in one place.

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

Q1 2026 Co-Invest NDA Batch — March Close

Sample numbers from a real run

NDAs sent to prospective co-investors	14
Countersigned within 48 hours	9
Follow-up emails auto-drafted by Starch	5
Average time per NDA (pre-Starch)	3,200
Average time per NDA (with Starch, in seconds)	420

In March 2026, you ran a $12M co-invest syndication alongside your fund's Series B follow-on. Fourteen prospective co-investors needed NDAs before you could share the deal memo and cap table. Pre-Starch, that was 14 rounds of: find the right template, update the legal entity name and notice address, create a DocuSign envelope, send, chase, file. Roughly 40 minutes each, spread across two people, on top of everything else March close demands. With Starch, you typed: 'Send our co-invest NDA to the 14 LPs on my March syndication list, pulling legal entity details from the CRM.' Starch queried your CRM live for each contact, merged the co-invest NDA template, and sent all 14 via Gmail in one batch. Nine came back countersigned within 48 hours; Starch filed each one automatically and updated the NDA tracker. For the remaining five, Starch drafted follow-up emails that you sent with one click from Email Triage. Total active time: under 30 minutes for the whole batch. The countersigned PDFs were logged before your GP asked whether NDAs were in place.

Measurement

How you'll know it's working

NDA turnaround time: hours from send to countersigned execution

NDA coverage rate: percentage of active LPs and prospects with a current, unexpired NDA on file

Follow-up rate: percentage of outbound NDAs requiring a chase email before execution

Data room provisioning lag: hours between NDA execution and data room access granted

Expired NDA exposure: count of LPs with data room access whose NDA term has lapsed

Comparison

What this replaces

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

DocuSign standalone

Handles e-signature well but does nothing to pre-fill LP details from your CRM, track expiration, or automate data room provisioning — you're still doing the merge and filing manually.

Ironclad or Contractbook

Full CLM tools with clause libraries and approval workflows, but pricing and implementation overhead are sized for legal teams, not a 2-person IR function.

Google Drive + DocuSign + spreadsheet tracker

The stack most small IR teams actually use today — functional but entirely manual, with no expiration alerts, no CRM merge, and no audit trail your CFO trusts.

Juniper Square or Allvue

Institutional LP portal platforms that include document workflows, but cost $50k+ per year and assume a dedicated IR-ops analyst to configure and maintain them.

On Starch RECOMMENDED

One platform — contract lifecycle management, crm, founder inbox 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

Can Starch actually send the NDA via email, or does it just prepare the document?

Starch syncs your Gmail on a schedule and can send outbound emails as part of an automation. The NDA gets prepared, merged with LP details from your CRM, and sent from your Gmail account. Inbound countersigned copies that land in your Gmail are picked up by the same sync and logged automatically.

What if our data room is on DocSend or Intralinks — can Starch integrate with those?

Neither DocSend nor Intralinks exposes a public API that Starch currently syncs with, but Starch can automate both through your browser — no API needed. That means logging in, navigating to the right folder, and granting access to a specific LP can all be part of the same automation that fires when an NDA executes.

The Contract Lifecycle Management app is listed as coming soon. What can I actually use today?

Today, the combination of the CRM app (to pull LP contact data), Email Triage app (to manage outbound sends and follow-ups via Gmail), and a custom NDA tracker app you describe to Starch covers the core workflow — send, track, follow up, file. Contract Lifecycle Management (coming soon) will add a formal clause library, multi-party signing orchestration, and renewal alerts in one surface. You can request beta access now and migrate when it launches.

Is Starch SOC 2 Type II certified? NDAs contain sensitive LP information.

Not yet — Starch is not SOC 2 Type II certified as of today. That's an honest limit worth knowing. If your fund's compliance requirements or LP agreements mandate SOC 2 Type II for data processors, you'll need to weigh that. For funds where the current risk posture is acceptable, Starch handles NDA workflows without storing document content beyond what your CRM and Gmail already hold.

We have three different NDA templates — mutual, one-way, and placement agent. Can Starch handle all of them?

Yes. You upload all three templates and tell Starch: 'Use the mutual NDA for LP co-invest discussions, the one-way NDA for placement agents, and flag anything else for me to choose manually.' The workflow routes to the right template based on the contact type in your CRM. If a contact's type isn't set, Starch surfaces it for your review before sending rather than guessing.

Our CFO wants to know which LPs have signed NDAs before sharing anything sensitive. Can they check that themselves?

Yes. You can publish the NDA status dashboard as a shared view in Starch so your CFO (or your GP) can pull LP NDA status, execution dates, and data room access tiers without asking you. It's a read-only view of the same data your workflow maintains — one less recurring question in your week.