LinkedIn activity intent flags companies whose employees post about topics tied to what you sell, and Lusha names the person who wrote each post. This prompt runs it through the Lusha connector in Claude, keeps only the posts that point to a real problem, and checks each author in Lusha before you reach out. You get a short list of people already talking about that pain, with an opener for each.More on Lusha’s intent data: Does Lusha have intent data?
Find prospects posting on LinkedIn about the pain you solve
The prompt
Use the Lusha connector to find people at my target accounts who are posting on LinkedIn about the problem I solve.
What I sell: [your product, e.g. sales intelligence]
Problem it solves: [e.g. reps waste time on bad contact data]
Accounts: [paste a list of domains, OR describe your ICP: industry, size, country]
Intent categories: [1-2 categories, e.g. Sales, CRM]
Topics that count: [3-5 exact topics, e.g. Sales Enablement, Sales and marketing alignment, Data Driven Sales]
1. Check my Lusha credit balance and estimate what this run will cost before you start.
2. If I gave an ICP, search for up to 25 companies in it with LinkedIn activity intent in my categories. Drop companies whose LinkedIn member count is far above their company size: those are communities, franchise or distributor networks, and their members' posts aren't buying signals.
3. Pull the LinkedIn activity intent posts for each company from the last 90 days, up to 3 posts per company.
4. Keep a post only if all of these are true:
- its topics include at least one of my topics
- its category is Pain Point or Challenge, Technology or Stack Discussion, Competitor or Market Comparison, or Company or Career Update
- it's about the author's own company, not an event recap, a reshare, a personal career story or a job post for another company
5. For each post you keep, check the author's current company and title in Lusha. Drop anyone who doesn't work at that company now. Flag anyone Lusha shows with two current roles.
6. Return a table: company, author, title, post date, post category, one-line summary, post link, why it's relevant to what I sell.
7. Add a list of the posts you dropped, with one line each on why.
8. For the top 3, write a two-sentence opener that references the post, not my product.
9. Ask me before revealing any contact details or saving anything to a Workspace table.Fill in the five lines in brackets. A list of target account domains gives cleaner results than an ICP description, because you’ve already ruled out the wrong kind of company.
What you'll get back
The situation
A rep wants a reason to reach out that isn’t “I saw you’re hiring.” The best one is a post where someone at the account describes the exact problem the rep’s product solves. Finding those posts by scrolling LinkedIn takes hours, and a raw signal feed is full of event recaps, reshares and posts by people who don’t work at the account.
The output
We ran the prompt for a sales intelligence product, with Sales and CRM as intent categories, on US companies with 51–500 employees. Lusha matched 32,110 companies on the categories alone. Narrowing to software companies cut that to 2,788. We pulled 19 posts from 8 companies. The prompt kept 3.
Posts kept
| Company | Author | Title | Date | Category | Post | Why it’s relevant |
|---|---|---|---|---|---|---|
| Company A (HR software, 201–500, Massachusetts) | K.A. | Director of Product Marketing | Oct 15 | Pain Point or Challenge | Argues product marketers should own both requirements and campaign copy so campaigns match the product. | Talks about sales and marketing alignment; a buyer-side voice on campaign targeting. Lusha shows a second current role at his own consultancy, so confirm before outreach. |
| Company A | S.K. | Customer Success Manager | Oct 15 | Company or Career Update | Company A is hiring account executives, customer success managers and professional services staff. | A growing sales team needs contact data for new reps. S.K. isn’t the buyer; use the post as context and go to the sales leader. |
| Company B (Healthcare, 201–500, New York) | C.J. | Head of Growth Strategy | Aug 26 | Company or Career Update | Company B is hiring growth strategy leaders to scale its sales and performance teams. | The author owns sales growth and is building the team now. Tagged Sales Enablement and Sales Performance Management. |
Posts dropped, and why
- Author doesn’t work there: two posts came from people Lusha shows at other companies, a freelance developer and a bug bounty hunter on a different platform. A third author wrote about their first 100 days at a fintech company.
- Community or network, not a company: posts from real estate agents at a brokerage, tutors on a tutoring marketplace and members of a professional network. These companies list thousands of LinkedIn members against a 51–500 headcount.
- Event recaps and career stories: panel thank-yous, conference booth reposts and a personal journey into executive coaching. They were tagged with sales and CRM topics but say nothing about a buying need.
- Job post for another company: an employee reshared a hiring post from a different startup.
Opener (example for C.J.): “Saw your post about hiring growth strategy leaders to scale the sales and performance teams. When the new leaders start, what will they inherit for pipeline data on day one?”
Cost of the run: 57 credits across two company searches, 19 posts and one author check. No contact details were revealed.
Contacts confirmed live via Lusha connector, November 5, 2026. Company names are masked; contact names show initials only.
Why it works
A post about a problem is a better opener than any firmographic trigger, because the person told you what they care about in their own words. In Claude, Lusha pulls each post with its date, category, topics and author, then checks the author against Lusha’s contact data, so the list holds people who work at the account now and wrote about something you can help with. The filtering is the point: in our test, 16 of 19 posts were noise, and the prompt removed them before a rep saw them. Nothing gets revealed or saved until you approve it. Lusha is GDPR and CCPA compliant; see the Lusha Trust Center and Is Lusha GDPR and CCPA compliant? for details.
FAQ
What is LinkedIn activity intent?
A company-level buying signal in Lusha. It flags companies whose employees post LinkedIn content that maps to an intent category, such as Sales or CRM. Lusha reads the last 90 days, up to 50 posts per company, and returns each post’s date, category, topics, summary, link and author.
Why does the prompt drop so many posts?
Because intent categories are broad. A post about a panel event can carry ten sales topics without saying anything about a buying need. Some companies on LinkedIn are communities or networks, so their “employees” are members, agents or freelancers. In our test, 3 of 19 posts survived the filters. Better to call three people with a real reason than nineteen with a weak one.
How many credits does this prompt use?
The company search costs 1 credit plus 1 for each company that returns the signal, so 25 companies cost 26 credits. Each post returned costs 1 credit, which is why the prompt caps it at 3 per company. Checking authors costs 1 credit per search. Revealing an email or phone costs more. Our test used 57 credits. The prompt estimates the cost before it starts.
How is this different from intent topics?
Intent topics, powered by Bombora, show which companies are researching a subject across B2B websites, scored 0 to 100. LinkedIn activity intent shows what a company’s employees post, and names the author. Use intent topics to find accounts in market, then this prompt to find the person at the account who is talking about the problem.
Can I filter by exact topic instead of category?
The search filters by intent category. Each post comes back with its full list of topics, so the prompt filters on your exact topics after the posts are pulled. Pick topics from Lusha’s topic library and paste them into the prompt.
Related prompts
Ready to run this?
One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.
