Product
How to Get Useful Feedback From Other SaaS Founders
, Community Leader
15 minutes
Launching a SaaS product without feedback is risky. Acting on the wrong feedback can be just as damaging.
The most useful feedback does not come from whoever is willing to comment. It comes from people who understand your business, your stage, and the decision you are trying to make. A founder who has already solved the problem you are facing will usually provide more valuable insight than dozens of well-intentioned opinions from people without relevant experience.
This guide explains how to identify the right people to ask, frame your questions, separate signal from noise, and turn conversations into better product and business decisions.
Key takeaway: Useful feedback depends on two things: the experience of the person providing feedback and the context you give them. If either is missing, even honest advice can send your SaaS product in the wrong direction.
Why Most SaaS Founders Receive Unhelpful Feedback
Many SaaS founders assume that collecting more feedback automatically leads to better decisions. In reality, the opposite often happens. More opinions create more uncertainty unless the feedback comes from people who understand the problem you are trying to solve.
One founder tells you to lower your prices. Another insists your pricing is already too low. A customer requests a new feature, while another says the product feels too complicated. None of these comments are necessarily wrong. They simply reflect different perspectives.
The goal is not to collect as much feedback as possible. The goal is to collect feedback that helps you make a better decision.
Good Intentions Do Not Guarantee Useful Advice
People naturally want to help, but good intentions are not the same as relevant expertise.
A founder building an enterprise SaaS company may recommend adding onboarding calls because this approach works well for large contracts. The same advice could hurt a self-serve SaaS product where automation is a competitive advantage.
Likewise, advice from developers often focuses on technical quality, marketers emphasize acquisition, and investors think about growth potential. Each perspective has value, but none of them represents the complete picture.
Before accepting any recommendation, ask a simple question:
"Has this person successfully solved the same problem in a similar business?"
If the answer is no, treat the feedback as an idea to investigate rather than a decision to implement.
Experience Matters More Than Opinions
Not all founder feedback carries the same weight.
A founder who recently improved activation from 20% to 45% has practical experience that is directly relevant if you are struggling with onboarding. A founder who has never faced that challenge may still offer thoughtful suggestions, but they remain hypotheses rather than evidence.
The same principle applies throughout SaaS. Advice becomes more reliable as the distance between someone's experience and your situation becomes smaller.
Feedback source | Best used for | Potential limitation |
|---|---|---|
Founders with similar products | Product strategy, pricing, positioning | May project their own market onto yours |
Founders at a later stage | Scaling, hiring, operations | Advice may not fit an early-stage company |
Customers | User feedback, pain points, feature priorities | They rarely know the best implementation |
Industry experts | Specialized topics such as SEO, legal, or security | Limited understanding of your overall business |
One conversation with the right founder can save weeks of unnecessary product development. Ten conversations with the wrong audience can create confusion instead.
Context Is What Makes Feedback Actionable
Even experienced founders cannot provide useful feedback if they do not understand your situation.
Compare these two questions:
"What do you think about my pricing?"
"We sell a $39 per month SaaS product to marketing agencies. Trial conversion is 14%, but only 2% upgrade to annual plans. We are considering introducing a $79 plan with additional reporting features. What would you evaluate before making that change?"
The second example provides enough context to produce actionable feedback by defining the business model, target audience, pricing, current metrics, and the specific decision being considered.
The more relevant context you provide, the more useful the answers become. This includes information such as:
Your target customer.
Current stage of the company.
Existing traction or revenue.
Metrics related to the problem.
Constraints you cannot change.
The decision you are trying to make.
Context transforms opinions into useful insight. Without it, even experienced SaaS founders are forced to guess.
Common mistake: Asking broad questions like "Can you review my product?" almost always produces broad answers. Narrow questions tied to a specific business decision generate far more actionable feedback.
Who Should Provide Feedback on Your SaaS Product
The quality of your decisions depends heavily on who you ask. Different people can provide feedback from different perspectives, but they should not be expected to answer the same questions.
Founders at a Similar Stage
Founders at a similar stage often recognize problems that larger companies have already forgotten. They understand the realities of finding product-market fit, acquiring early customers, and making trade-offs with limited resources.
Because they face similar constraints, their advice is often immediately applicable.
Founders Who Have Already Solved Your Problem
The most valuable conversations usually happen with founders who have already overcome the challenge you are facing today.
If you are redesigning onboarding, talk to someone who recently improved activation. If pricing is your biggest concern, seek founders who have successfully changed their pricing model. Their insight is grounded in experience rather than theory.
When Customer Feedback Is More Valuable Than Founder Feedback
Founder feedback and customer feedback serve different purposes.
Founders help you decide how to solve a business problem.
Customers help you understand whether the problem actually exists.
For example, customers may repeatedly complain that reporting is too limited. That customer feedback identifies a real need. Other SaaS founders can then help you evaluate different approaches, prioritize development, estimate implementation costs, or decide whether the request fits your long-term product strategy.
The strongest product decisions rarely come from relying on only one source. They emerge when customer feedback validates the problem and experienced founders help interpret the best path forward.
What Kind of Feedback Should You Ask For?
One of the biggest reasons founders leave conversations disappointed is that they ask for "feedback" without defining what kind of feedback they actually need.
Feedback is not a single category. Questions about positioning require different expertise than questions about pricing or product design. If you ask the wrong audience the wrong question, even thoughtful answers become difficult to use.
Before every conversation, identify the decision you are trying to make. That immediately determines who should provide feedback and what information you should share.
Product Feedback
Product feedback helps you understand whether your SaaS product effectively solves the intended problem.
This does not mean asking, "Do you like my product?" General impressions rarely lead to meaningful improvements. Instead, ask founders to evaluate specific workflows, onboarding steps, or product decisions.
For example, instead of asking for a complete product review, ask:
Which part of the onboarding process would you simplify first?
Does the product communicate its value within the first few minutes?
Which feature creates unnecessary friction?
Is there anything that slows adoption down more than it should be?
Whenever possible, combine founder feedback with customer feedback. Customers explain where they struggle. Experienced founders often explain why they struggle and suggest multiple ways to solve the problem.
Positioning and Messaging Feedback
Many SaaS products fail to attract customers not because they lack functionality, but because they communicate the wrong value.
Positioning feedback focuses on questions such as:
Is the target audience immediately obvious?
Does the landing page explain the problem clearly?
Is the primary value proposition memorable?
Does the messaging differentiate the product from competitors?
This type of feedback is especially valuable when it comes from founders serving similar markets. They have already tested messaging, experimented with positioning, and understand which language resonates with buyers.
A useful exercise is to ask someone to spend thirty seconds on your homepage and then answer three questions:
What does this product do?
Who is it built for?
Why would someone choose it over alternatives?
If they struggle to answer any of those questions, your positioning probably needs refinement.
Marketing, Pricing, and Growth Feedback
Growth advice is highly contextual.
A pricing strategy that works for enterprise software can fail completely for self serve SaaS companies. Likewise, acquisition channels that generate predictable growth for developer tools may not work for products targeting agencies or ecommerce businesses.
Instead of asking, "How would you grow this business?", narrow the discussion to a single decision.
For example:
Should we increase pricing before adding new features?
Is it too early to invest in SEO?
Would you focus on outbound or content marketing?
Is our free trial long enough?
Focused questions produce focused answers. They also make it easier to compare different opinions and identify recurring insight across multiple conversations.
Strategic Decision Feedback
Strategic feedback concerns decisions that shape the company's future rather than individual features.
Examples include:
entering a new market;
changing the ideal customer profile;
introducing annual pricing;
hiring the first salesperson;
rebuilding part of the product;
expanding into enterprise customers.
These discussions benefit most from founders who have already faced similar decisions.
A founder who successfully expanded from SMB to enterprise can explain challenges that are difficult to anticipate from customer feedback alone. Likewise, someone who abandoned an unsuccessful expansion can help you avoid expensive mistakes.
The value of strategic feedback lies less in copying another company's approach and more in understanding the trade-offs that influenced their decision.
How to Ask Other SaaS Founders for Useful Feedback
The quality of the answers you receive is strongly influenced by the quality of the questions you ask.
Many founders unintentionally invite vague opinions by providing almost no context. Others overwhelm people with lengthy explanations and dozens of unrelated questions.
The goal is to make it easy for someone to understand your situation and respond to one specific decision.
Share Enough Context Before Asking
Assume the other person knows nothing about your business.
A short introduction should usually include:
what your SaaS product does;
who your customers are;
your current stage;
the problem you are trying to solve;
any important metrics related to that problem.
This context helps people provide feedback that reflects your actual situation rather than their assumptions.
Ask Focused Questions Instead of Broad Opinions
Broad questions produce broad answers.
Compare these examples.
Weak question
What do you think about my product?
Better question
Our trial-to-paid conversion is 9%. After watching the onboarding flow, which step would you improve first, and why?
The second question defines both the objective and the decision that needs to be made. That makes it much easier to receive actionable feedback instead of general impressions.
Whenever possible, limit a conversation to one major topic. Mixing onboarding, pricing, positioning, customer acquisition, and feature requests into the same discussion usually reduces the quality of every answer.
Provide Evidence, Not Assumptions
Evidence leads to better conversations.
Instead of saying that users appear confused, show where they become confused.
Useful evidence might include:
onboarding analytics;
customer interviews;
support conversations;
product usage metrics;
churn reasons;
session recordings;
examples of customer feedback.
When multiple founders review the same evidence rather than relying on assumptions, the discussion shifts from opinions to problem-solving.
That does not guarantee agreement, but it significantly increases the chance that the feedback you receive can be validated through future experiments rather than accepted on intuition alone.
How to Separate Useful Feedback From Noise
Not every recommendation deserves the same attention.
Founders often leave a conversation with a long list of conflicting suggestions and assume the safest approach is to combine them all. In practice, that usually creates a product that tries to satisfy everyone and serves no one particularly well.
Your objective is not to collect more opinions. It is to identify which feedback deserves further investigation.
Look for Patterns Instead of Individual Opinions
One founder questioning your pricing does not necessarily indicate a problem.
Five independent founders identifying the same weakness after reviewing your product is a much stronger signal.
The same principle applies to customer feedback. A single feature request may reflect one customer's workflow. Repeated requests from different customers often reveal an underlying need worth exploring.
Rather than counting individual comments, group feedback into recurring themes.
Pattern | Recommended action |
|---|---|
One isolated opinion | Keep it in mind, but do not change direction. |
Similar feedback from several experienced founders | Investigate further and validate. |
The same issue appears in founder feedback and customer feedback | Treat it as a high-priority opportunity. |
Feedback contradicts your product vision | Evaluate carefully before acting. |
Repeated patterns usually provide more reliable insight than the loudest opinion.
Evaluate the Source Before the Advice
The quality of feedback depends as much on the person providing it as on the advice itself.
Before acting on any recommendation, consider questions such as:
Have they solved a similar problem?
Do they understand your market?
Have they built a comparable SaaS business?
Are they speaking from experience or personal preference?
A founder may recommend removing a free plan because that decision doubled their business's revenue. That does not automatically mean it will work for yours.
Experience increases credibility, but context determines whether advice transfers successfully.
Validate Feedback Before Making Changes
Even excellent feedback remains a hypothesis until it has been tested.
Avoid making significant product decisions immediately after a single conversation. Instead, treat feedback as input for an experiment.
For example, if several founders believe your pricing page creates unnecessary friction, you could:
Create a revised version.
Run an A/B test if traffic allows.
Compare conversion rates.
Review customer feedback after the change.
Decide whether the improvement should become permanent.
Testing reduces the risk of overreacting while allowing you to benefit from valuable external insight.
Common Feedback Mistakes SaaS Founders Make
Most founders do not struggle because they receive too little feedback. They struggle because they collect the wrong feedback or interpret it incorrectly.
Recognizing these mistakes early can save months of unnecessary work.
Asking the Wrong People
Many founders ask friends, family, general startup communities, or social media followers for product advice.
These audiences may provide encouragement, but they rarely understand your customers, business model, or market.
When the decision is important, prioritize conversations with founders who have solved similar problems or customers directly affected by the issue.
Looking for Validation Instead of Learning
Sometimes founders ask for feedback after they have already made up their minds.
Instead of exploring alternatives, they unconsciously search for people who agree with them.
That approach limits learning because contradictory opinions are ignored.
A better mindset is to ask:
"What am I missing?"
This question encourages honest discussion instead of confirmation.
Changing Direction After Every Conversation
Every experienced founder has stories about advice that worked brilliantly for one company and failed completely for another.
If every new conversation changes your priorities, your product roadmap becomes unstable.
Collect feedback continuously, but review it on a regular schedule rather than reacting immediately after every discussion.
Consistency usually produces better long-term decisions than constant course corrections.
Where to Find Experienced SaaS Founders
Finding high-quality feedback is often harder than asking for it.
The best conversations happen in environments where founders understand each other's businesses and are willing to invest time in thoughtful discussions.
Mastermind Groups
A well-run mastermind creates ongoing conversations rather than isolated feedback sessions.
Because members meet regularly, they understand each other's goals, previous decisions, and business constraints. That shared context makes future feedback significantly more actionable.
Instead of repeating your company story every time, discussions can focus directly on the next important decision.
Founder Communities
Founder communities expose you to a wider variety of experiences than individual conversations.
Members often contribute ideas on positioning, pricing, hiring, fundraising, marketing, and product development.
The quality varies across communities, so look for groups with active founders who openly share real-world experience rather than generic startup advice.
Private Founder Networks
Smaller founder networks usually generate deeper discussions because members are carefully selected.
People become familiar with each other's businesses over time, making it easier to provide detailed feedback that takes into account previous experiments, customer conversations, and long-term strategy.
One-to-One Conversations
Sometimes one conversation with the right founder is worth more than dozens of online comments.
Personal discussions allow follow-up questions, clarification, and exploration of trade-offs that rarely fit into written conversations.
Whenever possible, prepare specific questions in advance and respect the other person's time by keeping the discussion focused.
A Simple Framework for Evaluating Every Piece of Feedback
Before implementing any recommendation, run it through three simple filters.
Relevant Experience
Has this person successfully solved a similar problem?
If not, the advice may still be interesting, but it deserves additional validation.
Understanding Your Business Context
Does the person understand your customers, pricing model, growth stage, and constraints?
Advice without context often sounds convincing while leading to poor decisions.
Evidence You Can Validate
Can you test this recommendation?
The strongest feedback leads naturally to measurable experiments rather than immediate implementation.
If you cannot imagine how to validate a recommendation, treat it as an idea instead of a conclusion.
Build a Repeatable Feedback System
Useful feedback should become part of how you build your SaaS product, not something you seek only when you feel stuck.
A simple system is usually enough.
Before asking for feedback
Define the decision you need to make.
Prepare the relevant business context.
Collect supporting data and customer feedback.
During the conversation
Ask one focused question at a time.
Listen more than you speak.
Clarify assumptions before debating solutions.
After receiving feedback
Group similar recommendations together.
Look for recurring patterns instead of isolated opinions.
Prioritize ideas that align with both customer feedback and your product strategy.
Validate important recommendations through experiments before making permanent changes.
Over time, this process creates a reliable feedback loop that improves decision-making without making your roadmap dependent on every new opinion. The best SaaS founders do not simply collect more feedback. They build systems that consistently turn the right feedback into better products and better businesses.
