I built a sports SaaS company. I know exactly how good the pitch is, because I used to give it. Buy the tool, skip the build, go live in weeks, let someone else handle the maintenance. For a lot of teams and leagues, that was, and still is, the right call. So this is not an argument that software-as-a-service is bad. It is an argument that the price on the invoice is not the price you pay.
Walk into most sports organizations and look at how the social and content operation actually runs. You will usually find five or six tools, each bought at a different time to solve a different problem. One for scheduling and publishing. One for listening and analytics. One for asset management. A spreadsheet, or three, holding the parts none of the tools quite cover. Maybe a reporting product on top to stitch it into something a partner will accept. Each one is fine. Each one demos well. The problem is that none of them were built for how your organization works, and none of them were built to work with each other.
That is where the cost hides. It does not show up as a line item, so nobody adds it up.
The first hidden cost is integration. When your tools do not talk, your people become the integration. Someone exports from one system and imports into another. Someone rebuilds the same report every month because the dashboard almost does it but not quite. Someone keeps the master spreadsheet current because it is the only place the whole picture lives. That work is real, it is recurring, and it is done by your most capable people instead of the work you actually hired them for.
The second is fit. Off-the-shelf software is built for the average of its whole market, which means it is built for no one in particular. So you bend your workflow to match the tool. Your season, your roster moves, your game-day rhythm, your partner obligations, the specific way your org is structured, none of that shaped the software, so your team absorbs the gap with workarounds. Over a year those workarounds are a tax you pay in time and in the things you decide not to bother doing because the tool makes them hard.
The third is the one almost no one prices, and it is the one I care about most: you do not own your data. Your social performance, your content history, your athlete and account relationships, the numbers you use to make decisions and to prove value to partners, all of it lives inside someone else's product. You can usually get a CSV. What you cannot get is the living, connected, queryable foundation, because that foundation is the product, and the product is not yours. The day you cancel, the export is a graveyard. You were not buying an asset. You were renting access to your own information.
Add those up and the honest picture is not that SaaS is expensive. It is that SaaS is cheap to start and quietly expensive to live in, and the expense is paid in overhead, in fit, and in ownership, none of which appear on the invoice you approve.
For a long time this was simply the trade you made, because the alternative was worse. Building custom software meant a full engineering team, a long runway, and a real chance of ending up with something half-finished and already dated. Almost no sports organization could justify that for its social and content stack, so almost everyone rented. That was the rational choice.
What changed is the cost of building. AI has not just made software smarter, it has made building your own software dramatically cheaper and faster. Work that genuinely required a team and many months can now be scoped, built, and shipped in a fraction of the time. The build-versus-buy math that made renting obvious for twenty years has quietly flipped for a growing set of things, and it is starting to flip in sports. When owning a system that fits you exactly is no longer a multi-year capital project, "just buy the tool" stops being the automatic answer.
I have seen this kind of moment before. The last one in sports was social media itself, around 2009, when it went from a novelty someone handled on the side to a function every serious organization needed. The teams and leagues that moved early built advantages in audience and capability that the ones who waited never fully closed. The pattern is repeating, and the thing to move on this time is not another platform to post to. It is the infrastructure underneath, the question of whether the technology your organization runs on is something you rent and bend to, or something built for you that you own.
None of this means ripping everything out and building from scratch. The useful version is narrower and more honest. Keep the tools that genuinely serve you. Find the places where the rented stack is costing you in overhead, in fit, or in ownership, and build custom where custom actually pays. Start with the data foundation, because that is the piece off-the-shelf software will never give you and the piece everything else is built on. Own that, and you stop renting your own information.
I am not against SaaS. I built it, sold it, and I still think it is the right answer for plenty of problems. I am against paying its hidden costs out of habit, at exactly the moment the alternative became real. If you have not looked closely at what your rented stack is actually costing you, now is a good time to look. The number is bigger than the invoice, and for the first time in a long time, you have a real choice about it.