The short answer
To win paying design partners, target a tight ICP, reach owners and buyers from the founder's own LinkedIn and email, and offer a fixed-length partnership at a paid, discounted price. Sign a letter of intent first, then a paid agreement with an agreed success measure, and use a design partner waitlist to create urgency for buyers not ready yet.
Key takeaways
- Design partners should pay, because payment proves pricing and makes both sides commit, while a free pilot is only a conversation.
- Keep the cohort small and the ICP tight: five to 10 partners from one buyer type, one revenue band and one urgent problem.
- Outreach works from the founder's own account, in the founder's words, with copy tested every round and judged on calls booked.
- Sign an LOI first, then a paid agreement that fixes price, scope, length, commitments, the success measure and case study rights.
- A design partner waitlist turns not yet into urgency, and every converted partner becomes the case study your next buyers ask for.
What is a design partner?
A design partner is an early customer who uses your product inside their own business and helps you shape it before general launch, in exchange for early access and a lower price. They are not a beta tester and not a friendly adviser. They are a buyer who has agreed to work with you on a fixed problem for a fixed period.
a16z defines design partners as the first few users who help you define the problem space and shape your solution as you prepare the product for market. Bessemer describes them as a small, deliberately selected cohort of target customers who shape the product from the very beginning, in exchange for early access and discounted pricing.
The number is small on purpose. a16z recommends five to 10 design partners and warns against signing more than 20, because every extra partner adds conversations and expectations to manage. Bessemer puts the usual range at five to 12. Pick a number you can serve personally, because the founder runs every one of these relationships.
This article is about winning those first partners. Once you have them, From 10 design partners to 100 customers covers how to grow past your network.
Should design partners pay?
Yes. A paying design partner proves that someone will pay for the problem you solve, and it tests your pricing before you publish it. A free partner gives you feedback. A paid partner gives you feedback, evidence for investors and a commitment strong enough to get internal approvals moving.
There is a real debate here. a16z argues that pricing negotiations early on can slow down the work of building the product, and that conversion to paid comes once the product is ready for market. Bessemer takes the harder line that indefinite free access is an advisory relationship, not a validation signal, and that a programme needs a hard deadline and a binary ask: go paid or do not.
First Round Review's account of Sierra's design partner programme shows the paid approach working. Sierra made the fee large enough that a buyer had to get approval from their boss and go through procurement, which filtered out companies only curious about AI.
“10-20% of your total contract value feels right.”
Sierra set out to sign four design partners and ended up with six. All of them converted to customers, and First Round reports that more than half of Sierra's product offering today came directly from design partner requests. Payment kept both sides serious.
For an accelerator founder the case for paid is sharper still. You are building and raising at the same time. Revenue from design partners, even small revenue, is the clearest proof you can put in front of an investor that your pricing holds.
Who should you target as a design partner?
Target a tight ICP: one type of buyer, in one revenue band, with one urgent problem your product already addresses. a16z's framework asks for three things in each partner. They represent your target market, they have urgency because they have already tried workarounds, and they have the capacity to implement and give regular feedback.
Tightness matters because design partners shape your roadmap. If your five partners are five different kinds of company, you build five different products. If they are the same kind of company, every request points the same way and the roadmap sharpens.
Worked case: AI personalisation for ecommerce
An accelerator-stage martech startup was building AI-driven 1:1 personalisation for ecommerce and DTC brands. It was pre-revenue with a working product, and the founder needed paying design partners to prove pricing and shape the roadmap while building and raising at the same time. Generic outbound was getting ignored.
The ICP was set tight: DTC brands in the $5M to $30M revenue range, plus a few larger groups as stretch accounts. The result shows why. The $15M to $30M band held 8 of the 17 brands in qualified pipeline and 43% of pipeline value.
Pipeline by brand revenue band, AI personalisation for ecommerce
ARR potential by brand revenue band. The $15M to 30M band holds 8 of the 17 brands and 43% of pipeline value. Larger groups came in through the same founder-led outreach.
Two lessons come out of those numbers. The core band carried the pipeline, which confirms the ICP. The single largest opportunity, $100K from a $500M+ group, came from a stretch account, which is why you keep a few on the list without letting them define it.
How do you find and reach design partners pre-revenue?
Reach them from the founder's own LinkedIn and email, in the founder's words, about a problem they already feel. Buyers agree to a design partnership with a person, not a sequence. Paul Graham put the starting point plainly in Do Things that Don't Scale:
“The most common unscalable thing founders have to do at the start is to recruit users manually.”
A first message that earns a design partner conversation does four things. Keep it short enough to read on a phone.
- Names the problem in their words. One line about the cost they already carry, not a description of your product.
- Shows why you, why now. The founder's own reason for building this, in one sentence.
- Makes a specific offer. A small number of design partner places, a fixed period and a paid, discounted price.
- Asks for one thing. A 20-minute call to see whether the problem fits, not a demo request.
Manual does not mean small. In the ecommerce case, outreach went out from the founder's LinkedIn and email at volume, sharpened every round. Angles on conversion, order value and repeat purchase were tested in the open. What booked calls was kept and the rest was cut.
Worked case: revenue cycle AI
An accelerator-stage revenue cycle AI company automates billing and collections and grows by partnering with and then acquiring independent RCM companies, running them on its own AI. The buyer is an owner deciding who to trust with a business they spent years building, so standard SaaS outbound does not start the conversation.
- Straight to the owner. Lists of independent billing and revenue cycle firms, with outreach to founders and owners, never procurement.
- A message about their future. Succession, staffing, margins and the cost of keeping up with technology, tested with the founder until replies became calls.
- Design partner first. A design partnership lowered the stakes and let owners see the product inside their own operation.
- The founder in every room. Codax kept the calendar full and the founder ran every conversation from first call to terms.
The result was $8M ARR in design partnership across two acquisitions, one at $7M ARR and one at $1M ARR, from a $15M acquisition pipeline. That is 53% of the acquisition pipeline in design partnership, with further targets worth $7M ARR still in pipeline.
What goes in a design partner agreement?
A design partner agreement sets the price, the scope, the length, what each side commits to and how the partnership ends. Keep it to a few pages. Its job is to make expectations explicit so that the conversion conversation at the end is a formality.
Sequence it in two steps. First a letter of intent (LOI), which records that the partner wants to work with you on a defined problem at a stated price. Then the paid agreement, signed once the scope is agreed. The LOI is quick to sign and gives you something concrete to show investors. The paid agreement is the proof.
Design partner terms checklist
| Term | What to agree | Why it matters |
|---|---|---|
| Price | A paid fee below list price, stated in writing | Proves willingness to pay and tests pricing |
| Scope | One core problem and the workflows in scope | Stops the roadmap splitting across partners |
| Length | A fixed period with a start and end date | A deadline makes both sides show up |
| Founder commits | Regular check-ins, fast fixes, direct access | Partners give time when they see progress |
| Partner commits | Named owner, real data, scheduled feedback | Without capacity there is no learning |
| Success measure | One agreed outcome measured in their business | Turns the end date into a decision |
| Conversion | Full price and terms after the period | The binary ask is agreed at the start |
| Proof rights | Case study, reference and logo use | Your next customers need proof from this one |
On length, a16z suggests one, three or six months. Sierra's view, reported by First Round, was that under two months is too short and over six months is too long. Three months is a sensible default for most products. On cadence, a16z gives biweekly check-ins as an example of the feedback frequency to write into the contract.
On price, use Sierra's 10 to 20% of total contract value as a floor for seriousness. For example, if your full contract will be $60K a year, a design partner fee of 10 to 20% is $6K to $12K. The ecommerce startup charged its three paying design partners $3.5K a month each, which gave it $10.5K in monthly revenue while the founder was still proving pricing.
How does a design partner waitlist create urgency?
A design partner waitlist turns a no into a not yet. Some good-fit buyers will not commit this quarter. Instead of dropping them, offer a place on a named waitlist for the next cohort, with a limited number of places.
In the ecommerce case, brands that were not ready to commit joined a design partner waitlist. It kept them warm and created urgency, because places in a cohort that closes are worth more than an open offer. The funnel below shows how the programme narrowed from pipeline to paying partners.
From qualified pipeline to paying design partners, AI personalisation for ecommerce
$472K pipeline value, $28K average ARR potential per brand
$126K in signed letters of intent
$3.5K a month each, $10.5K monthly revenue
Run the waitlist properly. Tell people how many places the next cohort has and when it opens. Send waitlisted buyers the same progress updates your partners see. When a place opens, offer it to the best-fit account first, not the first name on the list.
How do you run a design partnership so it converts?
Run it against the success measure you agreed at the start, with a fixed cadence and the founder in every review. Conversion is decided by what the partner sees in their own business, so make that result visible every few weeks, not only at the end.
Running a design partnership, start to case study
Kick off with the measure
Restate the one outcome you will judge the partnership on, and record the baseline in their business.
Ship inside their operation fast
Get a working version into their real workflow early. Sierra aimed to build the first version of each agent within two weeks.
Hold a fixed cadence
Check-ins on the schedule in the contract, with a named owner on each side. Sierra ran weekly 30-minute standups.
Filter every request
Build what moves the core problem. Log the rest for later.
Review against the baseline
Show the result in their numbers at the midpoint and before the end date.
Make the binary ask
Full price on the agreed terms, or a clean exit. No open-ended extensions.
Capture the proof
Ask for the case study and reference in the same meeting as the contract.
Case studies are where a design partnership pays twice. Every new buyer asks who else uses you. A partner who signs a full contract and agrees to a case study gives you the answer, and gives your outreach a line no competitor can copy. Write the case study around the success measure, with their baseline and their result.
How does Codax help founders win design partners?
Codax amplifies the founder. The founder owns the product and roadmap, the thesis and the voice, every sales call, closing and terms. Codax builds target lists and buying signals, writes copy with the founder, runs LinkedIn and email outreach at volume and holds a monthly pipeline review. Copy is tested together every round, and what books calls gets more volume.
Codax is a growth department. A growth department is one senior team that owns qualified pipeline end to end, from strategy to execution, under a single accountable lead. For founders, the five phases work like this:
- Assess: the founder's thesis, the buyer and what a design partner needs to see.
- Fix: the founder's profile and positioning, ready for buyers who look them up.
- Build: target lists, signals and sequences across LinkedIn and email.
- Test: copy written with the founder, judged on replies and calls booked.
- Scale: more volume behind what works, with a monthly pipeline review setting the next round.
The two alternatives both fail at this stage. Hiring a sales team is too early, because there is no playbook to hand over yet and the message is still being found. Leaving it all to the founder is too slow, because every hour spent prospecting is an hour away from the product. Amplifying the founder gives you speed, with the founder's voice reaching more of the right people and their hours going into calls that close.
The same principle shows up in Codax's larger engagements. In the agentic AI healthcare engagement, the CEO as the sender produced 3x the replies. For more on running founder outreach, read Outbound for founders, and for the wider plan see The YC growth playbook and the accelerator founders hub.
Questions and answers
How do you get design partners for a startup?
Define a tight ICP, build a list of companies that match it and reach the decision maker from the founder's own LinkedIn and email. Lead with a problem they already feel, offer a fixed-length paid partnership and ask for a letter of intent first. Put buyers who are not ready on a design partner waitlist for the next cohort.
Should design partners pay?
Yes. Payment proves willingness to pay, tests your pricing and gets internal approvals moving. Sierra asked its design partners for 10 to 20% of total contract value, and all six converted to customers.
What should a design partner agreement include?
Price, scope, length, what the founder commits to, what the partner commits to, one agreed success measure, the conversion terms after the period and rights to a case study and reference. Keep it to a few pages so it signs quickly.
What is an LOI from a design partner?
A letter of intent records that a company wants to work with you on a defined problem at a stated price, before the full agreement is signed. It is quick to sign and gives investors concrete evidence of demand. In the ecommerce case, 4 brands signed LOIs worth $126K and 3 became paying design partners.
How many design partners should a startup have?
Five to 10 is the usual range. a16z warns against signing more than 20 because every extra partner adds conversations and expectations to manage. Pick the number the founder can serve personally.
Sources
- A Framework for Finding a Design Partner, a16z
- The Hard Way Pays Off: Inside Sierra's Design Partner Strategy, First Round Review
- Design partners: the pre-launch edge most AI founders ignore, Bessemer Venture Partners
- Do Things that Don't Scale, Paul Graham





