Design partners: how to find, choose and convert them
Updated By the SalesOne research team9 min read
The short answer
A design partner is an early customer who helps a B2B startup shape its product before launch, in return for early access and better terms. A good design partner program picks a handful of companies with a real, current problem, agrees the commitment in writing, sets an end date and asks each partner to go paid when it ends.
What is a design partner?
A design partner is a target customer who works with a startup while the product is still being shaped, giving regular feedback and real use in exchange for early access and better terms. Bessemer Venture Partners (Atlas, May 6, 2026) draws the line clearly: design partners help decide what to build, while beta users test something that already exists.
The difference matters because it changes who you pick. A beta user only needs to be willing to try the product. A design partner needs to own the problem you are solving, feel it now and be able to tell you whether your answer is worth paying for.
| Item | Design partner | Beta user | Pilot customer |
|---|---|---|---|
| When | Before or while the product is built | After a working version exists | When the product is close to ready |
| What they give | Problem detail, workflow access, regular feedback | Bug reports and usage | A real trial against agreed success criteria |
| What they get | Influence on the roadmap, early access, better terms | Early access | A decision based on results |
| Commitment | Scheduled sessions over a fixed period | Usually informal | A defined scope and end date |
| Ends with | A go-paid decision | Launch | A purchase decision |
How many design partners should a startup have?
Most startups should run a design partner program with somewhere between four and 12 companies, enough to see patterns and few enough to serve each one well. Bessemer reports that most practitioners recommend five to 12, and First Round Review (Sep 23, 2025) describes Sierra starting from a list of 40 candidates, aiming for four and ending with six. For where design partners fit among your first sales, see how to get your first customers.
Fewer than four and one loud partner can steer the product. More than a dozen and the founding team cannot give each partner the attention that makes the program work. The right number is the one where every partner gets a named owner on your side and a standing session on the calendar.
Who makes a good design partner?
A good design partner has the problem you solve today, someone senior who owns it, and the budget and authority to buy if you solve it. Lookalike traits such as size or industry are a weak test on their own; a problem you can link to the company is a strong one.
In the First Round Review interview, Sierra’s first go-to-market hire, Logan Randolph, describes what Sierra looked for: horizontal appeal, with partners across healthcare, CPG, media, retail and tech, larger companies where the problem was bigger, a concrete business problem rather than curiosity, and not too many warm introductions.
- Problem: the company has the problem now, and you can point to why (a change, a new target, a failed project, a new leader).
- Owner: one named person owns the problem and will attend the sessions.
- Ability to buy: the owner can get a purchase approved when the program ends.
- Representative: the company looks like the customers you want in two years, not an outlier with unusual needs.
- Variety: across the cohort, more than one industry or use case, so you do not build for one customer.
- Candor: few close friends, because friends are polite when a product is not working.
Write these tests down as an early ideal customer profile before you start looking. It keeps the cohort honest and becomes the first draft of who you sell to after launch.
How do you find design partners?
You find design partners by listing the companies most likely to have the problem now, reaching the person who owns it with a specific reason for writing, and asking for a short call about the problem rather than a product demo.
Your own network is the easy start, but Bessemer’s article argues for strangers: a cold yes carries no social obligation, so it is a more honest signal. It describes Strella recruiting all 12 of its design partners through cold outreach. A mix works for most founders: a few warm introductions for speed and a larger share of companies that owe you nothing.
| Source | Works when | Watch for |
|---|---|---|
| Your network and investors | The introduction is to someone who owns the problem | Polite feedback from people who want to help you |
| Former colleagues and customers | They now work where the problem lives | Choosing them for trust rather than fit |
| Communities and events | The problem is discussed openly there | Interest without a budget or an owner |
| Research-led outreach | Each note names what changed at the company and why the problem matters now | Generic messages sent to a long list |
The research-led route is the one founders usually skip because it takes time. It is also the one that teaches the most: if you cannot find a dated reason why a company would have the problem now, it is probably not a design partner yet. Our guides to trigger events in sales and founder-led outbound cover how to find those reasons and write the first note.
A sample design partner invitation
Fictional sample. Halvorsen Castings is a fictional foundry group in Toledo, Ohio. It announced a second plant on Sep 12, 2026 and named Ruth Adeyemi as COO on Aug 25, 2026. The sender is the founder of a fictional startup building software for foundry scheduling.
Subject: Scheduling two foundries from one team. Hi Ruth, congratulations on the COO role. With the second plant announced on Sep 12, melt and molding schedules will soon have to work across two sites. We are building software for exactly that and are choosing five foundries to shape it with us before launch: a 45-minute session every two weeks for three months, early access throughout and founding-customer pricing if you go ahead at the end. Would a 20-minute call about how you schedule today be useful, even if the answer is that it is not a fit? Dana Price, Founder.
Fictional sample: company, people and startup are fictional.
- Opening: a dated, checkable event and the problem it creates.
- The ask: the time commitment and the end date, stated up front.
- The trade: early access and better terms, with no price promised in the first note.
- The next step: a call about the problem, not a demo of the product.
What should a design partner agreement cover?
A design partner agreement should put the commitment on both sides in writing: what the partner gives, what the startup gives, how long it lasts, what it costs, and what happens at the end. A short agreement read by both sides beats a long one that nobody remembers.
| Term | What to agree | Why it matters |
|---|---|---|
| Scope | The problem you are working on together and the workflows the partner will test | Stops the program drifting into custom work for one customer |
| Partner commitment | A named owner, a session rhythm (for example every two weeks) and real use between sessions | Feedback without use is opinion |
| Startup commitment | Early access, a named contact, response times and roadmap input | The partner needs to see their input go somewhere |
| Length and end date | A fixed period, often two to six months | An end date forces the go-paid decision |
| Fees | Paid from the start, discounted, or free with a price agreed for after | Payment tests whether the problem is worth solving |
| Conversion | The price and terms that apply if the partner goes ahead | Removes a second negotiation at the end |
| Feedback and ideas | Who may use the feedback and ideas shared during the program | Avoids disputes once the feature ships |
| Confidentiality and data | What each side keeps confidential and how partner data is handled | Partners share real workflows and data |
| Reference rights | Whether you may name the partner, quote them or write a case study, and when | Ask now; it is harder after launch |
On length, Logan Randolph tells First Round Review that “under two months is probably too short and over six months is probably too long.” Agreement terms vary by company and country, so have your own counsel review yours.
Should design partners pay?
Design partners should usually pay something, because payment is the clearest evidence that the problem is worth solving and it gets the program the attention of someone who can buy. A discount rewards the extra work partners do; a free program often gets treated as optional.
Sierra structured its design partnerships as paid contracts, and all six partners were paying customers. Randolph suggests a commitment of about “10-20% of your total contract value,” saying anything less is not much of a commitment. If a partner will not pay anything, agree in writing what they will pay if the product does what you both set out to test.
How do you convert design partners to paying customers?
You convert design partners by agreeing the price and the success criteria at the start, showing progress against them during the program, and asking a clear yes-or-no question about going paid on the end date.
- At the start: write down the problem, how both sides will judge success, and the price that applies afterwards.
- During the program: send a short written summary after each session of what you heard and what changed in the product.
- Midway: review progress against the success criteria with the owner and the person who signs.
- Before the end: share the conversion terms again so nothing is a surprise.
- On the end date: ask the binary question Bessemer recommends, go paid or not, and treat a no as information about fit.
- After conversion: ask for the reference or case study you agreed at the start.
Bessemer’s point is worth keeping: enthusiasm on calls is not validation, conversion is. A partner who praises every session and declines to pay is telling you something the sessions did not. Our guide to how to qualify leads covers the same discipline after launch.
What did SalesOne learn from its own testing round?
In a SalesOne testing round with real customers under NDA, the results came from how accounts were qualified. The round was not a design partner program, but the lesson applies directly to choosing design partners.
With a consulting and strategy firm, more than 90% of the accounts found were a 90%+ fit to its own profile, and the research surfaced industries the firm had never considered. The clearest lesson cut the other way: companies were under 70% relevant whenever they could not be linked to an existing problem. That changed how SalesOne qualifies accounts, on a problem you can link to the company rather than on lookalike traits, and it is the same test this guide suggests for choosing design partners.
How does SalesOne help startups find design partners?
SalesOne does the research half of finding design partners, so founders spend their time on the conversations. S1 agents research the market, accept or reject each company against your profile with the reason, map the people who own the problem and draft a point of view for the first note.
A person approves every message before it is sent, and every approval is recorded with who gave it. Outreach rules decide who on your team may contact whom, and a reply pauses the account’s remaining steps. See how SalesOne works for startups and what account research covers.