Design partner agreement: 2-page MOU + short NDA

last updated: Sep 8, 2025
Minimal legal mock of a design partner agreement one-pager

TL;DR

Ship a design partner agreement in hours. Use a 2-page MOU to fix scope, one success metric, data rules, reference rights, and an end date. Add a short NDA. Then start weekly work.

How to:
  • Draft a 2-page MOU. Name scope, KPI (key performance indicator), data, reference permissions, and term.
  • Attach a short NDA. Send for e-sign. Kick off within 7 days.
  • Meet weekly. One session. One metric. Decide buy or no-buy at term.

Glossary

  • Design partner: Early customer who co-builds with weekly feedback.
  • MOU: Light agreement that captures scope and intent.
  • Memorandum of understanding: Formal name for a short MOU.
  • Pilot: Time-bound test with measurable outcomes.
  • KPI: Key performance indicator, the metric you move.
  • DPA: Data processing agreement that governs personal data.
  • Mutual NDA: Two-way confidentiality agreement.
  • Reference rights: Permission to use logo, quote, or case study.

How to write it step by step

  1. Draft the MOU shell. Two pages. Sections: Scope. KPI (key performance indicator). Data rules. Reference permissions. Term and end date. Attach the NDA. Optional: pricing guardrails. If you still need prospects, see /guides/design-partner-recruitment.
  2. Write scope for 6–12 weeks. Capture the job-to-be-done, user roles, and 3–5 deliverables. Name non-goals to stop scope creep. Example scope: “Automate L1 triage for IT tickets across Slack and email. Non-goal: agent hand-off.”
  3. Pick one metric. Tie it to buyer value. Examples: percent reduction in manual minutes per ticket. Percent lift in qualified leads after enrichment. Write the baseline, the target, and how you will measure it weekly.
  4. Lock the weekly cadence. One session of 30–45 minutes. Same day and time. Agenda: review the KPI trend, review last week’s build, decide the next one or two bets. Name the design partner lead and the maker on your side. If you need a crisp product walkthrough, use /guides/founder-demo-script.
  5. Set data rules. State sources, access, storage, retention, support hours, and security posture. Link your DPA if you process personal data. Define safe sample datasets if production data is blocked.
  6. Gate references and pricing. If the KPI target is hit by the end date, unlock public reference permissions and a preferred pricing offer. If not, part as friends. When targets are met, use /guides/b2b-case-study-template to ship a story within 30 days.
  7. Sign and kick off. Send the PDF, countersign, and run the first working session within 7 days. Put the decision meeting for the final week on the calendar.

Benchmarks

Element
Typical range
Source
What this means
Term length
3–6 months
[Common Paper Contract Benchmark (Q1 2024)] https://commonpaper.com/standards/design-partner-agreement/
Pick 12 or 24 weeks to drive urgency and a decision.
3-month terms
≈27% of agreements
[Common Paper Contract Benchmark (Q1 2024)] https://commonpaper.com/wp-content/uploads/2024/02/Contract-benchmark-metrics.pdf
Short windows focus teams and reduce drift.
Meeting cadence
Weekly or biweekly, 30–45 minutes
[Unusual Ventures field guide] https://www.unusual.vc/articles/how-do-you-work-with-design-partners
Short, predictable sessions are hard to cancel.
Mutual NDA format
Short standardized mutual form (oneNDA)
[oneNDA] https://www.onenda.org/onenda-template
Use a standard to reduce legal back-and-forth.
DPA requirement
Art. 28 contract when processing personal data
[GDPR Article 28] https://gdpr-info.eu/art-28-gdpr/
Link your DPA or use synthetic data.
Sample math. Baseline triage time per ticket: 10 minutes. Target: 30% reduction in 8 weeks. Volume: 500 tickets per week. Time saved = 10 × 0.30 × 500 = 1,500 minutes weekly.
Design-partner-agreement

Design partner agreement vs pilot agreement

  • Use a design partner agreement when you need weekly feedback to shape the roadmap, flexible scope, and a single KPI.
  • Use a pilot agreement when the product is capable, the pilot scope is fixed, environments are production-like, and there is a clear purchase decision at the end.

Templates

2-page MOU skeleton
Title. Design Partner Memorandum of Understanding.
Parties and purpose. Company A and Company B agree to collaborate to validate value and shape the product.
Scope. Describe the workflow, users, and 3–5 deliverables. List non-goals.
KPI. One metric with baseline, target, and how you will measure it.
Data rules. Sources. Access. Storage. Retention. Support hours. Security summary. Link to your DPA.
Reference permissions. If the target is met, Company B grants logo use, a public quote, and a case study review window before publication.
Term. Start date and end date. Renewal only by written agreement.
Fees. Optional. If used, tie any preferred pricing to the KPI target being met.
Signatures. Names, titles, dates, emails.

Short NDA: clause pack
Definition of confidential information. Carve-outs for information already known, independently developed, or publicly available.
Use and protection. Use only for the MOU and related evaluation.
Compelled disclosure. Notify promptly where lawful.
Term of confidentiality. 2–3 years from disclosure.
Residuals. No use of residual knowledge to disclose secrets.
Return or destroy. On request or at term.
No licenses. No IP transfer under the NDA.

Email to secure a design partner
Subject: 12-week design partner. One KPI. Weekly session.
Hi {{Name}},
I’m working on {{problem}}. The ask is simple: a 2-page MOU, a short NDA, and one weekly session of 30–45 minutes for 12 weeks. In return, you get a say in the roadmap, preferred pricing, and reference options if we hit the target. If helpful, I can start on a sandbox with synthetic data.
Want a 10-minute demo on {{day}}?

Risks

  • Scope creep if the MOU is vague. Write non-goals.
  • Legal drag on NDAs. Use a short standard and move.
  • Data access blockers. Agree on synthetic or sampled data in week 1.
  • No decision at term. Put the decision meeting on the calendar.

FAQ
  • You:
    Do I need a lawyer?
    Guide:
    You should get counsel to review final drafts. The templates here are for speed.
  • You:
    Can I skip the NDA?
    Guide:
    If no confidential data is shared, you can. Most teams still use a short NDA to keep everyone comfortable.
  • You:
    Who owns what we build?
    Guide:
    You own your data and your brand. The vendor keeps product IP. Any custom code should be agreed in Scope.
  • You:
    What if the target is missed?
    Guide:
    End the MOU, keep the relationship warm, and try again later with a new scope.
  • You:
    How many design partners at once?
    Guide:
    Start with three. That gives pattern recognition without overload.
  • You:
    Where do I link the DPA and NDA?
    Guide:
    Link your standard DPA. For the NDA, a short standard form works.
Ready to stop guessing?
© 2025
If you're an early-stage founder who needs a design partner fast,