It was just a normal discussion post that somehow ended up hitting around 3.6k views.

No ads.
No SEO.
No fancy launch.

Since that day I’ve been weirdly addicted to trying different Reddit posts just to understand what actually makes people engage.

Funny thing is:
the posts that worked best for me barely tried to sell anything.

Has anyone else here had random Reddit posts bring unexpected traffic before?

Stamped is a community driven platform built to help people discover incredible iOS apps before they disappear into the noise. https://stampedios.com

Every year, thousands of genuinely useful apps launch and almost nobody sees them. Not because they lack quality, but because visibility on the App Store is heavily dominated by companies with massive budgets, established brands, and existing audiences. The spotlight keeps circulating around the same names while smaller developers get pushed further and further out of view.

That’s exactly why Stamped was created.

Stamped gives independent iOS developers a place to actually be discovered. Every app includes a full creator profile, community based ratings across five categories, demo content so users can see the experience before downloading, and direct access to the builder through platforms like Discord and Telegram.

The goal is simple: connect users with great apps, and connect developers with the people who genuinely care about what they’re building.

The hook: We gamified the iOS app discovery process. Explore apps, verify votes, earn tickets, and compete for monthly prizes.

Explore the sites and tell us what you think

I've been in software for over 10 years. When AI started getting serious, my first reaction wasn't excitement — it was a low-grade panic. I think a lot of people in this industry know exactly what I mean.

But once I got past the anxiety, I started asking a more useful question: what actually changed?

Here's where I landed, thinking from first principles (Musk-style, strip it down to basics):

Old-school software = features + data. The feature was the product. Data sat quietly in a database, waiting to be queried. The whole development process was built around shipping functionality.

But that model is breaking down. In the AI era, the real asset isn't the feature — it's the knowledge. Every software product should now be built around a knowledge base first. You feed it your domain expertise, your methodology, your data. Then AI uses that knowledge to generate the product and build the experience on top of it. Features become the output, not the starting point.

So the architecture flips. Instead of build features → store data, it becomes:

Knowledge Base → AI Generate & Build → Deliver

I've been calling this the CBD model — Creation → Builder → Delivery.

• Creation: You bring the knowledge. AI turns it into a working app structure in minutes, not months.
• Builder: You refine it — the logic, the flow, the outputs — with AI as your co-pilot the whole way.
• Delivery: You ship it. Every end user gets a personalized, AI-generated result based on that original knowledge.

The diagram above is a real implementation of this — an AI assessment platform built exactly on this architecture. But honestly, I think this pattern applies to almost any software product you're building right now.

The anxiety I felt about AI? It came from thinking AI would replace what I do. The excitement came when I realized it actually replaces the parts I never liked doing — and makes the knowledge I've built over 10 years actually scale.

What's your take — are you still building feature-first, or have you started flipping the model?

https://preview.redd.it/i447n5s42e2h1.png?width=2782&format=png&auto=webp&s=b8c44d49a980e1c2d0dfd48f2435e371fe0d47d3

My saas is no code built on bubble and airtable. When a deal hits qualified in airtable I need to generate a branded pdf proposal with line items, pricing, and custom scope, then email it and log it in hubspot.

Zapier + docsautomator works but I hit task limits and formatting is painful. I also need if then logic for different packages and an approval step for discounts over 15 percent. What are other no code founders using to generate complex docs without writing a single line of backend code?

Hey r/NoCodeSaaS ,

(Looking for feedback)

I'm Matthew, a student founder building an AI interview and presentation assistant. It basically generates speaker notes for you to say in real-time while listening to your meeting. It also solves coding problems too. It's only available for Windows for now.

I'm done with the MVP and website. I'm looking for people who would want to test out the app, bug hunt, and give me some honest feedback. DM me if you're interested!

I came across Overskill through an AI challenge I’m doing because it’s being offered as part of their upsell. From what I can tell, it looks more workflow/app-focused, which is what I’m looking for, but I’m trying to compare it against Base44 so I don’t have to go down another rabbit hole.

Has anyone tried it, looked into it, or is willing to give an honest opinion on whether it’s actually worth considering? I’m mainly trying to figure out if I’m reading the value correctly or if it just looks good from the outside.

Here’s the link so you don’t have to dig for it: [https://www.overskill.com/join?ref=IIBMHBRZ]

No, I’m not an affiliate.

Real story, still painful. Had a great relationship with a client, $50K annual contract. Over 8 months, they made several feature requests across different channels: one in email, two in Zoom chat during calls, one in a phone conversation I didn't write down. I delivered the project. They were furious - I'd missed half their requests. I went back through everything and found them... scattered across 5 different places. They felt unheard and not valued. We lost the contract. The worst part? I HAD the information. I just didn't have a system to capture and track it. Hard lesson: scattered communication tools = lost context = damaged relationships. Now I use a simple practice: After EVERY client interaction (email, call, chat), I spend 2 minutes logging key points and action items in ONE place. Currently using a Notion database. What's your "never again" story that changed how you work?

I'm a solo developer, and I've been building TourKit for the past 3 weeks. Here's an honest breakdown of what I built, what broke, what I learned, and whether I should launch on Product Hunt.

What I built:

TourKit — a lightweight product tour SDK. One script tag, dashboard-controlled tours, works on any stack.

The core idea: most onboarding tour tools are either too expensive, too heavy, or require installing a library. I wanted something you could drop into any website in 5 minutes.

Stack I used:

- Next.js (App Router) — dashboard + docs + landing page

- Supabase — auth, database, row-level security

- Vanilla JS SDK — no framework dependency, bundled with esbuild

- Vercel — hosting and deployments

- Anthropic API (Claude) — AI tour generator for Pro users

**Biggest bugs I hit and fixed:**

1. React 18 StrictMode double injection — SDK was loading twice, causing overlapping tooltips. Fixed with an ID guard on the script tag.

2. localStorage seen flag — completing a tour on / was blocking tours on /dashboard. Fixed by making the seen flags path-scoped (tourkit_seen_KEY_dashboard instead of tourkit_seen_KEY).

3. Client-side navigation — Next.js and React change URLs without reloading. SDK wasn't detecting this. Fixed by exposing a window.TourKit global API and calling TourKit.startFor(pathname) on route change.

4. Demo mode — needed tours to replay on every page in the sandbox without affecting real user seen flags. Fixed with a demo flag that skips localStorage writes entirely.

What I shipped:

- One script tag SDK (HTML, React, Next.js, Vue compatible)

- Dashboard to build and manage tours without redeploying

- URL-based tour triggers (context-aware tours per page)

- Analytics — starts, completions, skips, step drop-off

- Multi-page demo sandbox for testing

- AI tour step generator (Pro feature, powered by Claude)

Current status:

- Fully working and tested across React, Next.js, and plain HTML

- Free plan: 1 project, basic analytics

- Pro plan: $19/month — unlimited projects + AI generator

- Live at: tourkit-phi.vercel.app

My honest questions:

1. What's missing that would make you actually use this?

2. Is $19/month reasonable or too high for a solo-built tool?

3. Should I launch on Product Hunt now or keep building?

Happy to share more about any part of the build. This community has been super helpful watching others build — figured it was time to share my own journey. 🙏

Problem :

A month ago my hostel opened a small gym.

Every evening it was packed with biginners trying to improve themselves, but after noticeing for few days, I noticed something.

Almost nobody actually knew if they were doing exercises correctly.

People copied random YouTube videos, copied the person next to them, or just kept lifting while hoping their form was fine.

There weired part was most of them aren't lazy, they genuinely wanted to improve. They just had no feedback while training.

The idea stayed in my head for days, so I ended up vibe coding my first SaaS around it.

The concept is simple:

You record your exercise, and the system analyzes movement/form and gives feedback so you can understand what might be going wrong.

Still very early.
Still fixing bugs constantly.
Still learning how hard it is to make something people can actually use.

But honestly, seeing an idea go from random observation in a hostel gym to a working product feels surreal.

Attached a small demo video below.

Would genuinely love feedback from builders and fitness people.

https://reddit.com/link/1tijyln/video/6h2pyfsjba2h1/player

I've been reading indie SaaS landing pages all week as research.

The #1 conversion killer isn't design. It's not the CTA color. It's not even the pricing.

It's that the copy sounds like ChatGPT wrote it. Because it did.

And here's the thing — your buyers are founders and developers. They're the most AI-literate people on the internet. They spot it in 3 seconds. The moment they do, trust is gone.

The phrases that kill conversions immediately:

• "Seamlessly integrates with your existing workflow"
• "Unlock the full potential of your team"
• "Revolutionize the way you work"
• "Cutting-edge AI-powered solution"

Every single one of these says: "I described my product to ChatGPT and published whatever came out."

The founders who convert well sound like this instead: "I built this because I couldn't find a tool that did X. It does one thing. It works."

Specific. Honest. Human.

I'm validating a tool that rewrites copy in the founder's actual voice. Testing manually this week — free rewrites for anyone who wants one.

Hey everyone, I know we are all constantly testing new stacks in here, so I wanted to share the exact workflow that finally helped me cross the finish line.

I’m a 26-year-old mechanical engineer, and I just made my first SaaS lifetime sales on my side project. (Full disclosure as per the sub rules: I am the sole founder and creator of the app, Hackamaps). Six months ago, I was juggling my day job and trying to manually learn and type out boilerplate Vite, React, and Supabase code. I was exhausted, moving way too slow, and honestly about to quit. Then I completely changed my approach, leaned into the "vibe coding" movement, and let the AI do the heavy lifting. I stopped acting like a syntax checker and started acting like a director.

Here is the exact "no-code to low-code" pipeline I used to get to my first customers:

Step 1: The UI & Frontend with Lovable I wanted to build a global map for hackers and digital nomads to find hackathons worldwide. Instead of stressing over every single component in Tailwind CSS, I used Lovable. I fed it my vision, and it rapidly generated the beautiful, responsive frontend components I needed. It got me 80% of the way there visually in a fraction of the time. After awhile it became buggy and my senior SWE told me to start from scratch and I took the leap of Faith.

Step 2: Exporting to the IDE & AI Agents Once the Lovable frontend was solid, I moved the code into my IDE. This is where I brought in my AI agents (mostly orchestrating between OpenClaw and NanoClaw). I directed the agents to wire up the complex backend stuff—connecting the Lovable UI to my Supabase database, setting up auth, and writing the logic for the interactive map pins. I barely typed any raw code; I just managed the prompts and the architecture.

Step 3: Focusing on the Customer Because I saved hundreds of hours not fighting with syntax errors, I was actually able to spend my time talking to users, doing marketing, and refining the UX.

The result is a live, functioning app, and a person paid for the membership and also recurring visitors (meaning, simply sticks). It proves you don't need an 80-hour manual coding week to ship a profitable product in 2026. The AI builds the engine; you just have to steer the ship.

For the other solo builders in here: have you experimented with exporting Lovable directly to your IDE yet? What does your AI/No-code stack look like right now for handling the backend?

Building a sales enablement tool (interactive sales proposals with built-in buyer analytics).

Currently DM'ing sales reps (AEs, sales managers and even some head of sales) on linkedin with short + personalised msgs. CTA is a 15min chat but response rate isn't very high (~5%).

Reps that do respond offer really great feedback, it's just been a grind getting enough volume.

Should we continue with the volume play, or have you found alternative approaches that have worked well?

been building something recently and honestly the build part was not that difficult
what caught me off guard was how unpredictable it is to actually get people interested
you can try outreach, posting, different approaches, but results feel all over the place sometimes something simple works, other times nothing lands at all
starting to feel like it is less about what you do and more about when people actually need it
not sure if others here ran into the same thing

so you vibe coded an entire app in two days with zero experience and now you want to go live

iconic honestly respect the chaos

but before you hand hackers a free gift let me save you from yourself real quick

1. surprise you are a business owner now

the second someone uses your app and you touch their data the law wakes up and looks at you

just write a basic privacy policy and pretend you know what you are doing

everybody else is doing the same thing

2. ask ai to fix the mess ai helped you create

the audacity but it works

just type this into your ai tool

review my app as a security specialist and make sure i have strong security headers and a solid baseline security posture

two minutes and you suddenly look like you know things

3. google owasp and act like you knew it already

sql injection xss broken auth these are not fancy words they are just ways your app dies publicly

prompt this

review my app against owasp standards and highlight vulnerabilities

you are welcome

4. you are literally leaking secrets and vibing about it

env keys in frontend too much data in api responses passwords chilling in logs

your app is basically posting its own diary online

prompt this immediately

check my app for any credential or sensitive data leaks in frontend or api routes

5. api key in frontend means everyone owns your api key now

not you everyone

move it server side use a proxy stop trusting the browser with your secrets

prompt this

ensure no api keys are exposed in frontend code or network calls

vibe coding is genuinely amazing and i am not here to gatekeep

but shipping a broken app publicly is a different kind of vibe

drop in comments if you have already been burned i need to feel less alone in this

I'm 19, skipped college, and have been building AI products full time for over a year.

Every single day I use AI. And every single day I hit the same wall.

Stop what I'm doing. Open a tab. Explain my context. Ask my question. Copy the answer back. Return to work. Repeat 30 times a day.

That's not AI working for me. That's me working for AI.

The chat box made sense in 2022. It was the easiest interface to ship. But three years later we're still using the same pattern and nobody has questioned whether it's actually right.

It's not.

The real version of AI doesn't sit in a tab waiting for you to remember to ask it something. It already knows what you're working on. It acts before you ask.

OpenClaw proved people want this. 247k GitHub stars for a tool that deleted inboxes and ran up $3,600 API bills. The demand is real. The execution wasn't there.

So I built Clarko with my brother. It sits in the background of your desktop, sees your screen, hears your audio, and acts without being asked. It already has full context on what you're doing so it helps before you even realize you need it.

The part that matters: everything runs locally on your machine. No cloud. No screenshots sent anywhere. No company seeing your screen. We built it this way specifically because Microsoft Recall showed exactly what happens when you don't. Your data stays yours.

It suggests actions and you approve or decline. You're always in control of what it touches. Over time it learns your workflow and gets smarter about what you actually want handled. One hotkey and you can tell it to do anything inside any app instantly.

We just opened the waitlist at clarko.ai

What would you want an AI like this to handle for you?

I keep seeing people say:

“just build a good product and users will come” 😭

But honestly getting the first real sale feels like a completely different game.

So I’m curious...

What channel actually brought your SaaS its first paying customer?

Was it:

• Reddit
• SEO
• X/Twitter
• cold DMs
• Product Hunt
• TikTok
• YouTube
• referrals
• Discord/Slack groups
• or something random you didn’t expect?

And lowkey I wanna know...

Did it feel repeatable or just pure luck at first? 😅

Feels like everyone talks about scaling... but getting that first Stripe notification is the real final boss.