r/NoCodeSaaS

Drop your startup idea and I’ll check if Reddit has demand for it.

I’ve been testing this with founders over the last few weeks and already checked 200+ startups/ideas.

You can drop your startup URL, app idea, ICP, niche, or the problem you want to solve.

I’ll look for useful Reddit signal: real pain, tool requests, alternative searches, niche conversations, and any sign of buying intent.

I’ll reply with a short public summary.

If there’s enough signal, I can also send a private report link with the full breakdown.

I’ll be honest if Reddit looks like a weak channel for your niche too.

Drop yours below.

reddit.com
u/StockAntique7450 — 2 days ago
▲ 4 r/NoCodeSaaS+1 crossposts

Looking to connect

Hey everyone i'm 15 from Sweden and i've been into this "entrepreneurship" for around a year now, i'm currently building my SaaS, but i'd be happy to connect with people that has similar interests!

reddit.com
u/Only_Spottr — 2 days ago
▲ 2 r/NoCodeSaaS+2 crossposts

From an idea to a full SaaS in 11 days — 130+ hours, 343 commits, 894 tests. Here’s how it happened

From an idea to a full SaaS in 11 days — 130+ hours, 343 commits, 894 tests. Here’s how it happened

I was working on a client project, and the feedback process was honestly a nightmare — WhatsApp messages, screenshots, voice notes… then I’d sit for hours filtering everything, figuring out what’s a bug, what’s a feature request, what’s noise.

So I asked myself:
Why doesn’t the client just open their website after delivery, click on what they want to change, record a voice note or type a message, and send it to me in a structured way?

Sure, tools like this exist.
But I’m already sending all this to a coding agent anyway… so why not take it further?

That’s where the second part of the idea came in:

Image + voice + text + console logs + the exact UI element the client is talking about → all packaged and sent to AI → AI generates a clean prompt → I send it to Antigravity / Codex / Claude / whatever.

And that’s how Tellback was born.

How I actually built it (using Vibe Engineering, not just Vibe Coding)

1. The “Project Brain”
I always need a place that acts like the CTO during product development — something that knows every detail.
I used Claude before, then Hermes Agent became my default.
But for this project, I went all‑in on ChatGPT as the brain.

2. Shaping the idea
I explained the product to ChatGPT, then asked it to interview me — question by question — until the full vision was clear.

3. The project.md file
This file becomes the product’s reference point.
All answers, all decisions, all details.
At this stage, I also choose the infrastructure stack — I went fully Google Cloud for reasons I’ll share later.

4. Turning project.md into Specs
AI coding only works when the AI has exact specs.
No guessing.
Spec‑driven development.
I used Speckit from GitHub and asked ChatGPT to generate the Speckit files based on the project.md.

5. The loop
Brain writes prompts → coding agent executes → I review → send back to the brain → repeat.
Stage by stage until the product is done.

It’s not “easy,” but that’s the core workflow.

Tellback .IO is live

Anyone can sign up now — there’s a free plan for a limited time.
I’d love to hear your honest feedback.

And of course… building is only half the game

Marketing is next.
I’m building a Hermes‑powered agent that will handle:

  • Email marketing
  • LinkedIn, Facebook, Reddit outreach
  • SEO + LLM‑optimized content
  • And more

I’ll share all of that soon.

reddit.com
u/Whole_Watercress_880 — 2 days ago
▲ 152 r/NoCodeSaaS+44 crossposts

I've been building a SQL learning platform for the past few months. It's called QueryCase and I'd love honest feedback

I've spent the last few months building something and I'm finally at the point where I want to share it properly rather than just quietly hoping people find it.

The idea came from a frustration I kept seeing (and feeling myself): SQL tutorials teach the syntax fine but there's never a reason to care about the answer. You filter a table called employees, get a result, and nothing happens. Your brain doesn't bother keeping it.

I wanted to try a different approach. QueryCase teaches SQL through detective investigations. You get a briefing from Chief Fox (our mascot), a real database to query, and a mystery to crack. The JOIN matters when a suspect has an alibi. The WHERE clause matters when you're trying to find who entered the building at 22:13. The SQL is the tool for solving something, not the point in itself.

Here's what's actually in it:

  • A structured learning path across 54 cases, going from Recruit through Rookie, Detective, Senior Detective, and Chief Detective. Each rank has drills and a level exam to pass before you progress.
  • Sandbox mode where you can explore real datasets (IMDB movies, Spotify, sports stats, Steam games) and run whatever you want with no pressure and no mystery attached. Just free exploration against actual data.
  • Everything runs in the browser using DuckDB WASM so there's nothing to install.

I'm a solo developer and this is genuinely early days. I'm sharing here because this community is exactly the kind of people I built it for, and I'd rather get honest feedback now than find out later I've built the wrong thing.

What's missing? What would make you actually stick with something like this versus what you've used before?

querycase.com if you want to take a look.

Any feedback appreciated!

u/conor-robertson — 4 days ago
▲ 1 r/NoCodeSaaS+1 crossposts

Can anyone recommend me the best no-code builders for eCommerce websites? No shopify please

So basically we've been looking for a no code ecommerce builder and shopify is not an option for us. Been searching for a while and can't find anything useful :((( 

reddit.com
u/Ancient_Detail6167 — 3 days ago
▲ 22 r/NoCodeSaaS+6 crossposts

Purchase Order Automation: 5 n8n lessons from a real client build [Workflow Included]

👋 Hey n8n community,

A few of you asked for more detail after my Purchase Order extractor post yesterday. The build looked simple on the surface, but a handful of things bit me along the way. Here are the five that cost me the most time, in case they save you some.

1. Only numbered rows are real articles. The POs had little note lines wedged between items ("2 Box", a location note under a lock, etc). My extraction kept swallowing those into the neighbouring product name, so one row would come out as two items mashed together. The fix wasn't in the workflow at all, it was in the document description I gave the extractor: spell out that only rows with a number in the No. column are real articles, and that unnumbered lines are notes belonging to the row above. That one paragraph cleaned up every merge. Lesson: when a document extraction misbehaves, describe the document better before you touch the nodes.

2. Keep numbers as text until you've checked for empties. Tempting to pull quantity and price straight as numbers. Don't, at least not yet. A missing field comes back as the string "null", and if the field is typed as a number that signal turns into a 0 or a real null and you lose the ability to spot the miss. I keep everything as text, run my checks, then cast to a number afterwards. Clean signal in, clean data out.

3. One helper to catch every flavour of empty. "Empty" is never just one thing. Across the docs I saw real null, the string "null", empty strings, and whitespace. I stopped writing one-off checks and made a single isMissing() helper that catches all of them, then used it everywhere. If a field is missing, the workflow flags it on the form's completion screen with the document name and which field failed, so my friend knows exactly which PO to eyeball instead of trusting the sheet blindly.

4. The Google Sheets checkbox that quietly broke everything. This one nearly broke me. New rows kept landing at the very bottom of the sheet instead of the top empty row. Turns out I'd added a checkbox column with Insert > Tick box, which silently writes a FALSE value into every one of the 1000 cells in the column. The Append node counts those as data, so it always appended below them. If you want checkboxes, add them through Data → Data validation instead, which draws the box without writing a value. Hours lost to a column that looked empty but wasn't.

5. Batch size 1 is not optional here. The extractor node bundles every input item into a single call, so if you hand it two PDFs at once you get one jumbled result. Wrapping it in a Loop Over Items with batch size 1 means each document gets its own clean pass. Small setting, big difference, and easy to miss until your two-file test comes back merged.

The whole thing runs on the easybits extractor node for the actual PDF reading, the rest is stock n8n. If you want to try the Purchase Order extractor yourself, feel free to grab it here:
https://github.com/felix-sattler-easybits/n8n-workflows/blob/c38749a68fd6ea4ae6ebff41789d35cceaacdef1/easybits-purchase-order-extractor-workflow/easybits_purchase_order_extractor_workflow.json

What's the dumbest time-sink you've hit on a build that looked easy? Always happy to hear how other builders tackle this stuff.

Best,
Felix

u/easybits_ai — 3 days ago

Help me Grow ???

I have built a utility tool or a micro saas the only benefits google search results and big traffic. But my website need intial number of request for google to index it and actually appears in the search results. I thought that reddit is the best place to start, but the platform allways remove my post because this is a new account and i only have one karma. So guys if this post hppen to lend to ur fyp (i doubt it) please give me some piece of advice so i can grow my account and validate my idea . Or even some other free strategies to share my idea . I am waiting for ur help ❤️

reddit.com
u/Gol_D_Anas — 4 days ago
▲ 40 r/NoCodeSaaS+7 crossposts

Purchase Order Automation in n8n – extract PO data straight into a Google Sheet [Workflow Included]

👋 Hey n8n community,

Last week I posted a workflow I built for a friend who runs an online shop (find it here). He called me again a few days later with a new headache: he's drowning in Purchase Orders. Every single one gets opened by hand, the data typed into a Google Sheet, and that sheet uploaded into his ERP to update his numbers. Hours a week, pure copy-paste.

So I built him something to kill that step. He uploads the PO PDFs through a simple n8n form, and a structured Google Sheet comes out the other end. He just downloads it and pushes it to his ERP.

How it's set up:

The form accepts multiple PDFs at once, so he can batch a whole stack instead of doing them one by one. Each PO loops through on its own so nothing gets jumbled.

The extraction runs on the easybits Extractor node (@easybits/n8n-nodes-extractor). I set the field structure up in two parts: the header fields that appear once per PO (PO number, PO date, delivery date, mark for, PR number, reference no), plus an articles array for the line items, each holding article name, unit and quantity. That array is the key bit, it gives you one entry per row of the PO table, and I flatten it into one sheet row per article with the header details repeated on each.

Two things I added because real documents are messy:

Error flagging. If any field comes back empty, the completion screen lists which document and which field didn't extract cleanly, so he knows exactly which PO to double-check instead of trusting it blindly.

Document name column. The original filename lands in the sheet next to every row, so if a number looks off he can jump straight back to the source PDF.

Workflow JSON is on GitHub: https://github.com/felix-sattler-easybits/n8n-workflows/blob/c38749a68fd6ea4ae6ebff41789d35cceaacdef1/easybits-purchase-order-extractor-workflow/easybits_purchase_order_extractor_workflow.json

I also made a short video showing how the workflow works.

Anyone else automating document-to-sheet data entry? Curious how you're handling the messy multi-line rows – that was the trickiest part to get right.

Best,
Felix

u/easybits_ai — 4 days ago

Do you design before building or build first and clean the mess later?

Genuine workflow question for no-code SaaS people.

When you’re building something new, do you:

A) Design the main screens first Figma / screenshots / wireframes / templates / AI mockups

or

B) Build first get logic working in Bubble/FlutterFlow/Softr/Lovable/Bolt/etc and then polish UI after

I keep switching and both are annoying.

If I design first, I move slower but the product feels clearer.

If I build first, I move fast but then I end up with a functional app that looks like 7 templates had an argument.

For mobile, build-first feels even worse because bad UI is so obvious.

I’ve been testing a third option:

rough idea → generate 4-6 mobile screens → build from that

Tool I’m using/working on: https://appthetics.com/

It’s not trying to build the SaaS. Just gives mobile screens/mockups so you have something to aim at before you start dragging components around.

What’s your actual workflow?

Not the ideal one. The real one.

u/Dear-Doughnut-1013 — 5 days ago
▲ 2 r/NoCodeSaaS+1 crossposts

Small update: RedditHub is becoming reditHub

Hey everyone,

Quick update: the project I’ve been calling RedditHub is now becoming reditHub.

Nothing major is changing in the idea itself. It’s still focused on helping founders research Reddit conversations, spot repeated pain points, understand context, and turn those signals into better validation work.

The name change is mainly for branding. I wanted something shorter, cleaner, and a bit less generic.

So from now on, I’ll be referring to it as reditHub.

Same idea, cleaner name.

Curious to hear what you think of the new name.

reddit.com
u/GagnoGabin — 4 days ago
▲ 13 r/NoCodeSaaS+7 crossposts

Not because bugs are hard to fix,
but because figuring out what actually happened takes time.

You end up:

  • digging through logs
  • jumping between services
  • trying to piece together the sequence of events

I ran into this enough times that I built something for myself.

It connects to your repo and helps surface what actually caused an issue, instead of manually correlating everything.

Still early, but if you're dealing with messy debugging in production, would love your thoughts:

https://tero.run/

u/_killam — 7 days ago

Built internal ops tools with AI and never hired a developer, how has nobody been talking about this!

Spent way too long thinking this was just how small companies had to run.

At 10 people the setup was whatever the founder threw together early on, sign offs over email, a budget sheet nobody really trusted, onboarding docs that were always like 6 months out of date, plus a couple other things nobody had ever bothered to automate.

Was messing with an AI tool one weekend and somehow ended up building some of this stuff myself, started with a vendor approval flow and a spending tracker, then a new hire checklist so people would actually stop ignoring the onboarding doc.

Took maybe three weeks total for those 4 and the part I didn't expect was how easy it is to just go change something now instead of waiting on whoever used to handle it.

Still haven't figured out how to handle the ones that need more than one person to approve though.

Anyone else end up building this kind of stuff without hiring someone technical?

reddit.com
u/FoundationDowntown72 — 6 days ago

Need ideas to make saas

Hey Reddit community. I am 14th year old and I want to make an saas app and I need an idea that solves actual frustrating problem . Guys pls give me some ideas or problems that you face daily and want to solve

reddit.com
u/bigbucksinbag — 6 days ago

the reason most SaaS fail is not just because of product

i have seen genuinely great SaaS products with zero users. So that explains that great or really problem solving SaaS can still be invisible if marketing is sh*t.

and I can show you mediocre SaaS with thousands. Just because they know how to market the SaaS

the difference is not just product quality. it is almost always one thing. the builder knew exactly where their users already were and showed up there consistently.

What lesson i learned is in this vibe coding and building is easy ERA. The only best advantage you can get is being better at marketing.

Btw I am trying to solve this marketing problem for app/SaaS founders. If you have any tips or anything that you think can make your marketing automated or faster better.lmk in the comments

reddit.com
u/hiten1818726363 — 6 days ago

What I’m learning after building an app and getting basically no users

I’ve been building apps recently and I’m starting to realise the actual building part is not the hardest part anymore.

The hard part is getting anyone to care after you launch.

I’m not posting this to promote anything, I’m not going to link my app. I’m more trying to have an honest discussion because I think a lot of beginners get stuck here.

What I’ve learned so far:

Building first and thinking about users later is probably a mistake.

Cold outreach sounds simple until you send messages and get nothing back.

“Just post content” is not very helpful when you don’t even know who the app is really for.

A bad offer can make a decent product look useless.

It’s hard to tell if the problem is the product, the niche, the messaging, or just not doing enough reps.

For people here who have launched small apps or projects, what actually happened after you finished building?

Did you get users?

Was it mostly silence?

What did you try next?

And what would you tell someone who is at the stage where they can build things, but has no real clue how to get the first few people to use it?

I’ll also summarise the best advice I get in the comments so other people in the same position can learn from it too.

reddit.com
u/Ornery-Whole-8326 — 6 days ago
▲ 4 r/NoCodeSaaS+1 crossposts

Am i the only one who has the fear of spending money?

I'm 15, and I recently got into SaaS and started building my tool. I'm currently doing cold outreach to try to find my first paying users. I recently also got my first paying user, but i don't think he'll keep paying for the subscription. I haven't invested in this at all yet, mostly because i have the fear of spending money, i always overthink on if i should buy this or not if you know what i mean.

So i wanna ask you if you also have something similar, and if somebody knows how to get over this fear?

reddit.com
u/RecordingAromatic693 — 7 days ago
▲ 1 r/NoCodeSaaS+1 crossposts

Is Claude the Killer of SaaS?

I'm currently building my SaaS and soon launching, but i want some people to get early access so that i get some users to use my tool and to get some capital first. Right now i'm doing discord cold outreach and recently got into reddit and X. One guy i dm'd to on discord said that my subscription ($10/month) and tool is not worth buying because for 5 dollars extra you can get claude and it has way more features than my tool, to be honest i don't really know how to react to that, but what do you think?

reddit.com
u/RecordingAromatic693 — 8 days ago
▲ 18 r/NoCodeSaaS+3 crossposts

How did you get your first 10 users?

I recently built a tool that might be pretty useful for some people, but it seems pretty hard getting users. The only thing I’ve been doing is discord cold outreach which made gave me one paying user (who I don’t think is gonna pay again) and 45 waitlist signups.

So my question is how did you manage to get your first 10 users to use your Platform? Which methods did you use, and if it was easy.

reddit.com
u/RecordingAromatic693 — 9 days ago

I’m building RedditHub: a tool to find SaaS ideas from Reddit pain points

Hey everyone,

I’m working on a small SaaS idea called RedditHub.

The idea is simple:
instead of manually scrolling Reddit for hours trying to find complaints, pain points, and SaaS opportunities, RedditHub would help you find them faster.

It would look for things like:

  • repeated complaints
  • people asking for alternatives
  • people saying “I hate using X”
  • users mentioning broken workflows
  • posts where people are already paying for bad solutions
  • problems that appear across multiple subreddits

The goal is not to magically “generate startup ideas”, but to help founders spot real problems people are already talking about.

Would you use something like this to find SaaS ideas?
Or does this sound like another “AI idea generator” that wouldn’t actually help?

Be brutally honest.

reddit.com
u/GagnoGabin — 7 days ago
▲ 5 r/NoCodeSaaS+2 crossposts

Distribution is the whole game, but what about the API costs? is social listening actually in your pipeline?

After almost a year in this space and reading every "I hit $X MRR" post on here, the pattern is obvious: **distribution is the whole game.** Vibe coding an MVP is now a weekend project. The hard part is finding the right conversations at the right time. i found the most believable reddit Saas playbook to be this:

90_days_in_3500_mrr_two_person_team_heres_exactly

So I started doing what this playbook advised: I manually scanned Reddit, LinkedIn, Twitter, and Quora every day looking for posts where someone was complaining about a problem my other product solves. It sort of worked, but it was soul-crushing manual labor.

I looked at the existing tools built for this—Devi AI, F5Bot, Reoogle, Tydal, Leadverse. They each do one or two platforms well, and they are clearly making decent MRR, so the need is there. But after trying their free trials, I noticed a huge limitation: **most of them are just keyword matching algos and a lot of their results were not AI optimised.

So, I started building a 5-in-1 AI social listening + lead finder tailored for SaaS founders, mostly for my own use.

Two hours into designing the landing page and the design of the dashboard, I hit a massive wall: **the API and proxy infrastructure costs. roughly 500$ per month if done rightly** Running continuous semantic scanners across 5 platforms at a meaningful scale made it totally unviable as a personal tool. It *only* makes financial sense if it's a SaaS that spreads the infrastructure cost across multiple users.

**Here's the landing page + dashboard demo I threw together, you can login directly with google button as auth is still inactive:**

👉 **Saasleadsbuddy**

I added a waitlist. The hypothetical price point I'm thinking is **$40–$50/month**. But let's be real: as a developer myself, I usually feel skeptical about any tool costing more than $10–$20/month. On the flip side, running a stable 5-platform scanner is a huge technical and financial task. Single-platform scanner apps are pulling an average of $29/month right now and getting users.

Also, since Reddit (rightfully) hates automated bot spam, I am highly skeptical about adding any kind of "autopilot" auto-reply feature. I think a **human-in-the-loop workflow** (where the app finds the lead, drafts a highly relevant context-aware reply, but *you* click send) is the only ethical way to do this.

Let’s be completely honest here—this isn't a proprietary, million-dollar breakthrough idea. I’ve even seen a few open-source Claude/MCP skills out there (like `last30days-skill`, `Panniantong/agent-reach`, etc.) that can technically hack something like this together if you know what you're doing. Anyone with an LLM can build a basic version of it.

**Honest questions for this community:**

  1. Would you actually pay $40–$50/month for a tool that completely unifies 5 platforms with actual semantic/AI intent matching (not just rigid keywords)? Or do you already have a manual workflow that handles it well enough?

  2. I know distribution isn't *just* social listening—it’s launching on directories, building in public, cold email, paid ads, and deeply understanding your ICP. Do developers actually want a tool that expands into managing those plays too, or should I keep the focus narrow?

I’m not fishing for validation here—I genuinely can't tell if I'm solving a widespread pain point or just my own niche frustration. I need to figure out if this is worth the 1–2 months of brutal engineering required to keep the data pipeline stable.

Would love brutal takes over polite ones. (And no, this isn't a bot post—just a dev who loves building things and needs a check before burning cash on APIs).

reddit.com
u/Ornery-Mind9549 — 6 days ago