Faceless ↗ video tool: AI videos with auto-posting
- MRR
- $43,410 Verified 2026-10-18
- Total revenue
- $220,786
- Active subscriptions
- 1,024
Verified by TrustMRR
In one line: A tool that generates and auto-posts AI short videos, with monthly plans that buy video credits.
- Founder
- Shivansh MehendirattaX ↗
Timeline
- Founded date listed on TrustMRR
- Revenue that month: $1,676 (TrustMRR)
- Revenue that month: $11,610 (TrustMRR)
- Revenue that month: $13,778 (TrustMRR)
- Revenue that month: $43,866 (TrustMRR)
Compared with similar products
Sources: TrustMRR: Faceless; TrustMRR: Vid.AI; TrustMRR: White Glove Content; TrustMRR: Gomotion AI.
TrustMRR figures are monthly revenue as shown on 2026-10-23 (read-only sync from the payment provider).
Moves Faceless made
No public information yet
How to copy it
Start from a small tool you already have, doing one thing: turn users' raw material into a ready-to-use result
Bring out the small tool people already use; if you have none, build one that does a single thing: users upload or paste raw material and get a ready-to-use result. Launch it free and public, charge nothing, and count how many different people export. What the founder did: the product began as a tool for turning audio and scripts into captioned vertical video (faceless.so About), reworked from the team's previous product (X post by @Pushpit07).Expand ▾Collapse ▴
Bring out the small tool people already use; if you have none, build one that does a single thing: users upload or paste raw material and get a ready-to-use result. Launch it free and public, charge nothing, and count how many different people export. What the founder did: the product began as a tool for turning audio and scripts into captioned vertical video (faceless.so About ↗), reworked from the team's previous product (X post by @Pushpit07 ↗).
- A public URL where uploading raw material exports a result; your backend counts how many different people have exported.
- A stranger comes back unprompted to export a second time.
Write me the backend of a single-purpose tool: users upload <the raw material your target users have> or paste text. 1) where needed, fill gaps with an AI API (e.g. text to speech); 2) produce <the result they want>; 3) output a downloadable file; 4) log each export: anonymous user id, input size, run time. Read API keys from environment variables; follow official docs and flag anything uncertain for me to check.
Step 1: turn the script into a voiceover and get word timings from the transcription API for captions.
Step 1: combine background and voiceover into a 1080x1920 MP4 and burn in captions with the subtitles filter.
Ask on the export-complete page "what do you still do after exporting" and pick the next feature from the answers
Embed a one-question form on the step 1 export-complete page: "After you get the result, what do you still have to do yourself?" Group and count the answers by meaning; the top item is your next feature, rather than copying someone else's answer. What the founder did: users kept asking for the part after the export, posting every day across platforms, so the product grew into a system that runs whole channels (faceless.so About).Expand ▾Collapse ▴
Embed a one-question form on the step 1 export-complete page: "After you get the result, what do you still have to do yourself?" Group and count the answers by meaning; the top item is your next feature, rather than copying someone else's answer. What the founder did: users kept asking for the part after the export, posting every day across platforms, so the product grew into a system that runs whole channels (faceless.so About ↗).
- The form has answers from many different exporting users; a grouping table (category, count, 3 quotes) with the top category in the header.
- The top group is clearly larger than the rest rather than spread evenly.
Below are answers collected on the export-complete page of my "<raw material> to <result>" tool to the question "After you get the result, what do you still have to do yourself?". Please: 1) group by meaning, with a count and 3 quotes per group, counting each user once; 2) take the top group and write it as a one-line product feature, plus what v1 won't do; 3) if the top group is publishing, list the channels users name and how often; 4) use only my answers. Answers: <paste>
Step 2: build a one-question form, embed it on the export-complete page, and collect what users still have to do after exporting.
Build the product: generate daily on the user's chosen topic and schedule it to their first channel
Add the feature step 2 ranked first. If it's publishing, let users pick a topic, generate one piece a day automatically and schedule it through the channel's official API, starting with only the channel users mention most. Use the cheapest visual format first and log each piece's generation cost for pricing. What the founder did: started with one platform and added more one by one (faceless.so), with narrated still images as the cheapest format (faceless.so pricing).Expand ▾Collapse ▴
Add the feature step 2 ranked first. If it's publishing, let users pick a topic, generate one piece a day automatically and schedule it through the channel's official API, starting with only the channel users mention most. Use the cheapest visual format first and log each piece's generation cost for pricing. What the founder did: started with one platform and added more one by one (faceless.so ↗), with narrated still images as the cheapest format (faceless.so pricing ↗).
- A test account gets 1 auto-generated piece a day for several days, each going public at the set time with no manual steps; each piece's generation cost is logged.
- Every piece on the test account went public at the set time with no manual uploads.
Add auto-publishing to my existing "<raw material> to <result>" tool: 1) the user picks a topic and a daily job generates one piece automatically; 2) upload it privately through the official API of <the channel users mention most> with a scheduled publish time, generating title and description from the content; 3) users grant publish permission via OAuth, with tokens stored encrypted; 4) log API usage and cost per piece so I can price it. Follow official docs and flag anything uncertain for me to check.
Launch a few free tool pages and submit them to Google Search Console
Build a few free tool pages that need no signup, do one thing each and sit close to your product, with a product entry at the bottom. After launch, submit your sitemap in Google Search Console and request indexing with URL Inspection. What the founder did: a co-founder said building free tools brought SEO traffic (X post by @shivanshco), and SEO is the main traffic source (X post by @Pushpit07).Expand ▾Collapse ▴
Build a few free tool pages that need no signup, do one thing each and sit close to your product, with a product entry at the bottom. After launch, submit your sitemap in Google Search Console and request indexing with URL Inspection. What the founder did: a co-founder said building free tools brought SEO traffic (X post by @shivanshco ↗), and SEO is the main traffic source (X post by @Pushpit07 ↗).
- The tool pages work without signup; Search Console shows the sitemap as successful and URL Inspection shows the pages indexed.
- These pages start getting impressions in the Search Console performance report.
I'm building a SaaS that <one line: what your product does> and want SEO traffic from free tool pages. Below are 20 Google autocomplete suggestions for a few terms in <your niche>. Please: 1) pick 3 suitable for free no-signup, single-purpose tools, stating each tool's input and output; 2) write each page's title, meta description, H1 and 3 subheadings; 3) end each page with one line leading to the paid product, stating only what it does and promising no results. Terms: <paste>
Step 4: submit the sitemap, request indexing of the 3 tool pages with URL Inspection, then watch their impressions in the performance report.
Create a monthly subscription in Stripe: signup is free, generating output is paid
On Stripe's Payment Links page, create a monthly subscription link whose name states the monthly credits and roughly how many pieces they cover, and place it at the tool pages' product entry and right before generation in the product. Set credits from the per-piece cost logged in step 3. What the founder did: signing up, writing the script and choosing a style are free, while rendering uses credits from paid plans, paid through Stripe (faceless.so pricing).Expand ▾Collapse ▴
On Stripe's Payment Links page, create a monthly subscription link whose name states the monthly credits and roughly how many pieces they cover, and place it at the tool pages' product entry and right before generation in the product. Set credits from the per-piece cost logged in step 3. What the founder did: signing up, writing the script and choosing a style are free, while rendering uses credits from paid plans, paid through Stripe (faceless.so pricing ↗).
- The payment link opens; unpaid accounts can do the prep but can't generate; the "pieces per month x cost per piece" math is written down.
- Pay once in Stripe's test environment: the subscription is active right away and the account shows the credits.
I'm building a SaaS that <one line: what your product does>. The first plan is $<price>/month; signup and prep are free and generating uses credits. Step 3 measured a generation cost of $<x> per piece. Please: 1) set the plan's monthly credits and cost per piece, convert to roughly how many pieces a month, and show the math; 2) write the Stripe product name and a one-line description; 3) write one English line shown before generation explaining why it's paid (each piece has a real cost); 4) use only my cost.
Step 5: on the Payment Links page, create a $29/month subscription link with no trial; TrustMRR shows Faceless.so's revenue verified through the Stripe API, and its pricing page says "Secure payment via Stripe".
Get your first revenue: the first subscriber's first piece publishes on schedule
When someone pays, confirm the payment in your Stripe payments list, then check the user's account to confirm their first piece went public at the set time; if they paid and nothing went out, you won't keep them. What the founder did: the selling point is handling it all the way to publishing, not just exporting (faceless.so About).Expand ▾Collapse ▴
When someone pays, confirm the payment in your Stripe payments list, then check the user's account to confirm their first piece went public at the set time; if they paid and nothing went out, you won't keep them. What the founder did: the selling point is handling it all the way to publishing, not just exporting (faceless.so About ↗).
- Stripe shows the first real subscription payment (not test mode) and the user's first piece has gone public automatically.
- The user doesn't cancel in the first month and replies with the next channel they want.
My SaaS that <one line: what your product does> just got its first paying user. Below are their topic, publish time, first piece's title and link, credits left this month and which free tool page they came from. Write an English welcome email under 100 words: 1) tell them when the first piece went out (with link); 2) when it posts each day and how many pieces this month's credits cover (my numbers); 3) ask which other channel they want auto-posting to; 4) promise no results. Material: <paste>
Step 6: check the first real $29 subscription payment in the payments list; TrustMRR shows Faceless.so's revenue verified through the Stripe API.
Sources
Next case
White Glove Content: done-for-you faceless videos with AI voiceover
Business model: Productized service subscription (done-for-you faceless short/long videos + auto-publishing)
Data source: TrustMRR, checked 2026-10-17
