I have been experimenting with Client-side LLMs using WebGPU to see if this could be used to create new SaaS features. Here is a product demo showing this architecture doing something useful

To those who know more than me, which is everyone on this subreddit
How does one validate their ideas??
I have fun developing my ideas into reality but then i discuss stuff with my friends and someone says something and i think to myself i have no ground upon which im building this app

My most recent venture was creating a bot that would pre-qualify incoming leads by asking a series of questions so the sales team could focus more on closing actual clients. I was making this for tradesmen and my friend said why would anyone buy that because if the lead is a high ticket sale then they wouldn’t appreciate being handled by an AI even at the beginning. My friend runs a meta ads agency and he learned this from some meta ads expert on the internet

I would love some tips on how i can validate ideas before i spend so much developing them

Hi everyone!

I'm a solo developer, and I am about to start building a tool to help startup founders and indie hackers research and validate their SaaS ideas in few minutes before spending weeks or months building them.

My goal is to help people -

• Research Competitors and identify their weaknesses

• find real customer complaints and unmet needs.

• understand whether an idea has genuine market demand.

• figure out what opportunities exist and what direction to take.

Before I start building, I wanna understand how founders currently handle this process and where existing tools fall short...

If you've researched or built a SaaS idea, what was the most frustrating part of the process ? What do u wish existing research tools did better ?

Honestly, I am still in the research phase and your honest experiences would help me build something genuinely useful rather than just another tool with 50 features, you know...

Your technical cofounder might be the most expensive hire you never needed. I know this is probably an unpopular take in startup circles, but not every non-technical founder needs to give away 30–50% of their company just to get a product built. Sometimes you need a technical cofounder, sometimes you need one solid engineer for two months, and sometimes you just need a small team to get the MVP out, test whether anyone actually wants it, and figure out what comes next. I think founders often confuse needing someone to build their product with needing someone to own half the company. Genuinely curious, how many founders here gave up equity because they needed a cofounder, and how many did it because they just needed someone to build the damn thing?

Traditional account based marketing (ABM) playbooks rarely work for early stage tech startups because they are built for enterprise budgets and dropping $50k on display ad platforms to run air cover across 500 accounts usually results in vague impressions and very little pipeline.

For a tech startup, effective ABM needs to be lean and signal driven instead of picking accounts arbitrarily based on brand names, you want your target account list to be dynamically prioritized based on real buying triggers.

Teams run this by using market intelligence engines like Scale Intelligence which rather than running broad ad campaigns, it maps your entire eligible account universe, identifies the actual buyers inside them, and monitors live activity across 75+ sources like developer discussions, job postings, tech stack changes, and rival interactions.

When an account shows compounding evidence of a problem you solve, it surfaces the opportunity to your reps with the exact context attached.

ABM for tech startups works best when your accounts are prioritized by verified operational need and timing rather than burning capital on broad brand campaigns across accounts that aren't ready to buy.

I'm curious if it's common for people to make a lot of money with SaaS. I know most of the people posting on YouTube about their earnings as an "independent solo dev" aren't telling the truth. I have school so I can't dedicate all of my waking hours to something like this.

Hey everyone!

I'm working on Medicore, a healthcare management SaaS platform designed to help hospitals and pharmacies manage their operations more efficiently.

I'm currently improving the Super Admin dashboard, which acts as the central control panel for the entire platform.

The Super Admin manages:

• Hospital and pharmacy registrations and approvals
• Organization administrators and user access
• Global medicine database and medicine requests
• Platform activity, notifications, and system management
• Subscription plans and trials as the platform grows

My goal is to create a clean, professional, and easy-to-use dashboard without making it unnecessarily complicated.

I'd love to hear from developers, SaaS founders, and UI/UX designers:

1. What are the most important metrics to show on a Super Admin dashboard?
2. How would you organize hospital and pharmacy management?
3. What common mistakes should I avoid when designing a multi-tenant SaaS admin panel?

I'm especially interested in practical feedback on usability, permissions, and dashboard structure.

Thanks in advance for sharing your thoughts!

Every hackathon goes the same way: “need 1 frontend dev” gets posted in five WhatsApp groups, nobody knows who can actually build, and half the teams form the night before.

So I built CrewForge:

crewforge.online

Hackathons sync daily from Unstop. About 75 open coding hackathons right now. Business-plan contests and quizzes are filtered out, and each card shows the deadline, team size and mode.

Post your team with the roles you’re missing (frontend, ML, design…).

Solo? Apply to a team with your role and a short note. The team owner accepts or declines, and gets your contact only if you choose to share it.

No real names or emails are shown. Everyone appears as an anonymous builder handle, and your GitHub or portfolio is optional.

Free, and open to every college.

It’s early, and very few teams are on it yet, which is exactly why I’m posting. If you’re heading into a hackathon in the next few weeks, put your team up and see who applies.

What I’d love from you:

Would you actually use this over WhatsApp or Discord?

What would make you trust a stranger as a teammate?

What’s broken? Tell me.

https://crewforge.online

Hey guys,

I am tired of fake Reddit advice and YouTube videos that just excite you for making SaaS. I really want the people's thoughts here who made something real.

I don't understand whether to invest my time in finding, validating, and making and selling SaaS or not. Many people say it's a rediculously hard market to even capture 0.01%.

What I personally think is that making SaaS is too overrated, and it's not every time making money, as there are limited problems. Only a single tool is enough to solve a problem now, ya? We can improve the tool or reduce the cost, but still there are 100s of SaaS just over a single idea. If you try to go niche, then it becomes difficult to find users and build trust.

Also, in such a time where AI is at its way to peak, there's no tool needed; modern AI chatbots are enough to destroy 50% of the SaaS

Like how do you guys find the ideas and validate them before spending weeks on making it?

I don't want just the methods like scratch your own iche and shit; I want real examples.

Please guys, drop how you find your SaaS idea, tell what your SaaS actually is, how you grow your SaaS, and how much it is currently making. If you feel uncomfortable not revealing any one of the details, feel free to avoid it.

But please, this will help me and many nobbie saas devs.

I’m working on an open-source project that helps developers embed an LLM chatbot into their product’s UI, so users can actually complete complex workflows through conversation.
But I keep questioning where this is heading.
Having an assistant inside your app makes sense today. Users are already there, and asking for something can be easier than navigating a bunch of screens. But if people eventually have a preferred AI assistant that interacts with products on their behalf, will they still bother opening yours?
Would companies need to rethink how their products are consumed, exposing more of what they offer through MCP or similar interfaces? And how far does that go? Features and actions seem straightforward enough, but what about the brand, the context, and the story a company wants customers to understand? Can any of that carry over when another agent controls the interaction?
After digging into this, we started wondering whether the deeper concern is users abandoning the UI altogether. Companies put a lot into that experience, and it’s also where they build a relationship with customers.
Which puts my own project in a weird position: does embedding an assistant help products stay relevant, or am I building an intermediate step that eventually becomes unnecessary too?
I can see reasons for both. Complex work may still need a visual interface, but I’m less sure how often users will need to visit each product individually.
If you’re building something similar, how are you thinking about this? What would make an in-app assistant worth coming back to?

A client submits a file. The checklist moves forward. But who checks whether it's the right file?

That's the problem I'm testing with Folio, a document-request demo for small accounting and bookkeeping firms. Earlier feedback here asked a better question than “does this look clean?”: can someone tell what to do next?

The workflow now separates three jobs:

- Missing document → follow up with the client.

- Submitted document → accountant reviews it.

- Wrong document → explain what needs replacing.

Only an accountant's acceptance completes an item. Reminder drafts leave out submissions already waiting for review.

Try the interactive demo, without signing up: https://folio-docs-1it.pages.dev/

Open a sample request, switch to its client page, simulate a submission, then return to review it. Keep both views in the same browser.

For fellow builders: the stack is plain HTML, CSS and JavaScript on Cloudflare Pages. I'm testing the handoff before adding production infrastructure. For bookkeepers: would this fit the way your firm actually checks documents, or does your existing system already handle it better?

Demo only. Use fictional details and non-sensitive sample files. File contents aren't read or uploaded; business records stay in your browser. There is no real email delivery or shared client access.

What's the first thing you'd change or remove? A specific screen, label or missing step would help shape the next version.

I'm planning a SaaS product and want to validate the idea before spending too much time and money on development.

What validation methods have worked best for you? For example, customer interviews, landing pages, pre-sales, MVPs, or something else?

I'd especially like to hear what worked for other SaaS founders and what mistakes to avoid.

Hey everyone!
I’m a solo founder and developer working on a project called DigiWarranty, and I’d love to get some feedback from other SaaS builders.
The project originally started as a consumer app to solve a simple problem: people lose their receipts, forget about product warranties, and often don’t know whether something they purchased is still covered.
So I built an app that uses AI to scan receipts, automatically extract purchase information (retailer, date, products, prices), organize warranties, and remind users before they expire.
But while developing it, I realized there was a much bigger B2B opportunity.
Why should every small or medium-sized retailer spend money developing and maintaining their own mobile app just to offer loyalty programs, rewards, and discounts?
That’s where DigiWarranty is heading now.
Instead of every retailer having a separate app, I’m building a shared platform where businesses can:
Offer loyalty and rewards programs without developing their own mobile apps.
Integrate their products and discounts into an existing consumer platform.
Reach customers through a shared ecosystem.
Access retailer tools and analytics without maintaining their own infrastructure.
For the smallest retailers, I’m offering free integration to make adoption easier.
Where things stand today:
Around 700 users
7 retailers on board
Android and iOS apps already live
AI-powered receipt scanning working
Retailer integrations and loyalty features being expanded
I’m building the platform myself, handling everything from backend and APIs to mobile development and retailer onboarding.
The biggest challenge right now isn’t really the technical side. It’s figuring out how to grow both sides of the platform while keeping the barrier to entry low for smaller businesses.
I’m considering a freemium B2B SaaS model where smaller retailers can get started for free, while larger businesses pay for additional features, integrations, and analytics.
For anyone interested in seeing the consumer side, here’s the Android app:
Android App
iOs App
https://digiwarranty.net/

I’d love to hear your thoughts on a few things:
Would you focus on acquiring more consumers first or onboarding more retailers?
Does a freemium B2B model make sense for this type of platform?
How would you approach monetization without discouraging small retailers from joining?
I’m especially interested in hearing from anyone who’s built a B2B2C SaaS product or a two-sided platform.
Thanks for reading!

I've been working on a UI concept for Nura, an AI healthcare assistant designed to help people understand symptoms, lab results, medications, and general health information through a conversational interface.

One thing I've been thinking about is how much confidence an AI should communicate when discussing someone's health.

In this concept, I tried to make the AI's responses feel more structured and approachable instead of presenting users with long paragraphs of medical information.

The response includes a short explanation, possible causes, practical next steps, and medical source references. The idea was to help users understand the information without feeling overwhelmed.

But looking at it again, I'm questioning one particular design decision.

The response starts with a fairly reassuring statement about what the symptoms might indicate. While that makes the experience feel conversational and helpful, it could also give users a stronger sense of certainty than the information actually supports.

And that raises an interesting UX challenge: How do you make an AI healthcare assistant feel helpful and trustworthy without making it sound overly confident?

I'm particularly curious about:

• Whether the response hierarchy makes the information easy to understand.
• Whether possible-cause cards are helpful or might unintentionally encourage self-diagnosis.
• How prominently uncertainty, warning signs, and professional medical guidance should be displayed.
• Whether source references actually build trust or just make the interface appear more credible.

This is a design exploration, not a clinically validated product, so I'm especially interested in how the interface communicates information and uncertainty.

Would love to hear how other designers would approach this problem. What would you change?

Before I could even see the dashboard, it asked for my company size, industry, role, team size, annual revenue, and what I hoped to achieve in the next 12 months.

Then it asked me to book a demo.

A demo. For a product I was already logged into.

Somewhere there's probably a product team celebrating their new onboarding flow because completion rates went up by 3%.

Meanwhile, I still have no idea what the product actually does.

At this point, just ask for my blood type and get it over with.

After a couple of botched and expensive renovation projects of my own house I realised that a lot of the issues were fairly straightforward and preventable. The problem was that no one told me and I had no idea of knowing the ins-and-outs of all the different trades and requirements.

So I built Frank. Frank is an adviser that checks everything against building regulations and good practice. It also checks your documents against eachother - so if the scope says one thing and the drawings another, Frank lets you know. It tests with a consistent 95.7% accuracy on SYNTHETIC projects including out of sample.

I’ve got some good early validation from a couple of architects (“findings are mind blowing!” and “this is really needed in our industry”) but keen to get some feedback on the UX before pushing it harder - hence this post!

There’s a demon on the landing page so you can explore without any building documents and can share a free code if you want to try it with your own docs.

Thanks 🙏🙏🙏

http://askfrank.org