okaihub

The Founder's Guide to Getting Design Partners for an AI Product

How to recruit design partners for an AI product, what to trade for their time, how to structure the relationship and when to end it.

Published 2026-11-11 · 4 min read

A design partner is a user who agrees to work with you closely while the product is unfinished, in exchange for influence over what gets built. It is the most efficient way to turn an AI product from a demo into something people depend on, and it is also easy to do badly.

Done badly it means free labour for a company that never ships what was promised. Done well it produces your first real case studies, your most honest feedback and often your first paying customers.

What you are actually trading

Design partners are not early customers and they are not beta testers. The exchange is specific: they give you time, candour and access to a real workflow; you give them influence and early access. Being clear about that trade is what prevents resentment later.

They giveYou give
An hour or two a week, reliablyDirect access to whoever builds the product
Honest criticism, including the unflattering kindA genuine vote on what gets built next
Real data and real workflows to test againstEarly access to features before they are public
Willingness to be named in a case study laterUsually a discount, extended free period, or both
The right column is not optional. If you cannot offer influence, you are recruiting beta testers, and you should say so.

How many, and who

Three to five is the workable range. Fewer than three and you are optimising for one company's unusual situation; more than five and you cannot maintain the relationship properly alongside building.

Choose for spread rather than for enthusiasm:

  • Different sizes. A solo user and a team of twenty hit completely different problems, and you need to know which you are building for.
  • Different maturity. One that has never solved this problem, one with a spreadsheet workaround, one with an existing tool they dislike. Each reveals a different part of the market.
  • At least one who is sceptical. Enthusiastic partners tell you what you want to hear. The one who doubts it will find the failure modes.
  • Nobody you cannot afford to disappoint. A design partner relationship that goes badly is worse than never having had one, especially in a small market where everyone knows everyone.

Finding them

  1. 1

    Start with people who already replied to you

    Anyone who answered a cold message, commented on a post or signed up and actually used the product has already volunteered. Ask them first — the conversion rate is far higher than cold recruiting.

  2. 2

    Ask for the problem, not the participation

    "We are trying to understand how teams handle X, and we are building something for it. Would you talk to us about how you do it today?" This gets a yes more often than "join our design partner programme".

  3. 3

    Look in the communities where the problem is discussed

    People complaining about an existing tool are ideal candidates: they have the problem, they have tried to solve it, and they are dissatisfied.

  4. 4

    Offer the trade explicitly in the first conversation

    Time commitment, what they get, how long it runs. Ambiguity here is what produces partners who vanish after week two.

Structuring it so it actually works

  • A fixed cadence. Every two weeks, thirty minutes, on the calendar. Ad-hoc contact drifts to zero within a month no matter how enthusiastic everyone is.
  • A shared place for feedback. One channel, one document, one thread — not three. If feedback is scattered it does not get acted on, and partners notice.
  • A visible loop back. The single most important practice: tell them what you built as a result of what they said, and when you decided not to, explain why. Partners who never see their input land stop giving it.
  • A defined end. Eight to twelve weeks, with an explicit conversation at the end about continuing, converting to a paid plan, or parting well. Open-ended arrangements decay into neglect.

What to collect

ArtefactWhy it matters
Their words for the problemBecomes your headline, description and first-line copy — better than anything you write yourself
Their previous workflow, step by stepShows the real competitor, which is usually a manual process rather than another product
Where they hesitated in your productYour activation problem, in order of severity
What they went back toThe core feature, which is often not the one you built first
A quotable resultThe basis of your first case study — with explicit permission to use their name

Ending it well

Most design partner relationships should end. The product stabilises, the partner's needs are met or turn out to be atypical, or priorities change. Ending deliberately preserves the relationship; letting it lapse damages it.

  • Tell them the programme is closing and thank them specifically for what they contributed — name the actual changes.
  • Offer whatever you promised: the discount, the extended access, the case study with their approval.
  • Ask if they will stay as a reference. A former design partner who will take a call from a prospect is worth more than a new one.
  • Ask what would have made it better. The answers are how you run the next cohort.

The point of a design partner is not the feedback. It is that five people who understand your product deeply will tell the next fifty how it works, and they will be believed in a way you never will be.

More in Cold start