Stop Calling Them Design Partners. They're Not.

Early in my career, I learned an expensive lesson about the difference between a prospect who is excited about your product and a design partner who will actually help you build it.

They are not the same thing. Confusing them will cost you months you don’t have.

At Data Guard, I had a handful of early prospects who were genuinely enthusiastic. They showed up to demos. They gave me detailed feedback. They told me exactly what features they needed and assured me that once I built them, they would be customers.

So I built the features.

Some of them converted. Most didn’t. A few disappeared entirely once the roadmap had shifted in their direction. I had essentially let excited prospects set my product priorities without any financial commitment from them, and without any real accountability on their end.

They were not design partners. They were free consultants who happened to be giving me advice in the direction of their own wishlist.

A real design partner pays you. Not necessarily a full contract price. But something. Enough to create a commitment on their side that mirrors the commitment you’re making on yours.

They are taking a risk with you. They are betting that you will build something worth using before it is finished.

That bet, made with actual money, changes the entire dynamic of the relationship.

When someone pays you to design something with them, they show up to every meeting. They give you honest feedback instead of polite feedback. They have a reason to want you to succeed that goes beyond intellectual curiosity about your product.

A prospect who says ‘come back when you build X’ is not a design partner. They are a spectator with opinions.

When I built AlertBoot, I carried this lesson with me. We landed significant early customers without anything close to a finished product. But those customers had made a financial commitment.

They were in the room with us, helping us build the right thing, because they had skin in the game.

That is what lets us move fast without building the wrong thing.

The design partner relationship created a feedback loop that free prospects never could, because free prospects have nothing at stake if you get it wrong.

The result was a product that fit the market from early on, rather than one that chased a revolving door of feature requests from people who were never going to pay.

The ‘come back when you build it’ prospect feels valuable because they are engaged. They are taking your calls. They are filling your pipeline spreadsheet. They make you feel like you are making progress.

But engagement without commitment is just noise. It will keep you busy while your real customers wait.

The filter is simple: are they paying you to design this with them, or are they advising you for free in hopes you will eventually build what they want? One of those is a design partner. The other is a fan.

Fans are nice to have. But they will not help you build a company.

Find the people who will write a check to be in the room with you. Those are your real partners.

Over the past weeks, I’ve been sharing lessons from three decades of building technology companies.

Three weeks ago, we uncovered why the best businesses aren’t built by copying existing models:

Two weeks ago, the lessons that shaped my approach as a founder and operator:

Last week, we uncovered 5 things cybersecurity taught me:

Next week, I’ll share another lesson from the technology, startups, and building products people rely on.

Subscribe to get the next lesson, and every future post the moment it goes live.