Design Partners Don’t Owe You Revenue

Design partners are often your best shot at future revenue. But the move from collaboration to commitment has its own timing, and trying to speed it up usually backfires.

Photo by Alexander Mils

Here is a dynamic I often see with early-stage companies or more mature companies introducing a new strategic product and expecting it to be the next big thing:

The CEO wants to sell. The runway demands it. Investors expect signals. The product leader wants more time with design partners. The product isn’t fully there yet.

So the company tells itself a comforting story: We’re still in learning mode, but these design partners could become real revenue soon.

The compromise feels reasonable.

No one is trying to manipulate anyone. The CEO is not wrong to worry about revenue. The product leader is not wrong to want more time to learn. On paper, combining both goals sounds efficient.

Why not learn and sell at the same time?

If design partners already believe in the vision, if they are engaged, if they are giving feedback, why not accelerate the process and convert them into paying customers?

The problem is that belief is not the same as readiness.

Saying “this makes sense” is not the same as allocating budget. Agreeing to collaborate is not the same as relying on the product. Participating in feedback sessions is not the same as changing behavior.

When we blur those lines, we mistake politeness for urgency and curiosity for commitment.

And so, quietly, those expected deals are built into the next funding plan, and the pressure starts to distort everything.

Why design partners exist

Design partners exist because building products in tech is fundamentally different from building in many other industries.

In most traditional industries, the problem is already well understood. The market knows what it needs. The questions are about efficiency, execution, distribution. You don’t need design partners to discover whether the problem exists or what “good” looks like.

In tech, especially when building something new, that certainty doesn’t exist.

Most teams operate in innovative spaces. They are trying to address unmet needs, or known needs in new ways. The problem is not fully defined. The solution space is wide open. Technology could go in many directions, and it’s rarely obvious which one actually creates value.

That’s why discovery is unavoidable.

You need problem discovery to understand what really hurts and for whom. You need solution discovery to test whether your ideas actually help. You need product discovery to see how people use what you build when it meets real constraints.

Design partners are how you do that learning in reality, not in theory.

From collaboration to commitment

When a company agrees to be a design partner, they are not agreeing to buy.

They are agreeing to mutual exploration.

On your side, you’re learning how to serve them well. What they actually need versus what they say they need. Where the real friction is, what matters enough to change behavior, and what doesn’t.

On their side, they’re learning whether your product truly helps. How it fits into their reality. What it replaces, what it adds, and what it complicates.

At the same time, something less explicit is forming on both sides: a sense of importance.

Is this painful enough to prioritize? Is it urgent enough to act on now? Is it worth spending time, energy, and budget on?

Pricing lives inside that understanding. Early ballpark numbers are abstract. As exploration deepens, assumptions get tested. What once sounded reasonable can change once the real impact and tradeoffs become clear.

Commitment comes at the end of that exploration, when value is experienced and urgency is felt.

That journey has its own pace. And it’s their pace, not yours. You can’t rush someone into commitment just because you need them to commit.

When you push too soon

Trying to turn design partners into customers too early doesn’t accelerate revenue. It makes it harder to get there.

You and the design partner entered an implicit agreement to explore together. To learn, test, and figure things out side by side. When you start pushing for commitment before they are there, you change that agreement one-sidedly, often without naming it.

From their side, this doesn’t feel like progress. It feels like a disconnect. Conversations lose their ease. What was convenient and open becomes demanding and slightly uncomfortable.

It also shifts your attention. Instead of understanding what actually matters, you start listening for buying signals. Feedback becomes narrower because you are afraid to rock the boat with in-depth questions. The product starts evolving around assumptions you haven’t validated yet, instead of the reality that’s emerging through exploration.

Pressure enters the relationship. Conversations move to pricing before value is fully formed. Decisions get delayed, not because there is no interest, but because the ground isn’t ready yet.

And it weakens your position. When commitment is pushed before clarity exists, hesitation grows. What could have become a confident “yes” later turns into a cautious “maybe” or a quiet no.

Rushing doesn’t save time. It compounds uncertainty.

Design partners are not there to rescue your revenue plan. They are there to help you build something worth committing to.

If they become paying customers, it won’t be because you pushed harder. It will be because, over time, the exploration did its work.

Revenue follows clarity, not the other way round.