Compliance & Legal

How to send an nda from a template as Professional Services Founders

Compliance & LegalFor Professional Services Founders2 apps11 steps~22 min to set up

You close a new engagement, shake hands on scope, and then spend 45 minutes hunting for the last NDA you sent, stripping out the old client's name, adjusting the governing law clause, and emailing a PDF that sits in someone's inbox for a week. Your Google Drive has six versions of 'NDA_FINAL_v3_USE_THIS_ONE.docx.' You have no idea which prospects have signed, which are pending, and which ghosted you after the kickoff call. DocuSign sends a reminder but doesn't tell HubSpot the deal is cleared to move forward. A senior consultant starts discovery before legal is done because no one updated the deal stage. At 12 people, every hour you spend on document admin is an hour you're not billing or selling.

Build this on Starch → See the apps used

Compliance & LegalFor Professional Services Founders2 apps11 steps~22 min to set up

Outcome

What you'll set up

A reusable NDA workflow that pulls client details from your HubSpot deal record, fills the template, and sends a signature request — without touching a PDF editor

A live view showing every NDA in flight: sent, opened, signed, or stalled — so nothing sits forgotten in an inbox

An automatic HubSpot deal-stage update and Slack ping to your team when the NDA is countersigned and the engagement is legally clear to start

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

Data sources & config

Starch syncs your HubSpot deal and contact data on a schedule; your NDA template lives in Notion (synced on a schedule) or Google Drive (connected from Starch's integration catalog, queried live). Gmail is connected as a scheduled-sync provider so Starch can send signature requests and track replies. Slack is connected from Starch's integration catalog for deal-stage notifications. Contract Lifecycle Management — coming soon — will handle the full e-signature and approval routing layer; today, the workflow is built as a custom Starch automation on top of these connections.

Prompts to copy

Build me an NDA send workflow. When I select a HubSpot deal, pull the contact name, company, governing state, and engagement type, fill our standard NDA template with those fields, and send it via Gmail for e-signature. Log the send date back to the HubSpot deal record.

Set up a tracker that shows all NDAs sent in the last 90 days — deal name, recipient, sent date, status (pending/signed/expired), and days outstanding. Alert me in Slack if any NDA has been open for more than 5 business days without a signature.

When an NDA is countersigned, automatically move the linked HubSpot deal to 'NDA Signed' stage and send me a Slack message with the deal name and signed document link.

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

Walkthrough

Step-by-step

1 Connect HubSpot as a scheduled-sync provider. Starch pulls your deals, contacts, and company records on a schedule — including the fields you actually use like engagement type, deal owner, and close date.

2 Connect Gmail as a scheduled-sync provider so Starch can send the NDA on your behalf and monitor the thread for a reply or signature confirmation.

3 Connect Notion (scheduled-sync) or Google Drive (from Starch's integration catalog) where your NDA template lives. If your template is in a folder you can open in a browser, Starch can reach it through browser automation — no API needed.

4 Tell Starch which fields to merge: 'Use the contact's full name, company name, deal owner's signature block, and the governing state from the HubSpot deal record.' Starch maps these to your template's placeholder fields.

5 Build the send automation: 'When I click Send NDA on a deal, generate the filled document, attach it to a Gmail draft addressed to the primary contact, and mark it sent.' Review before sending or set it to auto-send for standard NDAs.

6 Wire the status tracker: 'Create a dashboard showing every NDA sent in the last 90 days, with deal name, recipient email, sent date, last-opened date, and current status. Refresh it daily from Gmail thread data.' You now have one view instead of hunting through sent mail.

7 Set the follow-up automation: 'If an NDA has been sent but not signed after 5 business days, draft a short follow-up email and queue it for my review.' The Email Agent can handle the draft so you're approving, not writing.

8 Configure the HubSpot write-back: 'When Gmail receives a reply with a signed attachment, update the linked HubSpot deal stage to NDA Signed and log today's date in the NDA Signed Date field.' This keeps your pipeline data accurate without manual entry.

9 Add a Slack notification: 'When a deal moves to NDA Signed, post a message in #new-clients with the deal name, client company, and deal owner.' Your team knows discovery can start without chasing anyone for confirmation.

10 Test with a real deal: walk the workflow from deal selection to countersigned document. Verify the HubSpot stage updated, the Slack message fired, and the tracker reflects the correct status.

11 When Contract Lifecycle Management launches (coming soon), migrate the e-signature and clause library into that app for multi-party NDAs, renewal tracking, and a searchable audit trail. The automation wiring you built today carries forward.

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

April 2026 NDA — Meridian Strategy Group engagement

Sample numbers from a real run

HubSpot deal pulled	0
Time to send NDA (automated)	3
Time to send NDA (manual, previous process)	45
Days to signature (with 5-day follow-up automation)	6
Days to signature (previous average, no follow-up)	14
NDAs tracked in current dashboard	23

Your business development lead closes a scoping call with Meridian Strategy Group on a Tuesday afternoon and updates the HubSpot deal to 'Proposal Sent.' You open the Starch NDA app, select the Meridian deal, and hit Send NDA. Starch pulls Sarah Chen's name and title from the HubSpot contact record, pulls the governing state (New York) from the deal, and merges both into your standard mutual NDA template. A Gmail draft appears pre-addressed to sarah.chen@meridianstrategy.com with the filled PDF attached. You review it in 30 seconds and hit send. Starch logs the send timestamp back to the HubSpot deal record automatically. Five business days pass with no signature. The follow-up automation fires: the Email Agent drafts a two-line nudge — 'Hi Sarah, just checking in on the NDA — happy to answer any questions before we kick things off.' You approve it in one click. Sarah signs on day six. Gmail detects the countersigned attachment, Starch moves the HubSpot deal to 'NDA Signed,' and a Slack message hits #new-clients: 'Meridian Strategy Group — NDA signed. Deal owner: Jamie Park.' Your consulting team starts discovery that afternoon. No one had to ask whether legal was done.

Measurement

How you'll know it's working

Average days from NDA sent to NDA countersigned (target: under 7 business days)

Percentage of deals with NDA status current in HubSpot (target: 100% — no manual logging)

NDAs pending signature for more than 5 business days (want this at zero weekly)

Time spent per NDA send, including follow-up (target: under 5 minutes of founder/senior time)

Deal stage accuracy: proportion of 'NDA Signed' deals where the date in HubSpot matches the actual signature date

Comparison

What this replaces

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

DocuSign standalone

Handles e-signature well but doesn't talk to HubSpot or Slack without a separate automation layer — you're still doing manual deal-stage updates and status tracking in a spreadsheet.

HubSpot quotes + documents module

Keeps everything in HubSpot but the document editor is limited and you still need DocuSign for a real audit trail; the NDA template flexibility isn't there for professional services edge cases.

PandaDoc

Good template library and e-signature, but at 12 people the per-seat pricing adds up fast and it doesn't connect your NDA status to the rest of your ops stack without manual exports.

Google Drive folder + DocuSign + manual HubSpot update

Zero new software cost, but you've already lived the cost: 45 minutes per NDA, six versions of the template, and discovery starting before legal is done.

Ironclad or Icertis

Enterprise CLM tools built for legal teams at 200+ person firms — six-figure contracts, quarter-long implementations, and a dedicated admin to run them. Not the right fit for a 12-person consultancy.

On Starch RECOMMENDED

One platform — contract lifecycle management, email agent 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

Does Starch actually send the email, or do I still have to hit send myself?

Both modes are supported. You can configure the automation to auto-send NDAs for standard engagements, or queue a draft for your review first. Most consultancies start with review-before-send for their first few runs, then flip to auto-send once they've confirmed the merge fields are pulling correctly.

What if my NDA template has negotiated clauses that change by client type — enterprise versus SMB, for example?

You can build conditional logic into the automation: 'If the HubSpot deal type is Enterprise, use the enterprise NDA template from Notion; if it's SMB, use the standard template.' Starch maps the deal field to the correct template before generating the document. You tell Starch the rule in plain language; it applies it.

Will this work if my template is in Google Drive instead of Notion?

Yes. Connect Google Drive from Starch's integration catalog and the agent queries it live when the automation runs. If your template is on a platform without a formal API, Starch can reach it through browser automation — no API needed.

You mentioned Contract Lifecycle Management as 'coming soon.' What can I do today while I wait?

Today you build the full send-and-track workflow as a custom Starch automation: HubSpot pulls client details, Gmail sends the NDA and monitors for signature, the status dashboard shows every NDA in flight, and the write-back updates HubSpot when it's done. What's coming soon in the dedicated CLM app is multi-party signing workflows, a structured clause library, and renewal/expiration alerts built into a purpose-built interface. The automation wiring you set up today feeds directly into that app when it launches.

Is Starch SOC 2 Type II certified? I have clients who will ask.

Not yet. Starch is not SOC 2 Type II certified today. If a client's security review requires that certification before you can use any tool that touches their contract data, that's a real constraint worth naming. It's on the roadmap; we'll say so honestly rather than making you find out the hard way.

What happens if a prospect never signs? Does it just sit in the tracker forever?

You set the rules. A typical setup: if an NDA is unsigned after 30 days, Starch flags it in the dashboard and can trigger an automation to either archive the deal in HubSpot or prompt you to decide. You can also configure an automatic expiry note to the prospect. The tracker gives you visibility; what you do with it is your call.

We use Outlook, not Gmail. Does this still work?

Yes. Outlook is a scheduled-sync provider in Starch — same depth of integration as Gmail. Starch connects directly to Outlook for sending the NDA and monitoring the thread for a signature reply. The rest of the workflow is identical.