Saying No to Mark Cuban
I've admired Mark Cuban for most of my life. My family watched Shark Tank together, and he was the one we rooted for. He always seemed to actually care whether the person pitching got a fair shake, and of everyone at that level, he's still the one I'd most want to be like.
So when Webflow reached out a few years ago and asked if we'd build a website for one of his companies, I said yes before they'd even finished asking. Getting to work with Mark Cuban? Early in my career? Sign me up. I was already a customer of the company in question, too. I loved what it was doing and why it existed, and I spend most of my working life looking for projects that actually matter to someone. Here was one that mattered to me, with his name on it, and I didn't even have to send a cold email to get it.
Webflow connected me with his team to talk through the project, and I was thrilled right up until we got to the budget, when my stomach dropped a little. It was, to date, the smallest budget I've ever seen for a project — a fraction of a fraction of the smallest one we'd ever taken on. It wasn't going to move, either. So I asked for the one thing that would have made it work for me, which was the right to say we built it — a logo on our site, or a case study I could point to. They swiftly said no to that, too. The budget was the budget, and his name wasn't part of the deal.
Honestly, I don't blame his team. If your job is to protect Mark Cuban, you spend every day dealing with people who want a piece of him, and holding the line is the job. They were good at it, and I happened to be on the other side of it.
So I passed, and someone else built the site. Of all the decisions I've made at 8020 that I regret, this one is easily in my top five.
Why I said no
Some of it was where I was at the time. 8020 wasn't mine yet. We were part of Tiny, a much bigger group, and taking on a project at that number would have been hard to defend to anyone who wasn't sitting in my seat — especially my board (which, as an aside, is one of thousands of reasons I'm happy not to have a board anymore.) Picture telling a board that you're taking on a project that would be a pure loss on paper, with no publicity rights, purely for your own satisfaction. A board doesn't care about what you personally care about. It's there to return value to shareholders, so this was never going to be a decision I could justify.
What I got wrong
Every one of those reasons was technically accurate, and still is. The problem is that I let the terms make the decision, and once in a while, a deal matters more than the terms you get. This one was a chance to do meaningful work for someone I'd looked up to for as long as I can remember, and I scoped it like any other website.
The worst part is that I knew better. Years earlier, I'd read a piece by Peter Kang at Barrel about how he decides which clients to take on. One of his criteria is relationships — clients whose network can open a lot of other doors, where a price break or a little extra effort is really an investment that pays off for years. I loved that idea. I quoted it to other people, and I used it to talk my own team into projects. Then the one time it really counted, I didn't use it at all.
What's different now
Today, we're in a very different position. Joanie and I own 8020 outright, and we can take on any project we want. There's no board, no stock price, and no analysts to keep happy. If 8020 had been ours back then, we would have said yes to this project. More importantly, I know better now.
These days, I decide whether I want a client before we ever talk numbers, and I don't let the numbers answer that question for me. I still push on terms, and I still hold firm on the ones that would actually hurt us. But I've never once been glad I won an argument about terms after losing a client I really wanted.
And if Mark's team ever calls again, you can bet I'll do things differently.