u/Natural-Excuse9069

spent the last weeks trying to reduce the amount of repetitive support emails i deal with every day.

thought this would be mostly solved already because every second startup claims to have “AI support agents” now 😭

but most setups either:
reply with generic garbage,
break the moment context is missing,
or require rebuilding your entire support workflow from scratch.

the thing that finally started making an actual difference for me wasn’t full automation, but rather combining:

docs/knowledge retrieval,
OCR for screenshots,
reply drafting,
confidence scoring,
and human review before sending.

basically removing the repetitive parts without blindly trusting the AI.

cut down a surprising amount of support time already, especially for the same onboarding/setup questions over and over again. would recommend!

day 1:
“wait i actually made a working app??”

day 4:
“honestly i could probably build a startup”

day 9:
debugging something for 6 hours because the AI silently broke authentication across the entire project 😭

the emotional rollercoaster in vibe coding is insane because you alternate between feeling like a genius and a complete fraud every 48 hours.

noticed a lot of business owners try different ai tools but rarely get a structured way to compare them or see what actually works in practice.

most of the time it ends up being:
try tool -> maybe like it -> forget about it -> move on

so i’ve been experimenting with a small platform called Loopbase where people can test tools/products and leave more structured feedback (what worked, what didn’t, would they actually use it in their workflow).

still early, but it’s been interesting seeing how different the feedback gets when people actually try things instead of just reacting to a link.

if anyone here is actively testing ai tools for their business, curious how you currently decide what’s worth sticking with.

i saw someone casually post a “small side project” yesterday and it had auth, payments, ai features, polished UI, mobile responsiveness, analytics, onboarding emails and a waitlist system 😭

like 2 years ago that was basically a startup.

the craziest part is that people are starting to benchmark themselves against this now. you build something genuinely decent and then open twitter/reddit and some guy says “just hacked this together in 6 hours” followed by the most overengineered app you’ve ever seen.

vibe coding really changed the definition of what “small project” means. i guess people have too much money on them to spend on claude tokens.

I think something weird is happening with software right now.

building a product is getting cheaper and faster every month
you can go from idea to working app in like a weekend (even without a team).

but somehow that didn’t make products easier to succeed, it just made the competition invisible.

because now it’s not about whether you can build it,
it’s about whether anyone ever sees it.

you can have a solid micro saas, clean onboarding, good UX, everything works
and still sit at zero users because the internet is already full of similar tools.

so the bottleneck quietly moved:

from engineering
to attention.

and distribution is starting to look like the only real moat again:

audience building, timing, positioning, niche selection
things that used to feel “non technical” are suddenly deciding whether software survives or not.

was tired of people dropping their micro saas in comments and then everything just getting lost or half-read.

so i turned it into a small tool where you can actually submit your micro saas and other founders give structured feedback on it.

it’s called loopbase.

still very early, probably rough in a few places, but already feels way more useful than random “drop your link” threads.

if you’re building something small and want some honest eyes on it, you can try it here (i will also give feedback on a lot of submissions):

loopbase.pro

hope it helps!

one thing i keep noticing:

a lot of micro saas products don’t start with a painful real-world problem anymore, but rather with: “what can i build with this new tech?”

then people spend 3 months searching for users afterwards.

and honestly i get it, because building is fun now. especially with vibe coding. you can spin up a polished product so fast that it feels like progress.

but the dangerous part is that you can now build yourself into delusion way faster too.

clean UI,
landing page,
auth,
payments,
analytics...

and still zero proof anybody actually cares.

i think the people winning right now are the ones spending less time asking “what should i build?” and more time asking “what problem already annoys people enough that they’d immediately try a solution?”
What do you think?

a lot of people can now create pretty impressive apps with cursor/claude/etc without ever really learning how the code works underneath.

and yeah, you could say the apps still work.

which makes me wonder what programming even looks like in 5 years.

because traditionally, reading code was the skill.
now the valuable skill might become:
spotting bad logic,
understanding systems,
knowing when the AI is confidently wrong,
keeping projects from turning into spaghetti after 3 weeks.

i already know people who can ship products but completely freeze when they have to debug manually without ai help.

not judging it btw, i just think we’re watching the definition of “developer” change in real time.

every new AI tool promises “save time” but after trying a bunch of them lately, i feel like we’re slowly recreating the exact same mess SaaS created.

too many tools
too many subscriptions
too many dashboards
too many things that almost overlap

one tool for meetings
one for support
one for email
one for workflows
one for docs
one for CRM enrichment
one for analytics

and suddenly your “AI-powered workflow” is just another fragmented stack duct-taped together.

the weird part is that most of these tools individually do work. I mean that’s not the issue.

the issue is context fragmentation.

every tool knows one tiny piece of the business, but none of them really understand the full picture, so humans still end up stitching everything together manually.

do others feel this too or am I just overloaded with subscriptions at this point?

weird shift i’ve noticed lately

i can build way faster now, no question. spin up features, ship stuff, move on. that part feels insane.

but when i come back to a project a week later, it feels unfamiliar. not messy, like just distant. I understand what it does, but not fully why it’s built that way (you have to keep in mind I'm not a trained software engineer or smthng like that).

and that slows me down more than expected. small changes feel riskier because i’m not 100% sure what breaks.

it’s not classic bad code either. everything looks fine on the surface. it’s more like missing context in my own head.

I'm starting to feel like vibe coding trades speed for a bit less ownership over the system.

Do others feel this or is it just a skill issue on my side?

been testing a few AI support tools lately because I was tired of answering the same questions all day.

went in thinking this is mostly solved by now… it’s not.

for basic stuff they’re fine. simple questions, pointing to docs, that works.

but once things get a bit more real, they struggle.

biggest issues I noticed:

they don’t really get context.
answers are technically correct, but not for that specific user or situation. like edge cases break them easily. billing, account issues, anything slightly unusual almost always lead to an either generic or wrong answer.

After trying out all those tools, I found a solution that fits my business the best:
First, i set up a flexible chatbot on my website, that filters out the most common user questions. Then additionally, an email automation that automatically creates drafts which i can review and send to my customers without even having to open my mails.

The key takeaway is here: I ONLY automate the easy and repetitive questions, not the complex edge cases. This way my solution saves A LOT of time and headaches.

not talking about huge, complex systems,

i mean those small automations you set up in like 30–60 minutes that ended up saving you hours every week.

for me it was a super simple one:
auto-sorting + tagging incoming emails and only surfacing the ones that actually need attention

sounds basic, but it removed a lot of mental noise more than anything else.

So, what are yours?

figured it might be useful to have a thread where people can just share what they’re building and get some honest eyes on it.

if you’ve got a micro saas, drop it here with a short description and what you’re currently struggling with.

and if you’re reading this, don’t just scroll. pick a couple and actually give feedback. what’s confusing, what you’d change, if you’d ever use it, etc...

feels like most of us are building in a bit of a bubble, so this might help a bit.

So, what are you working on? 👇

not talking about the obvious stuff like “write better prompts” or “break tasks down”

i mean the little things you discovered that actually changed your output quality or speed.

for example, stuff like:
changing how you structure context,
restarting chats at the right time,
using different models for different steps,
feeding it your own codebase in a certain way,
tools that are overlooked.

i feel like those small tweaks that aren’t super obvious make a significantly big difference once you figure them out.

like everyone probably has 1–2 of these but nobody really shares them.

so yeah, interested in what yours are,
the kind of thing you only learn after building a lot, not from a youtube tutorial.

everyone talks about what vibe coding can do, but i feel like we don’t talk enough about the limits

like yeah, you can spin up SaaS tools, dashboards, little apps insanely fast now

but where does it actually start to break?

i’ve been wondering about stuff like:
real games (not just simple ones, but anything with real physics / performance)
complex systems with lots of state and edge cases
anything where latency or optimization really matters

feels like vibe coding is amazing for getting something working, but once things get deep or performance-critical, it gets messy fast

also debugging becomes weird
because you didn’t fully write everything yourself, so you’re kind of reverse engineering your own code

not saying it’s bad, just feels like there’s a ceiling people don’t really mention yet

what’s something you tried to build with vibe coding where it just… didn’t hold up?

been talking to a few small business owners lately and it’s kinda crazy how similar the situation is everywhere

no matter the industry, once things start picking up, support turns into the same 5–10 questions over and over again

"how does this work"
"where do i find x"
"did my order go through"

etc

and it’s not even hard questions, just constant interruptions that eat up hours every day

i tried the usual stuff before
faq page -> barely touched
templates -> still feels like copy/paste all day
chatbots -> either too dumb or too complicated to set up properly

recently started using a tool called lumyvo (tried to use Crisp before that but was too expensive for the start) to handle some of the repetitive stuff automatically, mostly because i was tired of answering the same things 20 times a day

it’s not perfect, but it made me realize the bigger issue isn’t “lack of answers”, it’s that customers just don’t go looking for them but rather try to waste your time.

how do you guys handle this?

do you just accept it as part of the business or have you found something that actually reduces the load?

I keep seeing “just build something” here, but not many concrete breakdowns of how to actually get started. So here’s a simple version of what’s worked for me and others. ONLY THE ESSENTIALS.

-> Find a real problem
Don’t try to be clever. Look for something annoying and repetitive people already deal with. The more boring it sounds, the better chance people will pay for it.

-> Validate a bit first
Before building, talk to a few people. Reddit, DMs, niche communities. Ask what they’re doing right now to solve it. If nobody really cares, move on early.

-> Build fast
Don’t overthink tech. You can get really far with tools like Claude/ChatGPT, a simple Next.js app, Supabase/Firebase, and Stripe. The goal is something usable in 1–2 weeks, not something perfect.

-> Put up a simple landing page
Doesn’t need to be pretty. Claude and Codex also work here. Framer, Webflow or even basic HTML is also fine. Just make the value clear and collect emails.

-> Take care of the basics
Set up a business account, hook up Stripe, generate terms + privacy pages (Termly, iubenda, etc.). Don’t get stuck here trying to be perfect.

-> Get your first users manually
Go where your users are and just show the product. No big marketing strategy for now. Talk to people, get feedback. First 10 users are way harder (and more important) than your first 1k visitors.

-> Don’t ignore support
At the start, just use email + maybe a chat widget. Tools like Intercom, Crisp, Tidio are common, but can also be expensive for the start. I would recommend using something like Lumyvo to deal with repetitive questions so you're not answering the same thing all day. Main thing is: stay close to your users.

-> Iterate on reality, not ideas
Don’t build random features. Fix main bugs/problems, improve onboarding, listen to what users actually complain about.

-> Scale later
Once you see people coming back or paying, then think about SEO, content, automation. Before that it’s mostly wasted effort.

That’s pretty much it. It’s honestly never been easier to start a SaaS than now. You don’t need a big budget, just focus on the essentials first.

So, where are you stuck right now?

i can spin up a landing page + product in a week now. that part feels almost unfair at this point.

but getting people to actually show up? completely different game.

posted on reddit -> a few upvotes, no users
twitter -> impressions, no clicks
product hunt -> small spike, then dead again

it’s like the faster i build, the more obvious it becomes that building was never the hard part

what’s actually working for you guys on the marketing side?

are you doing content, cold outreach, seo, something else?
or are we all just launching into the void right now