The Challenge
Accion Latina runs monthly product launches for their community. Each launch involves a full production cycle: content planning, graphic assets, YouTube videos, social posts, and dozens of recurring coordination tasks spread across channels and team members.
The problem wasn’t effort — the team was doing the work. The problem was structure.
- Content production and task assignment lived in spreadsheets.
- Launch coordination happened across Slack threads.
- Different people owned different channels, and each month started from zero: recreating the same task list, re-establishing who owned what, and trying to track progress across tools that didn’t talk to each other.
By the time a launch was in flight, visibility was low and catching delays meant asking around.
The Approach
We built a unified content and launch operations system inside Notion – no new tools, just a structure that made the tools they already used work together.
1. One content home, two workflows
Their content production splits naturally into two streams: graphic and social content and YouTube production. We built a dual content calendar that gives each stream its own fields and flows — different assignees, different statuses, different due-date logic — while keeping everything visible in one place. One home base for the whole team, no toggling between systems.
2. YouTube → Shorts, automatically
Every time a new YouTube video publishes, a Make.com automation fires and creates a Shorts production task in Notion – pre-assigned, with a due date, and linked to the right project. What used to require several manual steps, now happens in the background. The team’s attention goes to the work, not the coordination around the work.
3. A launch dashboard that builds itself
Launches aren’t a separate database. They live inside the existing Projects DB, tagged as type: launch. When a new launch is created, a Notion template fires automatically: generating calendar, Kanban, table, and Gantt views that are already filtered to show only tasks tied to that specific launch. No manual setup. Open the launch page and the workspace is ready.
4. One button, one month of tasks
Every launch shares a core set of recurring tasks: the same roles, the same dependencies, the same production rhythm. We encoded all of it into a sequential button. Click the button, wait for Notion to confirm – and every recurring task for that launch is created, with assignee, due date, duration, dependencies, and parent-child relationships already set.
The team can adjust individual tasks without rebuilding the whole flow.
Once the button is clicked, the launch is live in the system. The team can filter to that specific launch in any view, drag deadlines on the calendar, and watch changes sync across all four views in real time.
The Results
- The team ran their first monthly launch through the system immediately after delivery.
- As of May 2026, every monthly launch runs through this system.
- Recurring task creation that used to require manual setup across tools now takes one button click.
- Full launch visibility – calendar, Kanban, table, Gantt – available in one click, filterable to any specific launch.
- YouTube Shorts tasks are created automatically on every new video publish, with zero manual intervention.
Key Takeaways
Recurring work deserves a repeatable system. If your team runs the same type of project every month, the setup should be almost instant. A well-designed template and a button click is not an over-engineering — it’s compounding time back every single month.
Structure before new tools. We didn’t add anything to their stack. We connected what was already there — Notion, Make, YouTube — and built the structure that made them work together. Most teams don’t need more tools. They need their existing tools to fit together properly.
Visibility is a system, not a dashboard. The launch views aren’t reports you build after the fact. They’re built into the workflow from the start, so progress is always visible without anyone having to ask.
