Most ICP research fails for a boring reason: it is built from memory, politeness, and abstraction. By the time someone fills out your survey or joins your customer interview, they are already translating their real behavior into a cleaner story.
That makes the output sound useful while hiding the part you actually need: what people are trying to solve right now, in their own words, with real urgency attached.
What breaks in traditional ICP research
The standard playbook usually looks like this:
- define a target persona
- write a survey
- book a few interviews
- summarize the answers into a neat document
The document looks professional. The problem is that it is usually weak where it matters most.
Three common failure modes:
- Recall bias: people tell you what they think they do, not what they did when the pain hit.
- Courtesy bias: strangers are nicer in interviews than in real buying situations.
- Over-generalization: one polished quote turns into a fake rule for an entire market.
None of that means interviews are useless. It means they should not be your first layer of signal.
What live signal gives you instead
The same Gorilla demo run on the landing page surfaced 266 posts and flagged 91 as top leads. That is useful because it gives you behavior before interpretation.
The strongest examples were not polished "research answers." They were raw problem statements:
- Reddit /
r/startups: "How do you actually get first users for your SaaS? (I will not do cold email...)" - Reddit /
r/SaaSDevelopers: "How do I find people to actually beta test my software?" - YouTube /
@thestartupjourney: "How do you validate a SaaS idea without spending money on ads?"
Those lines tell you more about the real ICP than a persona deck does:
- the job to be done is immediate
- the buyer is constraint-aware
- the alternatives are already failing
- the wording is specific enough to reuse in positioning
That is what makes live signal valuable. It captures pain before someone has time to polish it.
A better ICP workflow
Instead of starting with persona fields, start with repeated pain.
Workflow:
- Search for phrases that describe the struggle, not the role.
- Pull recent posts across multiple networks.
- Group them by recurring problem, constraint, and trigger.
- Use interviews only after you have seen the patterns in the wild.
This flips the usual order.
Traditional ICP work says:
- choose the audience
- ask what they want
- hope the answers are true
Signal-first ICP work says:
- observe real behavior
- extract repeated patterns
- interview into the gaps
That produces a more grounded starting point.
What to capture from each post
Do not just save a link and move on. Create a lightweight record with:
- source network
- exact phrase used
- timestamp or recency
- stated constraint
- failed workaround
- whether the author is asking for help, tools, or examples
After 25-30 good posts, your ICP will stop being generic.
You will start to see:
- which pains are urgent versus aspirational
- which channels contain buyers versus browsers
- which objections show up before the sale
- which words belong on your landing page immediately
Turn repeated phrases into positioning
This is where most founders still leave value on the table.
If people keep saying:
- "first users"
- "beta testers"
- "validate without ads"
- "manual research takes forever"
then your copy should not say:
- "customer acquisition enablement"
- "audience intelligence platform"
- "prospect discovery workflow"
The market is already handing you the language. Good ICP work is partly about hearing it clearly enough to use it back.
Interviews still matter, but later
Interviews are powerful once you know what you are testing for.
The right sequence is:
- use live posts to identify patterns
- use interviews to deepen the strongest patterns
- use product conversations to validate buying motion
That keeps the conversation honest. You are no longer asking "what is your problem?" in a vacuum. You are asking "I keep seeing this exact pain pattern - is that true for you too?"
That question gets better answers.
The output should be a working ICP, not a pretty PDF
A useful ICP is not a static document. It is a system you can update every week.
At minimum, your working ICP should answer:
- what problem shows up most often
- where people talk about it in public
- what words they use when the pain is strongest
- what alternatives they already tried
- what makes them act now instead of later
If your ICP cannot improve your search queries, outreach copy, or landing-page headline, it is not finished. It is decoration.
What actually works
The shortest answer is this: collect live pain, cluster the repeated phrases, and only then layer on interviews.
That is how you get an ICP that is useful for shipping, not just for presenting.
Further reading: