25
65 Comments

I built a text-to-video AI in 30 days.

Here’s the stack, the bills, and why my initial launch flopped.
Long-time lurker, first-time poster. 👋

I’ve spent the last month building Textideo, a tool that turns text scripts into ready-to-post videos.

In the spirit of Indie Hackers, I’m not here to pitch you. Instead, I want to share the unpolished reality of building an AI product in 2024—specifically the tech choices, the surprisingly high server costs, and how I completely messed up my first launch.

😫 The Itch: The "Content Treadmill"

I’m a developer, not a video editor. But to market my previous side projects, I needed video content.

I found myself spending 4 hours editing a 30-second clip just to post it on Twitter. The friction was insane. I had folders full of blog posts and notes that were dying on my hard drive because I didn't have the energy to visualize them.

I wanted a tool where I could dump text and get a decent base video out. Since I couldn't find one that fit my budget/workflow, I decided to build it.

🛠 The Stack (Keeping it lean)

I time-boxed the MVP build to 30 days to avoid feature creep.

  • Frontend: Next.js + Tailwind (Hosted on Vercel)
  • Backend: Python/FastAPI (Needed for better library support with media processing)
  • The "Brain": OpenAI GPT-4o API (For script analysis and scene splitting)
  • The Visuals: [Stable Diffusion / Pexels API / Stock Footage API]
  • Video Assembly: FFmpeg (The true hero of this project, running on a separate worker)
  • Database: Supabase
  • Payments: Stripe

The Technical Nightmare:
Handling video rendering in the cloud is painful. My first few renders took 10+ minutes for a 30-second clip because I was processing everything synchronously. I had to rewrite the backend to use a job queue (Redis + Celery/BullMQ), which cut the user's perceived wait time significantly.

💸 The Bills (The "AI Tax")

This is something people don't talk about enough. AI wrappers are expensive to run.

  • OpenAI API costs: ~$0.03 per video script.
  • Image Generation/Stock API: ~$0.10 - $0.20 per video.
  • GPU/Worker Server: ~$40/month (fixed cost).

My margins are thinner than a traditional SaaS. This forced me to rethink my pricing model immediately—I couldn't offer a generous "Unlimited Free Tier" without going bankrupt.

📉 The Launch & The Flop

I launched on [Twitter/Product Hunt] thinking, "This solves a real problem, people will flock to it."

Result:

  • Visitors: 400
  • Signups: 15
  • Paying users: 0

Why? I positioned it as a generic "Text to Video" tool.
It turns out, nobody wakes up looking for a "general video tool." They look for "How to make TikToks without showing my face" or "How to turn blog posts into YouTube Shorts."

🔄 The Pivot

I stopped coding and started DMing. I reached out to content writers and newsletter authors specifically. I offered to manually convert one of their articles into a video using my tool.

This "Do things that don't scale" approach worked.

  • I got direct feedback on the video pacing.
  • I found my first paying customer after the 5th manual demo.

🧠 Lessons for other Indie Hackers

  1. UX > AI Models: Users don't care if you use Llama 3 or GPT-4. They care if the video export fails. Stability is your best feature.
  2. Niche Down Hard: The "AI Video" space is crowded by giants (Runway, Sora, HeyGen). As an indie, you can't compete on quality; you have to compete on workflow specific to a niche.
  3. Watch your margins: If you are building GenAI tools, calculate your unit economics on Day 1.

🤔 I need your help

I’m currently struggling with the pricing model. I'm debating between:

  1. Credit System: Pay-as-you-go (Good for margins, bad for MRR).
  2. Monthly Sub: Predictable revenue, but power users might kill my API budget.

If you’ve built an API-heavy wrapper, how do you handle this?

I’ll be hanging out in the comments all day. Feel free to roast the landing page (link in the first comment) or ask about the FFmpeg implementation!

on November 21, 2025
  1. 4

    Here is the link if you want to roast the LP: textideo.com

  2. 2

    This is such a real post. I’m currently building Matcha Resume (AI resume optimizer) using Next.js + Supabase as well, so I feel that "AI Tax" pain deeply.

    To answer your pricing question: Do not do unlimited flat-rate subscriptions. Since your COGS (Cost of Goods Sold) varies per user usage (GPUs/APIs), an unlimited tier is a death trap for an indie.

    I’d recommend a Hybrid Model (Subscription + Credits):

    $X/month: Includes Y videos (credits).

    Top-ups: Pay-as-you-go for extra credits.

    This secures your MRR (predictability) while protecting your margins from power users who would otherwise burn your API budget. It aligns your revenue with your costs.

    Also, the pivot from "Generic Video Tool" to "Newsletter-to-Video" is smart. Niche workflows > GenAI wrappers.

    Keep shipping! — Abhi

    1. 1

      Spot on, Abhi. The "AI Tax" is the biggest headache we share!
      You are absolutely right about the "death trap" of unlimited plans. Given the GPU costs involved in video generation, the Hybrid Model (Sub + Credits) is exactly where I'm leaning. It protects the margins while keeping the entry price reasonable.
      Thanks for validating the pivot strategy, too. Niche workflows definitely feel more sustainable than generic generation. Best of luck with Matcha Resume!

  3. 1

    Really cool breakdown of your journey thanks for sharing it so openly. Your pivot makes total sense too; most tools only take off once the creator stops building and starts talking to real users. I’ve been through something similar when I built a net salary calculator and realized the niche mattered way more than the tech.

    Your pricing struggle is real for API-heavy products. A lot of indie founders I know start with a credit system first to protect margins, then add a light monthly plan once usage patterns are clearer. Might be worth testing that combo.

  4. 1

    @Smoteria

    Love the clarity in your positioning shift. The 10x lift makes total sense,platforms reward specialization.

    Funny enough, this is the exact pattern I see when helping SaaS founders grow through Reddit: the moment their message becomes hyper-specific, subreddits respond insanely well.

    If you ever want to test how niche-focused Reddit marketing could amplify your SaaS design presence, happy to share a quick breakdown.

  5. 1

    Man, reading this felt like looking in a mirror from 6 months ago.

    I had the exact same “content treadmill” pain — folders full of scripts that never became Shorts because editing took 4+ hours and every tool wanted $50–$90/month. I was literally down to my last R400 and almost gave up.

    So I did the only thing I could afford: built my own version in 72 hours straight.

    AI Video Narrator is basically the “I’m broke and desperate” edition of what you’re building — pure client-side, no backend workers, no GPU bills, just Gemini + Web APIs. Takes a script → narrated + captioned Short in ~45–60 seconds.

    I’m keeping it stupid-simple on purpose because I never want another creator to have to choose between rent money and video tools.

    Just launched yesterday with a $45 lifetime deal for the first week (unlimited generations, better voices) because subscriptions were the whole reason I had to build this in the first place.

    Respect for shipping and being brutally open about the bills. That’s the kind of transparency this community needs more of.

  6. 1

    “nobody searches for a general tool” nice idea to keep in mind always it is easy to get lost in trying to make something work. On pricing for API-heavy products I’ve seen hybrid models work best. a small monthly base for commitment and predictable revenue plus credits for heavier usage. The logic is it protects margins without scaring off light users and big companies do it like this too. Thanks for your experience sharing!

  7. 1

    Hey! Cool idea. I'm actually looking for the opposite - I need a growth partner for
    my existing SaaS.

    If you know any growth-focused people looking for equity opportunities, send them my
    way!

    Good luck with your search.

  8. 1

    I have similar struggle. I created Container Load Optimization Solution available as SAAS.

    1. I entered a highly competitive market where free tools are already available.
    2. Porting users to paid tool is very much hard.
    3. I do have monthly fixed cost to cover.

    I have visited your site and text to video section show case beautiful videos, My advice to you shall be: Add the text along side to generated video. Users shall be available to visualize the input to output. Show them the value.

    The feedback cycle is too long. So be patient on DMing.

    Your customers are on Social media, You may think of automating the process, for example people submit the text and you post it on their social media (or send them interface to publish). The end to end integration can be your differentiator.

    The "Text to Video" is too generic.

    Consider the following benefit driven approach (I learned from Indie Hackers) :
    Before:
    We maximize container space utilization and significantly reduce your freight Cost.
    After:
    You will never see a partially filled container leave your factory gates again, maximizing profitability on every shipment, resulting in Zero dead freight and Shut-outs.

    You may advice me on my pricing strategy: https://www.loadviewer.com/introduction/plans

    Thanks

  9. 1

    That’s an impressive achievement — building a text-to-video AI in just 30 days shows real drive and technical skill. If you’re exploring data-driven or AI-powered tools, AltPaths offers powerful crypto analytics and market screening to help support smarter investment decisions.

  10. 1

    Simplicity is key for creators. Focusing on a clean, distraction-free editor is absolutely the right vision.

    1. 1

      Thanks so much — totally agree. A simple, quiet workspace is where the best ideas land. That’s exactly what we’re aiming for with Textideo. Appreciate you sharing this!

  11. 1

    You could do a combination of monthly sub and a credit system. Just make sure it is extremely easy to understand the tiers. E.g.

    • Free: 1 video per month
    • Basic: 29.99 per month (cap at 10 videos, use credits after that)
    • etc.
    1. 2

      Thanks — this is super helpful.
      Clear tiers + a simple sub/credit mix makes a lot of sense. Really appreciate the suggestion!

  12. 1

    “Wow, that’s impressive! Building a text-to-video AI in just 30 days shows incredible focus and skill. Excited to see the results and how it handles creative, real-world use cases.”

    1. 1

      Appreciate it! It was a sprint, but a fun one. My main goal now is exactly what you mentioned—moving beyond 'cool tech demos' to something that actually helps creators in their daily workflow. Stay tuned for the next update!

  13. 1

    Really appreciate how openly you shared the process — this is the side of AI tooling most people don’t talk about. Your stack makes sense, and the cost breakdown is a good reminder that “AI SaaS” isn’t anywhere near traditional SaaS margins. The pivot toward a specific workflow niche was smart. Content creators don’t buy generic tools; they buy shortcuts for their exact pain.

    For pricing, most API-heavy products I’ve seen end up using a hybrid model: a small monthly base + credits. The base covers fixed server costs, and credits protect you from power users eating your margins. It also keeps casual users from feeling locked into high plans.

    You’re on the right track. Getting your first paid user through manual demos validates that people will pay once they feel the workflow solving something real. Keep iterating on that.

    1. 1

      Thanks so much — this means a lot.
      You summed up the reality perfectly: AI tools only click when they remove a very specific pain, not when they try to be everything. And yes, the hybrid pricing model is exactly what we’re leaning toward for the same reasons you mentioned.

      Really appreciate you taking the time to share such thoughtful feedback. It’s genuinely helpful as we keep refining the product.

  14. 1

    impressive and cool project

  15. 1

    Really appreciate you breaking this down so openly. Honestly, it’s wild that you got all that done in a month, the product looks super polished already.

    I’m also exploring AI-driven tools and completely get the pricing dilemma. Credits make sense from a cost side, but users really don’t like thinking in “tokens.” It’s a tough balance.

    I’m curious where your backend is hosted, and why you still needed FFmpeg if you’re using newer video models like Veo or Sora. Seems like a smart choice for full control, though.

    Also wondering how you plan to stand out with so many AI video tools popping up every week. Still, huge respect for what you’ve built. Hope the next launch goes a lot smoother.

    1. 1

      Thanks! It was a crazy month for sure.
      Regarding FFmpeg: We use it for the "post-production" (stitching clips, adding subtitles, audio mixing) that raw AI models don't handle natively yet.
      To stand out, our bet isn't on having a "better model," but on building a better workflow. We want to reduce the friction from idea to final result. Appreciate the support!

      1. 1

        Really get what you mean about focusing on workflow instead of chasing better models. That actually hits one of my biggest pain points, every time I want to create a short promo video for my product DocBeacon (https://docbeacon.io
        ), I get stuck.

        I don’t have good footage, and I’d love to make something clean and professional with AI, but none of the tools I’ve tried can handle the whole process in one flow. It’s either great visuals with no editing control, or flexible editing that feels like manual labor.

        Still searching for something that makes the "idea to finished video" path feel simple. That’s why what you’re building really caught my attention.

  16. 1

    I visited your website, looks similar to leonardo ai. It would be nice to show the prompt that's been used to generate the sample video. Plus, I wasn't able to generate something, not even for once without signup. And how are you using the AI? Hosting the models yourself or relying on API providers?

    1. 1

      Taking the Leonardo comparison as a huge compliment! Great suggestion on showing the prompts—I'll add that to the roadmap.
      Regarding the signup: Video generation is extremely compute-expensive. We have to require accounts to prevent bot abuse and manage costs.
      On the tech side, we currently orchestrate top-tier API providers to ensure the best quality and stability, rather than self-hosting massive models.

  17. 1

    Just commenting to say I admire your commitment. It takes a lot of determination to keep going when you get a bumpy start. Glad it's paying off.

  18. 1

    The amount of convenience we provide is based on our infrastructure. Initially, it is confusing to price. So,rethink your products value and manually do the work of an PRO guy in your niche. The result a content maker & producer will depend on their tools & workflows in their workforce. So check the usage of those tools & $$ they provide as salaries.And do the thinking of how much results(shorts,videos,reels,etc) they produce per month and make a calculation of productive time consumed by their workforce(employees). So if you offload the mental load of the user & speed up the workflow between the workforce or replaces a percent of them to produce results efficiently you can be confident in pricing. Be delusional or DO the manual work and Ask yourself "How much would you pay?". And Ask or discuss with your users itself or with your AI personas "How much would they pay? whether monthly or pay as they go or yearly? ". Atlast, observe everything around which you build and invest accordingly and price. If you completely observe it,you can price it confidently and change by features and users.Price for the user first,they would love it if the price is affordable from their perspective and later price for yourself and the company bu doing long term calculations. So set an average and then raise accordingly and respectively.

    1. 1

      Thanks for sharing this — genuinely appreciate the depth of your perspective.

      You’re absolutely right: real pricing clarity comes from understanding the actual workflow value we replace or speed up, not just infrastructure costs. We’ve been doing a lot more of that manual “PRO-level” work ourselves lately, and it’s eye-opening to see what creators really spend time and money on.

      Your point about pricing for the user first, then adjusting for long-term sustainability, really resonates. Thanks again for taking the time to lay this out — it’s incredibly helpful as we refine our model.

  19. 1

    As a matter of fact, it is better to have payments fast and monthly subscription should not be mandate. People will pay and use just as per convenience. You don't use 2.5 GB/ DAY everyday as a normal person who purchase a monthly data pack.

  20. 1

    Wow, really impressive work building a text-to-video AI in just 30 days! 🎉 Your breakdown of the stack, server costs, and the launch flop is super transparent and valuable for any indie hacker.

    I totally relate to the “content treadmill” problem—spending hours on small edits feels like grinding in shadowfightmodapkcom: every little move counts, and if you don’t optimize, you burn out fast. I love how you pivoted to niche outreach and manual demos—that’s exactly the kind of strategy that wins when the big players dominate the generic space.

    1. 1

      Thanks so much — really appreciate this.
      The “content treadmill” analogy is spot on… it really is a grind unless the workflow is optimized. And yeah, the pivot to niche demos has been the most clarifying part of the whole journey.

      Thanks for the encouragement — comments like yours keep the momentum going!

  21. 1

    I'm currently learning AI and building some tools and websites with Cursor; I hope to launch my first site soon, just like you did.

    1. 1

      That’s awesome — huge congrats on taking the leap.
      Building your first product is the hardest and most rewarding step. Cursor is an amazing accelerator, and you’re already on the right track.

      If you ever want to share what you’re working on or bounce ideas, I’m happy to help. You’ve got this — ship it! 🚀

  22. 1

    Base monthly plan + usage based credits.
    Something like:
    A small monthly fee that covers your fixed costs
    A set number of video credits included
    If they need more, they buy extra packs
    That way:
    Casual users stay happy
    Power users pay for what they consume
    You protect your margins
    You still get predictable MRR

    1. 1

      This breakdown is spot on. It feels like the only sustainable path for AI video apps right now.
      Protecting margins while keeping casual users happy is exactly the balance I'm aiming for. Thanks for laying it out so clearly!

  23. 1

    "I Built a Text-to-Video AI in 30 Days" is an inspiring account of rapid AI development, detailing the challenges and breakthroughs in creating a system that converts text into video. The author shares practical insights, tools, and lessons learned, making it both motivational and educational for AI enthusiasts and developers interested in generative media.

  24. 1

    Love seeing honest build-in-public stories like this.
    I’ve been around founders for 15+ years and the pattern is always the same — things work the moment you stop pretending and start telling the truth about what’s actually happening. Respect for sharing the real journey, not the polished one. Following along.

    1. 1

      Thanks so much — really appreciate that.
      Being honest about the messy parts has actually made the whole journey clearer. Glad to have you following along!

  25. 1

    Building an MVP in 30 days with clear constraints is admirable discipline. Your transparency about costs is refreshing - the AI tax is real and catches a lot of builders off guard. The pivot from self-serve to manual demos shows good market instinct. Getting that first paying customer through direct outreach is often the hardest part.

  26. 1

    Wow, that’s impressive! Building a text-to-video AI in just 30 days shows remarkable focus, technical skill, and creativity. It’s exciting to see rapid innovation in AI, turning ideas into visual content so quickly. Curious to learn about your workflow, the challenges you faced, and how you handled video generation and optimization efficiently.

  27. 1

    That's impressive, man.

  28. 1

    good luck :) I just built one , image to video for AI UGC videos

  29. 1

    This is really cool and you have a fascinating tech. Definitely want to learn more not just in your tech, but in how your solution is differentiated from direct AI video generating promts

    1. 1

      Thanks! Really appreciate that.
      What we’re trying to do differently is focus on the whole flow — not just prompt → video, but turning an idea into a finished piece without all the little headaches in between.
      Happy to share more anytime!

  30. 1

    The main takeaway is that AI tech is amazing, but cloud costs and positioning are critical. Video rendering, API usage, and GPUs add up fast, so a generic "text-to-video" approach often flops without a clear target audience.

  31. 1

    This is really cool, I worked on a similar project https://vidbuilder.ai but not using Video models its for Text and Animation based videos. I would like to hear your comments and maybe we can join forces together

    1. 1

      Thanks for the kind words! I just checked out VidBuilder.ai, and it looks like a great tool. I think your text-to-animation approach complements the generative video model approach nicely—each has its own strengths. I’d be happy to chat and explore potential synergies.

      1. 1

        Thank you for checking the site out. Absolutely, lets talk my email is [email protected]

  32. 1

    That’s incredible! Building a text-to-video AI in just 30 days shows remarkable skill, focus, and creativity. The potential applications—from content creation to education—are huge. Excited to see how it performs and evolves. Truly inspiring work for anyone interested in AI and multimedia innovation.

  33. 1

    Love the "stopped coding and started DMing" lesson. That's such a hard shift to make as a developer—we want to believe the product will speak for itself.
    On the pricing question: I'd suggest starting with a credit system instead of subscriptions. Here's why—users are hesitant to commit to monthly fees for a new product they haven't tested thoroughly. Credits let them try it with low commitment, and you can always migrate to subscriptions once you have a solid user base and proven retention.
    The transition path could be: credits → credits + subscription bundles → pure subscription tiers. Lets you validate willingness to pay without scaring away early adopters.

  34. 1

    Damn, this is one of the most honest breakdowns I’ve seen about building an AI video tool — especially the part about the “AI tax” nuking your margins. The pivot to doing manual demos was a smart move; most people never talk to their actual users. Curious to see where you take it next, especially how you tackle pricing without letting power-users melt your GPU bill.

    1. 1

      Appreciate the feedback! The 'AI tax' is definitely the silent killer for many wrappers. Regarding pricing, that’s the million-dollar question I'm trying to solve right now. I’m prioritizing sustainable unit economics over massive user growth for now—likely via strict usage caps or tiered plans. I'd rather have fewer users and positive margins than a melted GPU bill!

  35. 1

    Wow, building a text-to-video AI in just 30 days is incredible! This showcases impressive technical skill, creativity, and dedication. The potential applications—from content creation to education—are huge. Excited to see how it performs and evolves. Truly inspiring work for anyone interested in AI and multimedia innovation.

  36. 1

    This is super impressive 30 days is a very tight build cycle for anything video-related, especially when dealing with rendering + model latencies.

    I’m curious about two things from your journey:
    1. Which part took the most time to get right?
    The model workflow, video pacing, or getting consistent visual quality?
    2. How did you validate that creators actually wanted this format?
    I’m building something for creator workflows myself, and picking the right use case has been harder than the technical side.

    Really admire the speed and the dedication. Would love to hear more about what surprised you the most during the build.

    1. 1

      Thanks!
      Visual consistency. Getting the model to not "forget" the character was 80% of the work.
      Concierge MVP. I acted as the AI manually for the first 10 users. If they stuck around, I knew I had a product.
      The biggest surprise? How forgiving users are if the storytelling is good.

  37. 1

    Loved the level of detail here.
    The job queue rewrite and async rendering were definitely the right move — cloud video assembly is brutal without proper workers. Also agree that stability beats model choice 100% of the time.
    On the pricing side, most AI tools I’ve built ended up using a “base subscription + metered usage” model. It filters out abusers while keeping normal creators happy.
    Thanks for sharing the honest numbers and lessons — super refreshing to read.

    1. 1

      Glad you enjoyed the read! The queue rewrite was painful but absolutely necessary. And thanks for the pricing tip—the "base + metered" model definitely seems like the smartest way to scale sustainably. Appreciate the insight!

  38. 1

    Speed of execution is everything here. Great job on shipping this fast! 🚀
    With giants like Sora and Runway dominating the general space, do you plan to niche down to a specific vertical (e.g., marketing, faceless channels, or education)? I feel like focusing on a specific use-case is the indie superpower right now.

    1. 1

      Appreciate the support! ⚡️ And I totally agree with your take on the "indie superpower."
      We are currently exploring a few verticals, including e.g., faceless channels and ads. Since we can move faster than the giants, we're letting our early users guide us to the most painful problem to solve. Do you have a personal favorite use-case you'd like to see?

  39. 1

    This comment was deleted 3 months ago.

    1. 1

      Totally agree. For our core users, Textideo cuts a 3–4 hour “script → clips → timing → captions” workflow down to about 8–12 minutes. We’re now adding proper time-to-output tracking so we can benchmark this against CapCut/Canva and validate the real 5–10× delta. Thanks for pushing us to quantify it.

  40. 1

    This comment was deleted 3 months ago.

    1. 1

      Love this question — it forces real honesty. We actually tested a small “concierge” version: turning users’ blog posts into Shorts manually. The demand was decent, but users kept asking for speed and repeatability, not my personal effort. That’s what convinced us the real value is automation, not a $20 gig.

      We’re continuing to run these manual tests to validate what’s worth productizing. Really appreciate the push to stay grounded.

  41. 1

    This comment was deleted 3 months ago.

    1. 1

      Great point — we’ve been too broad in describing our users. Our clearest ICP so far is: a Substack writer with 3–8K subscribers who turns their essays into 2–4 YouTube/LinkedIn Shorts per week. The consistent pain we hear is spending 3–5 hours cutting scripts, timing visuals, and stitching clips in tools like CapCut before publishing.

      We’re now wiring this ICP logic into onboarding so templates, generation modes, and defaults match their actual workflow. Thanks for nudging us toward more precision — it’s already helping us shape the product better.

  42. 1

    This comment was deleted 3 months ago.

    1. 1

      Really appreciate you calling this out — unit economics is exactly what we’re tightening up right now. Our current ~$0.23/video cost puts the 70% margin target around $0.75, and early data shows creators are generally comfortable in the $0.60–$1.20 range for high-quality generation (from actual usage, not guesses).

      We’re also building the per-unit cost dashboard + strict usage caps you mentioned, and overage billing is rolling out next. Thanks for the push — this is the kind of advice that actually moves the product forward.

  43. 1

    This comment was deleted 3 months ago.

Trending on Indie Hackers
I shipped 3 features this weekend based entirely on community feedback. Here's what I built and why. User Avatar 155 comments I'm a lawyer who launched an AI contract tool on Product Hunt today — here's what building it as a non-technical founder actually felt like User Avatar 139 comments “This contract looked normal - but could cost millions” User Avatar 53 comments 👉 The most expensive contract mistakes don’t feel risky User Avatar 40 comments The indie maker's dilemma: 2 months in, 700 downloads, and I'm stuck User Avatar 32 comments I spent weeks building a food decision tool instead of something useful User Avatar 27 comments