Outbound research: from a domain to a first line that lands

"I saw you're hiring a lot of engineers" is not research. Neither is "congrats on the Series B", or "I noticed you use HubSpot" when what you actually noticed was a tracking pixel on the marketing site. Prospects have read all of these. The tell is that none of them are specific enough to be wrong.

A first line that lands has one property: the prospect reads it and thinks this person looked at something real. Vendor evidence is one of the cheapest ways to get there, because the thing you looked at is a page the prospect's own company published.

One call, thirty seconds

curl "https://api.vendorstacks.com/v1/check?url=meridian-fleet.com" \
  -H "Authorization: Bearer $VENDORSTACKS_KEY"

{
  "domain": "meridian-fleet.com",
  "found": true,
  "vendor_stack": {
    "sms_messaging": ["twilio"],
    "support_cx": ["zendesk"],
    "payments": ["stripe"],
    "observability": ["datadog"]
  },
  "sms_messaging_evidence": [
    {
      "vendor": "twilio",
      "source": "https://meridian-fleet.com/legal/subprocessors",
      "quote": "Twilio Inc. — SMS and voice notifications to end users"
    }
  ],
  "subprocessor_urls": ["https://meridian-fleet.com/legal/subprocessors"],
  "vendor_confidence": "high",
  "scanned_at": "2026-07-11T08:41:55Z",
  "credits_used": 1
}

Three things in that response do work for you. The stack tells you what they run. The quote tells you what they said about it, in their own words. The source URL means you can open the page and read it before you write anything.

Do open it. It takes twenty seconds and it's the difference between citing a fact and citing a field.

What the stack actually tells you

Reps under-read this data. A vendor list isn't just a list of logos; the combination implies a shape.

• An SMS vendor plus a payments vendor usually means transactional messaging — receipts, delivery notifications, one-time passcodes. That's an operations problem, not a marketing one, and the buyer is different.
• A support platform plus an SMS vendor suggests two-way customer conversation, which means volume, which means somebody has an opinion about per-message cost.
• An observability vendor in the stack at all signals an engineering org mature enough to buy infrastructure. Your demo should assume technical questions.
• A long stack with a gap in your category is the most interesting shape of all: a company that buys tools freely and hasn't bought yours.

The 24 categories give you enough to form a hypothesis before the call. Not a conclusion — a hypothesis you can test in the first two minutes.

The message structure

Four moves. Keep the whole thing under 90 words.

1. The observation, sourced. Name what they run and where you saw it. One sentence.
2. The inference, offered as a question. What that stack usually implies, phrased so they can correct you.
3. The relevance. One line on why that matters for what you do. Not a pitch — a reason this email arrived today.
4. A small ask. A question they can answer in a sentence beats a meeting request they have to schedule.

Assembled:

Subject: Twilio + Stripe at Meridian

Your subprocessor page lists Twilio for SMS notifications alongside
Stripe — which usually means transactional sends: receipts, delivery
alerts, OTPs.

If that's right, the bill tends to scale with order volume rather
than with anything you control. Is per-message cost something your
team is actively looking at, or is it noise at your volume?

Happy to send the two-line version of how teams usually cut it —
no meeting needed.

Note what it doesn't do. It doesn't claim to know their spend. It doesn't assert that they have a problem. It states one verifiable fact, draws one reasonable inference, and invites a correction. If the inference is wrong, the prospect gets to tell you — and a reply that says "actually it's all marketing campaigns" is a great outcome.

The rule: cite, never bluff

The whole approach depends on the observation being true. Two ways reps break it:

Inflating the stack into a claim about the business. Knowing a company uses Twilio does not tell you their message volume, their contract terms, their renewal date, or whether they're unhappy. Write a line that implies you know any of those and the first reply will expose it. Stick to what the source says.

Treating a miss as a fact. When a lookup returns found: false, that means no public evidence was located — not that the company uses nothing. "I noticed you don't have an SMS provider" is a sentence you should never send off a miss. It is very likely wrong, and it is unrecoverable when it is.

The good news on misses: they cost nothing. Lookups are 1 credit each and you're billed for successful results only, so a research pass over a list of 200 accounts costs less than the coffee you drink during it.

Doing it at list scale

For a single account, one call before the call. For a list, invert it: start from /v1/prospect?vendor=Twilio&category=sms_messaging&page=1, which returns entities that name a given vendor, ten per page, one credit per result. That gives you a list where every row already has a citable observation attached — see the displacement playbook for how to sequence it. The public vendor pages are a free way to see which vendors have meaningful coverage before you spend anything.

Research isn't the bottleneck it used to be. One call, one quoted line from the prospect's own site, one honest inference — and you've written an opener that a competent buyer will actually finish reading.

Get a key with 25 free credits, run it on the five accounts you're working this week, and see whether the evidence gives you a better first line than the one you had.