What Sports Taught Me About SaaS (It's Not What You Think)

I grew up watching basketball the way some kids grow up in church. Every week, same ritual. The nervous energy before tip-off, the collective gasp when a three-pointer rattles the rim, the way 15,000 strangers can feel like family for two hours and then dissolve into the night like nothing happened.

My team is Anadolu Efes. If you know Turkish basketball, you know what that means. If you don't, just know it's a club that's been through everything: championships, financial collapses, rebuilds, European glory. The full emotional spectrum.

Two decades later I'm building a SaaS product for sports clubs. On paper, unrelated. In reality, the parallels have been the most useful mental model I've got.

Not the obvious stuff about teamwork. That's been done to death. What I mean is weirder and more useful than any motivational poster.

The crowd is your user base

A basketball club lives and dies by its relationship with the fans. Not the corporate sponsors. Not the TV money. The people in section 207 who rearrange their Thursdays around tip-off. The ones who have opinions about every rotation and will let you know at midnight on Twitter.

I once watched Efes lose a game where they were up 15 at halftime. The arena started emptying with three minutes left. But a few hundred stayed. Still chanting. Not because they expected a comeback. Because showing up is the point.

Your real users are the ones who stay.

Not the investors. Not the tech press. Not the people who signed up during your Product Hunt launch and never opened the app again. The ones who keep coming back. The ones who complain. Those are your season ticket holders.

I learned this the hard way. Early on, I'd chase feedback from people who tried the product once and vanished. Meanwhile the daily users were quietly dealing with things I hadn't noticed because they never complained. They'd just adapted. That's worse than a complaint. A complaint means someone wants it to be better. Silence means they're one bad day away from leaving.

Pay attention to the people who show up every week. Not the ones who wander in when something goes viral.

Every season ends

Sports has a rhythm that software refuses to respect. Basketball especially: regular season, playoffs, then the long summer. There's a beginning, a middle, and an end. Then a break. Then it starts again. New roster, new expectations, clean slate.

In SaaS, the calendar never stops. Sprint bleeds into sprint. Quarter bleeds into quarter. Nobody rings a bell and says "alright, season's over, go home."

But that rhythm matters more than I expected.

I started treating big releases like playoff games. The weeks before are training. The weeks after are recovery and review. Then we pick the next opponent. Without this, everything blurs together. You ship something, celebrate for eleven minutes, and immediately start worrying about the next thing.

That's how burnout actually works, by the way. Not from working too many hours. From never letting anything feel finished.

Some sprints are for building. Some are for fixing. Some are just for sitting back, watching what users actually do, and figuring out what matters next. If every week is a playoff game, none of them are.

Transfers matter more than tactics

Every club has a transfer window. Twice a year, you can bring people in, let people go, reshape the squad. Everyone obsesses over the big signings, the names that sell jerseys. But the clubs that win over time are the ones that get recruitment right across the board. Not just the star point guard. The sixth man who never makes a highlight reel but changes the game when he checks in.

Hiring in a startup works the same way.

The flashy hires get attention. The ones that actually change your trajectory are usually invisible from the outside. The engineer who refactors the billing system without anyone asking. The support person whose documentation cuts ticket volume in half.

And the uncomfortable part: sometimes you need to let people go. Not because they're bad. Because the squad changed and they don't fit anymore. A player who carried the team in the domestic league might not be a EuroLeague player. Same person, same skills, wrong context.

I've held on to people too long because they were loyal, or because I liked them, or because firing someone feels like personal failure. But keeping someone in a role they've outgrown is worse for them and worse for the team.

Training is boring

Nobody watches training. Nobody buys tickets for the Tuesday morning session where the team runs the same pick-and-roll coverage 40 times. Nobody clips it for YouTube.

But that's where games are won.

Software people love talking about the exciting stuff. The launch. The architecture call. The clever workaround that saved three days. Nobody wants to talk about writing tests, updating dependencies, or refactoring a module that technically works but feels bad to touch.

Most of building a SaaS product is training. The design system that means you can ship a new page in an afternoon instead of a week. The CI pipeline that catches bugs before they hit production. The on-call rotation that lets you sleep.

I used to feel guilty about spending time on this stuff. It felt like overhead, like I was avoiding "real" work. Now I think of it as conditioning. You don't skip training because training is boring. You do it because game day is chaos and you need the muscle memory to hold.

Game day is never what you planned

You prepare for months. You beta test, stress test, do the dress rehearsal. Then you ship and something breaks that nobody predicted. Or worse: nothing breaks and nobody cares.

Basketball is the same. All the training, all the tactics. None of it guarantees a win. The other team shows up. The ref makes a call that makes no sense. Your shooter goes cold from three.

I've had launches where I refreshed the dashboard every 30 seconds waiting for numbers to move. I've had launches where I forgot to check until the next morning because I was too fried from the final push. The second kind usually went better. Not sure what that says about me.

The metaphor breaks down in one important way. In basketball, the scoreboard is final. You can't patch a loss. In software, you can. You can update. You can ship a fix at 3am and by morning nobody remembers it was broken.

That's both a blessing and a curse. A blessing because second chances. A curse because you never really get closure.

What I actually learned

The parallels are real and useful. But they're not the thing that stuck with me. The biggest thing sports taught me about SaaS is simpler and harder to execute.

Caring.

Sports fandom is completely irrational. It makes no sense to feel genuine anguish when a group of strangers you'll never meet loses a game. But we do. Millions of us, every week, for our entire lives. That kind of emotional gravity is rare. It's hard to build. And it's the most valuable thing in the world when you're trying to get anyone to pay attention to anything.

I'm building Game Set Engage because I think sports clubs are sitting on something they don't fully understand yet. The fans are already there, in the arenas and the group chats and the comment sections. They already care. They just don't have anywhere to direct that energy between games. Most club apps are ticket portals with a news feed bolted on. The average fan experience outside the arena is worse than ordering a pizza.

That's the gap. Not a slightly better CRM. Not another analytics layer. A place where fans actually want to be.

Game Set Engage is launching soon. I'll write more about it when it's real. For now, the point is this: if you want users to care about your product the way fans care about their club, you have to go first. You have to show up every week. You have to listen when they complain. You have to make the boring training sessions count.

And you have to accept that sometimes, despite everything, you'll lose. Then get up and train for the next one.

Sports didn't teach me how to win. It taught me how to keep playing.