The Founder’s Guide to Design Partnerships
Startups need early customers to shape the product. Finding the right “internal champion” is key. In this article, Merantix Capital venture studio founders share their insights.
Every founder eventually hits the same wall. There is a demo (maybe even a MVP), you’ve put together a product deck, and a handful of friendly users say nice things. But somewhere between “promising prototype” and “product the customer actually pays for,” there is a gap that no amount of internal iteration can close. Design partners are the way founders can close this gap.
A design partner is not (yet) a customer; it’s not just a logo for your website, and not a free trial user with a fancier label. A design partner is a trusted product tester, an early adopter, and a champion inside their organization. They provide fast feedback, help shape product direction, and vouch for you to the people who hold the budget. The best founders ship a product that is roughly 80% right and use design partners to find the remaining gaps. That last 20% is almost always the part you cannot guess from the outside.
Partnerships as a path to PMF
The first reason design partnerships matter is feedback velocity. When you are building for a complex industry, especially ones like financial services, health care, or logistics, the difference between knowing specific industry requirements and the quirks of the organization is the difference between a product customers use and a product they politely ignore. Engineers can build, but they rarely have the domain depth to know which assumption is fatal. Design partners bring the domain knowledge that completes the picture.
As Miguel Conty, Co-Founder of AI-native energy supplier Meteoric, explains, “Our ideal design partner has already tried to solve the problem themselves: spreadsheets, manual broker calls, incomplete price data. When they see the product and immediately start describing how it fits their workflow, that’s the signal. That one sentence, ‘This would work if it connected to XYZ’ is worth more than any user survey.”
The second reason is risk reduction. A design partnership, properly structured, includes a clear success criteria document signed by both parties. Founders sometimes resist this formality, but the document protects everyone. Without it, even a successful pilot can be retroactively declared a failure, because two people remembering a verbal goal six months later is a recipe for disappointment. With it, both sides know what was agreed, what was delivered, and what happens if things go sideways. Even when a partnership fails, a clear agreement lets both parties walk away cleanly.
The third reason is access. A design partner with influence becomes your champion, and your internal salesperson. They introduce you to decision-makers, help you craft the messaging that lands inside their organization, and create the political cover you need to graduate from a pilot to a real vendor agreement. That graduation is where the real revenue lives. Vendor agreements at large enterprises typically run for three years, often with bulk-discount negotiations baked in. None of that happens without someone inside championing your product through the procurement labyrinth.
The fourth reason is product/market fit, in its truest sense. A design partner who is the right fit will already have tried to solve the problem you address, manually or with inferior tools. They will tell you, unprompted, what the integration gaps are. They will say things like, “This is great, but it would be transformative if it is connected to our reporting stack,” and that sentence is worth more than a hundred user-research interviews.
How to spot a real design partner
Not every interested party is a design partner. Many will agree to a call out of curiosity, but few will move with the urgency that makes the partnership valuable. You should look for these five qualities.
Motivation: A real design partner has the problem right now and can immediately picture how your product fits into their workflow. If they cannot articulate the use case after a single conversation, they are not motivated enough. A high-signal response to “can we schedule a weekly call to discuss how you are using the product?” is, “Yes, and in fact I already have ideas for how this fits into our workflow.” Anything less enthusiastic is a yellow flag.
Influence: Job titles vary wildly and matter less than you would think. What you need is someone who has “pull” with upper management and can rally their team. The clearest signal is when, within minutes of seeing the product, they want to introduce you to two or three other people in their company.
Problem fluency: They should describe the pain you address in concrete, business outcomes or ROI terms. The best partners speak in metrics: “this will save us X hours per week,” “this will mitigate Y in compliance risk,” “this could unlock Z in revenue.” If they cannot frame the value in numbers, they will struggle to justify the partnership internally when budget questions arise.
History with the problem: The strongest design partners have already tried to solve this themselves, with spreadsheets, internal tools, manual processes or competitor products. Their willingness to discuss those failed attempts honestly is a leading indicator of a productive relationship.
Profile: The sweet spot tends to be challenger-stage companies with significant annual revenue (the profile varies but perhaps between $20M - $100M, growing at more than 50% per year). They have enough budget to experiment but enough hunger to need an edge. High-gross-margin industries are particularly fertile because budgets for new capabilities are more flexible.
Where to actually find them
Tassilo Schmidt, Co-Founder of AI logistics platform TAIM Systems, said,“Depending on the industry, trade fairs can be extremely valuable. In the end the signing of design partners is usually through personal connections - the goal is to maximize the degree of personal connections. This can either be driven through warm introductions or networking and cold calls.”
Tassilo also indicated that when structuring a design partnership, keeping proposals lean helps with the discussions. “If you narrow yourself down too early, before you even have one or two design partners, you may miss the opportunity to hear about the other use cases industry experts could imagine your solution can solve” he said.
Tassilo recommended a delicate balance: “You need enough clarity to signal you’re not wasting their time, but you also need to stay open to going in different directions.”
Practical advice on where to find potential design partners is where most written advice falls apart, because the honest answer is unglamorous. There is no RFP. There is no public list. Design partners come almost exclusively through relationships.
Some come through investors and their networks. Others come through personal networks, maybe a member of the C-suite at a target buyer happens to know one of your co-founders from a previous role. Some come through corporate accelerators or partnership programs that institutions run specifically to vet earlier-stage companies in a structured way.
The implication for founders is straightforward: build relationships before you need them, and bring an idea to every conversation. You do not need a fully formed proposal to walk through the door, but you do need a clear hypothesis. Coming in cold and asking “what should I build for you?” is a waste of everyone’s time. Coming in with “here is the capability we have built, here is the problem we think it solves for you, let us refine the proposal together” reduces friction enormously.
Aim to line up between 5-10 qualified organizations and try to convert 3-5 into actual design partnerships. Go deep, not broad. A handful of design partners who genuinely shape your product and champion it internally will do more for your company than 50 interested observers. The work is slower than it sounds and more rewarding than it looks, and at the end of it you will have a product that survives contact with the market, and the customers to prove it.
A big thanks to Maxson Tee, Miguel Conty and Tassilo Schmidt for their insights and helping to shape this article.
Meteoric is an AI-native energy supplier for industrial companies. They are replacing the traditional supplier with a new system. One layer that owns both energy supply and the intelligence behind every decision.
TAIM Systems is building an AI-first platform for logistics operations, tackling one of the biggest remaining blind spots in the global supply chain. They apply computer vision and agentic workflows to messy, real-world operational environments and turn that data into actionable, automated decisions.
Merantix Capital works with exceptional founders at the idea stage - helping them identify category-defining opportunities, validate AI use cases, and build high growth companies from day one. If you’re ideating on a B2B AI-native case for a specific industry, please reach out to Rockman Law or a member of our team.
This is the second installment of our Founder’s Guide series. Check out our first article: The founder’s guide to building in AI Safety.