Content Operations Platform
No measurement taken
Built with
Client work
Built for a client on their infrastructure. The repository and the client roster are theirs, not mine to publish.
An agency running content for a large roster of brands accumulates a specific kind of mess: every client has its own voice, its own approval chain and its own cadence, and all of it ends up in spreadsheets, shared folders and people's heads.
This is the application that replaced that. Next.js and Supabase, with per-client brand contexts as first-class records rather than documents, content pipelines that track a piece from brief to published, and performance data attached to the thing it measures.
The design constraint that shaped it was that the people using it are not technical and did not ask for software. Anything requiring training would be abandoned inside a month, so the interface had to match the workflow that already existed rather than the data model underneath it.
What this does not show
- No adoption or time-saved measurement was taken, so there is no outcome number here.
- Client work. The repository is private and the screenshots cannot be shown.