Design Partner Program Setup

Purpose

This recipe produces a fully operational design partner program: outreach scripts, a lightweight MOU agreement, a feedback cadence structure, and a signed cohort of 3-5 design partners providing weekly structured feedback on your pre-PMF product. The output is a running program with scheduled sessions, documented expectations, and a clear graduation path to paid customers. [src1]

Prerequisites

• ICP definition available from customer research or founder hypothesis — clear description of target buyer persona, company size, and pain point
• Product demo or prototype — functional prototype, Figma mockup, or working MVP that partners can interact with
• Problem hypothesis — documented assumption about the problem, who experiences it, and why existing solutions fail
• Google Docs/Notion — for agreement drafting and feedback tracking ($0)
• Scheduling tool — Calendly, Cal.com, or Google Calendar for recurring sessions ($0)
• 3+ warm introductions — investors, advisors, or professional contacts who can introduce you to potential partners [src1]

Constraints

• Design partners are not beta testers and not pilot customers. They collaborate on product direction before product-market fit. Do not conflate these programs. [src5]
• Recruit 3-7 partners maximum. Fewer than 3 risks building for edge cases; more than 10 creates unmanageable feedback overhead. [src1] [src7]
• All feedback IP must be assigned to the vendor in writing. Ambiguous IP ownership creates serious problems during fundraising diligence. [src2] [src3]
• Do not optimize for early revenue from design partners. Prioritize raw, honest feedback over monetization. [src1]
• Each engagement should have a hard end date of 6-12 weeks. Open-ended engagements lose momentum. [src4]

Tool Selection Decision

Which path?
├── Founder has strong network (10+ warm intros available)
│   └── PATH A: Warm Outreach — leverage investors/advisors for introductions
├── Founder has moderate network (3-9 warm intros)
│   └── PATH B: Hybrid — warm intros + targeted cold outreach
├── Founder has weak network (mostly cold outreach needed)
│   └── PATH C: Cold Outreach — LinkedIn/Twitter DMs + community engagement
└── Founder is at an accelerator or has institutional investor backing
    └── PATH D: Investor-Facilitated — investors make introductions from portfolio

Execution Flow

Step 1: Define Partner Selection Criteria

Duration: 1-2 hours · Tool: Google Docs or Notion

Establish a three-part selection framework. Every prospective partner must pass all three filters: representativeness (ICP match), urgency (pain level), and capacity (ability to engage with weekly sessions and implement your product). [src1]

Filter 1: REPRESENTATIVENESS — matches your ICP (size, industry, tech stack)
Filter 2: URGENCY — has daily/weekly pain, will commit to call next week
Filter 3: CAPACITY — champion is actual user with authority, can commit 30 min/week

Verify: Written criteria for all three filters with specific thresholds · If failed: Complete customer discovery interviews first

Step 2: Build Outreach Pipeline

Duration: 2-4 hours · Tool: Google Sheets or HubSpot free CRM

Build a list of 15-25 prospects to yield 3-5 signed partners. Expect 30-50% conversion from warm intros and 10-20% from cold outreach. Prioritize sourcing from investors, advisors, LinkedIn, and community forums. [src1] [src6]

Verify: At least 15 prospects with ICP match score 3+ and at least 5 warm introductions · If failed: Switch outreach path; ask every contact for 2 additional referrals

Step 3: Craft Outreach and Conduct Discovery Calls

Duration: 3-5 hours over 1-2 weeks · Tool: Email + Calendly + Zoom

Send personalized outreach highlighting the specific pain point you observed. Run 20-minute discovery calls to qualify prospects on the three-filter framework before proposing the partnership. Focus on understanding their current workaround and urgency, not pitching your product.

Verify: At least 5 discovery calls completed with 3+ expressing strong interest · If failed: If call-to-interest conversion is below 30%, revisit your problem framing

Step 4: Draft and Send Design Partner Agreement

Duration: 2-3 hours + 1-2 days review · Tool: Google Docs

Draft a lightweight 2-3 page MOU covering scope, timeline, feedback obligations, IP assignment, KPI, reference permissions, and graduation terms. Keep it simple — heavy legal documents scare off early partners. Use Common Paper's open-source template as a base. [src3] [src4]

Verify: Agreement covers all 10 key sections; IP assignment clause is explicit · If failed: If partners resist signing, simplify to a mutual email confirming scope, timeline, and IP assignment

Step 5: Onboard Partners and Launch Feedback Cadence

Duration: 1-2 hours per partner · Tool: Calendly + Zoom + Google Sheets

Onboard each partner within 7 days of signing. Provision product access, run a 45-minute kickoff call, book all recurring weekly sessions upfront (same day/time), collect baseline KPI measurement, and set up the feedback tracking log. [src4] [src6]

Verify: All partners have product access, completed kickoff, and first 4 weekly sessions on the calendar · If failed: If a partner misses the kickoff or first two sessions, replace them from your pipeline

Step 6: Run the Program and Prepare Graduation

Duration: 8-12 weeks ongoing · Tool: All of the above

Execute weekly feedback sessions, track feedback in the log, ship partner-influenced improvements, and conduct bi-weekly cross-partner analysis. In the final week, run graduation decision meetings with each partner: review KPI achievement, assess willingness to pay, confirm reference permissions, and either convert to paid customer or conclude the engagement. [src6] [src8]

Verify: At least 2 of 3-5 partners complete the full program; at least 1 converts to paid or commits to a case study · If failed: If zero partners are willing to pay, review feedback logs for the gap between what partners need and what you built [src8]

Output Schema

{
  "output_type": "design_partner_program",
  "format": "document_bundle",
  "components": [
    {"name": "partner_selection_criteria", "type": "document", "description": "Three-filter scoring rubric", "required": true},
    {"name": "prospect_pipeline", "type": "spreadsheet", "description": "15-25 prospects with status and scoring", "required": true},
    {"name": "outreach_templates", "type": "document", "description": "Warm and cold emails + discovery call agenda", "required": true},
    {"name": "design_partner_mou", "type": "document", "description": "2-3 page MOU with IP, KPI, and graduation terms", "required": true},
    {"name": "feedback_log", "type": "spreadsheet", "description": "Running log with categorization and product decisions", "required": true},
    {"name": "graduation_report", "type": "document", "description": "Per-partner KPI results and conversion decisions", "required": false}
  ],
  "expected_partner_count": "3-5",
  "program_duration": "8-12 weeks"
}

Quality Benchmarks

If below minimum: If you cannot sign 3 partners within 4 weeks, your problem hypothesis or ICP definition likely needs revision. Return to customer discovery.

Error Handling

Cost Breakdown

Anti-Patterns

Wrong: Recruiting prestigious logos instead of urgent users

Founders target Fortune 500 logos for credibility but these companies have slow procurement, committee decisions, and low urgency. The partnership stalls because nobody internally champions daily usage. [src1] [src8]

Correct: Recruit based on urgency and capacity first

Target mid-market or growth-stage companies where the champion is the actual daily user with decision-making authority. A passionate user at a 50-person company gives better feedback than a disengaged VP at a Fortune 500. [src7]

Wrong: Running open-ended partnerships with no end date

Without a hard deadline, partners lose motivation, sessions become sporadic, and the founder avoids the graduation conversation. Six months later, you have free users, not product-market fit data. [src4]

Correct: Set a hard 8-12 week term with a pre-scheduled decision meeting

Book the graduation meeting on the day you sign the MOU. Both sides know the timeline, creating healthy urgency and forcing a clear buy/no-buy decision. [src4] [src6]

Wrong: Treating design partner traction as revenue traction

Founders tell investors they have 5 design partners as if it were customer traction. Design partners are not customers — they get free access in exchange for feedback. Investors know the difference. [src5]

Correct: Separate design partners from paying customers in all reporting

Track them in separate categories. The real traction metric is how many partners convert to paid after the program ends. [src5] [src8]

When This Matters

Use this recipe when a founder has a product concept or working prototype and needs structured feedback from real target users before committing to a product direction. It produces a running design partner program — not a document about the concept of design partners. Requires an ICP definition and some form of product demo as inputs.