How to make $10k/month from automated marketing

A Rork builder's YouTube channel hit 100,000+ subscribers and earned a YouTube Silver Play Button, fully automated. Not a single video manually uploaded, not a single hour spent in front of a camera.

The system that runs that channel takes about 10 minutes to produce 700 posts, and once it's set up, it runs forever.

This shouldn't be your only distribution strategy, but the videos are so cheap to produce that it's worth running as a layer on top of everything else you're doing.

The format is simple: take viral video hooks from a known creator, stitch a direct CTA for your app onto the back of each one, and schedule the result across TikTok, Instagram Reels, and YouTube Shorts.

Here's how to build the whole thing.

Step #1: Find your viral hooks

This is the most important part of the whole process.

Spend time finding creators with consistently strong numbers, ideally creators your target users are already watching.

Whoever the creator is, the video needs to feel like brainrot to the viewer. That low-friction, scroll-stopping shock is part of what makes this format work, and if the hook feels too produced or too polished, it stops feeling native to the feed.

Lock in your creator before you do anything else, everything downstream depends on this choice.

Step #2: Create the CTA clip

This is the only manual part of the whole pipeline, and once it's done, you never touch it again.

Open the editor of your choice and grab 2 images from Pinterest that match your niche. If you're building a fitness app, fitness images. If you're building a faith app, faith images. Whatever your audience is already saving on Pinterest is what they want to see on TikTok.

Drop the images into the editor as your base and add a recognizable viral song that fits your niche, ideally one your audience already associates with the emotion you're going for.

Add transitions and effects to make the clip feel native to the platform.

That's it. Export as a vertical MP4.

You can make one CTA variation or three to five, but one is enough to start. The format is more important than the variations at this stage.

This is also the only piece of the workflow that lives outside of Rork. Everything else from here on out gets built once, in one prompt.

Step #3: Build the automation pipeline with Rork

In the past, this step required two separate scripts: one to scrape viral hooks from a creator, another to trim and stitch them to your CTA clip. You'd run them locally, save MP4s to a folder, and manage the whole pipeline by hand.

Now you build it once with Rork and it becomes a reusable web tool you can come back to forever: upload your CTA, paste a creator URL, click a button, download a batch of finished videos.

We created Hook Stitcher, which is live right now at LINK. Upload your CTA clip and it generates your stitched videos for you.

If you just want the videos, use the tool and skip to Step 4.

But we'd recommend building your own version anyway, since you'll be able to customize it for your niche and add your own features.

Open Rork, paste the prompt below, and wait a few minutes. You'll get a working web app named Hook Stitcher that does the entire pipeline end to end.

Here's the exact prompt to use:

Build me a web app called "Hook Stitcher" that automates the creation of viral short-form video content for TikTok, YouTube Shorts, and Instagram Reels. The app combines a hook from a viral creator with my own CTA clip to produce ready-to-post stitched videos.

CORE USER FLOW

1. User uploads their pre-made CTA video (MP4, vertical format). Show a preview after upload.

2. User pastes the URL of a YouTube creator's Shorts page (e.g., https://www.youtube.com/@creatorname/shorts).

3. User selects how many videos to scrape from that creator (default 10, range 1-20).

4. User clicks "Generate Stitched Videos."

5. App scrapes the most recent YouTube Shorts from that creator's page.

6. For each scraped video, the app trims it to only the first 3 seconds, then concatenates the user's CTA video to the end. The result is one continuous MP4 per source video.

7. App displays the finished stitched videos in a gallery with thumbnail previews.

8. User can download each video individually or all of them as a ZIP file.

TECHNICAL IMPLEMENTATION

Video scraping: Use a third-party YouTube downloader API (such as RapidAPI's YouTube Shorts downloader, or yt-dlp running on a serverless function). Take the creator's Shorts URL, return MP4 files for the N most recent Shorts. Handle pagination if needed.

Video processing: Use ffmpeg.wasm in the browser for all video editing. For each scraped video:

• Trim to the first 3 seconds using -t 3

• Re-encode both the trimmed clip and the user's CTA video to identical codec, resolution, framerate, and audio settings (H.264 video, AAC audio, 1080x1920, 30fps, 44.1kHz audio) to avoid concat artifacts

• Concatenate the 3-second clip followed by the CTA video using ffmpeg's concat demuxer

• Output a single MP4 per source video

Storage: Store processed videos in browser memory or IndexedDB. No backend database needed. Provide download links and a ZIP export using JSZip.

UI REQUIREMENTS

• Clean, modern dark-mode interface with a subtle gradient background

• Top section: drag-and-drop uploader for the CTA video, with a video preview after upload and a "Replace" button

• Middle section: input field for creator URL with URL validation, plus a number stepper for video count

• A large primary button labeled "Generate Stitched Videos" that triggers the full pipeline

• Below the button: real-time progress UI showing each video's status (Queued / Downloading / Trimming / Stitching / Done / Failed)

• Gallery section that appears once videos are ready: grid layout, each cell shows a video thumbnail with a play-on-hover preview, a download button, and a delete button

• Floating action bar at the bottom with "Download All as ZIP" and "Clear All"

• Settings cog icon top-right that opens a panel with:

  • Hook length in seconds (default 3, range 1-10)

  • Output resolution (default 1080x1920)

  • Output framerate (default 30fps)

  • Audio: keep original / mute original / mute CTA / mute both

EDGE CASES TO HANDLE

• Source video shorter than the hook length: skip that video and show a clear error in its slot

• Mismatched aspect ratios between source and CTA: pad or crop the source to match 9:16

• Mismatched framerates or codecs: always re-encode both clips to the same settings before concatenating

• Audio sync drift: re-encode audio explicitly, do not stream-copy

• Failed scrapes: continue processing the videos that succeeded, show per-video error messages

• Large total file size: warn if the combined output exceeds 500MB

CONSTRAINTS

• This must be a web app, not a mobile app. If a backend is required for the scraping API, use a single serverless function (Vercel/Netlify/Supabase Edge). Otherwise keep everything client-side.

• Use Tailwind for styling.

• No user accounts, no login, no database. Single-session use only.

• The app should be usable on desktop only (this is a content creation tool, not a mobile experience). Lock the layout to a minimum width of 1024px.

Build the full app end-to-end. Do not stub out any of the video processing or scraping logic.

Whether you use our public tool or your own build, the workflow is the same: upload the CTA clip you made in Step 2, paste a creator URL, set the number of videos you want, and click Generate.

The app will scrape the requested number of recent Shorts, trim each one to the first 3 seconds, and stitch your CTA onto the back. A minute or two later, you have a batch of finished videos ready to download.

700 videos in 10 minutes is not an exaggeration. Once the tool exists, the only ceiling is how many creators you want to scrape from.

Step #4: Schedule and post

You now have a folder of stitched videos, and if you skipped the build, go generate your first batch right now with Hook Stitcher at LINK. The last step is getting them onto the platforms.

Use a content scheduler. There are several good ones, pick whichever fits your budget. The point is that you should never be uploading individual videos manually after the first week.

One important warmup tip for YouTube specifically: new accounts that immediately start uploading scheduled batches of videos get flagged. The platform doesn't like seeing a fresh account go from zero to fifty uploads in a day, so spend the first week uploading manually to warm the account up, and after that, switch to the scheduler.

This warmup matters. Channels that skipped it have been shadowbanned for weeks at a time, and one channel running this exact system got hit early and needed about 50 videos of consistent posting before YouTube lifted the shadowban and views came back.

What this actually gets you

The full pipeline takes 10 minutes to produce a week's worth of content, and the CTA clip is a one-time setup.

The result is a content engine that runs in the background while you focus on the higher-leverage parts of growing your app: influencer deals, UGC campaigns, paid ads, onboarding optimization. The work that actually compounds.

Automated content is the cheapest layer of content you'll ever produce, and the videos compound in the algorithm whether you're paying attention to them or not.

Build it once. Let it run.

Links

• www.youtube.com/@creatorname/shorts
• shorts-sticher.rork.app