The $1 Donation That Almost Broke #TeamSeas: Why You Fix the Foundation Before You Optimize

On August 17th, 2021, I sat in a presentation with Mark Rober and MrBeast's team.

They wanted to raise $30 million to remove 30 million pounds of trash from the ocean. The campaign was called #TeamSeas, and the launch date was October 29th, 73 days away.

They came in with a clear list of what they needed. The site had to handle donations of up to $1 million. It had to handle tens of thousands of transactions. And it needed 100% uptime, because their last campaign had gone down for 24 hours.

What they thought the project was

Everyone in that room wanted to talk about the website. The design, the conversion rates, how to get more people to donate once they landed.

That made sense. They were going to put this in front of tens of millions of people, and with millions watching live, any failure meant lost donations, lost credibility and a very public disaster. There was no soft open. It would be live in front of the world from the first minute.

So I started asking questions.

The questions that changed everything

"What's the lowest donation you'll accept?"

"One dollar."

"Who's your merchant?"

Crickets.

There was a long pause, mostly on my end. Seventy-three days from launch, they had no merchant account, and they wanted to accept $1 donations from the entire internet.

So I asked them whether they knew what happens when you open $1 transactions to the internet. You get hammered by credit card testers. Fraudsters love $1 charges, because they can check whether stolen cards work without setting off alerts. And if you don't already have a relationship with your payment provider, they'll freeze your funds in the middle of the campaign the moment fraud spikes.

They had no idea.

I kept going. Who's your hosting provider? They were still figuring that out. Customer service tools? Not yet. What happened when your last site went down for 24 hours? They'd been told it was a DDoS attack.

I didn't buy it. It sounded much more like a fraud attack they couldn't stop, so they had to shut the site down until they could put protections in place.

They weren't ready to optimize

While everyone wanted to focus on design and conversions, the real issue was that they didn't have a foundation to build on. No merchant relationship, no fraud protection, no hosting and no customer service, 73 days out, with the clock ticking.

They weren't ready to optimize. They were on track to fail spectacularly.

So I told them exactly what needed to happen.

First, get Stripe on board immediately. Have MrBeast send a tweet and tag Stripe's CEO, so the campaign gets a dedicated team assigned to its account. Without that relationship, the funds get frozen the second fraud spikes.

Second, build on AWS with infrastructure designed for global scale, protection against attacks through Cloudflare, no exposed database connections, and fraud detection from day one.

Third, once the design was ready, we'd build it and connect the payment systems, while their team secured the merchant accounts, contracts, approvals and customer service.

What happened

We won the project. The design was delivered on October 6th, which left us 23 days to build the entire system, including the website, the donation system, the real-time leaderboard and the hosting.

We launched on October 29th. At 4:07 p.m. Eastern on launch day, $260,000 came in during the first seven minutes.

On day two, fraud attacks started, and at the peak they hit 40 attempts per second. We were ready, and they continued for weeks. We kept adapting our defenses as the attacks evolved, while real donors kept giving without interruption.

The site handled more than a billion requests and never went down. More than $30 million was raised. When the campaign's co-founder started planning the sequel, I was one of the first people he called.

What won the project wasn't technical

People sometimes assume we won because of technical brilliance. It wasn't that. What won the project was listening.

I heard what actually mattered to them, asked the right diagnostic questions, and built the system around their real concerns, not my assumptions. They came to me for uptime and conversions. I gave them a foundation that could hold the weight.

What this means for your business

Your business probably isn't raising $30 million in front of millions of people. But the same mistake shows up at every size.

Owners pour time and money into the visible parts, like the website design, the ads and the marketing, while the foundation underneath is cracked. The payment setup that hasn't been checked in years. The booking system that's never been tested with a real rush of clients. The data nobody trusts.

You can't out-optimize a crack in the foundation. Most people can't see the gaps in their own foundation, so they optimize the wrong things and wonder why everything falls apart when they finally get busy.

It's not always what you don't know. It's what you think you already understand and leave unquestioned.

Frequently asked questions