Case Study · Content Automation
MPSS
From raw assets to published short-form video across 5 platforms — automatically
A custom content engine that generates short-form video from user-provided assets and distributes it to YouTube Shorts, Instagram Reels, Meta Threads, Reddit, and Telegram — without daily manual work.
Written by Ing. Hlib Yarovyi, Founder · Published
Type
Custom Internal Tool
Client
Digital marketing agency
Platforms
YouTube · Instagram · Threads · Reddit · Telegram
Stack
Spring Boot · Next.js · MongoDB
Maintenance time
~1 hour / month
The Problem
Running a consistent multi-platform content presence is labor-intensive almost by design. For a digital marketing agency managing short-form video content across multiple client accounts, the weekly overhead of creating videos, adapting them to each platform's format, writing captions, uploading manually, and coordinating publish schedules was consuming more than a full working day every week — per account.
The deeper problem wasn't scheduling. Most tools on the market — Buffer, Hootsuite, Later — already handle that half of the equation. The real bottleneck was content production itself. Someone still had to sit down and produce each video before any tool could schedule it. At scale, that labor cost doesn't stay constant: it compounds with every new client account added.
MPSS — Media Production and Scheduling Suite — was built to eliminate that bottleneck entirely. Users provide three things: a background video, a music track, and a list of titles and descriptions. MPSS generates finished short-form video clips automatically and publishes them to YouTube Shorts, Instagram Reels, Meta Threads, Reddit, and Telegram — each platform receiving correctly formatted content with the right metadata, on the right schedule, without manual intervention.
The result: approximately one hour of setup per month sustains a full, active content presence across five platforms. The rest runs itself.
The Challenges
Content Creation Was the Real Bottleneck
Publishing tools assume the content already exists. For an agency producing high volumes of short-form video across multiple client accounts, the creation step — not the upload step — is where hours disappear. No off-the-shelf tool addressed this. The system had to generate video content from source assets, not simply move existing files around.
Five Platforms, Five Different Rule Sets
YouTube Shorts, Instagram Reels, Meta Threads, Reddit, and Telegram each have distinct technical requirements: different aspect ratios, character limits, metadata fields, authentication flows, and API behaviors. A publishing pipeline covering all five had to handle each platform's constraints correctly without making that complexity visible to the user.
OAuth Credential Management at Scale
Every client account on every platform is a separate OAuth connection. Managing token lifecycles, handling expiry gracefully, and prompting users to re-authenticate before queued content is lost — across multiple connected accounts simultaneously — required a credential management layer built into the core of the system, not bolted on after the fact.
Publish Reliability Is Non-Negotiable
A missed scheduled post is a visible failure — there's no human fallback when the system handles distribution. The publishing pipeline needed to be reliable enough that failures were caught, logged, and surfaced to users before they became a client-facing problem. Silent failures are not acceptable in a system clients depend on daily.
How It Works
Automated Video Generation From Source Assets
Users upload a background video, a music track, and a list of content entries — titles and short descriptions. MPSS composes these into finished short-form video clips: overlaying text, applying timing, and rendering output sized for each platform's required format. No video editing software. No per-post manual work. The production pipeline runs server-side and deposits finished clips ready for distribution.
Campaign-Based Content Organization
Content is organized into campaigns, giving the agency a clean way to manage work across client accounts. Each campaign holds its own assets, content list, and publishing schedule — scoped independently and trackable at a glance. This maps directly to how agencies already think about client accounts, reducing the mental overhead of managing multiple concurrent content streams.
Platform-Native Publishing — Not Repurposing
Each platform receives content formatted specifically for that platform: YouTube Shorts get proper titles and recording metadata; Instagram Reels get captions structured for discovery; Threads, Reddit, and Telegram each receive platform-appropriate copy. MPSS doesn't post identical content everywhere — it publishes the correct version of each piece to each channel, respecting how audiences on each platform actually consume content.
OAuth Account Management Built Into the System
Users connect their YouTube and Instagram accounts directly through OAuth inside MPSS. Token management, refresh cycles, and re-authentication prompts are handled automatically — users are notified when action is needed, not surprised by a broken publish queue. Credential state is tracked per account, per platform, so a single expired connection doesn't disrupt the rest of the schedule.
Scheduled Distribution Engine
A background scheduling engine handles all distribution asynchronously — polling for content ready to publish and dispatching it without any user action required. Publish status is tracked per item, per platform, in real time on the dashboard. If a publish fails, it's flagged immediately with enough context for the user to understand and resolve what happened.
Expanding Platform Coverage
MPSS launched with YouTube and Instagram. Meta Threads, Reddit, and Telegram were added in a subsequent phase — each requiring its own integration, authentication model, and content formatting logic. The architecture was designed to absorb new platforms without rebuilding the core, which meant each expansion was a contained addition rather than a system-wide change.
Build Phases
MPSS was built in three sequential phases. Each phase delivered usable functionality before the next began — so the agency could start reclaiming time from manual work while the system continued expanding.
Phase 1
Core Publishing
OAuth integration for YouTube and Instagram, campaign management, platform-specific metadata pipeline, and the initial scheduled publishing engine
Phase 2
Video Generation
Automated video composition from user-provided assets — background video, music track, and content list — with output sized for each platform format
Phase 3
Platform Expansion
Distribution extended to Meta Threads, Reddit articles, and Telegram posts — each with platform-appropriate formatting and its own authentication flow
Results
Per month to maintain an active content presence across five platforms — down from 10+ hours per week
Platforms published to from one dashboard: YouTube Shorts, Instagram Reels, Threads, Reddit, Telegram
Per week recovered from manual video creation, formatting, uploading, and platform-switching
Common Questions
How is MPSS different from Buffer, Hootsuite, or Later?
Standard scheduling tools require you to create the content first — they only handle distribution. MPSS generates the video content from your source assets, then distributes it. That distinction is why the time saving is measured in hours per week rather than minutes per post. For agencies with high content volume, it's the difference between hiring another editor and not needing to.
What does a user actually need to provide?
Three things: a background video, a music track, and a list of content entries (titles and short descriptions). MPSS handles everything after that — video composition, platform-specific formatting, metadata, scheduling, and publishing across all connected accounts.
Does it work for any industry or content niche?
Yes. The generation pipeline is format-based, not topic-constrained. The system produces short-form video content from whatever subject matter the content list contains — e-commerce products, tips and facts, news summaries, motivational content. The niche doesn't matter; the assets and content list do.
What happens if a publish fails?
The scheduling engine tracks publish status per item, per platform. Failed publishes are flagged immediately in the dashboard with context about what went wrong — expired credentials, API rate limits, or connectivity issues. Content is never silently lost, and the system surfaces what needs attention before it becomes a client-facing problem.
Can this be built for my business or agency?
Yes. MPSS was built as a custom internal tool for a specific agency's workflow. We build similar content automation systems for agencies and brands that need to scale content output without scaling headcount. If your team is spending significant time on repetitive content production and cross-platform distribution, a custom system is often the most cost-effective solution at scale.
Content Automation for Agencies That Need to Scale
If your team spends hours every week creating and uploading the same content to multiple platforms, there's a better way. We design and build custom automation systems that handle production and distribution — so your team focuses on strategy, not repetitive execution.
Get in touch →