LeadHaste
IntermediateNo variables to fill — paste & go

Write a cold email from a prospect's tech stack

Converts raw technographic data into ranked implications about how the prospect operates, then writes a sub-85-word email that leads with the implied friction instead of reciting their tool list. It draws the line between insight and surveillance, and tells you when your stack data is too generic to use.

The prompt
You are a technographic outbound specialist. You've built campaigns off BuiltWith exports and Clay tech-stack enrichments, and you know the difference between using stack data and being creepy with it. The rule: the email should demonstrate understanding of what their stack implies, not surveillance of what they've installed. 'I see you use HubSpot' is creepy trivia. 'Teams running HubSpot with an outbound motion usually hit the same wall with sequencing' is insight.

I'm going to tell you what's in a prospect's tech stack. Do this:

1. Read the stack: what does this combination of tools imply about their motion, maturity, team structure, or likely friction points? Three insights max, ranked by confidence.
2. Write ONE cold email, under 85 words:
- Opens with the implication, never the tool list. The stack stays invisible unless naming one tool is essential to the point.
- Connects the implied friction to my offer with one proof sentence.
- Interest-based CTA.
- Banned: 'I noticed you use', any list of more than one tool from their stack, trash-talking a tool they chose (they picked it — insulting it insults them), and integration-pitch framing unless I actually sell an integration.

Also give me a lowercase subject line about the friction, not the tools.

Before you write anything, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time:
1. What tools do you know are in their stack, and how do you know (enrichment tool, job posting, case study)?
2. What do you sell, and where does it sit relative to those tools — replaces one, connects them, fills a gap?
3. Who are you emailing (role, seniority)?
4. What's your proof point with a company running a similar stack?

Once you have my answers, write the email. If the stack data is too generic to support a real implication (every company uses Slack), tell me which missing data point would make the signal usable.

How to use it

  1. 1

    Copy the prompt into Claude, ChatGPT, or any LLM.

  2. 2

    Answer with the specific tools and your data source — a Clay technographic enrichment or a tools-mentioned job posting both work.

  3. 3

    Check the top-ranked implication against what you know of the market before trusting the email.

  4. 4

    Template the pattern per stack combination: one email per meaningful tool pairing, reused across every prospect matching it.

Best practices

  • Combinations beat single tools — 'Salesforce plus a data warehouse plus no CDP' implies far more than any one logo.

  • Job postings are an underrated technographic source: 'experience with Marketo required' is stack data with a hiring signal attached.

  • Never open with the tool name even when it's accurate; leading with the implication reads as expertise, leading with the tool reads as scraping.

  • Refresh stack data before sending — technographic databases lag, and referencing a tool they churned from six months ago burns the email.

Example: what this looks like in practice

A RevOps consultant pulls a Clay enrichment showing a 150-person SaaS prospect running Salesforce, Outreach, and Snowflake with no visible attribution tooling. The prompt's top implication: a data-mature team whose pipeline reporting likely lives in hand-built dashboards someone maintains manually. The email to the VP RevOps opens 'Teams with a warehouse and a full sales stack usually end up with one person quietly owning the pipeline dashboards everyone depends on', names no tools, cites a similar client who cut reporting time from days to hours, and asks 'Sound familiar?'. Subject: 'the dashboard person'. Three of eight similar-stack prospects reply.

Best fit

Roles
SDR / BDRAccount ExecutiveRevOpsFounder / CEO
Company size
Startup (1–10)SMB (11–50)Mid-market (51–500)
Audience
B2B
Industries
SaaS
Works with
Any LLM
Difficulty
Intermediate

This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.

Apply for a Pilot Spot →
Prompt FAQ

Frequently asked questions

Technographic sources include BuiltWith and Wappalyzer for website-detectable tools, Clay enrichments that aggregate multiple providers, job postings that name required tools, and case studies published by the vendors themselves. Job postings are often the freshest source — a company hiring for 'Marketo experience' is telling you their stack today, not six months ago.