Design partners — the YC pre-PMF playbook.
The design partner is the canonical pre-PMF B2B motion — the structured arrangement between a not-yet-PMF startup and a small set of customers willing to engage deeply with the product in exchange for influence, discount, or first-mover access. Most YC B2B teams attempt this motion in their first year. Most of them execute it badly.
Six chapters. When the design partner motion actually fits (and the segment of B2B teams that should skip it), how to recruit them at the volume required for product signal, how to structure the agreement so it produces value rather than scope creep, how to run the program operationally, how to convert at the end of the engagement, and the reference-customer handoff that turns design partners into the case studies that anchor the next 12 months of GTM.
A well-executed design partner program produces 4-7 referenceable logos, 2-4 paid conversions, $80-300K in initial ARR, and 9-18 months of product feedback that shapes the next major release. A poorly-executed program produces 1-2 referenceable logos, 0-1 paid conversions, scope creep that distracts the engineering team, and 9-18 months of false-positive product signal from customers selected to please the founders. The asymmetry runs the same way as every other reference in this library — the operational discipline is the binding constraint.
Layer one — strategy and recruitment.
When the design partner motion fits
The pre-PMF B2B teams where design partners produce real product signal, the post-PMF teams where they produce noise, the consumer/PLG GTMs where the format is structurally wrong, and the alternative motions (founder-led discovery, LOI-based pilot, paid-trial).
Recruiting design partners
The empirical 30-to-3 conversion rate from initial conversation to signed design partner, the ICP-fit prioritization, the warm-network vs cold-outbound mix, the YC-batch leverage pattern, and the operational pattern of converting outbound replies into structured design-partner conversations.
Layer two — structuring and running.
Structuring the agreement
The exchange architecture (what they give, what you give), the term length (3-9 months typical, with explicit end), the scope boundaries that prevent custom-development drift, the pricing-discount-vs-LOI question, and the legal-document template structure that survives the engagement.
Running the program
The weekly check-in cadence, the feedback-capture discipline, the per-partner success-criteria tracking, the founder-time-allocation rule (10-15 hours per partner per month for the first 90 days), and the operational anti-patterns that produce scope creep and false signal.
Layer three — conversion and handoff.
Converting design partners to paid
The empirical 30-60% conversion rate from design partner to paid customer at end-of-term, the per-stage conversion mechanics, the pricing conversation, the renewal-vs-upgrade framing, and the operational pattern that produces conversions above the typical industry mode.
The reference-customer handoff
The transition from design partner to referenceable customer, the case-study production workflow, the per-partner asset (logo, quote, case-study, mutual-intro), the published-case-study conversion impact on downstream sales (typical 1.4-2.1x reply-rate lift), and the long-term partner-relationship maintenance.
The design partner motion is the highest-stakes customer-development decision a pre-PMF team makes.
Allston Labs runs the recruitment and operational layer of the design partner motion alongside the upstream outbound infrastructure. Pipeline construction, structured-conversation scheduling, per-partner program ops, and the conversion-and-handoff workflow.