For Influentia's Growth Lab, we built a Notion-based production system: update a video once, and every phase calculates its own status automatically, keeping calendars, task lists and timelines in sync.
Single
Gone
Self-clearing
Videos, people and production steps were tracked separately. Moving a piece of content meant updating several places, or hoping someone else would.
What was done, in progress or next was reconstructed in meetings instead of read from the system.
Four related databases, clients, team, videos and tasks, keep every piece of content in one connected structure.
The team changes global stage and production options on the video. Task rows are generated and driven from that, nobody maintains phase status by hand.
Each task computes completed / in progress / pending from the video's stage, including skips when a phase does not apply (no script, no brand, already optimized).
Per-client work tables, a live calendar, an auto-sorted task board, a personal task list and a Gantt timeline, all reading the same calculated state.
The first release locked the linked databases and automatic status. Later work layered client-specific flow rules and a companion daily notification path on top of the same model.
Platform limits that blocked native automation were worked around with precomputed stage numbers and a thin external layer, without asking the team to edit tasks directly.
Migrating off the old tracker followed the same discipline as everything else: a simulation pass, a diff report against what already existed, and a staged cutover, work already in progress first, then the next quarter's calendar, before touching older history.
Like what you see?
Tell us what you're trying to build or improve, and we'll show you how the system applies to your project.