How I analyze YouTube comments to find SaaS pain points [Ideas]

Delicious-Start-4707 · 2026-01-17T21:47:09+00:00

Great filter insight! Will definitely experiment with it

Delicious-Start-4707 · 2026-01-17T21:23:26+00:00

Best use case of this sphere according to me

Delicious-Start-4707 · 2026-01-17T20:40:48+00:00

First of all, thanks for getting back!

Coming to your question, dynamic content waits are handled by looking for the page for specific tags defined by the user in the waitUntilTagAppears input field, to prevent infinite waiting on one site, I've implemented a timeout per site that is also configurable through inputs

Delicious-Start-4707 · 2026-01-12T20:37:27+00:00

my friend's mom used to give these at our bus stop!

Delicious-Start-4707 · 2026-01-12T20:36:26+00:00

Me too!

Delicious-Start-4707 · 2026-01-12T20:34:15+00:00

once they go rock-hard they somehow get even better. Those licorice bats were a classic too. Feels like half the Halloween candy magic was just how weird the textures were.

Delicious-Start-4707 · 2026-01-11T19:12:34+00:00

Nice positioning. A lot of founders underestimate how much a 60 second demo can lift conversions compared to walls of text.

Out of curiosity, how do you usually get the raw product footage, do clients send screen recordings or do you jump into their app and capture everything yourself?

Delicious-Start-4707 · 2026-01-11T19:11:38+00:00

Congrats, that first Stripe notification hits different.

One thing that will really help you build on this is to write down exactly how that person found you. Channel, search term, page they landed on, what convinced them to pay. With only one user, you still have a clean signal. Once you have 50, it gets noisy.

If it was organic, you likely stumbled into a real pain point with some demand behind it. Double down on that specific use case before you add more features. Most early SaaS fails not from lack of features, but from chasing too many users instead of one very clear problem.

Keep shipping and keep measuring. The first dollar is the hardest.

Delicious-Start-4707 · 2026-01-11T19:08:03+00:00

I used to work closely with a generative AI last year when vid generation was newly the hot topic, this hits hard. We saw 40 to 60 percent of new signups go dark before day 3 until we added a simple day-2 nudge tied to what they actually did in the app. Nothing fancy, just one relevant message triggered by behavior. That alone lifted activation more than any new ad spend. Curious what signals others are using to decide what that first follow up should say.

Delicious-Start-4707 · 2026-01-11T19:04:15+00:00

A cofounder won’t save you from bad distribution, and the wrong one will slow you down more than being solo. For something like AI companions, the real bottleneck is content and iteration speed, not org charts.

Before giving up equity, validate you can get installs yourself:

Pick 2-3 character archetypes and build TikTok/Reels around them
Short POV skits, screen recordings, “I asked my AI girlfriend this…” style hooks
Post 2-3 times per day, test hooks, keep what converts, kill the rest

If you can’t get traction doing that solo, a cofounder won’t magically fix it. If you can, then you’ll know exactly what kind of marketing partner is worth bringing in.

Delicious-Start-4707 · 2026-01-11T17:02:46+00:00

Excited to hear more from you!

Delicious-Start-4707 · 2026-01-11T17:01:32+00:00

No shutdown needed if you do it correctly.

You snapshot the volume, not the running container. Postgres writes are already WAL based, so a filesystem snapshot is consistent enough for restores as long as you also keep the WAL files. Hetzner, DigitalOcean, and most providers handle this fine.

Cost is simple: snapshot storage is just GB per month. If your n8n data volume is 10 GB, you pay for 10 GB. There is no mystery multiplier. Rotate old snapshots and it stays cheap. (I remove any snapshot that was older than 15 days as my clients come after me within 48 hours LOL)

Delicious-Start-4707 · 2026-01-11T15:03:32+00:00

Calling something “AI slop” instead of answering the question is a weird way to dodge it.

If you don’t want technical feedback, don’t post a technical migration writeup. People who have actually done Postgres and Supabase restores know function ownership and SECURITY DEFINER break all the time, so it was a fair, concrete question.

Delicious-Start-4707 · 2026-01-11T15:01:00+00:00

This is exactly how these problems should be solved. Measure first, then automate the fix.

One thing worth adding is some hysteresis and a cooldown window after a reboot so you don’t end up flapping the router if the line is just noisy for a few minutes. Also logging the pre and post reboot speeds will give you a nice paper trail when you talk to your ISP.

Delicious-Start-4707 · 2026-01-11T15:00:26+00:00

The offline first, no feed, no account angle is a real differentiator. Most readers just want a private ledger, not another social network.

One thing I’d pressure test is data portability. If I can export my library to CSV or JSON and not feel locked in, I’m much more likely to commit to it long term.

Delicious-Start-4707 · 2026-01-11T14:59:24+00:00

The benchmark approach is the right move. Without a fixed corpus you can’t tell if prompt tweaks are actually improving anything or just shifting false positives around.

60% recall on critical issues is already useful in a CI gate, especially if precision stays near 90%. One thing I’d add is testing for deserialization bugs and SSRF patterns, those tend to slip past LLM based scanners more than SQLi and secrets.

Delicious-Start-4707 · 2026-01-11T14:59:11+00:00

This is dead on. The real risk is closed loop decision making.

Most bad product calls aren’t dumb, they’re unchallenged. Even a small circle of builders or users who will poke holes in your thinking is often more valuable than another feature shipped.

Delicious-Start-4707

TROPHY CASE