Case Study · Content Workflow Automation
MPSS
A workflow automation tool that turns source files into published short-form video
MPSS is a custom automation platform for a marketing agency. It creates short-form video from simple inputs and publishes each item across multiple platforms.
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
The client was a digital marketing agency that needed to publish short-form video for multiple accounts. The weekly process was repetitive: make the video, resize it, write captions, upload it, and repeat the same work for each platform.
Standard scheduling tools help with the last step only. They assume the content already exists. The real bottleneck was production. Someone still had to turn raw assets into finished video before anything could be scheduled.
MPSS was built as a content automation system to remove that manual workload. A user uploads a background video, a music track, and a list of titles and descriptions. The system builds the video, prepares the right post format, and publishes it on schedule.
The result is simple: the agency keeps an active content presence across five platforms while spending about one hour per month on maintenance.
The Challenges
Production Took More Time Than Publishing
The team was losing time before the scheduling step even started. The system had to create the video, not just send finished files.
Every Platform Has Different Rules
YouTube Shorts, Instagram Reels, Threads, Reddit, and Telegram each have different formats, text limits, and API behavior.
OAuth State Had to Stay Reliable
Each connected account needed token refresh, expiry handling, and clear re-auth flows. Broken credentials could not silently stop publishing.
Missed Posts Are Visible Failures
If the system fails, the client sees the gap right away. Publish tracking and error visibility had to be built into the product.
How It Works
Generate Video From Three Inputs
The user provides a background video, a music track, and a list of content entries. The system turns that input into finished short-form clips.
Organize Work by Campaign
Campaign-based structure keeps assets, schedules, and content lists grouped by client. That matches how agencies already manage accounts.
Publish Native Versions for Each Platform
The system does not copy the same post everywhere. It prepares the right caption, metadata, and output for each channel.
Handle OAuth Inside the Product
Users connect accounts directly in MPSS. The product tracks token state, refresh cycles, and re-auth needs before a queue breaks.
Track Failures Early
The dashboard shows publish status per item and per platform. If a post fails, the team sees the reason quickly and can fix it.
Expand Without Rebuilding the Core
The first version focused on YouTube and Instagram. Threads, Reddit, and Telegram were added later without rebuilding the core platform.
Build Phases
The system shipped in three phases. Each phase delivered useful functionality before the next layer was added.
Phase 1
Core Publishing
OAuth for YouTube and Instagram, campaigns, scheduling, and the first publishing engine
Phase 2
Video Generation
Server-side video composition from uploaded assets and content lists
Phase 3
Platform Expansion
Support for Threads, Reddit, and Telegram with separate posting logic
Results
Per month to maintain active publishing across five platforms
Platforms managed by one internal publishing platform
Manual work removed from the agency's weekly workflow
Common Questions
How is this different from Buffer or Hootsuite?
Those tools schedule finished content. MPSS also creates the video and prepares the right version for each platform.
What does the user need to upload?
A background video, a music track, and a list of titles and short descriptions. The rest is handled by the system.
Can it work in different niches?
Yes. The system is format-based, not topic-based. If the inputs are clear, the workflow can support many kinds of content.
What happens if a post fails?
The dashboard shows the failure status and the reason, such as expired credentials or API issues. Posts are not lost silently.
Can you build a similar system for us?
Yes. We build custom automation systems for teams that spend too much time on repetitive production and distribution work.
Need Content Automation for Repetitive Publishing Work?
If your team keeps doing the same content steps by hand, we can design a system that removes the repeated work.
Get in touch ->