DEV Community: Saviel Yamani

I Spent $312 Testing AI UGC Ads for SaaS. The Boring Hook Won. published: false

Saviel Yamani — Fri, 08 May 2026 03:37:32 +0000

I assumed a clever hook would win. A boring one did, by 4.2x.
Spent $312.47 over 11 days testing five video variants for my Postgres tool.
The lesson wasn't about creative quality. It was about removing my own taste from the loop.

The Hypothesis I Was Sure About

When I finally accepted that my Postgres schema visualizer wasn't going to grow itself, I sat down on a Sunday morning with too much cold brew and a hypothesis I was genuinely excited about: developers are tired of generic SaaS marketing, so a sharp, contrarian hook would crush a boring one.

I'd been writing software for ten years. Of course I knew my audience. I was sure.

This post is about how that hypothesis got demolished, and what I learned about testing AI UGC ads for SaaS when you're a solo founder with no marketing team and no patience for vibes-based decisions.

Spoiler: the winning ad sounds like something a tired tech lead would say at standup. No punchline. No edge. Just a problem statement.

What I Thought Would Win

My stack is Node, Postgres, and Stripe, with a thin React frontend. The product helps devs visualize complex schemas without dragging tables around in pgAdmin like it's 2009. I had ~40 paying users from a Hacker News spike and then a four-week flatline on MRR.

So I wrote five hooks. Just in my head, I'd already ranked them:

"Your ORM is lying to you about your schema." (Edgy. Contrarian. My personal favorite.)
"I rewrote our migration system after a 3 AM incident. Here's what I use now." (Story-driven.)
"Stop opening seven psql tabs. There's a better way." (Pain-focused.)
"Onboard a new dev to your codebase in under 10 minutes." (Utility, kind of dry.)
"What your database GUI isn't showing you." (Mystery.)

If you'd asked me to bet money, I'd have put it on #1. It was sharp. It started a fight. It would absolutely stop the scroll.

I was so wrong it's embarrassing.

The Filming Disaster I'd Rather Forget

Before I get to the test itself, a quick aside, because I think every solo founder needs to hear this. I tried to film these myself first. Bought a $43 ring light off Amazon. Set it up in front of the only wall in my apartment that doesn't have a leaky AC stain on it. Did 17 takes of hook #1.

They were unwatchable. I kept doing this thing where I'd glance at my notes mid-sentence and my eyes would dart sideways like I was committing a crime. My partner walked in, watched ten seconds, and said "you sound like you're being held hostage." Fair.

I burned a Saturday on this. I had nothing to show for it except a slightly sunburned forehead from the ring light.

The Tool Comparison

So I gave up on filming and looked at AI UGC video generators. I evaluated four:

Tool	Why I Considered It	Why I Didn't Pick It
HeyGen	Best-known, polished avatars	$89/mo starter tier was over my budget for a five-video test
Synthesia	Strong enterprise reputation	Output looked corporate; wrong vibe for TikTok-style UGC
Arcads	Designed specifically for ad creative	Limited avatar library at the time I tested
UGCVideo.ai	Native-looking phone-style output	Picked it for the per-video pricing — I needed five outputs once, not a subscription

I went with the last one purely because I didn't want a recurring charge sitting on my Stripe statement reminding me of this experiment if it failed. That was the entire decision.

Two honest gripes after using it: the lip-sync drifts noticeably on words ending in hard consonants, so "Postgres" sometimes lands a beat late, and the export queue can stall during what I assume are peak US hours — I had one render sit at 94% for 38 minutes before I refreshed and re-queued it. Not a dealbreaker for batch testing, but I wouldn't trust it for a same-day turnaround.

The Test Setup

Five scripts, five videos, one Meta campaign with Dynamic Creative Optimization, $25/day budget, 11 days. I tracked everything in a Notion doc because I refuse to pay for another tool. The columns were hook_id, spend, ctr, cpc, signups, notes.

Total burn: $312.47. Roughly what I'd pay for two months of a mid-tier SaaS subscription, which felt about right for a learning budget.

The Results

Here's what the data looked like after day 11:

Hook #1 (the contrarian one I loved): 0.41% CTR, 2 signups
Hook #2 (the 3 AM story): 0.78% CTR, 4 signups
Hook #3 (psql tabs pain): 0.92% CTR, 3 signups
Hook #5 (mystery): 0.33% CTR, 1 signup
Hook #4 (boring onboarding utility): 1.74% CTR, 19 signups

Hook #4 outperformed my favorite by 4.2x on CTR and converted ten times as many trials. The script was 23 seconds long and contained zero rhetorical flourishes. It just described a problem and showed the product solving it.

I sat with that result for a while. The reason it won, I think, is that "onboard a new dev in 10 minutes" is a thing engineering managers are actively, painfully searching for. It maps to a budget line. The contrarian hook was something I wanted to say, not something a buyer was looking to hear.

The Workflow I Use Now

This is the part I'd actually save if I were you. Whenever I push a feature worth promoting, I run this loop:

# my actual checklist, lives in a .md file in the repo
1. grep last 30 days of support emails for repeated phrases
2. extract 3 phrases that sound like job-to-be-done statements
3. write 5 hooks: 2 from those phrases, 3 from my own ideas
4. generate all 5 as UGC-style videos in one batch
5. ship to Meta DCO with $20-30/day cap
6. wait 7 days minimum before judging anything
7. kill bottom 3, double the winner, archive the data

The two non-obvious rules: never let yourself pre-rank the hooks (write them in a random order in the doc), and always include at least two hooks pulled verbatim from customer language. Your taste is the bug. The customer's words are the fix.

The thing I keep coming back to is that I spent ten years learning to write code that doesn't trust my assumptions — unit tests, type checks, assertions, the whole stack. And then the first time I tried to do marketing, I trusted my gut completely. The boring hook didn't win because it was clever. It won because I finally let the data overrule me.

I Make Music at 2AM — Here's How an AI Video Generator Changed My Whole Content Workflow

Saviel Yamani — Fri, 24 Apr 2026 03:52:55 +0000

I've been producing music as a hobby for about four years now. Nothing professional — just beats I make late at night after work, mostly lo-fi stuff and some experimental ambient tracks. For a long time, I kept everything to myself. The idea of "putting it out there" felt overwhelming, not because of the music itself, but because of everything around it.

Visuals. That was always the wall I couldn't get over.

The Problem Nobody Talks About in Music Content Creation

If you're a solo music creator, you probably know this feeling: you spend hours on a track, you're actually proud of it, and then you realize you need something to post it with. A video. A visual. Anything. Uploading a static image to YouTube feels lazy. Shooting a "studio session" video alone is awkward. Hiring a motion designer? Way out of budget for someone who's just doing this for fun.

I tried a few things. I messed around with After Effects tutorials on YouTube — spent a whole weekend on it and ended up with something that looked like a 2009 screensaver. I tried Canva's video editor, which is fine for social posts but not really built for music visuals. Nothing felt right.

Stumbling Into AI Video Generation (By Accident)

Honestly, I didn't go looking for an AI video tool. I saw someone in a Discord server for lo-fi producers mention they'd been using an AI Video Generator to make visualizers for their tracks, and it took maybe 20 minutes per video. I was skeptical. I've been burned by "it's so easy!" claims before.

But I tried it anyway.

The basic idea behind most AI video generators is that you feed them a prompt — sometimes an audio file too — and the model synthesizes visual content that matches a mood or style. It's worth understanding that these tools are built on diffusion-based models, which is the same underlying technology behind image generators like Stable Diffusion. Hugging Face has a solid explainer on how diffusion models work if you're curious about what's actually happening under the hood.

What Actually Worked (And What Didn't)

The first video I generated was... fine. Not great. I typed in something like "dark ambient music, slow moving fog, purple and black tones" and got a clip that looked a bit generic — like stock footage with a filter on it. Not what I imagined.

The learning curve was real. I had to figure out that vague prompts give vague results. When I got more specific — "slow camera drift over a dark forest at night, moonlight through branches, cinematic, no people" — the output got dramatically better. It took me probably five or six failed generations before I started getting things I actually liked.

One thing I didn't expect: the timing sync is still a manual job. The AI generates the visual, but you're still the one cutting it to your track in a video editor. I use DaVinci Resolve (free version) for that part. So it's not a one-click magic solution — it's more like one part of a workflow that still requires your own judgment.

I also hit a weird issue where the tool I was using — VideoAI — kept generating clips with subtle flickering artifacts when I used high-contrast prompts. Took me a while to realize that lowering the "motion intensity" setting fixed most of it. These little things aren't in the documentation; you just find them by breaking stuff.

What I Actually Use It For Now

My current workflow looks something like this:

Finish a track (or even just a demo)
Write 2–3 visual prompts that match the emotional tone of the music
Generate 4–6 short clips (usually 5–10 seconds each)
Stitch them together in DaVinci Resolve, synced to key moments in the track
Export and post

The whole visual side of things now takes me maybe 45 minutes instead of a full weekend. And honestly, the results look better than anything I was making manually.

It's also made me think more intentionally about the mood of my music. Writing a visual prompt forces you to articulate what your track actually feels like — which is a surprisingly useful creative exercise. There's actually some interesting research on how visual and auditory stimuli interact emotionally; this overview from the Journal of New Music Research touches on the relationship between music and visual perception if you want to go down that rabbit hole.

The Honest Takeaway

I'm not going to pretend AI video tools are perfect. The outputs can be inconsistent. Sometimes you generate ten clips and only one is usable. The prompting is genuinely a skill you have to develop, and there's a real risk of everything looking samey if you're not intentional about it.

But for someone like me — a solo creator with no video budget and limited time — it genuinely lowered the barrier enough that I actually started posting my music consistently. That's the real win. Not that the videos are stunning, but that they exist at all.

If you're a music producer who's been sitting on tracks because the visual side feels too hard, it might be worth experimenting with. Just go in with realistic expectations, be ready to iterate, and don't expect the first generation to be the one you use.

The music is still the main thing. The visuals just help people stop scrolling long enough to hear it.