My firmographic ICP was solid: 50–500 employees, Series A–C, US-based SaaS. I was still sending 800 emails a month to generate 12 demos. The problem wasn't the ICP — it was that I had no idea which of those 40,000 companies in my TAM were actually ready to switch.
Then I started running tech stack filters. Same email volume, 31 demos. Not because I wrote better subject lines. Because I stopped emailing companies that had no reason to care.
This is the operational playbook I wish existed when I started. Not a provider comparison — there are plenty of those. This is a 5-step workflow: how to pull technographic data cheaply, how to map signals to buying intent categories, and what to actually write in the email once you have the data.
Step 1: Pull the Data Without a Six-Figure Contract
Most articles mention HG Insights and ZoomInfo as the category leaders, which is true and also unhelpful if you're not ready to spend $30K/year. Here's what actually works at different budget tiers.
Free tier: BuiltWith has a free lookup that covers web-facing technologies — JavaScript libraries, analytics tags, CDNs, CRM embeds, chat widgets. For SMB targeting this is surprisingly good. I built a 1,200-account list of companies running HubSpot forms combined with a Drift chat widget using BuiltWith's free Technology Lookup plus their paid list builder ($299/month). The free API caps at 2,000 lookups/day — enough for a solid pilot.
Mid-tier ($500–3K/month): Clearbit enrichment (now owned by HubSpot) returns ~70 technology attributes per account via its company enrichment API. Not as deep as HG Insights, but the data quality on mid-market SaaS companies is better than I expected — I cross-checked 200 accounts against BuiltWith and Clearbit agreed on the CRM field 84% of the time.
Apollo includes technographic filters in its base plan. Coverage is inconsistent — strongest for US companies with 10–500 employees, weakest for enterprise and non-US accounts — but for a combined firmographic + technographic filter in one UI, the price-to-coverage ratio is hard to beat.
People Data Labs (PDL) has a company enrichment API that returns a tech array. At $0.003–0.006 per call depending on volume, you can enrich 50,000 accounts for under $300. It's the most programmable option for teams with an engineer who can write a simple script.
Enterprise tier: HG Insights is category-best for enterprise accounts and IT spend data. Their 14-day trial uses real data — worth running even if you don't buy, just to calibrate what you're missing with cheaper sources. 6sense and ZoomInfo both include technographic data but are expensive as standalone products.
Step 2: Map Tech Signals to Buying Intent — Not All Signals Are Equal
I categorize signals into four intent buckets before building any list:
| Signal Type | Example | Intent Level | Typical Sales Cycle |
|---|---|---|---|
| Direct competitor installed | Uses [Competitor X] | 🔴 High | 3–6 months (displacement) |
| Adjacent tool, no integration | Has Salesforce, no Outreach | 🟠 Medium-High | 2–4 months (add-on) |
| Missing tool your product replaces | No CDP, no enrichment layer | 🟡 Medium | 4–8 months (greenfield) |
| Complementary stack signal | Uses Segment + Amplitude | 🟢 Contextual | Depends on pain signal |
Competitor displacement is the highest-ROI bucket. I ran a displacement campaign targeting 340 accounts running a direct competitor (identified via BuiltWith + Clearbit cross-check). Reply rate was 11.4% vs. 3.2% for my control send — same subject line structure, different body copy tied to the competitor.
The critical mistake in displacement campaigns: emailing the decision-maker first. Wrong. Start with the champion. The IT admin or RevOps person running the current tool knows its limitations better than the VP buying it.
Integration-fit signals are underused as negative filters. If you sell a product that integrates natively with Salesforce and your ICP actually runs HubSpot, that's a negative signal — filter it out. I eliminated ~18% of my TAM this way and reply-to-demo conversion went from 31% to 44%, because I stopped booking calls with people whose stack I couldn't connect to.
Step 3: Build Three Lists, Not One
Most teams build one big ICP list and blast it uniformly. Segment into three lists from the start instead:
List A — Displacement: Accounts running a direct competitor. This list gets your most direct, problem-forward messaging. Short emails, named competitor, specific migration story.
List B — Integration Fit: Accounts whose stack aligns with your integration layer. Messaging here is about reducing friction: "You already use X, this plugs in within an hour."
List C — Greenfield: Companies in your ICP that are missing the category entirely. Longer educational sequence, higher effort per account, best for enterprise AEs running multi-thread campaigns.
I allocate 60/30/10 across A/B/C for SDR bandwidth. List A moves fastest; List C has the biggest upside per account but the longest payback period.
Step 4: Write Signal-Specific Messages
Generic outreach doesn't survive contact with technographic data. Each signal type needs different framing.
Template A — Competitor displacement:
Subject: [Competitor] → [Your product]
Hey [First name], noticed [company] is running [Competitor]. A few of our customers came from there — the migration typically takes [X days], and the main reasons they switched were [specific gap 1] and [specific gap 2].
Worth a 20-minute call to see if the switch makes sense for your setup?
Name the competitor explicitly. Cite a real migration timeline. Name the actual gaps — not vague "limitations." I tested naming vs. not naming the competitor across 200 sends: named version got 9.1% reply rate, unnamed got 3.8%.
Template B — Integration fit:
Subject: [Your product] + [Their tool]
Hey [First name], saw [company] is running [detected tool]. We built a native integration — [specific thing it does] in about [time]. A lot of [their tool] teams use us to [specific outcome].
Happy to show you the integration if it's on your radar.
Template C — Missing tool / greenfield:
Don't pitch your product first. Lead with the problem the missing tool was meant to solve. Ask a diagnostic question. Only mention your product after they reply and confirm the pain exists. Greenfield accounts need educating before they need selling.
Step 5: Layer Intent Data to Prioritize Sequencing
Technographic data tells you who fits. Intent data tells you who's ready. Layering them is where the real acceleration happens.
Bombora is the standard for third-party intent signals. Run your List A and List B accounts against a Bombora intent topic surge report. Accounts showing both technographic fit and active intent research go into a 5-day fast sequence (Day 1, 3, 5). Everyone else goes into a standard 14-day sequence.
I tested this split across 680 accounts: the intent-filtered group had a 4.1x higher demo rate in the first week compared to non-filtered accounts within the same tech segment.
Clay is the best tool I've found for orchestrating this multi-source enrichment workflow without writing custom Python. You can pull from PDL, Clearbit, and Bombora in a single table, write conditional logic for segmentation, and push directly to your CRM or sequencer. What used to be a multi-day data ops project now takes about 4 hours to set up once you have your source credentials.
Provider Comparison at a Glance
| Provider | Best For | Technographic Depth | Price Tier | Free Option? |
|---|---|---|---|---|
| BuiltWith | Web-facing tech stack | Medium | Low | Yes (limited API) |
| Clearbit | API enrichment, mid-market | Medium | Mid | No (trial) |
| Apollo | All-in-one prospecting | Medium | Low–Mid | Yes (limited) |
| PDL | Programmatic enrichment | Medium | Low (API) | Pay-as-you-go |
| HG Insights | Enterprise IT intelligence | Deep | High | 14-day trial |
| ZoomInfo | Enterprise, broad coverage | Deep | High | No |
| 6sense | Intent + tech combined | Deep | High | No |
| Cognism | EMEA + US, compliance-focus | Medium | Mid–High | Trial |
What I Actually Use
For the full workflow described here: BuiltWith for initial list building (free API + $299/month list builder for bulk exports), PDL API for programmatic enrichment at scale, Bombora for intent scoring, and Clay to wire it all together into a single enrichment table with conditional segmentation logic.
The full stack costs roughly $1,200/month across all four tools. The first displacement campaign I ran with this setup generated $84K in pipeline in 6 weeks.
For social profile signals specifically — when I need to validate job changes or cross-check Twitter and Facebook presence for contacts before adding them to a high-touch sequence — Ziwa has been faster for me than PDL's direct API for those particular lookups.
Start with BuiltWith free + Apollo filters. Build your first displacement list. Write one competitor-specific template using the format in Step 4. Send it to 50 accounts. If you don't hit at least a 7% reply rate, the signal mapping in Step 2 is wrong — not the email.
Top comments (0)