hey guys,

A solo developer here, trying to build my second saas , first one unfortunately failed (it was an new idea never done that by anyone else before).

Trying to build the next SaaS web app i was thinking that which is better new Idea or working on existing idea first? can anyone help me with this think, i also tried talking to claude about this but the answer was not satisfying.

Plz any developer who is running a SaaS help me with this thing, Thank you

Hey everyone!

I'm thinking about building my first SaaS product, but I'm struggling to decide which idea to pursue. After exploring different options, I've finally settled on an idea called QuizArena.

The concept is a web-based multiplayer quiz platform where hosts can create quizzes, start live quiz rooms, and invite participants using a room code or link. Participants can join without creating an account, answer questions in real time, and compete on a leaderboard.

The plan is to offer a free tier and a paid plan for teachers, tutors, community organizers, and others who want to host quizzes regularly.

Since this would be my first SaaS project, I'd really appreciate your honest feedback:

• Do you think this idea has real potential to attract paying customers?
• Is the market already too saturated with similar tools?
• Would you recommend starting with this idea, or validating a different one first?

I'm not expecting success overnight. I just want to choose an idea worth investing my time in before I start building.

Thanks for sharing your thoughts!

I'm a solo developer, not a fitness brand. I've been training for a few years and went through most of the popular workout apps out there. They worked, but I kept wishing the workout flow and progress tracking worked a little differently for how I actually train. So I built Liftora.

Here's what makes it different:

• Clean, modern UI — no cluttered menus or dated design, just a simple interface that gets out of your way during a workout.
• Guided workout flow — you move through sets in real time, the app follows your pace instead of just logging after the fact.
• Zero learning curve — open it and start logging your first set in under a minute, no tutorial needed.
• Ready-made programs — new to lifting or don't want to build a routine from scratch? Pick a program and go.
• Exercise videos during selection — don't know the name of a movement? See it in action and know exactly which muscle group it hits.
• Body fat % tracking, not just scale weight — because you can gain muscle and lose fat at the same time and the scale won't tell you that.
• Calorie estimate after each workout — rough, but genuinely useful context if you're managing a deficit or surplus.
• Progress charts that actually answer questions — "is my bench going up?", "how's my volume trending this month?" — without a data dashboard you need a manual for.

Links:

Liftora: Gym & Antrenman Takip Uygulaması - App Store

Liftora: Gym & Antrenman Takip - Google Play'de Uygulamalar

I've been using it daily for my own training and now I want outside eyes on it. If you try it, I'd love to know: Anything confusing or unnecessary?

Je cherche à échanger avec des fondateurs de SaaS qui ont déjà des utilisateurs et des clients payants, pour mieux comprendre leurs difficultés et leurs priorités actuelles.

Est ce que certains seraient partants pour répondre à 2-3 questions à l’écrit ici ou en message privé? Aucun démarchage commercial dans cet échange

Disclosure: I’m building Dreamtune Labs, and provider compatibility is a design concern for me.

When evaluating a different model provider for a SaaS feature, I’d separate two questions: does it produce better answers, and does it still satisfy the application’s contract? A better-looking answer wouldn’t compensate for an invalid tool call or a request that leaves a job stuck.

The small test set I’d want before switching would cover:

1. Output contracts: required fields, types, empty results and the application’s acceptance checks.

2. Tool calls: allowed tool names, validated arguments and what happens when a tool returns an error.

3. Failure handling: rate limits, timeouts, cancellation and whether the job can resume safely.

4. Usage reporting: which model actually ran, whether cost is known or estimated, and how extra attempts are attached to the original job.

I’d keep those checks separate from quality evaluations on representative user tasks. That way, a regression in integration behavior doesn’t get hidden by an improvement in average answer quality.

For developers who have changed providers in production: which test would have caught your most expensive surprise? Do you maintain a provider compatibility suite, or mostly validate the end-to-end feature?

Hey everyone,

I'm a full-stack developer, and I've been working on a project called Retail Analytics System, a SaaS product designed to help businesses analyze retail data and gain useful insights.

I'm considering selling the project rather than continuing to develop and market it myself. It's currently pre-revenue, so it doesn't have paying customers or established recurring revenue yet.

I wanted to ask a couple of questions:

1. Would anyone be interested in acquiring a pre-revenue retail analytics product?
2. If not, where would you recommend selling SaaS products that haven't generated revenue yet?

I'm particularly interested in marketplaces where developers can sell their existing software, source code, and complete projects to entrepreneurs or businesses that want a head start.

I'd also appreciate honest feedback on how to value a project like this and what buyers typically look for before making an acquisition.

Thanks in advance to anyone who shares their experience or suggestions!

I’m building an AI tool that lets you create agents by describing what you want in plain English. They can connect to apps like Shopify, Slack, Gmail, and Google Sheets, while requiring approval for important actions.
I want it to be simpler than tools like n8n and Zapier, with testing, troubleshooting, and clear activity reports.
Would you use something like this? Who would benefit most, and what would make it better than existing tools? How much would you realistically pay?
Honest criticism is welcome—I’m trying to improve the idea. Thanks! 🙏

Hiring a full time GTM engineer early on can be tough to justify where you often end up paying a hefty senior engineering salary for someone to put some scrapers together, fix broken n8n workflows and manage spreadsheet formulas before you even know which outbound channels convert.

This is why outcome based fractional GTM engineering has become such a strong alternative for B2B SaaS teams that need technical distribution infra without permanent payroll overhead.

A standout model here is Scale Intelligence's fractional GTM engineer service where they embed a dedicated GTM engineer directly with your team and the engineer maps your entire addressable market using their TAM mapping engine, wires up live signal monitors across 75+ sources and runs targeted channels like signal based outbound and AI search optimization as a connected mini GTM engine.

Because they operate on an outcome based structure where compensation ties directly to verified qualified meetings defined by your ICP criteria, the focus stays on pipeline generation rather than endless setup sprints.

For lean SaaS teams needing automated pipeline infrastructure that connects to existing CRMs and Slack, bringing in an embedded GTM engineer to build the engine saves months of trial and error.

You finally get your product UI looking good, record a demo, and use it in your launch posts.

Then you ship a few updates.

Now the buttons have moved, the onboarding flow has changed, and half your video no longer matches the actual product.

So you either spend another hour recording everything or keep using an outdated demo.

I'm curious how other indie founders handle this.

Do you re-record your demos after UI changes, record everything manually from scratch, or just leave old videos up?

I'm trying to understand how painful this problem actually is for small SaaS teams.

I built a website that lets people make their own music. For example, they just need to enter the baby name and a few fun facts and it generates a birthday song. I generated some songs for my friends and colleagues and they said they would pay 15 bucks for another one. Currently, I allow new users to generate one 5-minute song for free at first. If they want to generate more, they can spend $1 for one more song and $2 for 3 songs. I won’t mentioned the API I used on the backend because I don’t want to make this look like an ads, but it is really cheap. My friends enjoy building their own music on my website.

However, the problem is almost all users are my friends. I tried to post it on Reddit and TikTok but it just doesn’t work!

Recently I keep questioning myself, do people really need music generator? Is it a real pain point? Any advice would be appreciated.

Billing infrastructure shouldn't be a black box. Built in the open for speed, clarity, and control.

Meet QUANTUM BILLING :

QuantumBilling is a Phoenix LiveView application for Indian business billing: clients, GST invoices, document templates, credit/debit notes, e-way bills, recurring billing, payment links, reports, and compliance reminders.

It uses Elixir, Phoenix, PostgreSQL, and Oban. Business data is being separated into PostgreSQL schemas, with shared accounts and business memberships in `public`.

QuantumBilling: Where precision invoicing meets transparent, open-source engineering.

I've been curious about how other freelancers, indie hackers, and founders find clients, especially when they're just starting out.

There seem to be so many steps involved in getting a client, and I'm wondering which part people struggle with the most.

For example:

1. 1. Finding prospects: Knowing who to reach out to and where to find them.
2. Starting conversations: Figuring out what to say without sounding like you're trying to sell something immediately.
3. Getting replies: Spending time sending cold emails or DMs but barely hearing back.
4. Converting leads: Getting people interested but struggling to turn those conversations into paying clients.
5. Finding time: Managing outreach while also working on projects, building products, or handling an existing job.

I'm curious about your experience.

Which of these is your biggest challenge right now, and what have you tried to do to solve it?

Have you found anything that actually works, or are you still figuring it out?

Would love to hear your experiences and learn from people who've been through this.

Over the last few weeks I have looked at somewhere around 15 to 20 products from people in different subreddits, and I’m ngl the bit that surprised me was that nearly every one of them was stuck in the same place for a reason the person could not see, because the post would say they needed more marketing or needed to run ads, and then I would open the site and within a minute the real problem was staring back at me, the homepage led with a feature every competitor has while the one thing that was actually different was buried three screens down, or the price was nowhere to be seen, so people had to sign up just to find out what it costs, or the whole thing was a javascript shell that google and chatGPT could not even index properly, so no amount of marketing was ever going to fix it and the person had no way of knowing that.

So here is the deal, u drop ur link and one line on who it is for, and then u tell me where u are stuck. Maybe you have no users, or you do have signups but nobody pays, people come and bounce, whatever it is, u do not need to know why, that is the bit I am going to look at, and I will go through it properly and tell u what I think is actually holding it back, because when u have been staring at ur own product for months u lose the ability to see it the way a stranger does and that is exactly what cost me a year and about 4k on my first one.

The $20 is real money out of my pocket and here is what it is for, because a reply in a thread only gets u so far and then u go off and change things and have nobody to check it against, so everyone who posts their product here gets ur first month of Starter on AskSami paid for by me, that is the marketing expert I built after that first product died, it reads ur site and ur numbers itself, tells u why nobody is signing up or paying, and then keeps reading it every time u ship or change something and tells u what to fix next, no card to sign up and nothing to cancel if u decide it is not for u.

If u have numbers, visits, signups, payers, what u spent on ads, stick them in too, rough is fine, because they change the answer a lot, and if u would rather ur product was not sat in a public thread then DM me and I will do the read and sort the $20 there instead.

I will get through as many as I can this weekend, and I would rather u were blunt about where u are stuck than polite about it, being polite is what kept me spending for months.

EDIT: THERE ARE SO MANY POSTS AND SO MANY PEOPLE WANTING HELP, I AM TRYING TO GET THROUGH EACH ONE, PLEASE GIVE ME TIME. I WILL GET TO EVERY SINGLE ONE OF YOU!

Hey everyone! 👋

I launched Citetail, my AEO software, 50 days ago, but still haven't landed a single paying customer.

I'm trying to figure out what's missing. Is it the product, pricing, positioning, or marketing?

I'd really appreciate it if you could check it out and share your honest feedback on what I should improve to get my first paying users.

Hey everyone,

I’m a software engineer. I’ve been working on a side project for a few weeks, and I’m at the point where I need outside opinions before I put months into it.

The idea: a lot of recurring team meetings (weekly syncs, standups, refinement) are people reading out stuff that’s already in Jira or in a Slack thread. So every attendee gets an AI agent that reads their Jira tickets, Slack/Teams threads and GitHub PRs before the meeting. The agents settle whatever can be settled in writing. When they need a human answer, they ping the right person with a quick card. A couple of hours before the meeting, the lead gets one recommendation: cancel, shorten or keep. Decisions get written back to the Jira tickets.

Where I am:

• All the screens are designed
• Landing page is up: https://meetresolve.vercel.app/
• The actual product isn’t built. Realistically that’s 2-3 months of evenings and weekends to get a first version working with Jira + Slack

What worries me:

• It’s a lot of integrations for one person (Jira, Slack, Teams, calendars, GitHub)
• I’m not sure managers would trust an AI telling them to cancel a meeting, even if a human has to approve every decision
• I have no idea if anyone would pay for it (I’m thinking around €8 per user per month)

My questions:

1. Would you or your team actually use this?
2. If you manage a team, what would stop you from paying for it?
3. If you were me, would you keep going or drop it? What would you want to see in the next few weeks before deciding?

Please be brutal. I’d rather hear “this is useless” now than in 6 months.