00Director, AI Operations · 2024 to 2026

Where AI Operations became a function.

I did not arrive at SoundCloud with a tidy definition of AI Operations.

I got there by solving enough real AI problems to realize the model was rarely the hardest part.

99.36%
MAIA detection accuracy
~700K
Tracks scanned per day
6
Functions on one roadmap
1
Enterprise AI access layer
  • 01 SCOPE
  • Customer Operations
  • Platform Integrity
  • AI-Generated Content
  • Fraud
  • Legal
  • Copyright
  • Distribution
  • Monetization
  • Marketing
  • Internal Knowledge
  • Enterprise AI
  • Governance

01 SCOPE labels scroll automatically. They pause on hover or keyboard focus, and there is a button to stop or start the motion.

01 SCOPE labels motion playing
02Flagship case study
03Major work
04Also underneath
  • The AI Collective

    An open forum where people showed what they were trying, including the failures. I did not want experimentation centralized. I wanted the learning centralized.

  • Customer Operations

    UltimateAI and Zendesk, AI agents, Help Center, knowledge quality, routing, containment, CSAT, deflection, Looker analytics, human escalation. Measure the journey, not the bot.

  • Platform integrity

    Fake streams, fraud patterns, high-risk accounts, and noise tracks.

  • Legal and copyright

    License summarization, copyright review, and contract indexing.

  • Artist operations

    Distribution and monetization review where the artist impact was the constraint.

  • Enterprise AI

    Centralized access, routing, visibility, cost control, and reusable capability.

A technically excellent model can still produce a terrible system.

All the work →

Contact

Let's get into it.

Ambiguous problem, AI adoption that stalled, an operating model that stopped scaling, a support function that should be a product. That is the conversation I want.