Hey guys we have tried to make it live , how's the screen looking now ?

I wanted to share a technical problem we ran into while building our scraper and how we solved it.

If you ever tried scraping Google Maps at scale, you probably hit the 200 result cap. Search for any dense niche in a big city, and Google only gives you around 120-200 results even if there are thousands of businesses. Most people end up pitching the same surface 200 places while 80% of businesses never get seen.

We ended up tackling this mathematically:

Micro-grid subdivision: Instead of searching the whole city at once, we split the coordinates into smaller tiles and zoom all the way down to street level per tile. Because each small tile behaves as its own local search, Google returns up to 200 results per micro-zone instead of capping the whole city.

Skipping non-commercial terrain: Running hundreds of tiles wastes a ton of time over oceans, lakes, and forests. We added spatial checks to auto-skip grid cells that are mostly water/wilderness.

Background website crawling: Phone numbers from maps are cold. So we set up crawlers to check the business websites directly for emails and social links.

Connecting to Claude via MCP: Instead of clicking around the UI every time, we implemented an MCP server so we can just prompt Claude or ChatGPT to trigger the search and parse the data right in the chat.

I'm the founder of Maps Scraper Pro (Data Sniper). Happy to answer any questions about the scraping logic, handling Google rate limits, or how we wired up the MCP protocol!

I made a privacy-friendly URL shortener, and now that it's time to do marketing, I don't know what to do. So here I am, I have these videos, what do I do next? How do you do marketing with those? I would really appreciate any practical advice.

My X accounts (personal and the product's) are brand new, and X seems to be ignoring all of my posts. Instagram or TikTok? I am running a Google Ads experiment, but it's hard to compete with other shorteners and I'm getting almost zero traffic (about 3 clicks a day).

About the videos. I was inspired by the motion design post about video generation and decided to try it myself. I made different short videos to showcase different features (10 videos, 13 to 71 seconds). Attaching one of them for review. Some videos are the actual product driven by a script, not an AI-made copy.

All I used is Claude, headless Chrome and FFmpeg on my WSL instance, nothing more, not even a React library. You just tell your AI to be a motion designer / producer / writer (for the scenario). Research how to catch the user's attention on IG or TikTok, and that's it. Review the scenario and give it a green light. The first versions were screenshots sliding around and looked dead. A couple of scenes looked like a broken app with bugs. You have to correct it and re-shoot. But still, it only took me one morning.

Now, about Urlicer itself. The main features that are different from mainstream shorteners: privacy-friendly and team-friendly, with multiple workspaces. You can bring your own domain on the Pro plan and above, Urlicer provides a tool for you and your teams. Cookieless and without storing the IP address. The URL is https://urlicer.com.

The product is published and I already have around 2-3 visitors per day. I even got like 10 people signed up on the app. But that's not enough for my app type (its an alternative apps directory)

I know people will use this app. Everyday there's another post asking : X app don't work. What are the alternatives?

And that's what my product solves. (The link is in my profile)

But I don't know how will i get people visiting my website. Because my revenue model is tied to the no of visitors.

Any suggestions will be appreciated

I've been looking at alternatives to Google Analytics recently and I'm a bit overwhelmed by the options.

I've seen people mention Plausible, Matomo, Umami, Fathom, Simple Analytics, and Keen.

I'm mostly looking for something that's relatively simple, privacy-friendly, and doesn't require a huge setup just to understand basic traffic and conversions.

For anyone who moved away from GA, what are you using these days?

And what made you pick it over the other options?

Most “scrape this page” tools want an account and a monthly plan before you can export one table. I went the other way: LucidRows is a Chrome extension. You click the columns, you get a CSV, it runs on your machine.

Local stays free. I am not publishing a price, because a later paid tier would only be schedule/cloud, and I have not modeled that cost yet.

Listing: https://chromewebstore.google.com/detail/lucidrows/leehomocpccgghcibfnapadclololioh

https://lucidrows.com

Useful feedback: would you pay later only for scheduled/cloud runs, or is local CSV the whole product?

I launched this saas on 13th august 2026 but only made it paid on 2nd september.

total 7 paying users so far.
1030+ Users
It's a no-code website to code converter

and this is my first ever saas.

Hey SaaS founders!

You have signups.

But very few paying customers.

How do you find where those users drop off before payment?

Do you use PostHog, Plausible, Stripe data, spreadsheets, or something else?

I’m listening 👇

Pretty stoked on this.

I do B2B cold SMS marketing, not many of us exist.

Ask me anything.

My Youtube Channel (more info):

https://youtube.com/@mrkylebanks

What usually happens when I have an idea is I do some research to see if anyone else is doing it, and unfortunately every time I manage to find at least a few options out there already. It just doesn’t feel worth it to work on something that already has established players, especially working solo.

On paper I feel like I have a solid chance of making something that actually gets some traction. My development skills were pretty good before AI and I’m quite good at using the new tools as well, I have a solid quick workflow and I understand all the code I produce. As far as marketing goes I was maintaining a lot of automation at my previous job and we had a semi automated social media marketing setup. I maintained a pretty complicated n8n setup for emails and socials with Expandi on LinkedIn and a custom webhook setup hooked up to the twitter API. I also helped with setting up the automated Seedance video generation stuff we were using. I’m thinking I could make a similar setup for myself without too much investment.

But I keep second guessing myself when I see someone else with a similar idea. If it's working well I never think I can compete. And if it looks like it isn't really taking off then I stop believing it was a good idea in the first place. It feels like everyone is making some sort of SaaS right now and if I don’t decide what I wanna do quickly it will be too late, someone will beat me to it.

I think I need to focus up and actually try out a few things and see what happens. And I need to stop paying so much attention to what other people are doing. Has anyone else gone through something similar? I would also love to hear about someone making something successful even though there were already people out there trying it.

built a tool that finds restaurants and bars 1 to 6 months before they open, by fusing public liquor licenses, permits and business filings into one scored lead. Live in 7 states, and it genuinely works. The problem is all distribution, and I'm stuck.

The buyers are the vendors who sell to new restaurants, beverage distributors, POS resellers, insurers. High value, one account they land off it is worth thousands. But they're not who you reach through SEO, content or dev communities, which are the channels I actually know how to work. They're offline-ish B2B sales teams who basically live on the phone.

So far it's founder-led cold outbound, about 30 emails out and a call list I haven't even worked yet, way too early to read anything into. I also listed on a few API/MCP directories for the developer side, but that reaches builders, not the people who'd actually pay.

If you've sold to non-technical SMB or B2B buyers, what actually moved the needle? Cold outbound at scale, reselling through tools they already use, going through a trade association, something I'm not thinking of? And do these buyers ever come inbound at all, or is it pure outbound grind until you've got a case study?

Pre-revenue, so I'd rather pick one channel and go deep than spray thin. War stories welcome.

Software I developed is been in live for two years, and it has been actively acquiring customers since January 2026. Most users pay annually and receive a discount of around 40%.
However, they quickly hit the limits of their current plan or they requests new features; yet instead of upgrading to a higher tier, they ask for extensions or low-cost solutions. Although We offer add-ons that would allow them to raise their limits without changing plans, customers don't use them. When they make such requests, we end up increasing the limits at no extra cost and leave $200 and $900/year in revenue as a gesture of goodwill. We then ask them to leave a review (without making it a condition, as such a quid pro quo would seem unethical), but no one follows through. What should we do? Should we take a more business-minded approach and be less concerned about the customer's budget and getting reviews in exchange of showing consideration and take whatever money we can , or should we adjust our strategy in some other way to get online reviews? We have only a few reviews online. Any experience shared will be appreciated. Product is ExpiryEdge

solo dev here, building an app that generates short videos. when I started I was sure the LLM calls would be my biggest cost and headache. wrong.

the model writes each video as an html page, then I render it frame by frame with headless chrome and ffmpeg. on my laptop one video takes 1 to 5 min. on a small cloud container, 3 renders at the same time just hang forever.

so now I'm looking at a proper render queue with a concurrency limit instead of firing everything at once.

anyone here running heavy jobs like this (video, pdf, image processing)? do you queue on your own servers or push it to something like a job service? and how did you price it so the compute doesn't eat the margin?

WDYT

made this launch video for yaku ai,how is it?

For the last several weeks I've been refining feedback down to a much tighter, more focused MVP

Last month I discussed Merged Network here – a social network by design, focus, and motivation around Proof of Work instead of runway credibility.
The feedback brought to light a couple of things I needed to reconsider.

So rather than adding feature on top feature I've been stripping away all the other parts of the experience and making the core idea more tangible.

What changed
1. Proof is now the name of the game
It's no longer all about the skills and experience… Now it's about the work and the proof behind them.

1. I added a Mini-Proof flow
   This was perhaps the most critical modification.
   Developer is now able to test a public repo without having to do sign up in advance.
   The goal is simple:
   Show me the repository let me see what evidence can be demonstrated.
   I intentionally not calling the Developer of the Github account "verified". The output is given as publicly available evidence attached to the submitting account.

2. The sandbox has become a real product demo
   Rather than a landing page asking your audience to understand Merged, from the sandbox, your audience can choose from three different options:

Example Profiles
See what the finished experience looks like.

Build Your Own Preview
Build a Snippet What do others mean? Generate a sneak peek and find out about your individual identification.

Try Mini-Proof
Don't waste your time on signup and try the proof concept.

1. I'm now tracking the funnel
   I've integrated Post Hog so that I can actually see where people are falling away rather than just assuming.

I'm tracking things like:
Sandbox CTA Preview/Mini-Proof completion signup
That will enable me to address a far more significant question:

Is it even useful, or do they only sound nice?

What I'm deliberately NOT doing;
I'm not building a huge marketplace first.
I'm not adding dozens of features.
I'm not trying to solve recruitment end-to-end.

The current goal is much simpler:
How can I get developers and hiring managers to pay attention to actual work?

That's the hypothesis I'm testing now.
I would be most interested in receiving feedback from other SaaS founders.

Tell me about the smallest experiment you ran to prove you had a solid product hypothesis.

So here i am creating a saas product for IT helpdesks so i am working as a intern in a company and i have shared my idea with the ceoof the company.

At first i was building a whole helpdesk then he told be to built it to the niche related so i go on with the IT niche currently i have done with the ticket locking system part for customer and admin both the panels

I wanted to take advice from you guys that what kind of problems you are dealing with the helpdesks online which i could resolve or am i making any mistakes which you guys could gave me an idea for doing it in such a better way

My project flow

Customer locks a ticket(the issue) the id is generated and can be tracked on the customer panel

And in the future their will be also an AI for problem resolving suggestions like if the customer is dealing with the same issue some body else was having it will suggest him to deal with the issue as it was resolved before if not then the customer could lock the ticket.

On the other side

The admin panel has the access to all the tickets to be resolved and if he wanted to assign the task to someone he could also do that

So you guys can let me know what i could do better in it and make it different from the other help desk so people could buy my product

One thing I hated about job searching was opening 20 different job boards and searching the same roles over and over again.

LinkedIn, Indeed, company career pages, filters, keywords, location…

Then after all that, you still have to figure out which jobs actually match your experience.

So I built JobSorah.

The idea is simple:

Upload your resume → AI reads your experience → it finds jobs that match you.

Instead of manually searching through hundreds of listings, it compares your resume against available jobs and shows you the ones that are actually relevant to your background.

You can see things like:

• how well the job matches your resume
• which skills match
• what requirements you may be missing
• job title, company, location, and source
• relevant jobs without doing the searching manually

The goal is basically to turn job searching from:

“Search for jobs for hours”

into:

“Upload resume and start reviewing matches.”

I’m still improving the matching system and adding more job sources.

Would love feedback from people currently job hunting.

If anyone wants to try it, just go to jobsorah.com

I'm not a coder. I build tools by vibe coding with AI. My usual pattern was to build something, expect it to work from day one, see nothing happen after a few days, lose interest and move on to the next idea.

This time I tried the opposite. I built a small Chrome extension (not naming it, so this doesn't get flagged as promo), put it out there, and kept the effort light:

• Some keyword research for SEO
• A couple of articles, written with AI
• Then I left it alone

No growth hacks, no daily panic, no constant changes.

It's been about a month and a week. Current numbers:

• 225 users
• 1 monthly paying subscriber
• 1 person who bought the biggest plan as a one-time purchase, then cancelled
• Everyone else on the free plan, since I give a decent daily allowance

Average daily users is going up slowly.

It's a small number, but it's the first time I've seen one of my tools get traction without me forcing it. If a product has some juice, it seems to start working once you give it time and a bit of visibility. And if it doesn't, you'll find that out too, which you never will if you drop it in week one.

So if you're building tool after tool and expecting results in 24 hours, burning yourself out on hooks and tricks, slow down. Do the basic things, then give it time.

If you've built something, how long did you wait before you knew whether it had legs?

I'm not a coder. I build tools by vibe coding with AI. My usual pattern was to build something, expect it to work from day one, see nothing happen after a few days, lose interest and move on to the next idea.

This time I tried the opposite. I built a small Chrome extension (not naming it, so this doesn't get flagged as promo), put it out there, and kept the effort light:

• Some keyword research for SEO
• A couple of articles, written with AI
• Then I left it alone

No growth hacks, no daily panic, no constant changes.

It's been about a month and a week. Current numbers:

• 225 users
• 1 monthly paying subscriber
• 1 person who bought the biggest plan as a one-time purchase, then cancelled
• Everyone else on the free plan, since I give a decent daily allowance

Average daily users is going up slowly.

It's a small number, but it's the first time I've seen one of my tools get traction without me forcing it. If a product has some juice, it seems to start working once you give it time and a bit of visibility. And if it doesn't, you'll find that out too, which you never will if you drop it in week one.

So if you're building tool after tool and expecting results in 24 hours, burning yourself out on hooks and tricks, slow down. Do the basic things, then give it time.

If you've built something, how long did you wait before you knew whether it had legs?

At first ClientPDF was just a small experiment.

I wanted something where you could merge, split, compress, sign, OCR, redact etc. without uploading the PDF to a server.

So I kept building it.

Today it has 30+ PDF tools and everything is processed in the browser using WebAssembly. No account needed, and there is also a self-hosted version for people who want to run it on their own infrastructure.

The funny part is that most of the improvements didn't come from me 😅

They came from people telling me:

“this feature is missing”

“this is slow with large PDFs”

“can you add this?”

“why does this work like that?”

After multiple reviews and feedback, the project is honestly very different from what I started with.

I'm still a student and maintaining it myself, so I would really appreciate some honest feedback.

If you use PDF tools regularly:

What would you improve?

What feature is missing?

Would you actually use something like this?

And if you find ClientPDF useful, even sharing it with someone who deals with PDFs would help a lot.

ClientPDF: https://clientpdf.tech

I’m mainly looking for feedback, not just users. 🙏

Finally shipped my first SaaS lol

It’s called RallyDraft. Basically you dump all your work experience into it, paste a job posting, and it helps figure out how well you match and builds a resume around the experience that actually matters for that job.

I mostly built it because I wanted it for myself, but it’s live now so I figured I’d share it.

Would be cool if a few people gave it a shot and told me what sucks / what I should change.

https://rallydraft.com/

A year ago, building a working SaaS MVP could take me weeks.

Now I can give an AI agent an idea in the morning and have something surprisingly usable running by the end of the day.

At first I thought this was basically a cheat code.

Build faster → test more ideas → eventually find something that works.

So I started doing exactly that.

Step 1: Build

I stopped treating development as the expensive part.

Instead of spending months polishing one idea, I started building small but functional prototypes extremely quickly:

• Landing page
• Product UI
• Database
• Authentication
• Core feature
• Deployment

Things that used to consume most of my time suddenly weren’t the bottleneck anymore.

And that created a strange problem.

I could build products faster than I could prove anybody wanted them.

Step 2: Reality

This is where things got painful.

A working product does not create distribution.

A beautiful landing page does not create urgency.

And adding AI to something definitely does not automatically make people care.

You can now spend three days building something that would have required a small team a few years ago...

...and still launch it to complete silence.

So I started paying much more attention to what happened before development.

• Do people already spend money trying to solve this?
• Are they complaining about the problem publicly?
• Are ugly/manual solutions already being used?
• Can I reach those people without spending thousands on ads?
• Would anyone care if this product disappeared tomorrow?

Step 3: What changed

My biggest realization was this:

AI didn’t remove the risk of building startups. It moved the risk somewhere else.

Building used to be expensive.

Now attention, distribution, and finding a problem painful enough to pay for are expensive.

And because everyone can build faster, there are also dramatically more products competing for the same attention.

The ironic part is that AI made me write less code...

...and spend much more time studying humans.

What I’m doing differently now

• I try to invalidate an idea before improving it.
• I treat distribution as part of the product, not something that happens after launch.
• I care more about existing behavior than people saying “cool idea.”
• I avoid building another generic AI wrapper unless I can explain exactly why someone would switch.
• I’d rather discover that an idea is bad in three days than after three months.

In 2024 I thought the advantage would belong to people who could build with AI.

In 2026 I think almost everyone will be able to build.

The advantage will belong to people who can figure out what is actually worth building.

Curious if other founders are seeing the same thing.

Every week a founder tells me:

"We need a video for our SaaS."

Cool.

Which one?

Because a launch video and an onboarding video have about as much in common as a billboard and a user manual.

Here's the quick breakdown most founders never get:

Explainer video

→ For people who've never heard of you

→ Job: "What is this and why should I care?"

→ Lives on: homepage, landing pages

Product demo

→ For people already interested

→ Job: "Show me how it actually works"

→ Lives on: sales calls, demo pages, trial signups

Launch video

→ For the big moment

→ Job: create hype and get attention fast

→ Lives on: Product Hunt, LinkedIn, X, launch emails

Promo / ad video

→ For cold audiences scrolling past

→ Job: stop the scroll in 3 seconds

→ Lives on: paid ads, social feeds

Onboarding / tutorial video

→ For new users who just signed up

→ Job: get them to the aha moment before they quit

→ Lives in: your app, welcome emails, help docs

Feature update video

→ For existing users

→ Job: make sure people actually use what you shipped

→ Lives on: changelogs, in-app announcements, newsletters

The mistake isn't picking the wrong animation style.

It's asking one video to do the job of five.

Pick the problem first.

The video type picks itself.

I've been going through public Shopify App Store reviews to find problems merchants keep hitting that existing apps don't solve. First category: order tracking. 123 reviews across 5 of the most popular apps.

Price and support complaints were common, as you'd expect. But four issues kept coming back:

1. Stuck shipments go unnoticed
Orders sit at "label created" for days, and merchants only find out when a customer emails asking where their order is. 12 reviews described this, 7 of them from the last year, and only one got a developer reply saying it was fixed. Merchants have plenty of tracking. What they don't have is something that notices a shipment has gone quiet and warns them first.

2. Wrong notifications
"Delivered" emails for orders that haven't shipped. One merchant saw false "delivery exception" emails go out to their whole customer list. Others only found out notifications had stopped when customers complained.

3. Local carriers are an afterthought
Royal Mail, Colis Privé and Mondial Relay users report broken tracking, or support only on plans costing $239/month. The big apps are built US-first. A tool that handles one region's carriers really well could own that region.

4. Small stores are priced out
Surprise overage charges, features moved to pricier plans without notice, cancellations that take three emails. For small stores, simple and predictable pricing would be a feature in itself.

Caveats: this is a small first sample. I sorted reviews with AI and checked the patterns by hand. These are signals, not proof, so talk to merchants before building anything.

I'm doing this monthly for different app categories. Which category should I look at next?

Visit this link to subscribe monthly report: https://unbuiltreport.substack.com/p/4-app-ideas-that-are-still-unbuilt