When the work is blog posts, social drafts, carousels, video clips, and custom covers, it is hard to keep track of what is published, what is queued, and what is still waiting for review.
Read the full story →The content process was working, but it lived across spreadsheets, drafts, video files, and a queue only he could see. Nothing connected. Some days, finding the next thing to review took almost as much effort as making the content.
The fix was one place for blog, social, YouTube, carousels, and covers, with AI helpers added only where they saved real time.
A Flask plus React dashboard, deployed on the owner's machine over Tailscale, with a SQLite backend and tabs for every kind of work the content engine has to handle.
Research, draft, review, publish. The post is ready by morning, not midnight.
Upload, transcribe with Whisper, score the moments worth keeping, then cut the clips.
Drafts and carousels generated from the same source material the blog already used.
Cover art generated with Nano Banana 2 so the thumbnails do not look stock.
One queue, one calendar, one place to see what is published, queued, or waiting on him.
Useful local knowledge was buried in conversations instead of living on pages buyers, Google, and AI tools could read.
The new site turned local areas, buyer questions, and clear answers into a search-ready structure.
The owner had ideas to test, but too many tool choices kept slowing down the next move.
A steady advisory workflow helped sort the options and keep the setup moving.
If I can help, I will tell you what I would fix first. If I cannot, I will say that too.
Apply to work with me →