How to find design partners for a B2B SaaS

To find design partners, pick one narrow type of company with an urgent problem, look for people who already describe that problem in public or in your network, and ask for a short, written commitment: regular feedback calls in exchange for early access and a discount. End the program with a fixed date to go paid or stop.

A design partner is not a beta user who tries your product once. Bessemer Venture Partners describes design partners as a small, deliberately selected group of target customers who shape the product from the start in exchange for early access and discounted pricing. The rest of this guide covers who to pick, how many, where to look, what to agree on, and how to close the program.

Decide who counts as a design partner

The most common mistake is to take anyone who says yes. Unusual Ventures calls the choice of the wrong design partners one of the most expensive missteps a startup can make. Its advice is to choose partners who move fast, care deeply, and are alike in geography, company size, industry, user title and buyer title.

That last rule matters more than it looks. If your five partners are a dental clinic, a law firm, a bakery chain, an agency and a hospital, you get five different roadmaps. If all five are small dental clinics with two to four chairs, their requests overlap, and the overlap is your product. Write the profile down before you look for anyone. If you have not done this yet, start with a narrow ideal customer profile.

Unusual also suggests a few qualifying questions. Has the company already spent money on the problem and failed to solve it? Can they help you measure what your product saves them? Will they commit to a feedback call of 30 to 45 minutes every two weeks? A partner who answers no to all three is a friendly contact, not a design partner.

How many design partners to look for

The published advice gives a range, not one number. Common Paper's guide to working with design partners says most startups start with five or fewer, so the founder can own each relationship. Bessemer says most practitioners recommend between five and 12. Garuda Ventures puts the number between 10 and 20 active participants.

For a solo founder or a team of two, the low end is the honest choice. Each partner costs you time every week, and the time is the limit, as the example below shows.

A worked example: the time five partners take

Take a hypothetical scheduling tool for dentists with five design partners. Unusual's cadence is one call of 30 to 45 minutes every two weeks. Garuda reports that most programs it heard about last no more than six months. Six months is about 26 weeks, so each partner gets 13 calls.

• Calls: 5 partners × 13 calls = 65 calls.
• Low end: 65 × 30 minutes = 1,950 minutes, or 32.5 hours.
• High end: 65 × 45 minutes = 2,925 minutes, or about 49 hours.
• Per week: 32.5 to 49 hours over 26 weeks is about 1.3 to 1.9 hours of calls.

That is only the calls. Add notes, follow-ups, fixes and the time to recruit them. With 12 partners, the same arithmetic gives 156 calls and 78 to 117 hours. Start with the number you can serve well.

Where to find design partners

Look where the problem is already said out loud. A person who wrote last week that their clinic loses hours to rescheduling is a better first call than a friend who might use the tool one day.

• Public threads on Reddit, Hacker News, X and Threads where people ask for a tool like yours or complain about the current one.
• Your own network and your investors' companies, filtered by the profile you wrote down.
• Direct outreach to the person who owns the problem at companies that fit the profile.
• People who answered an earlier post, survey or waitlist and named the problem in their own words.

Warm introductions are not the only route. Bessemer reports that Strella recruited all 12 of its design partners through cold LinkedIn outreach and avoided warm introductions on purpose. A cold message works when it goes to the right person and names their problem. For that step, see how to find the decision maker at a company.

This search is the part that takes the most hours, and it is where LitePal helps. A founder pastes their site, and LitePal finds public conversations on Reddit, Hacker News, X and Threads where people ask for a product like theirs, with a reply drafted for each. It also finds companies that fit, the decision-maker to write to with a checked email, and a drafted first line. The founder sends every message from their own accounts.

What to agree on before you start

Put the deal in writing, even if it is one page. Common Paper lists the commitments a design partner agreement covers: feedback sessions, private or public references, roadmap influence, discounts and services. Its own agreement lets either side end it at any time, and its IP section survives the end of the agreement.

• The meeting cadence: weekly, every two weeks or monthly, as Garuda lists.
• What the partner gets: early access, a say in the roadmap, a discount after launch.
• What you get: feedback, product use, and a reference or testimonial if it works.
• The end date and the milestone at which the partner becomes a regular customer.

Ask for the reference early. Garuda advises founders to ask for a testimonial, a commitment to be a reference and a referral to peers upfront, not at the end.

End the design partner program with a go-paid date

A program without an end turns into free consulting. Bessemer advises a hard deadline and a binary ask: go paid or do not. Strella's 12 partners met the team every two weeks and were promised a discount at launch, and all 12 converted. Garuda's advice points the same way: even a design partner should pay you something at the end.

Treat the go-paid date as your real test. A partner who gives feedback for six months but will not pay is telling you something about the problem, the price or the fit. A partner who pays is your first reference customer, and the start of founder-led sales to the next ten companies like them.

A checklist to find design partners

• Write one narrow profile: industry, size, user title, buyer title, region.
• Pick a number you can serve, often five or fewer for a small team.
• Look for people who already describe the problem in public or in your network.
• Qualify each one: past spend on the problem, a way to measure value, time for calls.
• Put the cadence, the exchange and the end date in a short written agreement.
• Ask for a reference and a referral at the start.
• Close with a fixed go-paid date and count who pays.

Your first design partners are probably already asking for help somewhere. Paste your site into LitePal to see the public threads where people describe the problem you solve, and the companies that fit, with a reply and a first line drafted for each.