Where to Ask for Software Recommendations Online: 11 Communities That Actually Answer (2026)
Eleven real communities for software recommendations, and why phrasing your ask like a shopping question invites only shills to reply.
Most people post "what tool should I use?" into the void and get three affiliate links and a bot reply. The platform isn't the problem. You're asking a shopping question in a place built for something else, and phrasing it so vaguely that only shills bother to answer.
This guide covers 11 communities where real practitioners actually answer software questions, plus the exact phrasing that separates a thread full of genuine opinions from a thread full of referral links.
| # | Community | Format | Best for |
|---|---|---|---|
| 1 | Reddit (r/software, r/SaaS, niche subs) | Public forum threads | Broad first opinions |
| 2 | Software Recommendations Stack Exchange | Structured Q&A | Precise, constrained asks |
| 3 | Industry Slack communities | Private real-time chat | Practitioner-vetted picks |
| 4 | Discord servers | Private real-time chat | Fast-moving tool talk |
| 5 | Hacker News (Ask HN) | Public forum threads | Technical, dev-heavy crowd |
| 6 | Indie Hackers | Public forum + groups | Founder and bootstrapper picks |
| 7 | Product Hunt | Launch and browse platform | New and trending tools |
| 8 | requestproduct.com discovery guides | Demand-ranked guides | Skipping the ask entirely |
| 9 | Niche vertical forums | Public forum threads | Domain-specific tools |
| 10 | Facebook Groups | Private groups | Peer chatter, high self-promo |
| 11 | LinkedIn Groups | Private/semi-public groups | B2B, professional context |
Why "What Software Should I Use?" Usually Gets Bad Answers
Before picking a venue, it helps to understand why the average recommendation thread is useless.
The three failure modes: shills, affiliate lists, and "just use X" with no context
Open any thread asking for a tool recommendation and you'll usually see one of three replies. The shill, an account that only posts in threads about one product, always with a referral link. The affiliate list, a copy-pasted "top 10" that reads like it was written for a blog, because it was. And the drive-by, someone typing "just use X" with zero explanation of their use case, budget, or team size, which is often true for them and wrong for you.
None of these are malicious exactly. They're just low-effort responses to a low-effort question. Vague asks get vague answers.
Recommendation quality is a demand signal, not a popularity contest
The tools that get recommended most often aren't necessarily the best fit, they're the ones with the loudest marketing budget or the most Reddit karma farming going on in the background. A better filter is demand: is this tool something people are actually requesting, comparing, and switching to, or is it just something that shows up in every listicle because it pays for placement? Guides like best product discovery platforms rank tools by real demand signals rather than SEO reach, which is the same lens worth applying inside a recommendation thread: who's asking for this tool unprompted, and who's just repeating a talking point.
What a good answer actually looks like
A useful reply names the tool, states the specific use case it solved, and mentions at least one limitation or tradeoff. "We moved from Trello to Linear once our engineering team hit 15 people, the automation rules alone were worth the migration, but the free tier disappears fast" tells you more than five one-line drive-bys combined. That's the bar. If a reply doesn't clear it, treat it as noise.
Reddit: The Default First Stop (and How to Not Get Ignored)
Reddit is the highest-volume place to ask, which is both its strength and its weakness.
The right subreddits by use case (r/software, r/SaaS, niche pro subs)
General subs get you broad opinions fast. Niche subs get you people who actually work in the field you're buying for.
| Subreddit type | Example | Good for |
|---|---|---|
| General software | r/software | Consumer apps, general utilities |
| Startup/SaaS | r/SaaS | B2B tools, founder-to-founder opinions |
| Role-specific | r/sysadmin, r/accounting, r/marketing | Tools vetted by people in that exact job |
| Industry-specific | r/legaltech, r/healthIT | Compliance-aware, niche vendor knowledge |
Role and industry subreddits tend to produce better answers than general ones, because the people replying have actually procured software for that exact job function.
Using Reddit search before you post, most questions are already answered
Reddit's built-in search is weak, so search Google with site:reddit.com plus your question instead. Most "what should I use for X" questions have already been asked, often several times, and reading three old threads gives you a faster and more honest answer than posting a new one and waiting. It also shows you which tools keep getting recommended over months or years rather than during one hype cycle, which is a decent proxy for staying power. If you're evaluating a tool from the builder's side rather than the buyer's, the same subreddits are where founders go to find early adopters for your startup, which is worth knowing because some of the "organic" enthusiasm you're reading may be a founder doing exactly that.
How to phrase a post so power users, not marketers, reply
Skip "what's a good CRM?" Instead, state your constraints up front: team size, budget ceiling, must-have integrations, and what you've already tried and rejected. Specificity filters out marketers, because a generic pitch doesn't fit a specific problem. It also filters out low-effort replies, since "just use Salesforce" doesn't answer "we're a 4-person team on a $50/month budget that needs tight integration with our existing invoicing tool."
Stack Exchange & Software Recommendations SE: For Precise, Constrained Asks
When your question has hard requirements, a structured Q&A format beats an open forum.
When a spec-driven question beats a community vibe check
Reddit is good for "what do people generally like." Software Recommendations Stack Exchange is good for "what tool satisfies this exact list of requirements." If you can write your need as a bulleted spec, a self-hosted, GPL-licensed markdown editor with offline sync, for instance, the SE format forces answers to address that spec directly instead of drifting into general opinion.
Writing a question that survives moderation (requirements, must-haves, dealbreakers)
Software Recommendations SE moderates aggressively against vague or opinion-based questions, so structure matters. State what the software needs to do, what platform or budget constraints apply, and what would disqualify an otherwise good answer. Stack Exchange's own guidance on asking good questions applies here even though it was written for the programming side of the network: specificity is what gets your question answered instead of closed.
Reading old answers as a decision archive
Because SE questions rarely get deleted and answers get upvoted over years, old threads function as a decision archive. Searching for a category you're buying in, before posting, often surfaces a thread from years ago with an accepted answer and a comment thread debating the runners-up. That's usually more useful than starting a new thread from zero. This structured, single-best-answer format is a different shape from a review board where every submission stays visible and gets voted on over time, the way feature request board software works, so pick the format that matches whether you want one settled answer or an ongoing list of options.
Slack & Discord Communities: Where Practitioners Actually Live
Some of the best software opinions never touch the open internet.
Finding the invite-only community for your role or industry
Most professional niches now have a Slack or Discord that isn't indexed by Google. Marketers have several, so do indie SaaS founders, so do specific engineering disciplines. You typically find these through a newsletter signup, a conference, or a mention buried in a blog post. It's worth spending twenty minutes searching "[your role] Slack community" or "[your industry] Discord" before assuming public forums are your only option.
Why real-time channels surface tools that never rank on Google
A small, newer tool with no SEO budget can still be the best answer to your question, but it will never surface in search because nobody's written a listicle about it yet. Real-time community chat is where that kind of tool actually gets recommended, because someone just used it last week and remembers the details. This is especially true in categories where the strongest opinions circulate operator-to-operator before they hit public writing, which is a pattern worth knowing about if you're comparing customer feedback tools for startups, a category where a lot of the real signal lives in private channels months before it shows up in a roundup post.
Etiquette: search history, ask in the right channel, report back
Before posting, use the workspace's search to check if the question has already been asked, most active communities have asked every common tool question multiple times. Post in the specific channel meant for tool talk rather than general chat. And after you decide, post a short follow-up saying what you picked and why, it costs you thirty seconds and helps the next person who searches that channel's history.
Product Discovery & Launch Platforms: Browse Instead of Ask
Sometimes the fastest path to an answer is skipping the question entirely.
When browsing beats asking (broad category, no strong constraints)
If your need is broad, "a project management tool," rather than narrow, asking a specific question wastes everyone's time including yours. Browsing a discovery or launch platform and filtering by category gets you a wider view faster than waiting on replies. This is the case for categories with dozens of viable options and no hard dealbreaker driving your search.
Reading launch communities for demand signals, not just newness
Launch platforms like Product Hunt are often read as "what's new," but the more useful signal is what's getting sustained engagement weeks or months after launch, not just on day one. A tool still being discussed and upvoted long after its launch date has more staying power than one that spiked and vanished. If Product Hunt's format doesn't fit your search, several Product Hunt alternatives organize discovery differently, some leaning more toward ongoing usage data than launch-day hype.
Filtering hype from traction
Upvote counts and comment volume can be gamed with launch-day coordination. Traction is harder to fake: recurring mentions across unrelated threads, a changelog that shows continued development, and reviews written well after the launch window rather than clustered in the first 48 hours. Weight those over raw vote counts.
Niche Forums, Facebook Groups & Industry Communities
The oldest format on this list is still, in some categories, the best one.
Vertical forums where domain experts still gather
Categories like photography equipment, home networking, accounting software, and specific manufacturing niches still run dedicated forums that predate Reddit, and the people posting there have often been in the field for decades. These forums are slower and uglier than modern platforms, but the depth of domain knowledge is frequently higher.
Facebook/LinkedIn groups: high signal, high self-promo
Facebook Groups and LinkedIn Groups organized around a profession or industry can produce genuinely useful advice, because membership is tied to a real identity and reputation. The tradeoff is that the same real-identity structure makes them a favorite spot for vendors and consultants to soft-pitch their own tools under the guise of a recommendation.
How to weight advice from a community with skin in the game
Use a simple filter for any community where self-promotion is common:
| Signal | Weight it up | Weight it down |
|---|---|---|
| Poster mentions a specific limitation of the tool | Yes | No |
| Poster's post history is only about one product | No | Yes |
| Recommendation includes a referral or affiliate link | No | Yes |
| Multiple unrelated members independently name the same tool | Yes | No |
| Poster answers follow-up questions in detail | Yes | No |
The same demand-first habit applies here as anywhere else on this list, cross-check an enthusiastic forum recommendation the way you would cross-check any other source, the way a guide like best product discovery platforms ranks tools by actual usage rather than by who posted loudest.
Get Better Answers: Try requestproduct.com for Demand-Backed Recommendations
Skip the shill roulette, start from what people actually use and request
Every venue above still requires you to filter signal from noise after the fact. An alternative is to start from a source that's already filtered for demand: what people are actively requesting and switching to, not what's paying for placement. That's the whole premise behind requestproduct.com's approach to software guides.
How our demand-ranked guides shortcut the search
Instead of asking a question and waiting on replies that may or may not be honest, our guides rank tools by real request and adoption signals, so you get the same outcome as a good recommendation thread without needing to post one, wait for it, or sort shills from genuine users yourself.
Free resources to read next
If you're actively comparing tools right now, start with our breakdown of demand-ranked discovery platforms, then narrow into the specific category you're buying for. Both are free to read and neither requires you to create an account or post a question anywhere.
How to Ask So Real Users Answer (a Copy-Paste Template)
If you do end up posting a question, here's the format that consistently gets real answers instead of affiliate links.
The five things every good request states: job, constraints, budget, stack, dealbreakers
Copy this structure into any of the venues above:
- Job: what task or workflow you're solving for, in one sentence.
- Constraints: team size, platform (web, mobile, self-hosted), and any compliance requirements.
- Budget: a real ceiling, even an approximate one, so replies aren't wasted on tools you can't afford.
- Stack: what you already use that the new tool needs to integrate with.
- Dealbreakers: anything that instantly disqualifies an answer, no matter how good the tool otherwise is.
Before you even post this, it's worth treating the exercise like a mini version of how you'd validate a product idea, define the actual problem precisely before you go shopping for a solution to it. Half the value of writing this template out is realizing what you actually need.
Red flags that a reply is an affiliate plant
Watch for accounts with a post history limited to one product, replies posted within minutes of the thread going up (a sign of alert bots or paid monitoring), links that route through a shortener or obvious referral parameter, and answers that read like ad copy rather than a personal account of using the tool.
Following up and closing the loop so the thread helps the next person
Once you've decided, reply with what you chose, why, and what you passed on. This single habit is what keeps a community's recommendation threads useful over time instead of turning into an archive of unanswered questions.
If You're the Builder Being Recommended (Bonus)
If you build software, these same venues are worth understanding from the other side.
Why appearing in these threads organically beats spamming them
A founder who drops a link every time their product category comes up gets flagged as a shill within a few posts, and the community remembers. A founder who answers genuinely, helps people even when it doesn't lead to a sale, and occasionally mentions their own product when it's a legitimate fit, builds a reputation that produces recommendations without needing to write them yourself.
Turning recommendation venues into early-user pipelines
The same subreddits, Slack groups, and forums where buyers ask for recommendations are where you should be looking to find beta testers for a SaaS. Someone who posts a detailed, specific request for a tool that doesn't quite exist yet, or exists but is missing one feature, is often a better beta tester than a cold outreach list, because they've already told you exactly what they need.
Reading requests as feature and positioning signal
Even when a recommendation thread isn't about your product, the constraints people list, budget ceilings, integration requirements, dealbreakers, are free product research. Patterns that repeat across multiple threads over months are a stronger signal than a single feature request, and they're sitting in public view for anyone willing to read a few dozen threads instead of running a survey.
Frequently Asked Questions
Where is the best place to ask for software recommendations online? It depends on how specific your question is. Reddit is the best general first stop for broad opinions, Software Recommendations Stack Exchange is best when you have a precise spec, and industry Slack or Discord communities are best when you want practitioner-vetted picks that haven't hit the open web yet.
How do I ask for a software recommendation without getting affiliate spam? State your job, constraints, budget, current stack, and dealbreakers up front. Vague questions like "what's a good CRM" attract generic pitches. Specific questions filter them out because a canned pitch usually doesn't fit a specific set of constraints.
Is Reddit or Stack Exchange better for finding software recommendations? Reddit is better for broad, opinion-based questions and for reading a wide range of experiences. Software Recommendations Stack Exchange is better when you have hard requirements and want a structured answer format rather than an open-ended thread.
Are Slack and Discord communities worth joining just to ask about tools? Often yes, particularly in professional niches, because real-time practitioner communities surface newer or smaller tools that haven't built up SEO presence yet. Join communities tied to your actual role or industry rather than general ones for the best results.
How can I tell if a recommended tool is actually good or just being promoted? Look for specific tradeoffs mentioned alongside the praise, a poster history that isn't limited to one product, and agreement from multiple unrelated people rather than a single enthusiastic post. Referral links and ad-copy phrasing are red flags.
Can I just browse discovery platforms instead of asking a question? Yes, and it's often faster for broad categories with no strong constraints. Platforms built around demand signals, rather than launch-day hype, let you skip posting a question and waiting on replies entirely.
The eleven communities above cover most of what you'll need, but the underlying habit matters more than the venue: state your constraints clearly, weigh advice by whether the person has skin in the game, and treat demand, what people actually use and request, as your filter over popularity or ad spend. Do that consistently and you'll get real answers no matter where you ask.