Is Competitive Intelligence Still Too Scattered for Teams to Access Quickly?

·Jun 14, 2026 08:06 AM·

I keep thinking most teams don't actually have a competitor data problem anymore. The information is already out there: • pricing pages • changelogs • reviews • LinkedIn posts • ads • Reddit discussions The harder part is getting answers quickly. If someone asks, "What changed with Competitor X this month?" how many tabs do you have to open before you can answer confidently? Feels like competitive intelligence is one of the last workflows that's still scattered across a dozen different places instead of living inside the tools people already use every day. Curious if others feel the same, or if your team has already solved this.

12 comments

· Sorted by Oldest

Murad J.
·
·
If you use Claude Code, its literally just asking the question, no new tabs
🙌1
Aishwarya Gupta
·
(edited)·
Does Claude help with Linkedin behaviour research as well? Last I know was that Linkedin doesn't allow anyone touch its data and they're good at keeping scrapers away. Any thoughts or recommendations on it?
Soham S.
·
·
you can ask claude code to use playwright and your own browser to use linkedin
🙌1
Ashok A.
·
·
Agree. Data is easier now. The harder part is still judgement. Teams can know what changed with a competitor and still not know what reps should do differently in the live sales conversation. That’s usually where the gap shows up for me.
🙌1
Damian O.
·
·
Many tools help with Linkedin, the problem is really how risky it is. Linkedin has a tight control in their Terms and Conditions. You might get flagged, you might not. It's a risk-reward type of thing. That's how they built it so you need to use Sales Navigator
👀1
Murad J.
·
·
I still wouldn't replace Sales Nav, its gold. But scraper on top of Sales Nav? 💎
🙌1
Tetiana
·
·
I have set up an automated flow that scrapes / searches for info (perplexity and claude), logs in airtable DB and then using make.com updates corporate documentation tool so anyone in the organization could access the last updates. That actually does the "What changed with Competitor X this month?" in one place, but requires someone to spend time on configs and maintenance.
❤️1
Adrian G.
·
·
The research and practice both suggest the hardest problem is actually translation into action. Ashok touched on this: "Teams can know what changed and still not know what reps should do differently." That aligns with decades of competitive intelligence literature, which emphasizes that intelligence only matters if it informs decisions. Gathering and distributing facts is not the end goal. Action is. And, speaking as someone who has spent 20+ years training sales teams, I've rarely seen deals lost because a rep didn't know a competitor had updated a pricing page or launched a new feature. More often, the rep had the information but didn't know how to adapt. Should they change the questions they ask? Reposition value differently? Address a new risk? Involve another stakeholder? Slow down or speed up the process? The irony is that most teams don't lose because they missed a competitor's update. They lose because they noticed the change but never translated it into a different conversation, a different strategy, or a different decision.
👀1
Mary
·
·
Aishwarya Gupta LinkedIn is definitely the hardest source to work with because of the restrictions you mentioned. In my experience, Claude can still be useful for LinkedIn research, but only if you're feeding it the data yourself. For example: company pages, posts you've collected, profile exports, ad library data, hiring signals, website changes, earnings calls, etc. The challenge isn't analysis anymore. It's access.
Mary
·
·
Ashok A. I think that's exactly the distinction. Finding competitor information is becoming easier every year. Between AI, search, social, reviews, and public data, most teams can answer "what changed?" The harder question is: "So what?" A pricing change, messaging shift, or product launch only matters if someone can translate it into a decision. What should sales say differently? What objections become more important? Which deals become more vulnerable? What should product or marketing do next? A lot of competitive intelligence workflows still stop at information gathering when the real value is helping teams make better decisions from it.
Mary
·
·
Tetiana That's actually a pretty solid setup. I think a lot of mature teams eventually build some version of that: collect signals with AI, centralize them somewhere, then push them into the systems people already use. The tradeoff is exactly what you mentioned: someone still owns the workflow. Sources break. Prompts need updating. New competitors get added. Documentation structures change. The other gap I often see is moving from "what changed?" to "what matters?" A list of competitor updates is useful. Knowing that three of those updates point to an enterprise push, pricing strategy shift, or new ICP is where the judgment starts. That's one of the problems we're trying to solve with IndustryLens. Not just collecting pricing changes, changelogs, ads, reviews, social, Reddit, hiring and news in one place, but connecting those signals together and linking every claim back to its source so teams can quickly decide whether it's noise or something worth acting on. The information gathering is increasingly becoming a solved problem. The interpretation layer still feels much less solved.
Mary
·
·
Adrian G. I think that's right. Most competitive intelligence workflows are optimized around answering: "What changed?" But the business value usually comes from answering: "What should we do differently because it changed?" A competitor launching a feature isn't actionable on its own. The useful questions are:
Does this weaken our positioning?
Which deals become more at risk?
What objections should sales expect?
Which stakeholder is now more important in the buying process?
Do we need to change messaging, pricing, or packaging?
That's one reason I've become less interested in pure monitoring over time. The challenge isn't collecting more competitor updates. Most teams already have more information than they can realistically use. The challenge is connecting competitor signals to actual decisions across sales, product, and marketing. Otherwise competitive intelligence becomes an archive instead of a competitive advantage.

Murad J.
·
·
If you use Claude Code, its literally just asking the question, no new tabs
🙌1
Aishwarya Gupta
·
(edited)·
Does Claude help with Linkedin behaviour research as well? Last I know was that Linkedin doesn't allow anyone touch its data and they're good at keeping scrapers away. Any thoughts or recommendations on it?
Soham S.
·
·
you can ask claude code to use playwright and your own browser to use linkedin
🙌1
Ashok A.
·
·
Agree. Data is easier now. The harder part is still judgement. Teams can know what changed with a competitor and still not know what reps should do differently in the live sales conversation. That’s usually where the gap shows up for me.
🙌1
Damian O.
·
·
Many tools help with Linkedin, the problem is really how risky it is. Linkedin has a tight control in their Terms and Conditions. You might get flagged, you might not. It's a risk-reward type of thing. That's how they built it so you need to use Sales Navigator
👀1
Murad J.
·
·
I still wouldn't replace Sales Nav, its gold. But scraper on top of Sales Nav? 💎
🙌1
Tetiana
·
·
I have set up an automated flow that scrapes / searches for info (perplexity and claude), logs in airtable DB and then using make.com updates corporate documentation tool so anyone in the organization could access the last updates. That actually does the "What changed with Competitor X this month?" in one place, but requires someone to spend time on configs and maintenance.
❤️1
Adrian G.
·
·
The research and practice both suggest the hardest problem is actually translation into action. Ashok touched on this: "Teams can know what changed and still not know what reps should do differently." That aligns with decades of competitive intelligence literature, which emphasizes that intelligence only matters if it informs decisions. Gathering and distributing facts is not the end goal. Action is. And, speaking as someone who has spent 20+ years training sales teams, I've rarely seen deals lost because a rep didn't know a competitor had updated a pricing page or launched a new feature. More often, the rep had the information but didn't know how to adapt. Should they change the questions they ask? Reposition value differently? Address a new risk? Involve another stakeholder? Slow down or speed up the process? The irony is that most teams don't lose because they missed a competitor's update. They lose because they noticed the change but never translated it into a different conversation, a different strategy, or a different decision.
👀1
Mary
·
·
Aishwarya Gupta LinkedIn is definitely the hardest source to work with because of the restrictions you mentioned. In my experience, Claude can still be useful for LinkedIn research, but only if you're feeding it the data yourself. For example: company pages, posts you've collected, profile exports, ad library data, hiring signals, website changes, earnings calls, etc. The challenge isn't analysis anymore. It's access.
Mary
·
·
Ashok A. I think that's exactly the distinction. Finding competitor information is becoming easier every year. Between AI, search, social, reviews, and public data, most teams can answer "what changed?" The harder question is: "So what?" A pricing change, messaging shift, or product launch only matters if someone can translate it into a decision. What should sales say differently? What objections become more important? Which deals become more vulnerable? What should product or marketing do next? A lot of competitive intelligence workflows still stop at information gathering when the real value is helping teams make better decisions from it.
Mary
·
·
Tetiana That's actually a pretty solid setup. I think a lot of mature teams eventually build some version of that: collect signals with AI, centralize them somewhere, then push them into the systems people already use. The tradeoff is exactly what you mentioned: someone still owns the workflow. Sources break. Prompts need updating. New competitors get added. Documentation structures change. The other gap I often see is moving from "what changed?" to "what matters?" A list of competitor updates is useful. Knowing that three of those updates point to an enterprise push, pricing strategy shift, or new ICP is where the judgment starts. That's one of the problems we're trying to solve with IndustryLens. Not just collecting pricing changes, changelogs, ads, reviews, social, Reddit, hiring and news in one place, but connecting those signals together and linking every claim back to its source so teams can quickly decide whether it's noise or something worth acting on. The information gathering is increasingly becoming a solved problem. The interpretation layer still feels much less solved.
Mary
·
·
Adrian G. I think that's right. Most competitive intelligence workflows are optimized around answering: "What changed?" But the business value usually comes from answering: "What should we do differently because it changed?" A competitor launching a feature isn't actionable on its own. The useful questions are:
Does this weaken our positioning?
Which deals become more at risk?
What objections should sales expect?
Which stakeholder is now more important in the buying process?
Do we need to change messaging, pricing, or packaging?
That's one reason I've become less interested in pure monitoring over time. The challenge isn't collecting more competitor updates. Most teams already have more information than they can realistically use. The challenge is connecting competitor signals to actual decisions across sales, product, and marketing. Otherwise competitive intelligence becomes an archive instead of a competitive advantage.