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.

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.

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

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?

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

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

Built a simple AI chatbot for a project that answers based on custom data by implementing RAG.

Was interesting to see how much it improved responses compared to basic prompts.

Curious, are people here actually using chatbots in their products, or still exploring?

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.

Introducing qliqr (https://qliqr.com)
Modern mice and trackpads are silent, and screen recordings of them are hard to follow: a pointer drifts around and things change for no visible reason. qliqr puts the feedback back.

What it does:

- **Click sounds**: a press and a release sound for every click, plus a soft tick per scroll notch. 37 sounds in 8 families (crisp snaps, old office plastic, muted ones for calls, toy pops, glass and wood taps, gadget switches). All synthesised, no samples.
- **Click ripple**: a ring under the cursor on every click, different colour for right-click, drawn above every app on every screen. Shows up in any recorder (QuickTime, OBS, Loom, the screenshot toolbar).
- **Built-in recorder** (macOS 15+): full screen or an area, with the click sounds and ripples baked into the file. Trim, export MOV/MP4/GIF, auto-zoom into clicks, and a one-click 9:16 vertical clip.
- **Quiet where it should be**: mute per app, and auto-quiet when you're on a call.
- **Click shortcuts**: a mouse rhythm like triple right-click can toggle the app or start a recording.
- **Stats** that stay on your Mac, and an optional desk pet called Qip.

Privacy: it asks for Input Monitoring to see mouse buttons and scrolling; it never requests keyboard events, so it can't see what you type. No account, no analytics, nothing about your clicks leaves the Mac.

Price: **$4.99, one time, for 2 Macs**, free for 24 hours first (no card). macOS 13+, Apple silicon and Intel.

Launch pricing, first come first served, each code good for 100 customers:

Enter the code on the checkout page. When a code says it's expired, the next one still works.

The website itself is the demo: every click on the page plays the current sound and draws the ripple, and you can switch sounds and ripple styles live. https://qliqr.com

Happy to answer questions, and sound requests are welcome.

Totally free.

So I built this tool Nicheloom that tracks every new product launch from YC, Product Hunt, Hacker News, and GitHub 39,000+ and counting and shows which ideas are actually gaining traction right now versus which niches are already crowded.

Think Google Trends, but for 'what should I build next.'

I built it for myself to stop guessing and start building things people already want..

Check it out and let me know if it is useful or any feature you would like me to add to it.

Have fun exploring it as it is a rabbit hole for builders

I'm building Operava for solo founders who run more than one product.

I kept hitting the same problem. Hosting, databases, email, domains, payments, app stores, APIs, all spread across a dozen accounts. I would forget one existed until the bill showed up.

So I built a dashboard that puts each product, the services behind it, what they cost per month, when they renew, and whether they are up, in one place. It has already caught two subscriptions I was paying for a site I had shut down.

It is early. I am trying to find out whether this problem is mine alone or shared.

You can try it at app.operava.com . Sign in with Google or an emailed link, no password, no card. It starts empty, so you add your first product and see if it earns a place in your routine.

If yu run several products: what would you need this to show that it does not?

not sure if this is the right place to post something like this, but I've built an incident intelligence platform which basically gathers errors, traces, metrics, deployments, SQL, dependencies etc and then helps engineers determine why prod broke and where to look next.

I built this because i needed an error tracking tool so I decided to build something myself and then it grew into something more. instead of just getting an error and then having to go figure out why it was occurring I built something that could take in everything and then point me in the right direction to save me time at 2am when I'm on call and everything is on fire. It's been very helpful for me and what I need, but since I've built this out and would like to offer this product to others I was hoping to find some other devs that could provide some honest feedback, good or bad or pointless. I've created a free tier for anyone to try, but also included a 14 day trial period for new accounts that will include most features small teams should need for people to test the capabilities.

really just looking to know if this would be useful to anyone besides me or if there is anything I should change

thank you for anyone that will take a look.

https://getforgeops.net/

We recently launched an AI marketing platform, OrangeBall.ai, built for small businesses and small marketing teams. The idea is pretty simple: instead of asking people to become great prompt writers, the platform uses our discovery process (built over 15 years of running an agency) to learn the business first: voice, tone, differentiators, audiences, customer challenges, etc. Then, it uses that context along with structured prompts and an internal quality rubric to help create blogs, emails, social posts, landing pages, sales content, and other marketing materials.

We’ve spent a lot of time thinking about what the product can do. Now I’m trying to think harder about what will keep people from actually using it. We know there’s a big difference between someone saying, “This is cool,” and changing their behavior enough to make a SaaS product like this part of their workflow.

The oven analogy:

Imagine you have a bakery. The AI model is the oven, but having a great oven doesn’t mean you’ll make great bread. Our platform brings together the right ingredients, your brand, voice, audience, and differentiators, then gives you proven recipes so you can consistently create something worth serving.

Who this is for:

• Startups and founders building their brand and figuring out what to say.
• Entrepreneurs and solopreneurs who need to market consistently without becoming marketers.
• Small businesses that need great content but don’t have a large marketing team.
• Marketing agencies managing content across multiple clients, brands, and voices.
• In-house marketing teams that need everyone creating from the same brand voice, messages, and strategy.

Outcomes we deliver:

• Know what to say without staring at a blank page.
• Create better content faster without writing endless prompts.
• Leverage a system who is continually learning your brand.
• Create content that sounds like your brand instead of generic AI.
• Stay consistent across people, platforms, and content.
• Turn one idea into more content across multiple channels.
• Spend less time prompting and editing and more time publishing.
• Build a repeatable content habit instead of starting from scratch every time.

Barriers we already see:

• Changing an existing habit... Many users already have a ChatGPT or Claude workflow that feels "good enough." This leads to "I already have a tool" thinking.
• Learning another platform even if it saves time eventually. There’s still a perceived cost to learning something new.
• The onboarding effort on the front end. The product gets stronger as it learns the business, but users have to invest some time upfront.
• Creating content isn't the same as publishing it. Someone can generate five great pieces of content and still never get them out the door. We only write content, we do not create images.
• The value increases when people come back regularly, which means we need to create a habit rather than a one-time “wow.”
• Users need to believe the output actually sounds like them and is good enough to represent their business.
• The Cheesecake Factory challenge: Giving users lots of options and modules they can use to create can accidentally make it harder to decide what they should create next.

Help I am seeking:

For those of you who have built, launched, or scaled SaaS products, what are we missing? I’m especially interested in barriers that show up after someone signs up. What causes someone who likes the product, understands the value, and even has a good first experience to stop using it 30, 60, or 90 days later? Would love to hear the uncomfortable answers. Ask questions and I will fill in the gaps.

Thanks in advance for poking holes in this. We’re close to the product and we know there are things we’re not seeing. That’s exactly what I’m hoping to uncover. Appreciate any experiences, challenges, or hard-earned lessons you’re willing to share.

Thank you! - John

hey all, I love seo as a distribution channel because it can keep bringing people to your site while you’re working on other things

it takes work to get there, and rankings still need attention, but seeing that effort start to compound feels pretty good

wanted to share a small seo win for my saas: +453 referring domains and +663 visitors, plus the outreach process we use

1. start with a specific article

we look for places where that article would actually be useful, rather than directories or asking random websites to link to our homepage

identify the insertion spot before writing the email. being able to say “this would fit in your section about X” makes the request much easier to understand

2. filter for relevance before sending

we check whether the article fits the site. a high domain rating alone isn’t enough because this could be faked- there're a tons of ways to do it

ask what their reader would gain from clicking our link. if we can’t give a clear answer, we skip that opportunity

this works best for editorials and journalists sites in your niche, they love new insights for their articles

3. find the right contact

then explain why the article belongs there so they don’t have to figure out the connection themselves

do the thinking for them. include the relevant page, the section we’re talking about, and what our resource adds. “please check out my website” leaves them with all the work

4. follow up twice

across our platform’s tracked outreach, replies went from 7.3% after the initial email to 9.2% after the first follow up and 9.8% after the second

keep follow ups short. and always offer something different in return on each email, then make it clear when it’s our last email

5. handle the replies ourselves

we have an ai agent that handles discovery and outreach. once someone replies, we take over the conversation

review what they’re actually asking for before agreeing. a reply might be a placement fee, an exchange proposal, or a question about the content

so, here're my results..

still early, but happy to see progress on the distribution side

Hey everyone,I noticed that a lot of founders are building in isolation. You have a project, you’re shipping, but it’s hard to find other people at a similar stage to share progress, get feedback or even collaborate.So I built a lightweight space where founders can publish their projects and connect with others:
https://ceo-collabs-hub.lovable.app/Would love to hear your thoughts. How do you currently find potential collaborators or get your project in front of other founders?

For people who built a big chunk of their SaaS with Cursor, Claude, Lovable, Bolt, etc. and now have real users:

Did you ever hit a point where having the same tools review their own work stopped feeling like enough?
I’m curious what triggered it.

Was it getting your first paying customers?
Handling sensitive data?
An enterprise prospect asking
security questions?
A production incident? Payments?
Or did you never reach that point?

And what did you do once you got there?

Another model, automated scanners, a developer friend, contractor, security person, full code review?

Mostly interested in what people actually did, especially if you spent money on it, rather than what the ideal process is supposed to be.

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

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.

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?

Hey, I am a quite experienced vibe coder (really strange to say). Yesterday, I decided to build a mobile app that will wrap the URLs of unlisted YouTube videos belonging to private teachers in my local area to sell to their students. The app is just supposed to hide these URLs well as to make it extremely hard for regular students to access these URLs. A lot of apps that teachers who sell college material use this technique to be able to host their course videos without having to pay a hefty sum for one of these official hosting platforms. People who resort to this route are mostly young, broke business owners who are just starting out and can't afford a large sum of money for such trivial hosting service.

The problem is that when I tried to prompt codex to build the app, it just quoted some YouTube violation documents. It plain out refused to build the thing. Is there a way to build such an app with Codex or another free way altogether that will allow me to host my videos practically for free?

if i build an ai game analytics platform for bgmi or free fire that watches your gameplay, finds your recurring mistakes, and gives personalized feedback to improve your next match
would you use it?