How to get feedback on SaaS design from community: what 15 Reddit threads reveal

By Tomáš Cina, CEO at Discury · AI-assisted research, human-edited

Editor's Take — Tomáš Cina, CEO at Discury

What strikes me reading these threads is how often founders blame the template when the real issue is list quality. I've watched this pattern repeat in conversations with SaaS operators: a founder ships a clever, punchy cold-email variant, sees poor replies, and concludes "cold email doesn't work for us," when the ICP was always the bottleneck. Copy only matters once the audience can plausibly care.

The second trap is timing noise vs. founder intuition. Reddit threads are full of "Monday vs Thursday, 10am vs 2pm" optimisation — the real signal is whether the recipient has a reason to open the mail AT ALL. When the trigger (funding round, new hire, feature launch) is fresh, day-of-week noise washes out. When there's no trigger, no send time rescues you.

If I were starting a B2B outbound motion today, I'd spend the first week building a 100-name list I can personally defend as "these people have this specific problem right now," and only then write copy. The founders in this sample invert the order, and Reddit threads amplify that inversion because template talk is more shareable than list-building talk. The most successful founders don't look for "feedback"; they look for "confirmation of pain." If you ask for feedback, you get opinions. If you ask for help with a workflow, you get design requirements.

Solving the comprehension problem to get feedback

Most new SaaS founders face a comprehension problem rather than a distribution problem, as discussed in this r/SaaS thread on user acquisition. If a visitor lands on your site and needs more than 20–30 seconds to grasp the value proposition, they leave, and the founder incorrectly blames the lack of traffic.

"Early users usually aren’t a traffic problem, they’re a comprehension problem. Most new SaaS founders (me included) try to increase acquisition before confirming a new visitor actually understands the value quickly enough." — u/whereusersdrop, r/SaaS thread

Founders often seek feedback by posting in broad communities, but this usually yields low-quality responses. Instead, u/Profbora90 suggests skipping broad "marketing" and focusing on manual founder-led sales until you hit 10 users. By picking one narrow persona and reaching out with a specific observation about their workflow, you gather design insights that are far more valuable than general feedback.

The risk of ignoring this comprehension gap is high; u/Ozone183858 reports in this r/startups thread on app growth that even after building a social video app and securing 100+ downloads, the user reaction remained "neutral" because the core value was not communicated effectively within the interface. Without a clear value proposition, your design is essentially invisible to the user.

Why 15-minute workflow teardowns help you get feedback

The most effective way to validate your design is to offer a 15-minute workflow teardown to people who are already complaining about a specific pain point. In a recent r/SaaS thread on zero-budget marketing, u/its_avon_ outlines a manual 7-day sprint where the primary goal is speed of feedback loops.

"I would run a 7 day manual sprint: pick one micro niche... find 30 people who publicly complained about the exact pain... send a plain text DM with one sentence on why you picked them, then ask for a 15 minute workflow teardown." — u/its_avon_, r/SaaS thread

This approach ensures you are talking to people who have "skin in the game." u/Founder-Awesome notes that finding five people actively complaining about a specific problem is worth more than 50 Product Hunt upvotes. When you engage with these individuals, you learn the exact vocabulary they use, which directly informs your design and messaging.

By helping a user solve a problem in real-time, you build trust that a survey link can never establish. u/simon_mo, discussing agency business in an r/smallbusiness thread on payment patterns, notes that when you set clear boundaries and processes—like requiring 50% upfront—you filter out the "ghosters" who don't value your time. The same logic applies to design feedback: if a user isn't willing to spend 15 minutes discussing their pain, they aren't your target user, and their design feedback would likely lead you astray.

Signal-based outbound to get feedback on the new tack

High-volume cold email is often viewed as a blunt instrument, but when used with intent signals, it becomes a powerful source of design validation. u/BoGeee, who runs an IT staff augmentation business at Eur280K ARR, describes a signal-based approach in this r/Entrepreneur thread on client acquisition.

"The signal-based cold email approach you're describing is exactly what still works when generic blasts are dying. The job change and new hire triggers show you actually looked rather than just scraping a list." — u/erickrealz, r/Entrepreneur thread

This method involves monitoring for job changes, promotions, or new hires to craft hyper-relevant messages. For SaaS founders, this means identifying when a potential user is likely to be re-evaluating their current tooling. Designing for a user who is actively looking for a change is fundamentally different from designing for someone who is content with their current, albeit flawed, workflow.

To scale this, u/BoGeee manages 100 mailboxes and sends 30,000 emails per month, but the key is the 35% gross profit margin that sustains this infrastructure over a five-year period. While a solo founder should not aim for that volume, the principle of "intent-based triggering" remains the most reliable path to valid design feedback. If you identify a user who just started a role and is tasked with "optimizing workflow," they are the perfect candidate to show your design mockups to, as they are actively searching for solutions to justify their new position.

Managing the emotional highs and lows when you get feedback

Emotional ups and downs are a standard part of the startup journey, particularly when validating ideas through social media. u/danainto, in this r/startups thread on emotional resilience, shares the exhaustion of early-stage validation.

"Some days I get good traction and feedback . Some days I feel like I’m wasting time. These emotional ups and downs are draining my energy." — u/danainto, r/startups thread

The community consensus is to "embrace the suck." u/ToddFromLeon reminds founders that 70% of people won't try, and 20% stop too early. The key to successful validation is not necessarily finding the perfect design immediately, but continuing to iterate based on direct, pain-focused conversations. If you are not getting feedback, it is likely because you are asking for "opinions" rather than solving a problem the user is currently venting about online.

For those struggling to get their first 10 users, u/iAmPawanBhatia highlights in this r/SaaS thread on zero-budget marketing that the struggle often stems from treating the product as a "vitamin" rather than a "painkiller." If your design doesn't exist, how much would it hurt the user? If the answer is "not much," you will never get honest design feedback. The most successful founders, such as the one who scaled a loyalty product for restaurants, rely on volume—specifically cold LinkedIn outreach—but always ensure they don't pitch in the first message, instead asking one specific question about a known business problem as noted in this r/SaaS thread on building loyalty.

Audit your design validation in two hours

If your current feedback loop is stagnant, stop sending surveys and execute this two-hour audit to reset your process.

1. Identify the pain source: Use Reddit search to find 10 threads where users are currently venting about the exact problem your SaaS solves. Do not look for "potential" users; look for people who are currently using a workaround they hate.
2. Draft the teardown invitation: Write a plain-text DM template that references their specific complaint. Example: "I saw your post about [pain point] on r/SaaS. I’m building a solution for that and I’m looking for someone to tear down my current workflow. Would you be open to a 15-minute call?"
3. Conduct the 15-minute call: During the call, do not pitch your product. Ask them to walk you through how they solve the problem today. Watch where they get frustrated. If they don't reach a point of frustration, the problem is not painful enough to warrant a new tool.
4. Iterate within 48 hours: Take the top three friction points identified during your calls and update your design mockups in Figma. Reach back out to the same users to show them the fix. If they don't respond, the design was not the primary issue.

Where these threads come from

This analysis draws on 15 r/SaaS, r/startups, r/Entrepreneur, and r/smallbusiness threads. This analysis was compiled with Discury, which aggregates discussion threads across SaaS-adjacent subreddits. The thread selection prioritized comments that provided specific, tactical playbooks over general advice to filter out noise.

discury.io