02 / System-first

2026 · US · Live

Creator Operations Platform

Internal creator ops product for DITCH LA (submission, approval, and payouts at 100+ creator scale) behind the public brand at ditch.la.

Creator OpsApparelInternal ProductClient Build
Creator Operations Platform, shipped client work
  • 01

    Public brand at ditch.la, internal product for creator ops

  • 02

    Submit → review → approve/reject/revise → payout

  • 03

    Seat-efficient architecture at 100+ creators

  • 04

    Dropbox archive of approved submissions

The brief

DITCH LA runs UGC and creator content at volume. Onboarding, raw video submission, approval with feedback, earnings, and payment status were scattered across email and DMs. The hard constraint: scale past 100 creators without buying a paid Airtable seat for every creator, or the tool itself becomes the cost problem it was meant to solve.

The outcome

  1. 01Full MVP (creator onboarding, submissions, bulk approval/payout workflows, admin dashboard, notifications) delivered on a 7-day build plus a 3–4 day revision cycle
  2. 02Architected to scale to 100+ creators with zero additional Airtable seats, backend stays limited to the internal admin team
  3. 03Reused the approval/payout architecture from Arth Saathi rather than designing ops from zero

The build

ditch.la is the public storefront. The product we built sits behind it: an internal creator system for the team that actually runs UGC, not another customer-facing shop.

An Airtable backend handles creator records, submissions, approval workflow, and payout tracking, kept strictly admin-only. Creators log into a separate lightweight portal and see only their own submissions, status, feedback, and earnings, with zero Airtable seat cost per creator.

Automated notifications fire on submission and on approval, rejection, or revision request. Approved raw video auto-archives to Dropbox, organized by creator. The approval/payout flow reused the pattern from Arth Saathi rather than designing ops from zero.

Specs

Backend
Airtable, database, forms, interfaces/dashboard, automations
Creator portal
Softr or lightweight Next.js frontend, separate from the Airtable backend
Workflow
Submit → admin review → approve/reject/revise → payout, with bulk actions for admins
Integrations
Dropbox (auto-archive approved submissions by creator)

Stack

Backend
AirtableFormsInterfacesAutomations
Creator portal
Softr / Next.js
Storage
Dropbox API

Building something in this layer?

Start an inquiry
View live site

More System-first

All System-first