You can describe an offer very clearly and still be solving a problem differently from how the customer understands it. I'd want to discover that while the offer is easy to change.

Public questions can help. They give you examples of the language, constraints, and workarounds people choose to discuss. Read them as evidence you can investigate, with enough humility to recognize what they leave out.

Write the assumption before collecting examples

Choose one thing you believe about the customer. Perhaps you think they need help coordinating approvals, or that a missing integration is the main reason they look for another tool. Write down what would support that belief and what would challenge it.

Otherwise, it's easy to collect posts that sound encouraging and ignore the ones that complicate your idea. I want the research to have a chance to change the offer.

Look for requirements and workarounds

Read what the author tried, why it failed, and what a useful solution would need to preserve. For a fictional approval product, you might discover that requiring clients to create accounts is a bigger obstacle than organizing comments.

Keep the original link and distinguish a quote from your interpretation. Remove unnecessary personal details from working notes. A recurring concern is worth investigating, but don't turn a small set of public posts into a claim about the entire market.

  • What task are they trying to complete?
  • What have they already tried?
  • Which requirement keeps limiting the options?
  • What would make your current offer unsuitable?
  • What question would you need to ask next?

Make a specific revision you can explain

You might clarify who the service is for, narrow its scope, or change the way you explain a capability. Choose a revision tied to evidence. Avoid promising a feature simply because one discussion made it sound attractive.

Then look for more conversations that test the revised assumption. If you join a discussion, contribute honestly and disclose your connection when relevant. A question from someone considering your idea can teach you more than agreement with a vague pitch.

Use ICPSignal to keep finding relevant examples

Create an ideal customer profile around the audience and problem you are studying. Review matching posts and inspect the explanation of fit. Treat those results as research leads, with the same care you would give manually found examples.

A matched post isn't a purchase commitment, and a public sample isn't representative market proof. Use what you learn to improve the offer and decide which direct conversations or tests should come next. That's a useful outcome even when the original idea needs to change.