Lemlist MCP Use Cases: What You Can Actually Do With It

Most outbound lists are cold, not because the contacts are wrong, but because the timing is. You're reaching a company when nothing is happening for them that could use your solution, so your message comes across as noise. Intent signals fix that. They tell you when something real has changed at a target account, and they give you a specific reason to reach out right now.

lemlist surfaces 13 of these signals natively. Each one maps to a moment when a company's situation has shifted, making them temporarily receptive to exactly the kind of conversation you want to have. Here's what each signal is, why it matters, and how to think about using it.

Why "intent data" is the wrong frame

The term "intent data" makes it sound like you're reading minds. You're not. What you're actually reading is context.

When a company posts a VP of Sales job, that's a context signal. It tells you the company is building a revenue function, probably scaling headcount, possibly evaluating new tools to support that growth. The job posting isn't the intent; it's evidence of a situation. And situations condition what problems a company is open to solving.

This reframe matters because it changes what you look for. You're not hunting for some abstract "buying signal." You're tracking changes in a company's operating context because those changes determine what they'll actually care about when you show up. The richer and more current your picture of that context, the more relevant your outreach can be.

Most databases give you a snapshot. Signals give you motion. Those are very different things.

The 48-hour window that changes the math

Here's something most outbound teams don't account for: signals expire.

When a company raises a funding round, posts a new executive hire, or flags a technology change, there's a short window where that information is fresh and the decision-makers involved are actively in motion. Outreach during that window can see reply rates running four times higher than standard cold outbound. Meetings sourced this way close at a 74% higher rate than meetings sourced from cold prospecting, according to intent-signal research from www.rodz.io.

After roughly 48 hours, that window starts to close. The team has moved on to the next priority. The decision on whether the signal points at has either been made or parked. Your message, if it arrives a week later, doesn't land as "you caught this at the right moment." It lands as just another email.

lemlist surfaces signals as they happen, so you can act while the context is still live. That's the operational premise behind everything below.

The 13 intent signals available in lemlist

1. Company hiring for a specific role

Job listings are one of the most readable signals in B2B. When a company posts a role, it reveals where they're allocating budget and attention.

The use case: I want to contact a company WHEN they post a job for a specific role, because that role tells me exactly what they're trying to build and where they probably have gaps right now.

A company recruiting a Head of Revenue Operations is likely evaluating its entire sales stack. A company hiring five SDRs in 30 days is building outbound capacity and probably needs the infrastructure to support it. The job post is a detailed brief on what the company is working on, published publicly, for free.

2. Company visited my website

When a company visits your website, they already know you exist. That changes the conversation significantly.

The use case: I want to contact a company WHEN they've visited my site, because a warm company is fundamentally different from a cold one.

Cold outreach opens with you proving you're worth attention. With a site visitor, the conversation can open on what they were looking at and why. In 2026, with inbox competition at record levels, starting from "they already showed up" is a real advantage. Response rates reflect that difference.

3. Custom signals

Not every relevant trigger fits a standard category. Custom signals let you define what you're tracking based on what you actually know about your buyers.

The use case: I want to contact a company WHEN a specific trigger appears in daily web content, because your market has patterns that generic signal libraries don't capture.

This might be a regulatory mention in a trade publication, a specific term appearing in a company's job descriptions, or a topic your ideal customers tend to publish about before a buying cycle. Custom signals are how you move from off-the-shelf intent data to something that fits your actual business. According to intent-signal research, there are roughly 108 distinct real-time signals worth tracking across the B2B market. Most teams use a fraction of them.

4. Contact changed jobs

When someone moves companies, they carry their problems with them but not their solutions.

The use case: I want to contact a person WHEN they've changed companies, because a former customer at a new employer already knows what your product can do.

They've been through the evaluation, the onboarding, the proof of value. The decision cycle is shorter because trust was already built at the previous company. This is one of the fastest paths to a new contract in outbound, and it's consistently underused. People change jobs often enough that tracking this across a decent-sized customer base produces a steady flow of warm contacts throughout the year.

At one French mutual bank, 40% of new professional account openings came directly from job-change signals tracked on former customers. That's not a marginal improvement on cold lists. That's a pipeline rebuilt from the ground up.

5. Competitor new connections

LinkedIn connections are a public record of who a salesperson is actively building relationships with.

The use case: I want to contact a company WHEN a competitor's sales rep adds them as a new LinkedIn connection, because that tells me the company is in an active sales conversation with someone I'm competing against.

Timing here is the whole point. If a competitor's rep just connected with a VP at a target account, that account is probably in some form of discovery or evaluation. Showing up in the next 48 hours with a relevant message puts you in the conversation before anything is decided. Arriving three weeks late is just another email.

6. A new hire joined the company

A new hire, especially in a decision-making role, resets the vendor landscape.

The use case: I want to contact a company WHEN a new decision-maker joins, because newly hired leaders are more likely to make purchasing decisions within their first 100 days than at any other point in their tenure.

New hires come in with a mandate to make their mark. They review existing tools, often find gaps or tools they disliked at their last company, and have both the motivation and the organizational permission to make changes. After that 100-day window, they're embedded in the status quo, and the friction of switching rises sharply.

7. Technology change

When a company adopts or drops a technology, it reshapes its stack and the problems they face.

The use case: I want to contact a company WHEN they adopt or drop a specific technology, because a technology change creates adjacent needs almost immediately.

Adopt a new CRM, and you probably need data to feed it. Drop a marketing automation tool, and you need something to fill the gap. Technology changes show up in job postings, LinkedIn announcements, and stack-detection tools. The companies in transition are the ones with the live budget question. The ones who finished the transition six months ago have already answered it.

8. Company raised funds

Funding is the clearest signal that a company is about to spend money.

The use case: I want to contact a company WHEN they close a funding round, because fresh capital creates purchasing capacity that wasn't there the week before.

Post-funding, companies are under pressure to deploy capital toward growth. Headcount is expanding, tool evaluations are open, and decision-makers are actively seeking vendors to help them scale. The window between announcement and "we've sorted out the budget allocation" is short. Inside it, a well-timed message about what you can help them build lands differently than the same message sent six months later.

9. Engaged with a profile on LinkedIn

When someone comments on or reacts to a thought leader or competitor in your space, they're advertising what they're thinking about.

The use case: I want to contact a person WHEN they engage with a competitor's or industry leader's LinkedIn profile, because that engagement tells me what topics and vendors are on their radar.

Engaging with a competitor's posts is a particularly clear signal. The person is paying attention to what that competitor says, which means they're either a customer, evaluating, or comparing options. Any of those is a conversation worth starting, and you know exactly what to lead with.

10. Engaged with a company profile on LinkedIn

Similar to profile engagement, but pointed at company pages rather than individual accounts.

The use case: I want to contact a person WHEN they engage with a competitor's or industry company page on LinkedIn, because page engagement signals active interest in that company's solutions or news.

Company page engagement tends to cluster around product announcements, hiring news, and thought leadership posts. People who engage with those are often in an evaluation posture, whether they'd describe it that way or not. That's your opening.

11. Mergers and acquisitions

M&A creates disruption. Disruption creates purchasing decisions.

The use case: I want to contact a company WHEN they're involved in a merger or acquisition, because M&A brings operational challenges that require new solutions and almost always triggers vendor consolidation.

Two companies coming together mean two tech stacks, two processes, and two sets of vendor relationships to reconcile. Someone has to decide what stays and what goes. That review process is a buying process by another name, and it involves decisions that would normally take years to reopen. Most vendors wait to see how the integration plays out. The ones who engage early shape the conversation.

12. Engaged on specific keywords on LinkedIn

This is the most targeted of the LinkedIn engagement signals. Instead of tracking who follows a company or person, you track who engages with posts containing specific keywords.

The use case: I want to contact a person WHEN they engage with LinkedIn posts that mention a specific keyword, because keyword-level engagement shows topic-specific attention, not just broad interest.

If someone is commenting on every post about "outbound automation" or "sales enablement," they're probably thinking about those things actively, not passively. Building a workflow around a specific keyword means your pipeline is naturally pre-filtered for people already in the conversation you want to have.

13. Promotion (coming soon)

When someone is promoted, their purchasing authority often increases at the same moment their incumbent vendor relationships are up for review.

The use case: I want to contact a person WHEN they receive a promotion, because recently promoted decision-makers often reassess the tools and vendors around them as part of establishing their new scope.

A new title comes with new accountability. What worked for the previous role may not fit the new one. That reassessment is a genuine opportunity, not a manufactured one, and it's time-bounded in the same way as a job change: early in the new role, doors are open; once they've settled in, the status quo re-establishes itself.

Signal stacking: when two signals point at the same account

One signal is a reason to pay attention. Two or three signals overlapping on the same account are a reason to move today.

Here's what that looks like in practice. A company posts a job for five SDRs in 30 days. At the same time, they announced a new Head of Sales who joined three weeks ago. Stack those two signals, and you've got a company actively building outbound capacity, led by someone who just came in with a mandate to prove results. That's not a marginal lead. That's the top of your contact queue.

Add a third signal, say they just closed a Series A, and the case for moving immediately becomes hard to argue against. The budget is there, the team is building, and the new leader hasn't settled on vendors yet. Three arrows pointing at the same account at the same time is the clearest prioritization signal you'll get.

Signal stacking doesn't require a complicated scoring model. It just requires looking at your signals together rather than in isolation.

How to write outreach around a signal

The instinct is to reference it directly and then pitch. That's close, but not quite right.

The signal tells you why you're reaching out now. It doesn't tell you what to say. The message still needs to connect your product to the situation the signal reveals.

If a company just posted a job for a data analyst, don't write "I saw your job post." Write about the problem that kind of hire usually signals. You're demonstrating that you understand their situation, not that you monitor their job board.

One message per signal. No follow-up sequence.

The logic: a follow-up sequence is what you send when you don't have context, compensating for a weak reason to reach out with volume. When the signal is strong and timely, one well-written message is enough. If they don't respond, wait for the next signal on the same contact.

The average contact crosses about four meaningful signals per year. That's four separate, fresh reasons to send a new first message, never a follow-up. Across a list of 500 contacts, that's roughly 2,000 signal-triggered messages per year, each one a first message, not a fifth.

Frequently asked questions

What is intent data, exactly?

Intent data is the set of signals that reveal what a company or person is actively dealing with at any given time. In practice, it's any public event, a hiring post, a funding announcement, or a LinkedIn comment that tells you something meaningful about a company's current situation and, therefore, what problems they're open to solving. The signals in the lemlist map directly to that definition.

How is this different from a static contact database?

A static database tells you who exists. Intent signals tell you who is in motion right now. You can enrich a database with firmographics to get a perfectly accurate, perfectly cold list. Signals give you the specific moment when a contact at that company is likely to be receptive. The same person on a cold list and on a signal list is in completely different outreach situations.

When someone posts a job listing, announces a funding round, or publishes a LinkedIn comment, they're creating public information. Tracking and responding to that public information falls under legitimate interest, one of the lawful bases under GDPR. The key is that the signal itself is the legitimate interest: you're not inferring private behavior; you're responding to something they chose to publish. That's the framework in which these signals operate.

How many intent signals does a typical contact generate per year?

On average, a single contact crosses about four intent signals per year. That might sound low, but across a list of 500 contacts, it means around 2,000 signal-triggered moments annually, each a genuine first-message opportunity. That's a very different kind of pipeline from a cold list with a seven-step sequence attached.

About 8% of the B2B market currently knows what an intent signal is, according to research from www.rodz.io. That means the vast majority of your competitors are still running purely cold outbound in 2026. For now, using signals well is a real competitive edge, not a table stake.

Signals expire. The 13 above give you a working list of reasons to reach out; the only variable is how quickly you move once one fires. Inside the 48-hour window, you're in a different conversation than everyone else planning to send the same message next week.

Test out lemlist's Intent Signal Agents for free: https://www.lemlist.com/product/intent-signals

Peter Cools

CEO @Rodz

WEBSITE

https://www.rodz.io/