design-partner-finderlisted

Find, verify, qualify, compare, and manage companies as design partners, co-development partners, beta partners, paid pilots, lighthouse customers, or early adopters. Use for design-partner discovery, early-adopter shortlists, qualification of an existing candidate list, cohort selection, partner-readiness validation, active-partner review, or revalidation of prior candidates. Go deeper than generic prospecting by optimizing for learning value, urgency, representativeness, implementation feasibility, real user/champion access, mutual commitment, evidence quality, transferability, cohort coverage, and cost-to-learn. Separate desk-research fit from live readiness, preserve evidence lineage/freshness, and prevent prestige or contract size from replacing product-learning quality. Hand off broad lead generation to prospecting, research synthesis to customer-research, and outreach copy to cold-email.
MaciejZet/agent-skills · ★ 1 · AI & Automation · score 74

Install: claude install-skill MaciejZet/agent-skills

# Design Partner Finder Find the small set of organizations that can reduce product uncertainty quickly and credibly while remaining plausible early customers. Treat a design-partner program as a **learning system with commercial optionality**, not as a lead list or logo-collection exercise. ## Non-negotiable principles 1. Separate **desk-research fit** from **live partner readiness**. Never infer willingness, feedback commitment, user access, procurement approval, or pilot readiness from public evidence alone. 2. Optimize for **learning transferability**, not prestige. A famous company with weak problem evidence is a poor core design partner. 3. Decide the **engagement motion** before scoring. Research partner, design partner, beta partner, paid pilot, and lighthouse customer have different readiness gates. 4. Decide the **learning strategy** before composing a cohort. Narrow validation and deliberate segment exploration are both valid, but they answer different questions. 5. Treat every material claim as `observed`, `confirmed`, `inferred`, `unknown`, or `contradicted`; preserve source lineage and freshness. 6. Use behavior over opinions after activation. Product usage, implementation progress, recurring feedback, and real workflow evidence outrank enthusiasm on calls. 7. Do not let one partner silently become the roadmap. Classify requests by transferability and require explicit exceptions for bespoke work. 8. Preserve rejected and near-miss candidates with reasons so f