From Marketplace to Operating System: Applied AI and the NIL Back Office

The first wave of NIL software solved discovery — match an athlete to a brand. The revenue-sharing era turned NIL into an ongoing operation someone has to run. Marketplaces don't run operations. Operating systems do, and that's where applied AI earns its keep.

Keith Pattison

Keith Pattison

June 24, 2026 4 min read
A cluttered marketplace handshake on one side transforms into a clean operations dashboard with a pipeline of deal cards moving through labeled stages, one flagged for review

The first wave of NIL software was a marketplace problem. Athletes needed brands, brands needed athletes, and the platforms that won were the ones that made that match fast and liquid. Discovery was the hard part, and discovery got solved.

Then the ground moved. Direct revenue sharing, per-school caps, a clearinghouse vetting deals above a threshold, disclosure requirements that vary by state and conference — the House-settlement era turned NIL from a series of one-off transactions into an ongoing operation that somebody has to run, every day, for hundreds or thousands of athletes at once.

Marketplaces don't run operations. Operating systems do. That shift — from matching to managing — is the real product frontier in the NIL economy, and it's where applied AI earns its keep or makes an expensive mess.

The problem: discovery is solved, the back office isn't

The hard, unglamorous work is now operational. Every deal has a lifecycle: proposed, disclosed, vetted, approved, delivered, paid, taxed, documented. Each step carries judgments that used to be rare and are now constant — does this deal cross the clearinghouse threshold? Is the disclosure complete and on time? Does this payment fit under the school's cap? Are the content rights clean?

Multiply those judgments across a full roster and they stop being a paperwork annoyance and become the binding constraint. You can't hire your way out of it, and the cost of getting one wrong isn't a bad quarter — it's eligibility, a clawback, or a compliance finding.

Why it's stuck: operational judgment doesn't scale by adding people

The instinct is to add a coordinator, then a compliance hire, then a spreadsheet, then three. But the work is inference over messy, fast-changing information: rules that differ by state and update mid-season, deals that don't fit a template, disclosures with missing fields. That's exactly the shape of problem modern AI is good at — and exactly the shape that punishes software with no judgment built in. A system that auto-approves a deal it doesn't actually understand doesn't save time; it manufactures risk.

The path: build the back office as an applied-AI system

The platforms that win the operating-system layer won't be the ones with a "generate" button bolted onto a marketplace. They'll be the ones who treat operations as a system with clear principles:

  • Keep a human in the loop where being wrong is costly. Eligibility and payments are exactly those places. AI should triage the routine 90% of disclosures and flag the genuine edge cases for a human — not own the approval.
  • Separate the rules from the judgment. Thresholds, caps, and state rules change constantly; they belong in editable policy a compliance lead can update without a deploy. The judgment layer — is this deal clean, is this disclosure complete — can then improve on its own track.
  • Start where judgment is expensive and repetitive. Disclosure triage and deal-lifecycle status are the highest-leverage first builds: the work that scales worst by hand and best with a model that explains its reasoning.
  • Earn trust with explainability. "Flagged: payment exceeds remaining cap for this athlete this period" beats a silent auto-decision every time — especially when a regulator or an athlete's family asks why.

The move from marketplace to operating system isn't a rip-and-replace platform project. It's a focused question: which operational judgment is most expensive and most repetitive right now, and what's the smallest system that compresses it without giving up control? That's a two-day conversation before it's a roadmap.

The NIL economy already solved the easy half — finding the deal. The half that decides who runs this market is the half nobody wanted to own: running it. The winners won't have the flashiest matching algorithm. They'll be the ones who built something trustworthy on top of rules, money, and eligibility that never sit still.


Black Flag Design builds applied-AI products for operations that can't afford to be wrong. If this is your world, spend two days with us — we call it a Foundation Sprint.

About the author

Keith Pattison
Keith Pattison

Founder, Black Flag Design

Keith leads Black Flag Design, a studio that ships production-ready software with AI-assisted development. He writes about the disciplines — small scope, weekly evidence, and human oversight — that keep AI-built systems reliable in the real world.

Related stories

More from the journal

Pen-and-ink sketch of a small clockwork robot working at a tool-covered workbench late at night while a human sleeps peacefully on a couch in the background, a wall clock reading 2:00 above
ai April 24, 2026 13 min read

The Agent Stays Up Late, Not Me

Every senior engineer knows the right way to set up a codebase. None of them do it. Here’s the four-stage framework we use — The Ratchet — to take a vibe-coded project all the way to a thing you’d trust in production, and the punchline about why this only just became worth doing.

Most teams have always known they should be running tests, type-checking, security audits, accessibility checks, dead-code analysis, prose linting, and a coverage floor. Most teams run two of those. Here’s why that math has finally inverted, and the four-stage framework we use to ratchet a vibe-coded project to a hardened one.

Keith Pattison

Keith Pattison

Founder, Black Flag Design

Read
Black Flag Journal
claude code April 20, 2026 5 min read

What a Year of Claude Code Trails Tells You About Your Team

Claude Code leaves evidence — sessions, commits, PRs, review notes. Read it like a logbook and you'll find what devs actually need to know before they go deeper.

After a year of shipping with Claude Code across real client work, the signal isn't in any single session — it's in the trails. Here's what those trails told us about where Claude Code shines, where it drifts, and the habits devs should build before they lean in harder.

Eli Wood headshot

Eli Wood

CEO, Black Flag Design

Read
Black Flag Journal
playbook April 20, 2026 6 min read

The Black Flag Playbook: Six Principles for Shipping with AI

Battle-tested principles for teams building real software with AI-generated code. Human judgment, tight scope, and weekly evidence — the disciplines that keep AI-built systems reliable.

The six rules we use to ship production software with AI. Small scope, weekly demos, human-led oversight, and continuous improvement — drawn from six months of real client engagements.

Keith Pattison

Keith Pattison

Founder, Black Flag Design

Read