Find companies that recently adopted Salesforce or HubSpot

Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own ICP and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.

A company that just adopted Salesforce or HubSpot isn’t done buying. They’re at the start of a purchasing cycle — building workflows, evaluating integrations, and making decisions about every tool that connects to the new CRM. The team that sold them the CRM is already in. Every adjacent vendor has a window. This Claude prompt uses Lusha to find companies that recently added Salesforce or HubSpot to their tech stack, filters them against your ICP, checks for stacked signals that strengthen the case, and verifies the right contact at each account — so you reach them while the window is still open.

The prompt

Open in Claude Open in ChatGPT 
<context>
I want to find companies that recently adopted Salesforce
or HubSpot — they're in an active buying cycle for every
tool that connects to their new CRM and I want to reach
them while the window is open.

My ICP: [describe your ideal customer — industry, company
size, geography, funding stage]

CRM to target: [Salesforce / HubSpot / both]

Timeframe: companies that added the CRM in the last
[90 days / 6 months / 12 months]

My product: [one sentence — what you sell and how it
connects to or enhances Salesforce or HubSpot]
</context>

<task>
1. TECH STACK SIGNAL SCAN — Use Lusha to find companies
   that recently added the specified CRM to their stack:
   - Filter by CRM adoption signal within the specified
     timeframe
   - Return all matching companies before ICP filtering

2. ICP SCORING — For each company showing the CRM
   adoption signal, score against my ICP:
   - Firmographic fit: industry, size, funding stage,
     geography
   - Remove companies that fail must-have criteria
   - Score remaining: Strong fit / Moderate fit

3. STACKED SIGNAL CHECK — For each ICP-fit company,
   check for additional signals that strengthen
   the case:
   - Hiring in sales ops, RevOps, or CRM admin roles
     — indicates active CRM buildout
   - New VP of Sales or Head of RevOps hired recently
     — new leader building their stack from scratch
   - Funding event in last 90 days — budget to invest
     in the new stack
   - Intent signals on tools that integrate with
     the CRM — active evaluation in progress
   - Flag companies with 2+ stacked signals as
     highest priority

4. CONTACT VERIFICATION — For each final account,
   verify the right contact via Lusha:
   - Primary target: Head of Sales Ops, Head of RevOps,
     VP of Sales, or CRM Admin depending on what
     you sell
   - Current title and tenure confirmed
   - Verified email and direct dial
   - Flag recent hires — tenure under 6 months means
     they're actively building the stack

5. RANKED OUTPUT — Return accounts ranked by signal
   strength and ICP fit. For each account:
   - CRM adopted and approximate adoption date
   - ICP fit score
   - Stacked signals if present
   - Verified contact with email and direct dial
   - One-line outreach angle tied to the CRM
     adoption and your product's integration
</task>

What you'll get back

Companies that just adopted Salesforce or HubSpot, filtered against your ICP, ranked by signal strength — each one with a verified contact and an outreach angle built around the CRM adoption.

Companies showing CRM adoption signal: 47  ·  ICP-fit after scoring: 14  ·  High priority (stacked signals): 5  ·  Contacts verified: 14

High priority — stacked signals

These accounts adopted the CRM and have two or more additional signals firing. The buying cycle is active. Reach out this week.

CompanyCRM adoptedApprox dateICP fitStacked signalsContact
[Company A]Salesforce6 weeks agoStrongNew VP Sales + RevOps hiring✓ Head of RevOps verified
[Company B]HubSpot8 weeks agoStrongSeries A closed + 3 sales ops roles✓ VP Sales verified
[Company C]Salesforce10 weeks agoStrongNew CRO + intent on sales tools✓ CRO verified
[Company D]HubSpot5 weeks agoStrongFunding + RevOps hire + intent✓ Head of RevOps verified
[Company E]Salesforce7 weeks agoStrongNew VP Sales + hiring surge✓ VP Sales verified

[Company A] — full detail

CRM adoption signal

FieldValue
CRM adoptedSalesforce
Approximate adoption date6 weeks ago
Previous CRMHubSpot (based on tech stack history)
IndustryRevenue Intelligence / SaaS
Employees220–260
FundingSeries B

Stacked signals

SignalTypeDate
New VP of Sales joinedExecutive move[date]
3 Sales Ops / RevOps roles postedHiring surge[date]
Intent — sales prospecting toolsIntent signalScore 74

Verified contact

FieldValue
NameR.M.
TitleHead of Revenue Operations
Tenure14 months
Emailr.m@[company].com
Direct dial+1 512 555 ••••

Contact confirmed live via Lusha connector, [date]

Outreach angle: Just moved from HubSpot to Salesforce, new VP of Sales in seat, actively hiring RevOps — the stack is being rebuilt from scratch. Lead with how your product integrates with Salesforce and accelerates the motion they’re building. The RevOps hire is the right door — they’re the ones evaluating every integration right now.

ICP-fit accounts — single signal

These accounts adopted the CRM and match your ICP. No stacked signals yet. Worth reaching out within the next two to four weeks before the initial buildout phase closes.

CompanyCRMApprox dateICP fitContactOutreach timing
[Company F]Salesforce9 weeks agoStrong✓ VP Sales verifiedThis month
[Company G]HubSpot11 weeks agoStrong✓ Head of RevOps verifiedThis month
[Company H]Salesforce12 weeks agoModerate✓ VP Sales verifiedThis month
[Company I]HubSpot7 weeks agoStrong⚠ Contact not found
Built by: Lusha
Time to build: 1 min
Tools: Claude, Lusha
Type: Prompt

Why use Lusha in Claude

A CRM adoption is one of the clearest buying signals in B2B — not because it tells you a company is researching your category, but because it tells you they’re actively rebuilding their stack. The moment a company switches to Salesforce or HubSpot, every tool that connects to that CRM goes into evaluation. Integrations get assessed. Existing vendors get reviewed. New vendors get considered. The team responsible for the buildout — RevOps, Sales Ops, the new VP of Sales — is making purchasing decisions right now, before the initial implementation phase closes.

Lusha’s tech stack signals track CRM adoption as a named, verified event — not inferred from a job posting or a news mention, but confirmed through Lusha’s multi-source verification process. The adoption date gives you the timing window. A company that adopted Salesforce six weeks ago is deep in the buildout phase. A company that adopted it six months ago has probably made most of its adjacent tool decisions already. The timeframe parameter in this play lets you target the window that matters for your sales cycle.

The stacked signal check is what separates the accounts worth calling this week from the ones worth monitoring. A CRM adoption alone is a reason to reach out eventually. A CRM adoption combined with a new VP of Sales, three RevOps roles posted, and an intent signal on sales tools is a reason to call today. Lusha’s 1.2B+ data points processed daily and 7M new signals every week mean the stacked pattern surfaces in real time — not after someone manually pieces it together from three different tools.

The contact verification step identifies who is actually making the decisions. A Head of RevOps who joined 14 months ago and is actively hiring their team is a different conversation than a CRO who has been in seat for three years and has a locked vendor stack. Tenure is a signal too — and Lusha verifies it live so the outreach angle reflects who’s actually in the room, not who the CRM record says should be.

Lusha data is sourced and used in accordance with Lusha’s Privacy Policy and Terms of Use.

FAQ

  • How does Lusha know when a company adopted a CRM?

    Lusha tracks tech stack signals as part of its data layer — verified through multiple independent sources that confirm which technologies a company is actively using and when changes occur. A CRM adoption signal means the technology appeared in the company’s confirmed tech stack within the specified timeframe. It’s not inferred from a job posting that mentions Salesforce or a LinkedIn update — it’s a verified change in the company’s technology profile. The approximate adoption date gives you a timing reference so you can prioritize companies in the early buildout phase over ones that adopted the CRM a year ago and have long since locked their adjacent tool stack.

  • Should I target Salesforce adopters, HubSpot adopters, or both?

    Depends on what you sell and which CRM your best customers typically run. If your product integrates with both and you sell into mid-market SaaS, run the play for both and compare the output — Salesforce tends to appear more in companies with dedicated RevOps or Sales Ops functions, HubSpot more in growth-stage companies where marketing and sales share a single platform. If your product has a native integration or a stronger use case with one over the other, run it for that CRM first and use the other as a secondary pass.

  • What's the right timeframe to use?

    90 days is the highest-conviction window — companies in this phase are actively building workflows and evaluating integrations. Six months catches companies that are past the initial setup and moving into optimization and expansion — a different conversation but still a live buying cycle for adjacent tools. Twelve months is the outer edge — companies this far past adoption have usually made most of their tool decisions, but leadership changes or dissatisfaction with the initial stack can reopen the conversation. Start with 90 days for the highest-signal list and widen if the output is too thin for your ICP.

  • Who is the right contact to target at a CRM adopter?

    Depends on what you sell. If you sell a tool that RevOps configures and manages — integrations, data enrichment, workflow automation — the Head of RevOps or Sales Ops is the right door. If you sell a tool that sales reps use daily — prospecting data, sequencing, calling — the VP of Sales or CRO is the right door. If you sell something that sits at the intersection of both, start with RevOps — they’re the ones building the stack and they’re more likely to be in evaluation mode than a VP who’s focused on the pipeline. The play defaults to the most senior relevant contact based on your product description, but you can specify the target function explicitly in the ICP field.

  • Can I use this play to find companies switching away from a specific CRM?

    Yes — and it’s a strong displacement angle. Pass “previous CRM: [name]” in the context field and the play focuses on companies where the tech stack history shows the specified CRM was recently removed. A company that just moved off a legacy CRM is making a full stack evaluation — not just replacing the CRM but reassessing every tool that was built around it. That’s a wider buying window than a greenfield adoption and often a more urgent one, because the new team is actively dismantling the old infrastructure and replacing it piece by piece.

Related Prompts

Ready to run this?

Connect once, run anywhere. Works in Claude, ChatGPT, n8n, Clay, or any agent connected to Lusha.

Get free access Read the Docs