--- # === IDENTITY === id: business/customer-validation/design-partner-program-setup/2026 canonical_question: "How do I set up a design partner program — recruit 3-5 partners, agreement templates, expectation management?" aliases: - "Design partner program setup for B2B startup" - "How to recruit and manage design partners before product-market fit" - "Design partner agreement template and feedback cadence" entity_type: execution_recipe domain: business > customer-validation > design partner program setup region: global jurisdiction: global temporal_scope: 2024-2026 # === VERIFICATION === last_verified: 2026-03-11 confidence: 0.86 version: 1.0 first_published: 2026-03-11 # === TEMPORAL VALIDITY === temporal_validity: status: stable last_breaking_change: null next_review: 2026-09-07 change_sensitivity: low # === CONSTRAINTS === constraints: - "Recruit 3-7 design partners maximum — fewer than 3 risks overfitting to edge cases, more than 10 creates unmanageable feedback overhead" - "Partners must have genuine urgency — if they will not commit to a 30-minute follow-up next week, they are not in enough pain" - "Design partner agreements must assign all feedback IP to the vendor — ambiguous IP ownership creates diligence problems during fundraising or acquisition" - "Do not treat design partners as revenue — optimize for raw, honest feedback over early monetization" - "Each partner engagement should last 6-12 weeks with a hard end date — open-ended engagements lose momentum and delay product-market fit" # === SKIP CONDITIONS === skip_this_unit_if: - condition: "User already has paying customers and needs to formalize a beta testing program" use_instead: "Search knowledgelib.io for beta testing program design — no dedicated unit yet" - condition: "User needs to validate a startup idea before approaching partners" use_instead: "business/customer-research/customer-interview-guide-template/2026" - condition: "User needs channel/reseller partner program, not product design partners" use_instead: "business/go-to-market/partner-program-design/2026" # === AGENT HINTS === inputs_needed: - key: product_stage question: "What stage is the product?" type: choice options: ["concept/wireframe only", "functional prototype", "working MVP", "launched but pre-PMF"] - key: target_market question: "What is the target market segment?" type: choice options: ["SMB (1-50 employees)", "mid-market (50-500 employees)", "enterprise (500+ employees)", "mixed"] - key: founder_network question: "How strong is the founder's professional network in the target market?" type: choice options: ["strong (10+ warm intros possible)", "moderate (3-9 warm intros)", "weak (mostly cold outreach needed)"] - key: technical_skill question: "What is the user's technical skill level?" type: choice options: ["non-technical (no-code only)", "semi-technical (can edit code)", "developer (can write code)"] # === EXECUTION METADATA === execution: required_inputs: - name: "ICP definition" source: "business/customer-validation/icp-definition or user-provided" format: "structured data or text description" - name: "Product demo or prototype" source: "product development" format: "deployed URL, Figma prototype, or slide deck" - name: "Problem hypothesis" source: "business/startup-planning/startup-idea-structuring-template/2026 or user-provided" format: "text document" outputs: - name: "Design Partner Program Package" format: "document bundle" description: "Contains MOU template, NDA, outreach scripts, partner tracker spreadsheet, and feedback session agenda — ready to send to prospective partners" - name: "Signed Design Partner Cohort" format: "CRM records or spreadsheet" description: "3-5 signed partners with scheduled kickoff calls, defined KPIs, and weekly feedback cadence established" - name: "Partner Feedback Log" format: "spreadsheet or Notion database" description: "Structured record of all partner feedback organized by theme, feature request priority, and product decision impact" tools_required: - name: "Google Docs or Notion" purpose: "Agreement drafting, feedback tracking" tier: free cost: "$0" alternatives: ["Microsoft Word", "Coda", "Slite"] - name: "Google Sheets or Airtable" purpose: "Partner pipeline tracking and feedback log" tier: free cost: "$0" alternatives: ["Notion database", "Excel", "HubSpot CRM free tier"] - name: "Calendly or Cal.com" purpose: "Scheduling recurring feedback sessions" tier: free cost: "$0" alternatives: ["Google Calendar manual invites", "SavvyCal"] - name: "Loom or Zoom" purpose: "Feedback session recording and async demos" tier: free cost: "$0" alternatives: ["Google Meet", "Microsoft Teams"] credentials_needed: [] estimated_duration: "5-15 hours over 2-3 weeks (setup through first signed partner)" estimated_cost: "$0 (self-directed) to $500 (legal review of agreement)" # === DISTRIBUTION === canonical_source: "https://knowledgelib.io/business/customer-validation/design-partner-program-setup/2026" suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-11)" # === RELATED UNITS === related_kos: depends_on: - id: "business/startup-planning/startup-idea-structuring-template/2026" label: "Problem hypothesis and solution vision before recruiting partners" feeds_into: - id: "business/customer-research/customer-interview-guide-template/2026" label: "Problem Discovery Interview Script — full question-by-question guide (opening, context, pain deep-dive, willingness to pay, buying context, closing) with Mom Test anti-patterns and a synthesis template" alternative_to: [] # === SOURCES === sources: - id: src1 title: "A Framework for Finding A Design Partner" author: Andreessen Horowitz (a16z) url: https://a16z.com/a-framework-for-finding-a-design-partner/ type: technical_blog published: 2022-10-12 reliability: authoritative - id: src2 title: "How To Work With Design Partners" author: Common Paper url: https://commonpaper.com/blog/design-partner/ type: technical_blog published: 2024-03-15 reliability: high - id: src3 title: "Free Design Partner Agreement (Standard Terms v1.3)" author: Common Paper url: https://commonpaper.com/standards/design-partner-agreement/ type: official_docs published: 2024-06-01 reliability: authoritative - id: src4 title: "Design partner agreement: 2-page MOU + short NDA" author: Do What Matter url: https://dowhatmatter.com/guides/design-partner-agreement type: technical_blog published: 2025-01-10 reliability: high - id: src5 title: "Design Partners — Who Are They and How To Find Them" author: FortyTwo VC url: https://fortytwovc.substack.com/p/design-partners-who-are-they-and type: technical_blog published: 2024-05-20 reliability: high - id: src6 title: "Running a Successful Design Partner Program" author: Garuda Ventures url: https://garuda.substack.com/p/design-partner type: technical_blog published: 2024-08-15 reliability: high - id: src7 title: "Founder's Guide — Choose Your First Design Partners" author: Horizon Capital url: https://horizoncap.vc/founders-guide-choose-your-first-design-partners/ type: technical_blog published: 2024-11-01 reliability: high - id: src8 title: "How to Choose and Run Design Partners That Don't Waste Six Months of Your Runway" author: Building Alpha url: https://buildingalpha.substack.com/p/how-to-choose-and-run-design-partners type: technical_blog published: 2025-02-10 reliability: high --- # 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 and provide feedback on - [ ] **Problem hypothesis** — documented assumption about the problem you solve, 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 in your target market [src1] ## Constraints - Design partners are not beta testers and not pilot customers. They collaborate on product direction before you have 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 and slows iteration. [src1] [src7] - All feedback IP must be assigned to the vendor in writing. Ambiguous IP ownership creates serious problems during fundraising diligence or acquisition. [src2] [src3] - Do not optimize for early revenue from design partners. Prioritize raw, honest feedback over monetization — charging too early filters out candid criticism. [src1] - Each engagement should have a hard end date of 6-12 weeks. Open-ended engagements lose momentum and delay product-market fit validation. [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 ``` | Path | Tools | Cost | Time to First Partner | Success Rate | |------|-------|------|----------------------|-------------| | A: Warm Outreach | Email + Calendly | $0 | 1-2 weeks | High (40-60% conversion) | | B: Hybrid | Email + LinkedIn + Calendly | $0 | 2-3 weeks | Moderate (25-40%) | | C: Cold Outreach | LinkedIn Sales Nav + email | $0-80/mo | 3-4 weeks | Lower (10-20%) | | D: Investor-Facilitated | Investor intros + Calendly | $0 | 1-2 weeks | Highest (50-70%) | ## Execution Flow ### Step 1: Define Partner Selection Criteria **Duration**: 1-2 hours **Tool**: Google Docs or Notion Establish your three-part selection framework before reaching out to anyone. Every prospective partner must pass all three filters. [src1] ``` DESIGN PARTNER SELECTION CRITERIA ══════════════════════════════════════════════ Filter 1: REPRESENTATIVENESS (ICP Match) - Company size: _____ employees - Industry: _____ - Tech stack: _____ - Buying process: [ ] Self-serve [ ] Sales-led [ ] Committee - Must represent your ACTUAL target buyer, not aspirational logos Filter 2: URGENCY (Pain Level) - Problem frequency: [ ] Daily [ ] Weekly [ ] Monthly - Current workaround: _____ - Cost of status quo: $_____ /month (time, money, or opportunity) - Quick test: Will they commit to a 30-min call next week? [ ] Yes → proceed [ ] No → deprioritize Filter 3: CAPACITY (Ability to Engage) - Internal champion: Name: _____ Title: _____ - Champion is actual user (not just executive sponsor)? [ ] Yes [ ] No - Can commit to weekly 30-min sessions for 8-12 weeks? [ ] Yes [ ] No - Has authority to implement/test your product? [ ] Yes [ ] No SCORING: Must pass ALL three filters. Failing any one = skip. ``` **Verify**: You have written criteria for all three filters with specific, measurable thresholds for your market. **If failed**: If you cannot define your ICP clearly, stop and complete customer discovery interviews first before recruiting partners. ### Step 2: Build Outreach Pipeline **Duration**: 2-4 hours **Tool**: Google Sheets or CRM (HubSpot free tier) 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. [src1] [src6] ``` PARTNER PROSPECT TRACKER (Google Sheets) ══════════════════════════════════════════════ Columns: A: Company Name B: Contact Name C: Title D: Source (warm intro / cold / community) E: Introducer Name (if warm) F: ICP Match Score (1-5) G: Urgency Signal (what pain indicator you observed) H: Status (prospect / contacted / call scheduled / interested / signed / declined) I: Next Action J: Notes Sourcing channels (prioritize top-down): 1. Ask investors: "Who in your portfolio has [problem X]?" 2. Ask advisors: "Who do you know struggling with [problem X]?" 3. LinkedIn search: [ICP title] + [industry] + [pain keyword] 4. Community forums: relevant Slack groups, Discord servers, Reddit 5. Twitter/X: search for people complaining about the problem 6. Conference/meetup attendees from your target segment ``` **Verify**: Pipeline has at least 15 prospects with ICP match score of 3+ and at least 5 warm introductions. **If failed**: If fewer than 5 warm intros, switch to Path B or C. Ask every person you 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/Google Meet Send personalized outreach, then run 20-minute discovery calls to qualify prospects before proposing the partnership. ``` OUTREACH EMAIL TEMPLATE (Warm Intro) ══════════════════════════════════════════════ Subject: [Introducer] suggested we connect — [problem] in [their industry] Hi [Name], [Introducer] mentioned you're dealing with [specific pain point]. We're building [one-sentence product description] and looking for 3-5 design partners to shape the product before launch. What this means for you: - Free access to the product during development - Direct influence on features and roadmap - Weekly 30-min feedback sessions for 8 weeks - Preferred pricing when we launch commercially Time commitment: 30 minutes/week for 8-12 weeks. Would you have 20 minutes this week to see if this is a fit? [Calendly link] OUTREACH EMAIL TEMPLATE (Cold) ══════════════════════════════════════════════ Subject: Solving [specific problem] — looking for design partners Hi [Name], I noticed [specific signal: their blog post, job posting, LinkedIn comment, or public complaint about the problem]. We're building [one-sentence description] and recruiting 3-5 design partners to co-develop the solution. Partners get free access, roadmap influence, and preferred pricing at launch. Commitment: 30 min/week for 8-12 weeks. Interested in a quick 20-min call to explore fit? [Calendly link] DISCOVERY CALL AGENDA (20 minutes) ══════════════════════════════════════════════ Minutes 0-5: Your background and what you're building (brief) Minutes 5-12: Their pain — how they experience the problem today - "Walk me through how you handle [X] today." - "What's the most frustrating part?" - "What have you tried? What didn't work?" Minutes 12-17: Partnership fit assessment - "If we built this, would you use it this quarter?" - "Who else on your team would need to be involved?" - "Can you commit to 30 min/week for 8 weeks?" Minutes 17-20: Next steps - If qualified: "I'll send over our design partner MOU this week." - If not qualified: "Thanks — can I check back in 3 months?" ``` **Verify**: At least 5 discovery calls completed with 3+ prospects expressing strong interest (willing to commit time and sign an agreement). **If failed**: If conversion from call to interest is below 30%, your problem framing may not resonate. Revisit your problem hypothesis before continuing outreach. ### Step 4: Draft and Send Design Partner Agreement **Duration**: 2-3 hours (drafting) + 1-2 days (review cycle) **Tool**: Google Docs Draft a lightweight MOU covering scope, timeline, feedback expectations, IP assignment, and graduation terms. Keep it to 2-3 pages — heavy legal documents scare off early partners. [src4] [src3] ``` DESIGN PARTNER MOU — KEY SECTIONS ══════════════════════════════════════════════ 1. PARTIES & PURPOSE "This MOU establishes a design partnership between [Company] ('Provider') and [Partner] ('Partner') to validate and shape [Product Name] through structured feedback and collaboration." 2. SCOPE - Job to be done: [specific workflow or problem] - Users involved: [role titles, number of seats] - 3-5 deliverables from Provider (e.g., working prototype, weekly builds, onboarding support) - Explicit NON-GOALS to prevent scope creep 3. TERM - Start date: [date] - End date: [8-12 weeks from start] - Decision meeting: scheduled for final week - Renewal: by written agreement only 4. FEEDBACK OBLIGATIONS - Weekly 30-45 min session (fixed day/time) - Named partner contact: [name, title] - Named provider contact: [name, title] - Partner agrees to provide candid product feedback 5. KPI (One Primary Metric) - Metric: [e.g., "reduction in manual processing time"] - Baseline: [current state] - Target: [goal — e.g., "30% reduction by week 8"] - Measurement: [how you'll track it] 6. INTELLECTUAL PROPERTY - Provider retains ALL rights to the Product - Partner assigns all feedback, suggestions, and enhancement ideas to Provider - Partner retains ownership of their own data 7. CONFIDENTIALITY - Mutual NDA (attach separately or include inline) - 2-3 year confidentiality term - Standard carve-outs (public info, prior knowledge) 8. REFERENCE PERMISSIONS (Conditional on KPI Achievement) [ ] Logo use on Provider website [ ] Public testimonial quote [ ] Joint case study (Partner review before publication) Permissions unlock ONLY if KPI target is met. 9. FEES & GRADUATION - During partnership: $0 (free access) - Upon successful completion: preferred pricing offer at [X]% discount for [12] months - If KPI not met: partnership ends, no obligations 10. TERMINATION - Either party may terminate with 14 days written notice - Upon termination: access revoked, confidential info returned/destroyed SIGNATURES Provider: _____ Date: _____ Partner: _____ Date: _____ ``` **Verify**: Agreement covers all 10 sections above. IP assignment clause is explicit (not implied). Have a legal-savvy advisor review if possible, or use Common Paper's open-source template as a base. [src3] **If failed**: If partners resist signing, simplify further — a mutual email confirming scope, timeline, and IP assignment is better than no agreement at all. Never proceed without IP assignment in writing. [src2] ### Step 5: Onboard Partners and Launch Feedback Cadence **Duration**: 1-2 hours per partner **Tool**: Calendly + Zoom/Meet + Google Sheets Once agreements are signed, onboard each partner within 7 days. Set up the recurring feedback infrastructure. [src4] [src6] ``` PARTNER ONBOARDING CHECKLIST ══════════════════════════════════════════════ [ ] Signed MOU received and filed [ ] Product access provisioned (account created, credentials sent) [ ] Kickoff call scheduled within 7 days of signing [ ] Recurring weekly session booked (same day/time for 8-12 weeks) [ ] Partner added to feedback tracking spreadsheet [ ] Slack/email channel created for async questions [ ] Decision meeting pre-scheduled for final week KICKOFF CALL AGENDA (45 minutes) ══════════════════════════════════════════════ Minutes 0-10: Restate scope, KPI, and timeline Minutes 10-25: Product walkthrough / initial setup together Minutes 25-35: Collect baseline measurement for KPI Minutes 35-40: Confirm weekly session format and expectations Minutes 40-45: Q&A, confirm next session date WEEKLY FEEDBACK SESSION TEMPLATE (30 minutes) ══════════════════════════════════════════════ Minutes 0-5: KPI check — review metric trend Minutes 5-10: Review what was shipped since last session Minutes 10-20: Structured feedback collection: - "What worked well this week?" - "What was frustrating or broken?" - "What's the one thing that would make the biggest difference to your workflow?" Minutes 20-25: Prioritize next 1-2 things to build/fix Minutes 25-30: Confirm action items for both sides FEEDBACK LOG (Google Sheets) ══════════════════════════════════════════════ Columns: A: Date B: Partner Name C: Feedback Category (UX / Feature / Bug / Pricing / Workflow) D: Verbatim Feedback (exact words) E: Severity (blocker / important / nice-to-have) F: Frequency (how many partners mentioned this) G: Product Decision (build / defer / reject) H: Status (logged / in-progress / shipped / declined) ``` **Verify**: All partners have completed kickoff calls, have product access, and have the first 4 weekly sessions on the calendar. Feedback log is set up and accessible to the team. **If failed**: If a partner misses the kickoff or first two sessions, they lack urgency. Replace them with the next prospect in your pipeline — do not chase disengaged partners. ### Step 6: Run the Program and Prepare Graduation **Duration**: 8-12 weeks (ongoing) **Tool**: All of the above Execute weekly sessions, track feedback, and prepare for the graduation decision at the end of the term. [src6] [src8] ``` PROGRAM MANAGEMENT CADENCE ══════════════════════════════════════════════ Weekly: - Run all partner feedback sessions - Update feedback log after each session - Ship at least one partner-influenced improvement - Send async update to all partners: what you built, what's next Bi-weekly: - Cross-partner analysis: which themes appear across 2+ partners? - Apply the "dependency test" for each feature request: "Would I build this if this partner disappeared tomorrow?" - Update product roadmap based on cross-partner patterns Week 6-8 (Mid-point Check): - Review KPI progress with each partner - Assess engagement level (attendance, feedback quality) - Replace disengaged partners if needed Final Week — GRADUATION DECISION MEETING ══════════════════════════════════════════════ Agenda (30 minutes per partner): 1. Review KPI: did we hit the target? (5 min) 2. Value assessment: "Has this been worth your time?" (5 min) 3. Willingness to pay: "At $X/month, would you continue?" (10 min) 4. Reference permissions: confirm logo/quote/case study (5 min) 5. Next steps: paid conversion or friendly conclusion (5 min) Graduation outcomes: - KPI met + willing to pay → Convert to paid customer - KPI met + not willing to pay → Capture case study, end engagement - KPI not met → Analyze why, end engagement, apply learnings - Partner requests extension → Max 4 additional weeks with new KPI Conversion pricing: - Standard: 20-30% discount off list price for 12 months - Premium: 40-50% discount if they commit to annual contract + case study ``` **Verify**: At least 2 of your 3-5 partners complete the full program. At least 1 partner converts to paid or commits to a case study. You have a cross-partner feedback synthesis identifying the top 3 product priorities. **If failed**: If zero partners are willing to pay, this is a strong signal that you have not achieved product-market fit. Review feedback logs for the gap between what partners need and what you built. [src8] ## Output Schema ```json { "output_type": "design_partner_program", "format": "document_bundle", "components": [ {"name": "partner_selection_criteria", "type": "document", "description": "Three-filter scoring rubric for evaluating prospective partners", "required": true}, {"name": "prospect_pipeline", "type": "spreadsheet", "description": "Tracked list of 15-25 prospects with status, ICP score, and next actions", "required": true}, {"name": "outreach_templates", "type": "document", "description": "Warm and cold outreach emails plus discovery call agenda", "required": true}, {"name": "design_partner_mou", "type": "document", "description": "2-3 page MOU covering scope, IP, KPI, timeline, and graduation terms", "required": true}, {"name": "feedback_log", "type": "spreadsheet", "description": "Running log of all partner feedback with categorization and product decisions", "required": true}, {"name": "graduation_report", "type": "document", "description": "Per-partner KPI results, conversion decisions, and cross-partner synthesis", "required": false} ], "expected_partner_count": "3-5", "program_duration": "8-12 weeks", "deduplication_key": "partner_company_name" } ``` ## Quality Benchmarks | Quality Metric | Minimum Acceptable | Good | Excellent | |---------------|-------------------|------|-----------| | Partners signed | 3 | 4-5 | 5-7 with waitlist | | Session attendance rate | > 70% | > 85% | > 95% | | Feedback themes across 2+ partners | 3 themes | 5-7 themes | 8+ themes with clear priority | | Partner-to-paid conversion | 0% (learning value) | 20-30% (1 of 4) | 50%+ (2+ of 4) | | Time from outreach to first signed partner | < 4 weeks | < 2 weeks | < 1 week | **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 before retrying. ## Error Handling | Error | Likely Cause | Recovery Action | |-------|-------------|----------------| | Cannot find 15 prospects matching ICP | ICP definition too narrow or niche too small | Broaden one filter (company size or industry) while keeping pain urgency high | | Partners sign but do not attend sessions | They lack genuine urgency or champion is not the actual user | Replace with next prospect; in discovery call, verify the champion is the daily user, not just an executive [src1] | | All feedback points in different directions | Partners are not representative of the same ICP segment | Review selection criteria; you may have recruited from different segments unintentionally | | Partner wants custom features unrelated to vision | Single partner is an outlier, or your vision does not match market need | Apply dependency test: "Would I build this if they disappeared?" If no, log and defer [src8] | | Partner refuses to sign IP assignment clause | Legal team pushback at larger companies | Offer mutual confidentiality + narrow IP scope to "product suggestions and feedback only"; escalate to partner's exec sponsor | | Partner wants to pay immediately (skipping program) | Strong product-market fit signal for this segment | Accept payment but still run the feedback program — paying partners give even more honest feedback [src6] | ## Cost Breakdown | Component | Free Tier | Paid Tier | At Scale | |-----------|-----------|-----------|----------| | Agreement drafting | Google Docs ($0) | Lawyer review ($200-500) | Standardized template ($0 recurring) | | Outreach tools | Email + LinkedIn free ($0) | LinkedIn Sales Nav ($80/mo) | CRM + Sales Nav ($150/mo) | | Scheduling | Calendly free ($0) | Calendly Pro ($10/mo) | Calendly Teams ($16/mo) | | Feedback tracking | Google Sheets ($0) | Airtable Pro ($20/mo) | Productboard ($20/mo) | | Video calls | Zoom free ($0) | Zoom Pro ($13/mo) | Zoom Business ($18/mo) | | **Total for one cohort (8-12 weeks)** | **$0** | **$200-700** | **$200-400/mo ongoing** | ## 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 after signing 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 uncomfortable 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, which creates healthy urgency and forces a clear buy/no-buy decision. [src4] [src6] ### Wrong: Treating design partner traction as revenue traction Founders tell investors "we have 5 design partners" as if it were customer traction. Design partners are not customers — they are getting free access in exchange for feedback. Investors know the difference. [src5] ### Correct: Separate design partners from paying customers in all reporting Track design partners and paying customers 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. ## Related Units - [Startup Idea Structuring Template](/business/startup-planning/startup-idea-structuring-template/2026) — prerequisite: define the problem hypothesis before recruiting partners - [Problem Interview Script Template](/business/customer-validation/problem-interview-script-template/2026) — structured interview scripts for partner feedback sessions - [Beta Testing Program Design](/business/customer-validation/beta-testing-program-design/2026) — next stage after design partners validate PMF direction - [ICP Definition Framework](/business/customer-validation/icp-definition/2026) — prerequisite: define your ideal customer profile before recruiting