← All works
Internal Platform4 min read 8 sections

ContentFlow: Running a Five-Language Content Operation

The internal platform behind a multi-language video operation: 30+ role-based dashboards and an eight-stage pipeline from script to posted video, plus a live analytics command centre — YouTube data, thumbnail click-through, and velocity alerts — all under one set of permissions.

Product
Content operations and analytics platform
Role
Design and build
Languages
Telugu, Hindi, Tamil, Marathi, Kannada
Stack
React, PostgreSQL, REST APIs, YouTube Data API
  • 30+

    Role-based dashboards

  • 8

    Pipeline stages

  • 2,000+

    Videos orchestrated

  • 100K+

    Followers on channels it runs

ContentFlow: Running a Five-Language Content Operation
0108

Overview

Producing content at scale across YouTube and Instagram in five languages means dozens of people touching every video: writers, voice artists, editors, designers, and managers. Then, once a video is live, someone has to read what it did. Spreadsheets and chat threads survive neither job. ContentFlow is the internal platform I built to run the whole operation in one place — the production work, and the numbers that follow it.

The team knows the analytics side as Content Nexus. It isn't a separate tool but the command centre inside the same platform, sharing one login, one set of roles, and one set of permissions.

LanguageLanguageLanguageLanguageLanguage
TeluguHindiTamilMarathiKannada
Every video can exist in five languages, each with its own team
0208

The Pipeline

Every piece of content moves through eight stages, from the first draft of the script to the posted video — Script, Review, Voice Over, Audio Cut, Raw Upload, Editing, Ready, Posted. Each stage has an owner, and every handoff is recorded instead of lost in chat.

Eight stages from script to posted
Eight stages from script to posted

The pipeline is visible on a shared content calendar, filterable by channel and by status, so anyone can see what's stuck and where.

0308

Key Decision: A Dashboard per Job

One dashboard trying to serve everyone ends up serving no one: a voice artist doesn't need channel analytics, and a manager doesn't need the recording queue. So ContentFlow ships 30+ purpose-built views, and each role sees exactly the screens, actions, and data its job needs.

RoleWhat they need from the platform
WriterScripts to write and review notes
Voice ArtistScripts ready to record and studio slots
Editor and Editing ManagerRaw uploads to edit, and what's due
Graphic DesignerThumbnails and assets to make
ManagerStatus across the pipeline and the team
Central Team and AdminEvery channel and language, and roles
A few of the roles, each with its own views
0408

Access by Role, Language, and Region

Role-based access control decides what each person can see and do, and everything is also scoped by language and region. A Telugu editor sees Telugu work; a Hindi manager sees Hindi channels. The same permission model carries straight into the analytics side, which is why outside collaborators can be let into the numbers without being let into everything.

ScopeWhat it limits
RoleWhich screens and actions a person has
LanguageWhich language's content they work on
RegionWhich channels and teams they see
Three layers of access
0508

The Analytics Command Centre

Once a video is posted, the platform stops tracking work and starts tracking performance. The YouTube Data API feeds a PostgreSQL store, the platform tracks thumbnail click-through, and it watches each video's velocity for anomalies — flagging a video that's suddenly taking off, or stalling, instead of waiting for someone to notice.

From the YouTube API to tiered dashboards
From the YouTube API to tiered dashboards
CapabilityWhat it does
Live YouTube dataChannel and video metrics through the YouTube Data API
Thumbnail CTR trackingAutomatic click-through tracking for every thumbnail
Velocity anomaly alertsFlags videos whose growth suddenly changes
Permission tiersSeparates internal teams from outside collaborators
One command centre instead of a dozen YouTube Studio tabs
0608

Key Decision: Permissions as a First-Class Feature

Most analytics tools treat sharing as an afterthought. This operation runs with internal teams and external collaborators side by side, so permission tiers are built into every view rather than bolted on. The numbers a partner can see are a property of their tier, not a report someone remembers to redact.

WhoWhat they get
Internal teamThe full picture across channels and languages
External collaboratorsOnly what their tier allows
Strict permission tiers, by design
0708

Around the Pipeline

SystemWhat it does
Content calendarEvery video on one calendar, filtered by channel and status
Channel analyticsPerformance across channels, including live YouTube data
Studio bookingRecording slots for voice artists
Team managementRoles and access for every member
The supporting systems
0808

Impact

ContentFlow is the operational backbone behind more than 2,000 videos and channels grown past 100,000 followers, with every handoff between roles tracked instead of lost in chat — and every posted video measured in the same place it was made.

BeforeAfter
Spreadsheets and chat threadsOne platform
Handoffs lost in messagesEvery handoff recorded
Everyone sees everythingEach role sees its own work
Status by asking aroundStatus on a shared calendar
Numbers in scattered YouTube Studio tabsOne analytics command centre
What changed for the team

ContentFlow is an internal platform, so there's no public build or source to link to.