ACTION_ID: company_tech_stack_enrichment_using_their_stack
NAME: TheirStack: Enrich Company Tech Stack
CATEGORY: Company Enrichment
CREDITS: 0.3

Find the technologies a company uses, via TheirStack. Solid
technographics with a uniquely useful second data source: signals
derived from a company's job postings (e.g. a JD requiring
"3+ years of Salesforce admin experience" is hard evidence the
company runs Salesforce in production, not just a marketing site
that mentions it). Compared to BuiltWith — TheirStack is more
precise but narrower; compared to Floqer native — better coverage
but flat-listed rather than department-bucketed.

Returns the detected stack as both a structured blob and a
comma-separated string, useful for ICP filtering on tech-stack
signals (e.g. "uses Salesforce", "runs Shopify") and for
technographic enrichment to derive insights — integration angles
the prospect already has, modernization signals, or gaps your
product fills.

1. INPUTS

company_domain (type: url, required) — Company Domain
  URL or domain of the company (e.g. "acme.com" or
  "https://www.acme.com").

2. OUTPUTS

all_technologies (type: raw_array) — All Technologies
  TheirStack's full tech-stack result for the company. Nested
  detail per technology (category, vendor, etc.). Use
  formula to extract specific fields, or
  raw_to_structured_array to fan out into rows.

all_technologies_csv (type: string) — All Technologies CSV
  Comma-separated list of technology names detected on the company's
  site — convenient for filter rules ("contains 'Salesforce'") and
  LLM prompts.

3. HOW TO CONFIGURE

Configure Action body:

{
  "inputs": {
    "company_domain": "{{input.company_domain}}"
  }
}

Pass the company URL or domain as `company_domain`.

4. KEY NOTES

- `all_technologies_csv` is the easiest field to filter on for ICP
  rules (`contains "Salesforce"`, `does not contain "Shopify"`).
  Use `all_technologies` (raw_array) when you need nested per-tech
  metadata.
- Two underlying data sources behind TheirStack: standard
  technographic detection plus signal extracted from the company's
  job postings (requirements / qualifications text). The latter
  catches tools that are used internally but not exposed on the
  marketing site — typical for sales-ops / data / engineering
  stacks. If a prospect has hiring-derived hits in
  `all_technologies`, that's a stronger production-use signal
  than a marketing-site detection alone.
- Per-item shape is flat (Name, Category, Parent Category) — no
  FirstDetected / LastDetected dates and no department bucketing.
  If you need historical detection, use BuiltWith; if you need
  pre-bucketed-by-department output, use Floqer native.

5. WHERE IT FITS IN A WORKFLOW

Pattern (tech-stack ICP filter): score or filter companies on
whether they use specific technologies before reaching out — useful
when your product targets companies on (or off) a particular stack.

  input (company domain)
    -> company_tech_stack_enrichment_using_their_stack (returns
       all_technologies + all_technologies_csv)
    -> filter / score on all_technologies_csv (e.g.
       contains "Salesforce", does NOT contain "Shopify")
    -> outreach.

Pattern (technographic enrichment for insights): pull a company's
stack as context for a downstream LLM step that generates
per-prospect insights or talking points.

  input (company domain)
    -> company_tech_stack_enrichment_using_their_stack
    -> llm_models (prompt: read all_technologies_csv and generate
       per-company integration angles or modernization signals)
    -> outreach.

6. WHEN TO USE

Use company_tech_stack_enrichment_using_their_stack to:

  - Filter or score companies on the technologies they use, for
    tech-stack ICP targeting (e.g. "only target companies running
    Salesforce", "exclude Shopify-based companies").
  - Enrich each company with technographic context — feed the
    detected stack into a downstream LLM step to derive per-company
    insights, identify integration angles, surface modernization
    signals, or write personalized outreach copy that references
    a specific technology the prospect already has.

7. WHEN NOT TO USE

Need the broadest possible coverage (e.g. catalog every
technology the site has ever touched), or need historical
detection dates (FirstDetected / LastDetected per technology).
TheirStack doesn't surface either — BuiltWith does.
  -> action-detail/company_tech_stack_enrichment_from_builtwith.txt

Need the detected stack pre-bucketed by department (sales /
marketing / HR / IT security / programming_languages_frameworks /
etc.) — useful when your ICP filter is "uses X *in sales*" rather
than "uses X anywhere."
  -> action-detail/company_tech_stack_floqer.txt

Last updated: 2026-05-14.