Draft a Mutual NDA with this AI Prompt
Most NDA drafts fail in the same boring way. They’re either too generic to enforce, full of “reasonable efforts” fluff, or missing the clauses that matter when a deal goes sideways. Then you’re stuck in redlines for days, arguing over basics instead of moving the conversation forward.
This mutual NDA prompt is built for startup founders sharing product roadmaps with potential partners, agency leads exchanging client data during a pitch or RFP, and biz dev managers comparing pricing, processes, and technical details during early-stage negotiations. The output is a contract-style mutual confidentiality agreement with defined terms, exclusions, duties, term, remedies, and signature blocks you can paste into a doc and send to counsel for a fast review.
What Does This AI Prompt Do and When to Use It?
| What This Prompt Does | When to Use This Prompt | What You’ll Get |
|---|---|---|
|
|
|
The Full AI Prompt: Mutual NDA Contract Draft
Fill in the fields below to personalize this prompt for your needs.
| Variable | What to Enter | Customise the prompt |
|---|---|---|
[PARTY_A_NAME] |
Enter the full legal name of the first party involved in the agreement. For example: "Acme Corporation"
|
|
[PARTY_A_ADDRESS] |
Provide the physical or registered address of Party A, including street, city, state, and postal code. For example: "123 Main Street, Springfield, IL 62704"
|
|
[PARTY_B_NAME] |
Enter the full legal name of the second party involved in the agreement. For example: "Global Tech Solutions LLC"
|
|
[PARTY_B_ADDRESS] |
Provide the physical or registered address of Party B, including street, city, state, and postal code. For example: "456 Elm Street, Austin, TX 78701"
|
|
[EFFECTIVE_DATE] |
Specify the date when the agreement will come into effect. Use the format YYYY-MM-DD. For example: "2023-11-01"
|
|
[GOVERNING_LAW] |
Enter the state or country whose laws will govern the agreement. For example: "Delaware, USA"
|
|
[PURPOSE] |
Describe the reason or context for sharing confidential information between the parties. For example: "Exploring a potential joint venture in renewable energy technologies."
|
|
[TERM_LENGTH] |
Specify how long the agreement will remain in effect, typically in months or years. For example: "2 years"
|
|
[SURVIVAL_PERIOD] |
Indicate the duration for which confidentiality obligations will survive after the agreement ends. For example: "5 years after termination"
|
|
[UPPERCASE_WITH_UNDERSCORES] |
Use this format for placeholders in the document, ensuring clarity and consistency. For example: "[PARTY_A_NAME], [EFFECTIVE_DATE]"
|
Pro Tips for Better AI Prompt Results
- Feed it real party details, not nicknames. Use the exact legal entity names and addresses you want on the signature page. If you only have “Acme” and a website, you will get placeholders; that’s safer, but it slows execution. After the draft, you can ask: “Replace placeholders with: Acme LLC, 123 Main St, Austin, TX 78701; Beta Inc., 55 Market St, San Francisco, CA 94105.”
- Describe the disclosure context in one tight sentence. Even though the prompt handles mutual NDAs by default, you’ll get cleaner definitions when the purpose is clear. Add a line like: “This NDA supports evaluation of a potential integration partnership and exchange of APIs, architecture notes, and customer requirements.” If you want to narrow scope, follow up with: “Limit Confidential Information examples to product, technical, and go-to-market items (exclude HR).”
- Force specificity around “reasonable” safeguards. The prompt aims to avoid vague standards, but you can push it further by naming expectations. Try: “Define reasonable safeguards as: encryption at rest where available, restricted access, and no forwarding outside the evaluation team.” Then ask: “Add an obligation to notify the other party within 5 business days of a suspected breach.”
- Iterate the negotiation posture on purpose. After the first output, choose what you want to optimize for: speed, strictness, or fairness. Ask: “Now make remedies more protective for both parties, but keep it commercially standard,” or “Make term and survival more conservative for a Fortune 500 counterparty.” Small tweaks beat a full rewrite.
- Pair the NDA with your communication assets. An NDA is only half the workflow; you also need the emails and collateral that trigger the exchange. If your deal motion uses a newsletter or outbound sequence, draft those next and keep language consistent (same “purpose” and “evaluation” framing). For example, build outreach copy using https://flowpast.com/prompts/build-three-funnel-email-campaigns-with-this-ai-prompt/ and align the email’s wording with the NDA’s permitted-use clause.
Common Questions
Startup founders use this to share product plans, investor materials, or integration details without emailing a flimsy one-pager. Partnerships and business development managers rely on it when both sides are exchanging sensitive commercial info and they need mutual obligations, not a one-way agreement. Agency owners use it to protect client data and proprietary processes during pitches, audits, and vendor transitions. Ops or procurement leads like it because it produces a complete structure with clear exclusions, term, and remedies that’s easier to route for internal review.
SaaS and software companies get value when sharing architecture notes, API documentation, security practices, and product roadmaps during integration talks. E-commerce and consumer brands use it when discussing supplier terms, pricing models, marketing plans, and customer data with agencies or fulfillment partners. Professional services firms (consulting, accounting, IT services) apply it to protect methodologies, deliverable templates, and client information during discovery. Media and content businesses lean on it for collaborations where unpublished content plans, sponsorship rates, or audience analytics need clear boundaries.
A typical prompt like “Write me a mutual NDA for my business” fails because it: lacks a contract-grade structure with defined terms and consistent cross-references, provides no clear exclusions (so the definition of Confidential Information becomes overbroad and messy), ignores practical protection measures like need-to-know access and copying limits, produces generic “reasonable efforts” language instead of specific obligations you can enforce, and misses critical cleanup items like compelled-disclosure steps, return/destruction language, remedies, and a “What This Is NOT” boundary section.
Yes, but you customize it by tightening the context and filling placeholders, not by rewriting the whole thing. After you get the draft, replace bracketed fields like [ADD GOVERNING LAW STATE], [PARTY NAME], [ADDRESS], and any missing effective date items, then re-run with your exact purpose (for example, “evaluation of a reseller partnership” versus “M&A exploratory discussions”). You can also request alternative positions: “Revise the term to 2 years, but keep trade secrets protected indefinitely,” or “Add an explicit non-solicitation clause if appropriate (and label it optional).” A good follow-up prompt is: “List the top 8 clauses most likely to be negotiated in this NDA and provide two fallback options for each.”
The biggest mistake is leaving party details blank, which forces placeholders and creates extra work later; instead of “Acme and Beta,” use “Acme Logistics LLC (Delaware) and BetaWare, Inc. (California) with addresses for notice.” Another common error is failing to specify the deal context; “business discussions” is weaker than “evaluation of a data-sharing integration and joint go-to-market pilot.” People also forget to confirm governing law and venue, which leads to [ADD GOVERNING LAW STATE] hanging around in the final doc. Finally, they accept vague security language; push for specifics like “limit access to employees/contractors with a need to know and require written obligations at least as protective as this agreement.”
This prompt isn’t ideal for regulated or high-stakes situations where you already know you need jurisdiction-specific counsel, like healthcare PHI, financial services compliance, or export-controlled technical data. It also may not fit one-way disclosures where only one party shares sensitive information and the other refuses mutual obligations. And if your org requires a locked corporate template with mandatory clauses, generating a fresh draft could create extra approval work. In those cases, use your approved template first and ask AI only to propose redlines for specific sections.
A solid NDA doesn’t “sound legal.” It makes the rules obvious, fair, and hard to wiggle out of. Paste this prompt into your model, generate a first draft, and get back to the deal.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
