Find Company Techstack

Give it a company domain, get back the technologies that company uses.

What it does

• Finds the technology stack used by a company.
• Runs waterfall enrichment — providers are tried in sequence until a result is found.
• Takes a domain only.
• Resolves a stack from a domain. It does not search for companies that use a given technology.

An empty result means no provider had the stack for that domain — not that the company runs nothing.

Use cases

• Qualify integration fit. If your product plugs into a CRM or a data warehouse, knowing which one the account runs decides whether the deal is possible.
• Find displacement targets. Accounts running the competitor you replace are the shortlist for a switch campaign.
• Personalise on the stack. Naming the tools a team already uses shows the outreach was written for them.
• Route leads to the right motion. An enterprise stack and a starter stack need different pitches, and the technographics separate them before a rep does.

How to use it

What technology stack does stripe.com use?

Get the tech stack for these 60 domains. Flag the ones running HubSpot.

Drop any account already running a direct competitor to us, and tell me which
tool it was.

Example prompts

Best prompting practices

• Name the tool. Say find_company_techstack. “What software do they use” is a question several tools will answer, and enrich_organization answers it at double the price.
• Pass a bare domain. stripe.com, not a deep URL.
• Ask for the filter, not the dump. “Flag the ones running HubSpot” is far more useful than “list all technologies for 60 companies”.
• Name the technologies you care about. “Keep only accounts whose stack includes Shopify or Shopify Plus, and tell me the hit rate out of the 50.” A qualification pass needs a rule, not a list.
• Do not expect a reverse search. This tool goes domain → stack. Asking “which companies use HubSpot” is a different question and this tool cannot answer it — source with find_companies first, then confirm the stack per domain.
• Number the steps when it is the confirm stage. Step 1 find_companies to get domains, step 2 this tool per domain at 1 credit each, step 3 keep the matches. Gate step 2 — 50 domains is 50 credits.
• Treat an empty stack as a real answer. “If nothing is detected, mark it unknown — do not infer the stack from the industry.”
• Cap the batch. “Stop after 50 and report credits used.”

Output

{
  "domain": "stripe.com",
  "technologies": ["HubSpot", "Segment", "Cloudflare"]
}

Credits and limits

1 credit per lookup, flat. Run check_credits (free) before a large batch.

Parameters

Related tools

Next steps

• All MCP tools — the full catalogue with credit costs
• TAM Sourcing — workflows that chain this tool into account qualification

Keep learning

Two courses take these tools past the reference page — clustered by GTM job, then chained into workflows.