A client pays you. A partner bets with you

A client pays you.

A partner bets with you.

They can look identical. Same email address, same meetings, sometimes even the same invoice. But they want different things, and treating one like the other is a very quiet way to get hurt.

I've been thinking about this a lot since we started turning what we built for sports clubs into a product of our own. Suddenly the line between "client" and "partner" got blurry. And blurry lines, in my experience, are where the misunderstandings live.

What a client actually buys

A client buys a result. They have a problem, you solve it, they pay. Clean.

They don't care how hard it was. They don't care that you learned something. They don't care that the thing you built might become a product one day. Nor should they. They paid for their problem to go away.

That's not cold. It's healthy. A good client relationship is simple on purpose: clear scope, clear price, clear "done". That simplicity is exactly why client money is the most patient money there is. Nobody asks for a share of your future. They ask for their website to work.

What a partner actually brings

A partner brings something different: risk.

A pilot club that tries something unfinished is betting a bit of its time and its patience on you. A collaborator who builds with you, before there's anything to sell, is betting that the thing will be worth it.

That bet is valuable. Probably more valuable than the money. But it comes with expectations a client never has. A say in what gets built. A bit of tolerance from you when they need something. Sometimes a different price, because they took a risk the next customer won't take.

And that last bit is where I have to be careful. I have a rule against discounts. Every discount comes back as scope. If I ever break it, I want it to be for someone who's betting with us, not for someone who just negotiated well. And I want to know exactly why I'm doing it.

Treat a partner like a client and they feel used. Treat a client like a partner and you end up working for free.

Where it goes wrong

It goes wrong in both directions, I suspect.

You treat a partner like a client. You charge them full price for the privilege of testing your unfinished product, then wonder why they don't give you honest feedback. They were betting with you. You sent them an invoice.

Or you treat a client like a partner. You listen to every idea, build every request, give little extras "because we're in this together". Except they're not. They're paying for a result, and they'll happily accept all the free stuff without ever feeling they owe you anything. Which is fair. You never told them otherwise.

Saying it out loud

The fix, as far as I can tell, is boring: say which one it is.

Out loud. At the start. "This is a project, here's the price." Or: "This is a pilot. You'll get it early, and in return we need your honesty and your patience."

Most people are fine with either. What nobody likes is finding out halfway which one they were.

Clients pay for the company. Partners help shape the product. We need both, and I'm grateful for both.

I just try not to send the partner an invoice and the client a thank-you card.

P.S. Yeray has been my partner for more than twenty years. He has never once paid me. That's how you know.