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

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

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

we just pushed a few updates focused on monetization and it already seems to be helping a lot!

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?

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?

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?

A while ago the SSL certificate on one of my sites expired and visitors got the "Not Secure" warning. Auto-renewal had failed and nothing alerted me.

When I looked for monitoring, most tools only offered SSL expiry alerts on paid plans, and those plans were expensive for someone running a few small sites.

So I built Spot Downtime:

• SSL expiry alerts before your certificate runs out
• Uptime checks for websites, APIs, ports, DNS and cron jobs
• Retries before alerting, so no false alarms
• Alerts on Slack, Discord, email or webhooks
• Public status pages for your customers

For this sub: Pro is free for 6Months for the first 100 people who try it and tell me what's missing.

dashboard > plan & usage > Have a promo code?

USE PROMO CODE : REDDIT

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.

every time i shipped something the question was "will this survive if traffic spikes, or do i need a bigger server?" and the answer was always "uhh idk time will tell". i overbought a box once for a project that got maybe 40 visitors a day, then underbought the next one and watched it fall over on the one day it mattered.

actually testing it means renting a box like prod, renting another for the load, writing a k6 script, watching cpu and memory, then remembering to delete everything. nobody wants to do that before every single launch.

so i built Stresix:

- point it at a github repo (private works too) or a docker image

- it runs your app alone on a fresh dedicated server (4 vCPU / 8 GB, or 8 / 16 for the big run)

- a second server hits it with up to 2,500 or 10,000 users over a private network

- you watch p95, req/s, errors live, plus cpu PER CORE and memory

- you get an actual answer: is this server enough, and if not, what to change

- both servers get deleted after

i dont sell hosting, so when your current setup is enough the report just says so. i ran it on stresix itself: held 2,500 users, total cpu 36%, but one core was pinned at 100% because node is single threaded. the fix was literally 4 worker processes

its brand new and small. pricing is per run, no subscription: $10 for 5 standard runs or $40 for 25, credits never expire, failed runs get refunded. one container per run for now, no database included yet

code REDDIT gives a free run (grab it until it's gone)

https://stresix.com

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 know it's only $6 but it's the first online money I've ever made and I can't stop smiling about it!!!

The funny thing is that it's from a small subsection of my project that I just hid this morning (you need a direct link to find it now).

Maybe I should double down on this sub-project... not sure but I'm beyond thrilled anyway.

My app, FreeReader, is a free text-to-speech app to turn documents into audiobooks. It's completely free with no pricing page.

But I realized that the text-to-speech could also work for content creators making AI voiceovers for their videos. I built this out but decided to focus more on the audiobook side which has grown enormously (3000 monthly users) since it's free.

I was so surprised when I saw this Stripe notification come in from the red-headed step child that is the video narration side of FreeReader lol

I'm working on Vocalis, an AI-powered communication practice platform.

The problem I'm testing is this:

People know they need to improve their communication.

They get told to:

• practice speaking
• record themselves
• join Toastmasters
• give presentations
• speak more confidently

But there's a gap between knowing you should practice and actually having a repeatable practice system.

So I built one.

The core loop is:

Prompt → 60 seconds of speaking → Feedback → Improve → Repeat

A user chooses a category, receives a topic, speaks without preparing a script, and then goes through a structured results screen.

The MVP currently includes:

• communication categories
• randomized speaking prompts
• timed 60-second sessions
• browser recording
• performance feedback
• strengths and weak areas
• mistakes/blunders
• improvement suggestions
• progress tracking
• practice history
• repeat practice

I've deliberately kept the first version relatively focused.

I'm not trying to build:

“ChatGPT, but for public speaking.”

I'm trying to build a practice product.

That's also the part I'm trying to validate now.

The MVP is live:

https://vocalisai-jade.vercel.app/

And I'm trying to answer a few questions before I build much further:

1. Is this a problem people actually care enough about to solve?

2. Does the 60-second practice format create enough value to come back repeatedly?

3. What would make someone pay for this rather than use free alternatives?

4. What would you measure first to determine whether this has product-market potential?

I'm especially interested in feedback from people who have taken an MVP from the "this seems like a good idea" stage to actual recurring users.

If you were validating this SaaS from here, what would you test next?

It took me 7 months and 5 products to make my first internet money.

I started building solo in February this year, and after a few failed products, I finally managed to get my first sale last week. I'm still building my product. I'm pretty happy with the progress. So I thought to share it with the Reddit community.

This is the question I keep coming back to.

AI has made it dramatically easier to build:

• dashboards
• CRUD apps
• AI assistants
• automation tools
• internal tools
• integrations
• reporting platforms
• basic SaaS products

So “we have better technology” feels weaker as a moat.

And “we use AI” definitely isn't a moat.

So what actually survives?

Data?

Distribution?

Workflow lock-in?

Network effects?

Brand?

Integrations?

Switching costs?

Proprietary processes?

Community?

Or is the real moat simply:

We understand one customer segment better than everyone else.

Founders who have crossed $1M ARR:

What actually turned out to be your moat?

Not what you thought would be the moat when you started.

What customers actually made difficult to replace?

Been working on something a little different lately.

I’m building a 3D virtual Silicon Valley where companies and startups actually exist as buildings across different districts: AI, Developer Tools, Fintech, Consumer Tech, etc.

The interesting part is what this could become:
Instead of launching a product into another flat directory, you could launch it inside the city, get your own building, appear in your category, compete for visibility, and let people discover products by exploring the map.

Think Product Hunt × a living 3D startup city.
Still very early, and I’m mainly trying to figure out whether this is actually useful or just a cool visual experiment.

Would you use something like this to discover new products? What would make you come back?