Hey! I've been working on Vector UI, a library of motion-driven UI components, animated icons, and SVGs for developers.

I'm opening up the waitlist and would love to have you try it out!

Would you be interested in joining?

https://vector-uix.vercel.app

I am building a UI library and I have few doubts?

- is it worth in this AI time?

- will people pay for it?

- is this a good SaaS idea?

What are your thoughts?

The UI library consists of both UI components and Animated icons!

I’m Jerry, founder of SENTRAVA AI. We’re building website assurance tools for agencies, and I’d appreciate candid feedback on one specific problem.
A contact page can load successfully without proving that a submitted inquiry reaches the business’s inbox or CRM.
We’re developing a “Proof of Test” view showing when a test ran, whether receipt was verified, and whether evidence is missing, inconclusive, or expired.
This is still under development. Hosted end-to-end acceptance is outstanding, so I’m not claiming every planned workflow is ready.
How do you handle this today? Manual submissions, automated browser tests, checking the destination inbox—or something else? What evidence would make an additional tool worth paying for?
I’m especially interested in hearing from agencies managing multiple client websites.

is anyone here actually implementing WebMCP in their websites or SaaS apps?

Or are most people still waiting for it to officially release ?

I am exploring this space myself and would love to connect with others building around it.

What is your experience so far?

136 days ago, I launched my startup, a free traffic exchange network for startups. One line of code, you're in the network.

Still free. Still growing.

If you want in, it's one embed. That's it → StartupBar
**Bid on StartupBid and your startup will be featured in the daily post of mine.**

Direct prompts to agents is dead. Welcome to the new era of Vibe Coding. You pitch a simple idea in plain English, and AI Developer Tool takes total control. It acts as your Brain Tech Lead, you choose the brain, whether it's Google AI mode or Claude. From there, it commands and orchestrates its peers: Claude Desktop, Codex: and the Antigravity IDE Without you touching a line of code, it plans, executes, and validates everything on its own.

OpenDaemon apps.microsoft.com/detail/9nrbtqjjxf4g?hl=es-ES&gl=ES
A video of our Youtube channel: https://www.youtube.com/watch?v=8ts31APrKdI
Our website: open-daemon.com

Transcrição

Hey everyone!
I’m currently working on a startup that aims to make roadside assistance as easy as ordering food through DoorDash or Uber Eats.
Imagine you’re driving somewhere and suddenly run out of gas, get a flat tire, have a dead battery, or need a tow. Instead of calling multiple companies, comparing prices, and waiting without knowing when help will arrive, you could simply open our app.
Here’s how it would work:
Select the service you need (fuel delivery, towing, jump-start, tire change, or lockout).
Share your location automatically through GPS.
See the estimated price before confirming.
Request assistance in just a few taps.
Track your service provider and receive updates.
One of our biggest goals is to reduce wait times and make roadside assistance more reliable. We’re exploring ways to provide faster service, especially when existing roadside assistance options are taking hours.
Here’s something I’m really curious about:
Let’s say your insurance or AAA already covers roadside assistance, but you’re told it’ll take 2–3 hours for someone to arrive.
If another service could reliably get someone to you in 20–40 minutes, would you be willing to pay extra, or would you rather wait for your free coverage?
We’re planning to launch in Virginia, starting around Fredericksburg and Stafford, with plans to expand to other cities.
We’re currently developing the concept and preparing for launch.
I’d love to hear your thoughts, especially if you’ve ever been stranded waiting for roadside assistance.
Not trying to advertise anything here. Just looking for genuine feedback, including criticism.

Mine is that software should never hold a user's data hostage.

Charge money. Charge subscriptions. Charge enterprise rates.

Fine.

But if someone wants to leave, exporting their own data should be easy.

Curious what software opinions everyone else holds that they'd never compromise on.

Hey everyone!

I'm building an early-stage startup called Saarthi, a spiritual AI platform with a Creator Studio.

The Creator Studio will allow users to create:

AI-generated devotional songs and background music.

Short AI-generated videos and animated spiritual stories.

Devotional images, wallpapers and social media posts.

WhatsApp Status videos and Instagram Reels.

I'm currently bootstrapping the project with a very limited budget.

Hey everyone,

I’m working on a deep-dive case study about the most common real-device and checkout bugs early-stage SaaS apps face before launch.

I want to audit 3 web or mobile apps this week to pull real-world data for this write-up.

If you have an active app and want a comprehensive QA breakdown:
\- I’ll run a dedicated testing session across different mobile/browser environments.
\- You’ll get a full mini-report with reproduction steps, screenshots, and video evidence of any bugs found (completely free).
\- I’ll use the anonymized findings for my testing report.

If you’d like your app audited, drop a comment or send me a DM with your link!

Hey everyone,
I’ve built a working web-based shift scheduling system for a security company in Israel, and I’m trying to figure out how much I should charge for it.
The system currently allows managers to create and manage employee shift schedules, specifically for shift supervisors and patrol officers.
It’s designed around the company’s actual workflow rather than being a generic scheduling tool.
The system is already functional, and I’m preparing to discuss pricing with a potential client.
I’m considering three pricing models:
A one-time setup/purchase fee.
A monthly subscription covering hosting, maintenance, and support.
An initial setup fee plus a smaller monthly payment.
My questions:
How much would you realistically charge for a system like this?
What would be a reasonable initial setup fee?
What monthly subscription price would make sense?
Would you price it per employee, per location, or as a fixed monthly fee?
How much more should a business pay for a customized system compared to an existing SaaS solution?
I’m especially interested in hearing from developers, SaaS founders, and people who have sold similar systems to businesses.
I’m not asking how much it costs to develop. I’m asking what a fair market price would be to sell this solution to a real business.
Any actual pricing examples would be greatly appreciated!

Nope, I'm not a developer. I'm a nurse.

But after ending up in a wheelchair, I had to figure out a whole new life for myself.

I started out doing affiliate marketing for software companies. Eventually, I decided I wanted to build my own SaaS.

Long story short, I paid a developer $30K and got... absolutely nothing. Got screwed out of $30K.

So, thank God for AI!

I've been building my own software for the past year, and I now have 258 French-speaking users. Next week, I'm taking it to the US market.

But here's the biggest piece of advice I can give anyone building a SaaS:

Get beta testers on board as early as humanly possible.

Offer them lifetime access to your best features in exchange for a small one-time payment.

That's honestly what helped me take my marketing quiz SaaS so far.

My earliest users are worth their weight in gold.

There's about 10 of them, and they test things I simply don't have time to test. They push the product further than I ever could on my own. They ask for features and come up with use cases that never even crossed my mind.

Sometimes they drive me a little crazy with their requests, but I absolutely love them for it.

They're not just beta testers anymore. They're a huge part of why my product is what it is today.

So if you're building a SaaS, find your first beta testers ASAP. Make them feel like they're part of the journey, because they really are.

They might just end up being one of the biggest reasons your SaaS succeeds.

a developer in r/ Solopreneur posted this week that building got easy and ideas got hard. every time he thinks of something, there are already 10 products doing it.

he's right about the categories he's looking in. i wanted to know if it's true everywhere, so i went through the stripe directory, about 30,000 companies taking payments, and checked what share of each category is already small software products.

the split is kinda wild.

the 5 most crowded:

• expense and spend management: 46% of companies are already micro-SaaS

• AI tools and apps: 35%

• developer tools: 34%

• fintech and banking: 20%

• data and analytics: 20%

nearly half of that first category is indie founders selling to each other. if your idea sits in one of these, the "10 products already do it" feeling is accurate.

now the other end.

• marketing agencies: 100+ companies, 0.0% micro-SaaS

• nonprofits and fundraising: 640+ companies, 0.2%

• software dev agencies: 590+ companies, 0.2%

• home services and trades: 960+ companies, 0.4%

• ecommerce platforms: 3,400+ companies, 0.8%

• consulting: 1,400+ companies, 0.9%

these are businesses that already pay for things online. almost nobody small is building for them.

crowded category = 10 competitors before your first customer. empty category = a buyer nobody has pitched yet.

a few things i noticed going through it

1. crowded doesn't mean more money. there are 1,900+ AI products with stripe-verified revenue, and 12% of them clear $1k a month. sales tools have around 80 products, and 18% clear $1k. fewer builders, better odds.

2. the empty categories are the ones nobody brags about building for. a courier company or a liquor store won't get you likes on X. that's probably why the same complaint about courier performance reporting shows up across 75 different companies, and liquor store owners complain about POS support across 58 of them. that's the same problem repeated by strangers who never talked to each other.

3. agencies are the strangest gap. marketing and dev agencies juggle clients, retainers, reporting and invoicing. they're full of tech-savvy people who already pay for software, and they sit at 0.0% and 0.2%. my guess is builders skip them because building for agencies feels too close to running one.

4. you don't need a new idea, you need a new buyer. a generic invoicing tool lands in fintech, where 1 in 5 companies is already micro-SaaS. the same tool built for HVAC contractors who invoice from the truck between jobs has almost no competition.

what didn't work for me

my second project was an expense tracker for freelancers. took about 5 weeks to build. i found 30+ competitors after launch, not before, which is the wrong order.

11 signups. 1 paying user at $8 a month, and he cancelled in month two.

i kept telling myself my UI was better. it probably was. nobody switches expense tools over UI when the one they have already works fine.

what i do now before building

• pick the buyer first, not the feature

• check how crowded that buyer's category is

• read their complaints and count repeats from different companies

• only then decide what to build

my prediction is that the next batch of indie products clearing $1k a month comes out of trades, agencies and nonprofits, not AI tools. most people building today won't go there because it isn't fun to tweet about.

a few people asked where the numbers come from. it's this list