Use the Technology change signal to get notified when companies in your target segment adopt or replace tools in their stack. This is a strong buying signal because stack changes often trigger vendor reviews, workflow updates, and new purchasing decisions.
Billing for this signal is 100 credits per identified signal.
Learning objective
By the end of this tutorial, you’ll know how to create a Technology change signal agent, define which technologies and companies to monitor, choose when alerts should trigger, set a daily identification limit, and prepare your team to act on those signals quickly.
Why this matters
When a company adds or swaps a tool, it usually means the team is actively rethinking processes, integrations, and budget. That makes it an ideal time to reach out with a relevant message that shows how your solution fits into their evolving setup.
Prerequisites
You should already know how to access the Signal agents area in lemlist.
You should already have a clear idea of the technologies and company segment you want to monitor.
You should already know who on your team should review or act on identified signals.
Core lesson — step-by-step workflow
Phase 1: Start a new signal agent
Go to Signal agents, then click Create signal agent to open the builder.
In the Buyer intent category, expand the section and select Technology change as the signal to detect.
Phase 2: Configure the technology change signal
Enter a clear agent name, then add the technologies to monitor in the technology field. You can add multiple technologies depending on the tools most relevant to your targeting strategy.
Choose when to check. You can either trigger the signal when a new technology is detected, or set it to trigger X months before the anniversary date if you want to time outreach around likely contract renewal windows.
This is an important decision:
When new technologies are detected is best if you want to react immediately to change.
X months before the anniversary date is best if you want to get ahead of renewal conversations and competitive evaluations.
Phase 3: Define the scope to monitor
Select the audience scope for the signal agent. You can monitor All segments, a Company list, or a Specific segment. This lets you align signals with your ICP instead of tracking the entire market.
Set your maximum number of signals identified per day. This limit helps you control volume and budget while keeping the signal flow actionable.
Billing for this signal is 100 credits per identified signal, so setting a daily cap is a good best practice when you are testing a new signal agent.
Phase 4: Decide how signals should be processed
Choose what should happen after a signal is identified. You can review signals manually or create tasks for your team automatically. If your workflow depends on sales reps reviewing each opportunity, task creation is usually the best option because it keeps follow-up structured and visible.
Phase 5: Review and launch the signal agent
Review the summary to confirm the signal type, technologies selected, timing logic, billing, processing method, and scope settings.
lemlist processes these signals daily, so once the signal agent is live, identified companies will start appearing as new opportunities to review and contact.
What signal details you’ll see
Each identified Technology change signal includes the key company context your team needs to act fast:
Company
Location
Company size
Industry
Technology detection date
Practical application
Technology-change signals are most useful when you pair them with timely, relevant outreach. Instead of sending a generic prospecting message, reference the new tool and explain how your product complements the company’s new setup.
Real-life examples
A SaaS company installs HubSpot after relying on spreadsheets.
A sales team replaces Outreach with another outbound tool.
A startup adds a new enrichment platform or CRM to its stack.
What this usually means: the company is changing priorities and improving workflows. That’s often the moment when teams are most open to discovering complementary tools, better integrations, or smarter processes.
Email example
Here’s a simple outreach template you can adapt:
Subject: Noticed {{companyName}}{{newTool}}
Hey {{firstName}}
Noticed {{companyName}}{{newTool}}{{newTool}}{{processArea}}
{{referenceCompany}}{{impactMetric}}{{relatedProcess}}
Want me to show you how they approached it?
Try it yourself
Reference the newly detected technology in the first line.
Tie that technology to a business process the buyer cares about.
Use a relevant customer example or proof point.
Keep the CTA light and consultative.
Troubleshooting & pitfalls
Issue: You’re getting too many signals
Root cause: Your scope is too broad or your daily identification limit is too high.
Narrow the scope with filters like industry, location, and company size.
Use a company list or specific segment instead of monitoring all companies.
Lower the daily signal cap to control both volume and credit usage.
Issue: The signals aren’t relevant to your ICP
Root cause: The selected scope or technologies are too generic.
Choose only technologies that strongly correlate with your best-fit customers.
Use a company list or specific segment instead of monitoring all companies.
Review whether your filters reflect your actual target market.
Issue: Sales reps don’t act on the signals quickly
Root cause: Signals are identified, but no follow-up workflow is assigned.
Use Auto-create tasks instead of relying only on manual review.
Assign the right owner or fallback owner.
Add clear instructions so the next step is obvious for the team.
Issue: Credit usage is higher than expected
Root cause: Each identified signal costs 100 credits, and the signal agent may be finding more companies than planned.
Start with a lower daily cap while testing.
Tighten the scope before scaling up.
Monitor how many signals are identified each day and adjust limits as needed.
Best practices
Start small with one or two high-intent technologies before expanding.
Use specific segments instead of broad monitoring when testing signal quality.
Match your outreach message to the detected technology and likely workflow change.
Review signals daily so you can contact companies while the stack change is still fresh.