I Built a YouTube Automation Framework in 3 Months with Claude Code
I just launched my YouTube Automation Framework
on Gumroad after 3 months of building.
Most YouTube automation tools force you to choose their AI.
I wanted control over which AI to use (Gemini, ChatGPT, Claude).
Built a modular Python framework where developers can:
-Choose their own AI provider
-Automate any topic (not just emotions)
-Full control over credentials
-Production-ready code
Just launched on Gumroad.
Targeting global developer audience.
Tech Stack:
- Python 3.8+
- Claude Code for rapid development
- Google Cloud APIs
- Pluggable AI architecture
Metrics:
- Built in 3 months
- Using Claude Code for 70% faster development
- Sold to first customers
What I'm Learning:
- Bootstrapped marketing (no paid ads yet)
- Developer-first positioning
- Multi-channel growth strategy
I'm sharing this because:
- Other indie hackers might face same problem
- The approach could inspire similar projects
- Would love to hear if you built something similar
Anyone building developer tools or automation frameworks,
I'd love to hear your approach!
Link: https://jyedam.gumroad.com/l/osjzob
Questions welcome! 👇
Trending on Indie Hackers
The strongest angle here is not “YouTube automation” by itself. That market is already crowded and often feels low-trust. The sharper positioning is developer-controlled media automation: bring your own AI provider, own your credentials, modify the pipeline, and avoid getting locked into someone else’s black-box tool.
That matters because developers do not just want another content generator. They want a framework they can inspect, extend, and run around their own workflow. I’d probably lead harder with the modular/pluggable architecture and less with “YouTube automation,” because the framework angle feels more serious and global.
One thing I’d watch is the brand layer. Right now it feels like the product is sold as a descriptive Gumroad asset, not a real developer platform. If this expands beyond YouTube into broader AI media automation, Xevoa .com would carry that platform direction much better.
Oh.....you told me very meaningful words. I really appreciate it. Thank you!!
Glad it helped.
The main thing I’d pressure-test is whether you want this to be remembered as a YouTube automation asset or as a developer framework for AI media workflows.
Those are very different categories.
If it stays YouTube-only, a descriptive name is fine. But if the bigger direction is modular AI media automation where developers can bring their own providers, credentials, and pipeline logic, then the brand should probably feel more like a platform than a Gumroad tool.
That is why Xevoa came to mind. It gives the product more room if you expand beyond YouTube into broader media automation.
Happy to connect on LinkedIn if useful:
https://www.linkedin.com/in/aryan-y-0163b0278/
I'm so grateful for you. Thank you! I absorbed your advice and made new domain for new project which would be developer platform. I hope this can lead me to a new way.
That’s a smart move.
If the new project is meant to become a developer platform, the domain/name matters more than it would for a small Gumroad asset.
The key test is whether the new name feels like:
a real developer platform
something broader than YouTube automation
something builders can trust, extend, and remember
What domain/name did you choose for it? Happy to give you a direct outside read before you get too far into building around it.
It is called 'jinhwa'. It means evolution in korean. I thought developer platform should be something endlessly adaptable onto diverse ways.
Jinhwa has a good internal meaning, especially if the idea is evolution and adaptability.
The thing I’d pressure-test is whether that meaning travels clearly to the developers you want to reach globally.
For a developer platform, the name has to do two jobs fast:
feel technical enough to trust
feel broad enough to grow beyond one automation use case
Jinhwa may work if you build the story around it clearly, but the risk is that most users will not know the meaning unless you explain it. So the brand may depend more on education.
That is why I still think a name like Xevoa.com fits the platform direction more naturally. It feels more like a modern developer/workflow system from the first impression, without needing the meaning explained.
I would not say Jinhwa is wrong. I’d just compare it honestly against the kind of global developer brand you want this to become before you build too far around it.
I understood! Thank you for you advice..!!
Makes sense.
Jinhwa can work if you make the “evolution/adaptability” story clear from the first impression.
The main thing I’d watch is whether global developers remember the name after seeing it once, or whether they only understand it after you explain the Korean meaning.
If the platform starts getting traction and you feel the name needs a more global developer-system feel later, that would be the right time to revisit it.
Happy to keep an eye on it as you build.
You got huge gratitude from me. Thank you. I really reflected on your advice!