Most athletics programs have more stories than they know what to do with. The problem is never a shortage of content — it’s the absence of a system to make it all work together.
Running digital for a multi-sport athletics department is one of the most complex content challenges in any industry. You’re managing dozens of programs, each with its own identity, season, and audience — all under one institutional brand.
Most departments solve this by adding people or posting more. Neither scales. What scales is infrastructure — shared standards, repeatable workflows, and governance that gives every program what it needs without requiring every program to build it from scratch.
I spent nine years at Stanford Athletics building the content operating system that powered 36 varsity sports. That meant 1.3B+ impressions, 1.75M+ followers, two nationally recognized Heisman campaigns, and a production infrastructure that a lean team could actually run.
I know what it takes to serve a women’s volleyball program with the same rigor as a nationally televised football broadcast. The methodology is the same — the system just has to be designed for it.
College athletics audiences aren’t monolithic. Fans want emotion. Recruits want identity. Donors want impact. Media wants access. A content system needs to serve all of them without becoming four separate operations.
In the NIL era, the programs that build real brand equity — not just social followings — are the ones that will attract and retain the best talent. Content infrastructure isn’t a nice-to-have anymore. It’s a competitive advantage.
Full assessment of your current content operations, workflows, and output — with a roadmap for what to fix first.
Shared frameworks that give every sport a clear standard without requiring every sport to reinvent the process.
Multi-platform campaign architecture for marquee moments — from rivalry weeks to Heisman pushes to postseason runs.
Ongoing embedded support for departments that need senior strategic direction without a full-time hire.
Let's talk about what a real content operating system could look like for your program.