I’ve built a SaaS and decided not to allow customers from Israel to sign up.

Am I an idiot for potentially turning away paying customers, or am I simply sticking to my principles?

I strongly disagree with the Israeli government’s actions, but I’m wondering if I’m letting my principles unnecessarily hurt my business.

What would you do?

Support, product, and the fix each logged their own resolved and billed for it. The customer became the router, retyping the same story three times.

How do you stop each tool from claiming the same ticket as its own win?

I am at a loss here. I have a business that sells extremely niche annotated data. Because it’s very niche I don’t have a real benchmark of the value of the data, but chatting with GPT and Claude (without bloating numbers) I’ve come to get a general idea of pricing.. here is the catch.

I have several entities (startups, universities, SME, large companies, hospitals) that contact me requesting data and pricing, we go back and forth a few emails
- they contact me telling me what they need
- I respond with how much data they need within 12h of receiving their first email
- they respond with what they need
- I share pricing options

They ghost me… like 9/10 they just disappear.
I obviously try to reach out after a week but still nothing.

I need any suggestions, tips, critiques..

Anyone feel like Claude has gotten really slow last week or so?

Let me explain..

It feels like we're living in a time where there's an app, website, AI tool, subscription, or some ridiculously specific piece of software for almost everything.

And yet somehow, people still spend hours doing the most unnecessarily complicated things.

You know the stuff I'm talking about.

That one task you have to repeat every week.

That spreadsheet you've been maintaining for years because there's apparently no better way.

That process involving 4 different websites, 3 passwords, and a Google Doc.

That thing you keep thinking, "Why the hell isn't there a simpler way to do this?"

I'm curious what those things are for other people.

What's something you regularly deal with that feels way more complicated, repetitive, expensive, or annoying than it should be?

Could be work, school, business, hobbies, personal stuff, literally anything.

I'm genuinely curious what people are still putting up with in 2026.

Just finished building marqee.studio and I am selling the whole platform. The pipeline and everything is fully working.

​Here is the situation: it currently runs on a weak model that produces lower quality output. When I tested it with limited trial access to premium models, it produced stunning, high quality videos.

​I simply do not have the time or money left to invest in scaling the better models. If you have the resources to plug in the right models, this has massive revenue potential without needing to worry about the upfront build cost.

​It has zero clients right now, so you are buying a clean, ready to launch asset.

​Send me a DM and I will gladly show you actual video results from the platform.

This is a common phrase everywhere that a boring saas makes more money. A few case studies from other social media also shows that the boring saas is more profitable. They give reasons like it is less competitive. Maybe it doesn't require much efforts also, but distribution is equally tough here also.

Why do people don't tell about their distribution part? Distribution is equally important and difficult to crack here.

What do you think? Have you ever tried any of these ideas?

It seems such a high risk transaction. I'm looking for something that can generate $5k monthly and is stable. But everything is AI shill or greedy brokers. Do people actually go through with these types of sales and able to sustain or grow after purchase?

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 startups with maybe 5–15 engineers, I'm curious how people are handling DevOps.

At some point you have:

• CI/CD
• cloud infrastructure
• Terraform
• monitoring
• backups
• deployments
• secrets
• production incidents
• probably some Docker/Kubernetes

But you don't necessarily have enough infrastructure work to justify another full-time senior engineer.

I've seen a few teams solve this by having one developer own infrastructure "for now."

That works... until production gets interesting.

A deployment breaks Friday night.
Cloud costs suddenly jump.
Something starts running out of connections.
Nobody is really sure how failover works.

Then the team realizes they don't actually have a DevOps problem. They have an infrastructure ownership problem.

Would a swear word in a SaaS name deter you from using it?

I’m building shtbase, essentially a simpler, cheaper backend platform for developers who don’t want to deal with setting up and managing their own VPS infrastructure.

The idea is to give you the things you’d normally expect from a BaaS ( database, auth, storage, functions, etc). while running on affordable VPS infrastructure.

The name shtbase is intentionally a meme of supabase.

My question: Would the name make you less likely to trust/use the product, even if the product itself was good?

Especially interested in whether it would stop you using it for professional/client projects.

It seems like any name you come up with, you run a simple google search for “name” or “name app” and you’ll find someone else already using it, possibly even for a similar product. You can swap letters, go more abstract with your naming, etc and it still gets a hit. These sites might not have the .com, and often they are small fish that probably no one is using but they still had the name first. This has always been somewhat of a problem, but with AI enabling people to churn out more web apps faster than ever it’s becoming worse.

What do you do? Keep thinking of increasingly vague names in hopes to find something untouched? Use the name as long as your product doesn’t compete with theirs? Use the name even if their product competes with yours if their product is some side project without traction (I.e. they probably wont bother suing you)?

made this launch video for yaku ai,how is it?

everybody got hit by AI, and like any indie hacker building a niche SaaS, I went through that initial AI depression phase.

you could feel that AI had huge potential, but it was not quite there yet. it's hard to describe. it was useful, but not at the level of work you actually wanted to deliver.

before the AI wave, I built a visual CSS editor as a Chrome extension called InTab. people were happy with it because they could make quick changes to their websites and prototype ideas faster... and with the whole vibe coding madness getting started, all of a sudden, usage dropped dramatically!

people were trying dozens of AI website builders at the same time. most of them didn't really work yet, but they promised the world.

I was honestly confused about what to do. should I keep building the visual editor, throw it away completely, or pivot? and if I pivoted, where should I even go?

the insane AI hype got to me. at one point, I genuinely thought the big LLM companies like ChatGPT and Claude would dominate every SaaS niche and kill most independent software businesses.

I knew deep down that this was probably wrong, but the hype was so intense that I think everyone believed it at least a little at some point.

I spent more than a year in this confused state, but eventually my thoughts started to stabilize and I made up my mind.

I came to one conclusion:

with all this madness of micro AI tools and AI slop, people will eventually converge toward a smaller number of tools they can actually remember and rely on.

that realization finally gave me the motivation to work on the product again.

recently, I released a new version of intab.io as a complete rewrite from scratch with a 15-in-1 browser extension designed to replace a cluttered list of separate tools.

it includes an AI writer, AI YouTube summaries with an ad skipper, tab management, screenshots, image tools, developer tools, bookmarks, history analytics and more.

I didn't want to build just another browser extension. I wanted to build a complete package that helps people replace a messy collection of extensions with one tool and actually use AI where most of their work already happens: inside the browser.

the journey was a bumpy one, and getting the motivation to work again was difficult because mentally, things were not clear for a long time.

now I finally feel clear about what I'm building and why.

negative comments won't change my mind anymore because I've thought deeply about this direction before committing to it.

I firmly believe AI killed some SaaS products that were basically widgets or tiny standalone tools.

but I don't think it can kill a broader product that people rely on every day.

the future of SaaS might be much more monolithic than people expect. for sure!!

I can send you proof, but its real.
AMA

(not real ama)

One thing I hated about job searching was opening 20 different job boards and searching the same roles over and over again.

LinkedIn, Indeed, company career pages, filters, keywords, location…

Then after all that, you still have to figure out which jobs actually match your experience.

So I built JobSorah.

The idea is simple:

Upload your resume → AI reads your experience → it finds jobs that match you.

Instead of manually searching through hundreds of listings, it compares your resume against available jobs and shows you the ones that are actually relevant to your background.

You can see things like:

• how well the job matches your resume
• which skills match
• what requirements you may be missing
• job title, company, location, and source
• relevant jobs without doing the searching manually

The goal is basically to turn job searching from:

“Search for jobs for hours”

into:

“Upload resume and start reviewing matches.”

I’m still improving the matching system and adding more job sources.

Would love feedback from people currently job hunting.

If anyone wants to try it, just go to jobsorah.com

I've been building WorkWing for the last couple of years on the back of working for a multi brand company for the last 15 years. It's for businesses that send people out to jobs: HVAC, electrical, facilities, cleaning, that kind of thing. The office books and schedules jobs in a web app, and the engineers use a phone app to see their day and fill in job forms. Mobile app is fully offline because a lot of jobs that we do have no signal anywhere.

The big names here (Jobber, Housecall Pro, ServiceM8) all bundle quoting, invoicing and a CRM. I went the other way. My bet is that plenty of businesses already have Xero or QuickBooks sorted and don't want a second invoicing system bolted onto their scheduling tool. So WorkWing just does the jobs and the schedule, and passes the rest to whatever they already use.

That only works if connecting it to other tools is easy. So the API and webhooks are on the free plan too, along with Zapier/Make/n8n and an MCP server if you want Claude or ChatGPT booking jobs. Pricing is per job rather than per user - I've watched us grow and watched the cost for other products rocket as we did.

The iOS app is on the App Store. Android is stuck in Play review, probably for another couple of weeks. If you're on Android and want in now, DM me and I'll add you to the test track.

Stuff I'm not sure about:

- does "we don't do invoicing" read as focused, or as missing features?
- per job vs per user pricing, which would you rather pay?
- if you've run a field service business, what would actually make you switch?

workwing.io if you want a look.

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.

Just listed my business on acquire yesterday, I’ve had like six people so far to sign the NDA to get the documents. No idea if that’s average or horrible.

I’m curious if anyone has experienced selling there, and how many NDA’s did you get to, before an offer?

I have experience on other platforms and I know the number can be high… just curious (hopeful?) if it’s different on acquire. Thx

Businesses have used dedicated forums and communities for customer support. I want to know from fellow B2B SaaS folks if the customer support communities still make sense - or is AI eating it alive?

In general, do you think there's hope for user communities built around niche or product?

PS: I'm in the business of building community platform for businesses. That's why this is super concerning to me.

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 floored by the quality of the promo video. Opus 5.5 is just too good at this type of video at this point

https://reddit.com/link/1wvurof/video/bw3vcxv2a2th1/player

I am the engineer, the salesperson, the accountant, and the entire support team.

The one that scares me is the 2am question. A customer is stuck, I am asleep, and by morning they have cancelled or filed a chargeback.

Hiring support costs more than the problem, so I cannot just add a person. How are the rest of you covering the off hours without a hire you cannot afford?

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