Own product · In production

Content factory

My video workshop: a repository holding the scripts, the Remotion graphics sources, the diagrams and the platform rules. Claude Code writes the script and assembles the materials, filming and editing stay with the human, and publishing is done by hand.

The pain

Video means a scriptwriter, a motion designer, an editor and someone to lay the text out across platforms. For one author that is a contract per video, or no videos at all.

Now

A workshop in a repository: commands write the script in blocks, overlays and diagrams are built in code, and a local Whisper does the transcription. Filming, editing and publishing stay with the human.

What the business gets

A video does not hinge on a contractor: script, graphics and subtitles are put together on the spot.
Graphics are reused: branded overlays are rendered once and laid over any footage.
Transcription runs locally, so subtitles cost neither a per-minute fee nor an API key.
A command prepares the texts per platform, but a human posts them - there is no auto-posting at all.

From source to result

A description of the video
A script in blocks
Overlays, diagrams, slides
Filming and editing
Subtitles and platform texts

The script marks every block with its recording mode: a voiced block carries the words verbatim, a screen block carries what is open and which actions to show. One shared template would give either an unreadable script or improvisation off a sheet of paper.

How it works

Each kind of material has its own tool, and a table says which: a branded overlay is Remotion, a diagram is a single Excalidraw canvas, a list of points is slides, an interface is a live walkthrough. Otherwise one tool gets dragged where another works better.

Auto-posting was removed deliberately: the social posting servers are gone and the command only prepares the texts per platform. One external connection is left - Telegram search for research, not distribution.

Heavy renders are not tracked in the repository: what is published lives on the platforms, and what stays here are the composition sources and the scripts - the things everything is rebuilt from.

After publication a video’s folder moves to a separate directory: its state is visible from where it sits rather than from a status line someone forgets to change.

Who maintains it now

Me. This is my own workshop rather than a service for sale: the repository is not published.

Other cases for this step

Internal system · In production

Management finance loop

A finance analyst develops it, not a programmer

The pain: Every change ran into hiring and a queue to the developer: growth depended on whether a person could be found.
Now: The finance analyst extends the system directly; the engineer owns review and the release to production.

Maintained by: a finance analyst
Specialist’s path: one month to margin calculation

43 % of changes are made by a company specialist, not a programmer

The same system pays off across 3 more steps

Internal system · In production

Product portal

A product specialist runs it: 73 % of changes are theirs

The pain: A fix in product data had to be ordered: from the PLM vendor as a paid modification, internally as a ticket to a developer. Either way it meant a queue.
Now: The portal is run by the product specialist - the person who fills in the product cards every day. The engineer owns review and the release to production, not the next card attribute.

Maintained by: a product specialist
Specialist’s path: days to a working portal

73 % of changes are made by the product specialist

The same system pays off across 2 more steps

Open source · In production

Starter application template

Seven applications in a month with one team

The pain: Every new project started with a week of setup, and only an engineer could do it. The queue to that engineer was the real ceiling on speed.
Now: Setup stopped being the bottleneck: the order those three production systems were built in is folded into a single command. In that same month one team launched seven applications.

Launched
Maintained by: an engineer and company specialists
Workspace: skills and commands for daily work

The same system pays off on one more step

GitHub

Open source · In production

Seller workspace

A seller runs sales without hiring an analyst

The pain: Going through sales, unit economics, the funnel, card SEO, ABC analysis, competitors - that is a job for a separate person. A small store has nothing to hire them with.
Now: An open template: one clone per store, keys in the environment, connectors to three marketplaces and seven commands for those questions. Intended so; how far it replaces an analyst I have not measured.

Commands: report, unit economics, funnel, SEO, ABC, competitors
Model
Changing a price: «before → after» first, confirmation after

GitHub

Type: Own product
Status: In production
Coverage: script, graphics, subtitles, platform texts
Maintained by: the author
Replaced: contracting out the script, graphics and editing

Remotion 4React 19TypeScriptTailwind 4Claude CodeWhisperFFmpegExcalidrawPythonTelethon