The earliest version of your SaaS will be shaped less by your roadmap and more by the people who use it first. That is the premise behind design partnerships — a structured arrangement where a small cohort of carefully chosen customers helps you co-build the product in exchange for early access and genuine influence.
This guide explains what a design partner actually is, how they differ from ordinary beta testers, and exactly how to find, qualify, and work with them from day one.
What is a design partner?
A design partner is a customer who commits to a sustained, deep collaboration with your founding team. They are not passive observers who occasionally leave a comment in your feedback widget. They are active co-shapers: they attend recurring working sessions, stress-test half-built features, challenge your assumptions, and help you understand whether you are solving the right problem in the right way.
The term comes from hardware and enterprise software, where vendors would embed engineers inside a customer's team to prototype together. In SaaS the dynamic is lighter, but the principle is the same: you are exchanging influence and early access for honest, structured input from someone who has skin in the game.
The key word is structured. A design partnership is different from an informal arrangement where someone agrees to "take a look." It has a defined scope, a cadence, and mutual accountability.
Design partners vs. beta testers vs. regular customers
These three labels get conflated, but the distinctions matter for how you recruit, manage, and extract value from each group.
- Beta testers try a near-complete feature and report bugs or impressions, usually asynchronously. Their feedback is useful but shallow. The relationship is transactional and short-lived.
- Design partners are involved much earlier — often before a feature is built. They attend regular sessions, give ongoing structured feedback, and influence the direction of the roadmap. The commitment on both sides is high and the relationship spans months.
- Regular customers pay for and use what you ship. They give feedback opportunistically, through support tickets or NPS surveys. They are the goal, not the starting point.
A well-run design partnership is the bridge from "we think people have this problem" to "we know people have this problem, and here is how they want it solved." If you skip this stage, you risk shipping a product that is technically correct but commercially wrong.
How to find design partner candidates
Finding the right design partners is the hardest part. You need people who match your Ideal Customer Profile (ICP) closely enough that their input generalises, but who are also willing to invest real time in a pre-revenue product. That combination is rare.
Here are the most reliable sourcing channels:
- Your warm network. Start with first-degree connections who match your ICP. These conversations convert at a much higher rate than cold outreach. Ask your contacts for warm introductions: "Do you know a [role] at a [size] company who struggles with [specific problem]?"
- Niche communities. Slack groups, Discord servers, and subreddits built around your ICP's professional problems are high-signal sourcing grounds. Answer questions related to the pain you solve, become a visible member, and introduce your design partner programme when the fit is obvious.
- LinkedIn outreach. Boolean searches let you filter by role, company size, and industry. Keep your outreach short: explain the problem you are working on, the mutual benefit, and ask for a single 20-minute exploratory call — not a demo.
- Dedicated platforms. Services like first10 match founders with ICP-fit users who are actively open to trying early-stage products. This removes much of the cold-outreach grind and ensures the people you speak to already have context and intent.
Whichever channel you use, aim to have exploratory conversations with at least fifteen to twenty candidates before committing to your first cohort of three to five. Many will seem promising in a first call but reveal misfit once you go deeper.
How to qualify a design partner
Not everyone who seems enthusiastic will make a good design partner. Here are the qualifying signals to look for in your discovery calls:
- They have the problem today. They can describe a specific instance of the pain you solve, not a hypothetical. "We spend four hours a week doing this manually" is a qualifying statement. "That sounds like it could be useful" is not.
- They can commit time. A design partner who cannot attend a monthly session or respond to async questions within a week is not actually a partner — they are a passive user. Confirm availability before moving forward.
- They have decision-making proximity. Ideally your design partner is the person who would eventually purchase your product, or is close enough to that person to understand what would drive a buying decision.
- They give direct feedback. In your discovery call, notice how they respond to gentle challenge. Do they agree with everything you say? That is a red flag. The most valuable design partners push back when they disagree.
What to offer a design partner
The core exchange is straightforward: they give you time and honest input; you give them access and influence. In practice, a design partnership package typically includes:
- Free access for the partnership term. Usually the duration of the formal collaboration, often twelve months. This removes friction and signals you are serious about the relationship.
- Early access to roadmap features. Design partners should see things before the general population. This is both a benefit and a practical necessity — you need their feedback before you ship, not after.
- Genuine influence over the product. Be honest about what "influence" means. You will not implement every suggestion, but you will explain your reasoning when you do not, and you will credit their input when you do.
- A shared narrative. When the product matures, a case study or testimonial that credits them as a founding collaborator has real career and professional value. Many design partners appreciate this more than the free subscription.
Avoid paying cash to design partners who are also potential customers. It introduces a transactional dynamic that makes honest feedback harder to come by — people who are being paid tend to soften criticism. The value exchange should be product-centric.
Structuring the feedback cadence
The most common failure mode in design partnerships is letting the feedback become sporadic and informal. Without structure, sessions drift into product demos instead of genuine discovery, and the relationship fades before you have extracted meaningful signal.
A reliable cadence for early-stage SaaS typically looks like this:
- Monthly video feedback session. A scheduled, recorded walkthrough where the user shares their screen and narrates their experience — what they tried, what worked, what did not, and what they wished existed. This is richer than written surveys because you see the context, hear the hesitation, and catch the moments where they work around a problem rather than solving it.
- Async channel between sessions. A dedicated Slack channel or email thread where they can flag quick observations without waiting for the next session. Keep the bar for contribution low.
- Quarterly synthesis. Every three months, summarise what you heard, what changed because of it, and what is coming next. Send it to every design partner. This closes the loop and demonstrates that their input has real consequences.
The monthly video feedback format is deliberately demanding. Passive observation would be easier, but the screen-share walkthrough captures behaviour you would never surface in a survey: where users click by instinct, where they pause and read carefully, where they abandon a flow. That behavioural context is irreplaceable.
How first10 formalises the design partner model
Running a design partner programme manually — sourcing, qualifying, scheduling, following up — is a substantial operational burden on top of building the product itself. first10 is built around the premise that this overhead should be handled by the platform, not the founder.
When you apply and are admitted to first10, you define your ICP and set a target of ten to one hundred matched users. The platform surfaces people who fit, and every matched user receives a free 12-month subscription to your paid plan. In return, they commit to structured monthly video feedback for all twelve months — continued free access is conditional on keeping that commitment.
The result is closer to a formalised design partner cohort than a typical free trial: users are ICP-matched, engaged, and accountable for delivering feedback month after month. You pay a flat fee per genuine user rather than burning budget on ads that reach people outside your target market. See why this compares favourably to ad spend.
Over twelve months of monthly video feedback, you accumulate the kind of insight that normally takes years to gather. That depth informs not just product decisions but also your positioning and messaging — because you hear exactly how your users describe the problem in their own words.
Converting design partners to paying customers
The end goal of a design partnership is not just a better product — it is a cohort of users who are deeply familiar with what you have built and understand its value. That is the ideal starting point for a commercial conversation.
Design partners who have seen a feature evolve from a rough prototype to a polished release have a different relationship with it than a cold prospect who sees it for the first time. They know the thinking behind it, they contributed to it, and they have already integrated it into their workflow.
Time your conversion conversation around a natural milestone: the end of the free access period, a major release, or the moment a design partner spontaneously tells you the product has solved their problem. Do not rush it, but do not let the transition drift — a clean, deliberate offer converts better than a vague assumption that they will upgrade when ready.
For more on this conversion path, see our guide on finding your first 10 SaaS customers and the conversion strategies that work for early-stage SaaS.
Ready to build a design partner programme without the sourcing grind? first10 matches you with ICP-fit users who commit to twelve months of monthly video feedback in exchange for free access to your product. Apply to get started.