A software engineer built a pipeline that scripts, narrates, animates and renders history reels in Urdu for about $0.11 each, with a one-click Slack approval. One video passed 21k views on its first day. h/t the original builder on r/SideProject.
Faceless video channels are one of the most talked-about AI side hustles, and also one of the most crowded. Most attempts fail on one of two things: the videos cost too much to make at volume, or they look so generic that nobody watches. A software engineer on Reddit shared a build that tackles both.
Their pipeline turns a topic into a finished reel about Pakistan's history and geography, in Urdu, for about $0.11 per video. One recent reel reached 21.1k views in its first day. Below: how the system is structured, why the cost decision matters more than the tooling, and how you could scope a similar build in your own niche.
What the builder made
The builder describes themselves as a software engineer, not a video editor. Instead of learning editing, they wrote software that does the whole job. According to their post, the pipeline:
- Writes the script in Urdu
- Generates the narration
- Draws animated maps and infographic scenes in code
- Renders the finished reel
- Sends the reel to Slack, where the builder approves it
The builder did not share the specific models, libraries or hosting behind each step, so treat this as an architecture to learn from rather than a stack to copy line for line.
The numbers so far
| Item | Reported figure |
|---|---|
| Cost per finished video | About $0.11 |
| Rejected 2.5D workflow cost | $15-40 per video |
| Build time | A few weeks of evenings and weekends |
| Testing spend | "A fair bit of money" (amount not shared) |
| Best reel, first day | 21.1k views, 898 likes, 45 shares |
The breakout reel covered the Pakistan Steel Mill, which has been shut since 2015. The builder is careful not to overclaim: one video doesn't make a channel, but it is the first proof the system works.
They have not reported any revenue. This is a distribution milestone, not an income milestone.
Why the $0.11 decision is the real story
The most instructive detail is the experiment the builder abandoned. A 2.5D workflow came in at $15-40 per video, and they dropped it.
Short-form channels usually need many posts before any single video breaks through. When each attempt costs cents, you can afford to publish, learn and iterate for a long time. When each attempt costs tens of dollars, a slow start burns your budget before you find what works.
| Factor | Low-cost coded visuals | Premium 2.5D visuals |
|---|---|---|
| Cost per video (reported) | About $0.11 | $15-40 |
| Room for experimentation | Wide | Narrow |
| Visual style | Maps and infographics drawn in code | 2.5D depth effect |
| Fit for history and geography | Strong: maps carry the story | Possibly nicer, not required |
| Risk if a video flops | Negligible | Noticeable |
The lesson generalizes: pick the cheapest format that still serves the content, then spend your savings on volume and testing. For a geography channel, an animated map is not a compromise. It is the content.
Three design choices worth copying
A narrow, underserved niche
One country's history and geography, narrated in Urdu: a specific audience in a language with far less AI-generated competition than English. Narrow topics also make scripting easier to template, because every video follows a similar shape: a place or event, context, and a payoff.
Visuals generated from code, not stock footage
Drawing maps and infographic scenes programmatically gives the channel a consistent look and avoids the recycled-stock feel of many faceless channels. It also keeps costs predictable, since rendering code is cheap compared with generating video frames.
A human in the loop
The reel arrives in Slack and the builder approves it before it goes out. That single step catches factual errors, awkward narration and off-brand topics. For a history channel, accuracy matters for credibility. An approval gate is cheap insurance.
Risks and reality checks
- One hit is not a trend. The builder says so directly. Judge the system on dozens of videos, not one.
- Hidden build costs. Weeks of evenings plus testing money came before the first win.
- Accuracy liability. Automated scripts about history can state things wrong. Keep the approval step and verify facts.
- Platform dependency. Reach can change without warning. Post across more than one platform if you can.
- Skill requirement. This route assumes you can write and maintain software.
How to scope a similar build
- [ ] Choose a narrow topic and language where you can judge accuracy yourself.
- [ ] Define a repeatable video template: hook, context, visual payoff, closing line.
- [ ] Map your pipeline stages: script, narration, visuals, render, review.
- [ ] Prototype the cheapest visual style that fits the topic before testing premium options.
- [ ] Track the full cost of each finished video and set a ceiling before you scale.
- [ ] Add a human approval step, such as a chat message with approve and reject options.
- [ ] Publish consistently and review results after a meaningful batch, not after one video.
Source: the builder's original post on r/SideProject
Originally published on SoloAgentFlow.
Top comments (0)