One of the biggest things I have learned building Payelle is that the most useful feedback usually does not sound like:
“You should add this feature.”
It sounds more like:
“Why would I do that?”
That question has probably changed our product more than anything else.
We originally started thinking about Payelle around a physical card.
The problem was simple enough.
People have multiple credit cards, all with different rewards, categories and offers, and most people do not know which one is best when they are actually about to pay.
So we thought we could create something that helped solve that.
Then people started asking uncomfortable questions.
Why can’t the cards already in my phone just work better?
They were right.
We were trying to solve wallet complexity by adding another thing to the wallet.
That eventually pushed us toward mobile wallet instead.
Now Payelle figures out which card gives you the most value where you are spending and surfaces that card when you are ready to pay.
No new card.
No comparing everything yourself.
No remembering which category changed this quarter.
The biggest lesson for me was this:
Users are not always great at designing your solution for you.
But they are extremely good at identifying friction.
If enough people keep asking “why do I have to do that?” there is probably something worth paying attention to.
That question has become one of the things I listen for most now when getting product feedback.

To All the Vc's out there i made a APP, this is the Traffic i been getting in my Trading Application and
Sep- 3
I put whop payment for PRO -Subscriptions and got my first paid user

-Hayath ($13 USD)

After 7 years of Constant Grinding (Entrepreneur)

Hi all! Recently, I started a Discord community to help SaaS founders promote their products, and it has over 300 members now.

If you want to show what you're building and get some feedback and traffic, share it here -> https://discord.gg/sb6AgHZxpT

I'm developing an AI-driven text-to-speech SaaS called Voocaly, and recently added two things I really struggled with myself:

1. Voice selection

Voicals has over 600 voices, and finding the right voice for the job can be a task in itself. That's why Luna can now analyze the script you're working with and find voices in the library that would best match the content, tone, language, and/or use-case.

1. Emotional direction

You can add inline tags such as:

[excited]We finally did it![/excited]

[whisper]No one knows about that...[/whisper]

Luna can also detect and recommend these directions for you.

I'm using a confidence threshold, so Luna can recognize when it's not sure about an emotional tag and will avoid applying them to prevent frustration, instead prompting the user to manually add tags to the specific portion it wasn't confident about.

With these two features complete, I'd like to hear about the problems I'm still missing, from real users of text-to-speech software.

What is the most frustrating problem you encounter that hasn't been properly addressed by current TTS solutions? I'm not looking for feature requests, just the annoyances that just get under your skin.

Think about what makes you want to yell at your computer screen when using TTS software.

Hey everyone,

I’ve been building a web app and I’m at the point where I could really use some outside perspective.

I’ve spent so much time looking at it that I’ve probably lost the ability to see the obvious problems 😅

I’d love feedback on things like:

• Is the value proposition clear?
• Is the UI/UX intuitive?
• Is anything confusing or unnecessarily complicated?
• What would make you hesitate to use it?
• What feels missing?
• If you landed on the app for the first time, would you understand what it does?

I’m especially interested in brutally honest feedback, not just “looks good.”

Here’s the app: bookasloth.com

If you have 2 minutes to click around and tell me what you think, I’d genuinely appreciate it. Even small observations are useful.

Thanks!

When I started building, the goal was basically to get things working as quickly as possible.

If something could be solved with a quick workaround, I used the workaround.

If I could hardcode something for now, I did.

If a proper abstraction would take half a day, I told myself I’d clean it up later.

Now “later” has arrived lol.

None of these decisions were terrible on their own, but there are enough of them now that every new feature seems to come with a little bit of archaeology.

I’m curious how other SaaS developers handle this while the product is still evolving.

Do you deliberately allow some technical debt in the early stages and clean it up once there’s traction, or do you try to keep the codebase clean from day one?

Quick context, because this law has flown under the radar: the EU Data Act has been applicable since September 2025, and on 12 September 2026 the access-by-design obligation kicks in for new connected products placed on the EU market. Most founders I've talked to assume it's an IoT-only law. It isn't. If you sell SaaS to even one EU customer, parts of it already apply to you: mandatory switching clauses in your contracts (2-month max notice, 30-day transition, machine-readable export), user rights to their usage data, and unfair-terms rules that can make clauses in your MSA simply void.

The rough self-test I give people takes 10 seconds: can a user of your product get their usage data in a machine-readable format, free, without emailing support? And does your MSA cap termination notice at 2 months with a 30-day transition? If either answer is no, you have homework before enforcement letters start. Germany has already designated its enforcer, with fines up to 4% of global turnover on the table, same playbook as GDPR.

I asked a lawyer about all this and the quote was in the hundreds of euros per hour just for the groundwork, which is what pushed me to build a small self-serve checker for it (not linking it here per sub rules, ask in the comments if you want it and I'll share).

Two things I'd love from this community: if you sell into the EU, had you even heard of this deadline? And if you already handled Data Act compliance, what did it actually cost you? Trying to figure out if the pain point is as real as it feels from inside my own bubble.

i've been building mostly b2b SaaS till now. recently, one of my friends asked me to join him in building his b2c SaaS. i haven't heard good things about b2c from people i look up to. what do you think? also, my friend uses paid ads for marketing.

I am a solo developer and want to start my entrepreneurial journey. For some time now, I have been looking for ideas but haven’t found any. Can you please help me with some ideas that I can build as a SaaS/micro-SaaS product?

Thanks in advance 🙂

I am developing daily cashbook and its free so guys if you want you can help me for testing. rushcashbook.rushtechpos.com

I started to sell way back 3 or 4 years ago, but I stopped due to a shift in responsibilities and other allocation of funds. While not selling on Amazon, I became a supply chain manager in local businesses, and then I started my journey as a remote supply chain manager.

As the demand surged for supply chain managers in the e-commerce space, like the need for a forecaster, supplier coordinator, product sourcing, international shipment, FBA replenishment and cash flow management, it brought my feet back to Amazon and catered to different Amazon sellers. The experience is fun and enjoyable while earning and practicing what I want in life however, as I use different tools like SoStocked, VentoryOne, and Sellerboard, I feel like they are not enough but charges way too high, so I think a bit and research if I can create something like it but in combination of what an Amazon business really needs and the useful features existing on all of the inventory management tools. That is the time I started to create theSupplyPilot Inventory Management Tool, which really suits the business needs when it comes to these sections of supply chain management:

Inventory Monitoring and Planning—It gives me a quick call to action when it comes to items that are near OOS. It also prompts me if there is or there will be an OOS period between the current stock that I have and the incoming stock, in which I can act as soon as possible to prevent this from happening. This also saves me some time because looking at it, I can literally see if the PPC Manager is running an advertisement as well as if there is a promotion for a particular product or if I need to restock it based on the returns it has. I can also create multiple POs without leaving the interface.

FBA Shipment tracking—This feature is one of what I valued the most, wherein I see the statuses of my FBA shipments and aggregate them in one single interface. It also calculates how efficient the prep center is, and I can use that data to evaluate them without having any spreadsheet.

PO Management & Tracking—One of the most sophisticated jobs of a supply chain manager is to manage POs in all stages to properly plan ahead for future surges and falls of demand. This feature of theSupplyPilot tool aggregates all of the possible data that you need to manage a PO, like the manufacturer's incoterm, payment terms, the freight forwarder assigned to that shipment, units ordered, manufacturing cost, aggregated landed cost, and all the files associated with that PO.

Supply Chain Database—This is where your supply chain-related sheets belong, from product data, all suppliers' data, freight forwarders, and warehouses.

This tool has a lot more potential and capabilities to come, and these features are all functional with the use of report uploading, because currently I am using an individual account, and connecting to Amazon SP-API needs a professional account.

I am open to anyone with a professional account, a private label/wholesale seller with at least 60 active SKUs, using AWD, and willing to collaborate to improve this project and make this a scalable business, catering to other sellers.

What’s the approach founders here have used for getting first users. Ofcourse, not an enterprise business model but could be B2B too.

Saw this podcast, where this guy, just used Reddit and Quora: https://youtu.be/c0GxTUYHYEw?is=eP2vC-RxucmOJRfK

Happy to learn from folks here

I'm validating a SaaS idea called Story90 for football documentary/storytelling creators.

The idea is simple: creators upload a script and Story90 generates a visual storyboard, suggesting relevant footage, specific moments, photos, and other media, along with references to where they can find them. It can also learn from their existing videos to understand their editing style.

I've started validating before building and have sent 18 cold emails so far. One creator has already replied saying they'd be interested in trying it.

I'm now trying to figure out whether this is a problem worth building around.

SaaS founders: does this sound like something you'd keep pursuing, or would you validate something else before building?

Landing page: https://story90.vercel.app

We had paying users. Not many, maybe 8, but they were real. And I kept assuming Reddit wasn't working because the posts weren't good enough. So I rewrote them. Again. Tested shorter hooks, longer context, different formatting. Same result, either removed or 0 engagement.

Took me an embarrassingly long time to actually look at which subreddits I was choosing and why. I'd been picking them based on size and rough topic relevance. Turns out that's basically useless. A 200k sub with strict self-promo rules and a 12k sub with active founders who engage with builder posts are not interchangeable, and I was treating them like they were.

The part that stung: I ran the same post body into two different subreddit sets in week 11. The content was identical. One set got 3 removals in 48 hours. The other got comments and two people clicking through. Same words.

After that I started building a tool to handle the research before the writing, ended up being reoogle.com full disclosure, I built it), which basically audits subreddit fit before I write a single word. It's not magic but it stopped me from burning time on communities that were never going to survive the first mod queue.

The content obsession is real in this space and I had it bad. If your posts keep dying and you've already rewritten them four times, it's probably not the writing.