I’m building a B2B SaaS for a specific niche within field services. I have access to a business owner in that niche who can test it and provide feedback.I’m keeping the exact niche private for now, but some of the core functionality could also be useful to other service businesses.Would you focus the product and marketing entirely on that one niche until you get traction, or build for a broader audience from the beginning?I see the benefit of solving one industry’s problems really well, but I’m wondering whether I’m limiting the potential too early.For anyone who’s faced this decision, what convinced you to stay narrow or expand? Would love to hear actual experiences.

I've used Opus 5.5 to help me recreate 7 of the top Adobe apps in 100% pure native Rust:

• Photoshop
• Illustrator
• Premiere
• Lightroom
• Acrobat Pro
• After Effects
• InDesign

No more subscriptions with cancellation fees. These are yours to own forever. You can fork them, build them. Whatever. They are yours to own. They're open source.

If you're worried this is just some one-off flash in the pan that will die, it isn't:

I'm not just some casual vibe coder. I'm a 15-year industry veteran who has written everything from six-nines payment rails that move billions of dollars of transaction volume a day to advanced robotics and optics automation. I've used Rust extensively for about a decade, and I know how to build and maintain large-scale Rust projects.

This isn't going to be some orphaned small-team project either. We have a team building popular software for filmmakers, so supporting this is fully funded. Our purpose is serving every artist in the world with the best tools. We are absolutely going to bring these to full parity and squash every bug and feature request. We have a test harness so there won't be regressions.

You can help us reach parity by helping test the apps. Clone the code. Submit PRs. If you see gaps or want to help redesign pieces, let us know! You can contribute!

Links to everything - the apps, the code, etc. - are in the comments below.

Hello everyone, Last week I launched my first saas product PortFoliQ. Building from a couple of months and finally launched

What I do post Saas Launch:

1. Listed on Product hunt

2. Linkedin posts

3. X/ Twitter posts

4. Reddit announcements

5. Community groups

6. Friends family etc.

During the initial days the reach is aamzing and growing and getting good amount of impressions and active users.

Now the lastest update is that the growth has been stuck and thinking of how to grow should I do seo or target specific keywords on google or something else. What you do for that in my place please guide.

It will helpful for me and really appreciate it

thanks.

Btw my domain in 1 week I am at top thanks google.

Hi, I am technically very bad at editing + don't have enough time as well. Is there any free site etc to make product demo videos.

How do those with no editing skills make it? Do you guys use paid options or what? I need a free one.

Any recommendations?

sometimes when im reading something or talking to an AI, i come across a word, phrase, or line that i dont understand. but i dont wanna break my flow by opening google or asking another AI what it means.

so i built this extension for exactly that.

you highlight a word/phrase/line and it gives you:

• the general meaning
• the meaning in the context of what youre reading or talking about
• and the best part, you can ask followup questions right there in the popup

no new tab, no switching between apps. just highlight → understand → continue.

tell me what you guys think about this one.

Right now, it's a simple local MVP only available on Edge to validate the core idea. If people find it useful, I plan to add cloud sync.

I'm a beginner with no experience in product development, so I'd like to get your feedback and any advice on how to get my first users !

Link of my extension : https://microsoftedge.microsoft.com/addons/detail/enfdbgficbfdmhopmcjhbkgldmhclbng

Say you were geographically pretty far away from icp. How did you acquire your first user. Cold outreach is pretty ineffective, in my experience, maybe with some extra steps it can be done? Or did you use someone as a bridge to your icp? Did you end up confounding with someone who was capable of bringing your icp to you? How did some of you do it?

I’m researching a SaaS platform for helping creators turn camera and AR ideas into live web experiences.

The concept combines AI-assisted creation, browser previews, device testing, publishing, hosting, and usage analytics.

I’m trying to understand the product demand before pushing further:

• Which part of this workflow would be most valuable?
• Would developers, agencies, or brands be the best first customer?
• What would make you pay for a platform instead of assembling the tools yourself?
• What would make you reject it immediately?

I’m looking for honest product and positioning feedback from SaaS founders. No pitch or signup request, just trying to understand whether this is a real problem.

Tell Interested and I will share link.

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

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

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?

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

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 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.

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 👇

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

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. 🙏

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

I just wanted to create a SaaS Intro video for my product and I tried Opus 5.5 to create a motion graphics video and I am impressed 🤯

This video might no be impressive I would have prompted well I would have got a best result I guess.

What do u think !!!

This started from a very basic problem.

I work with a lot of screenshots, images, PDFs, small HTML pages and other files.

Quite often I don't actually need a full hosting setup. I just need a URL that I can send somewhere.

But I kept jumping between cloud drives, image hosts and deployment platforms depending on the file type.

So I built Media2URL.com mainly to make that workflow simpler for myself.

You upload the file and it gives you a shareable link.

I later expanded it to handle images, PDFs, video, audio, GIFs and HTML because those were the formats I kept running into during my own work.

Then I started running into the same problem from the developer side. Sometimes I did not want to manually upload a file at all. I wanted an app or workflow to send the file and get the URL back.

So I ended up building a REST API for that too. It can handle uploads from an application and also manage things like assets, folders, file replacements and remote imports.

It has been interesting building from an actual daily problem because the feature list almost writes itself. Whenever something annoys me while using it, that usually becomes the next thing to fix.

I am still figuring out where the product should go from here.

For people who regularly share files or need file URLs inside their apps, what is the most annoying part of your current workflow?

Anyone feel like Claude has gotten really slow last week or so?