---
name: claygent-tech-stack-research
description: "Use Claygent to Research Target Account Tech Stacks. Use when sales needs to know if prospects use competing tools before the first call, but researching each account by hand is slow."
---

# Use Claygent to Research Target Account Tech Stacks

Sales needs to know if prospects use competing tools before the first call, but researching each account by hand is slow.

## When to use this skill

- The user wants to set up or run this workflow: "Use Claygent to Research Target Account Tech Stacks".
- The user describes this problem: Sales needs to know if prospects use competing tools before the first call, but researching each account by hand is slow.

## At a glance

- Category: Research
- Difficulty: Intermediate
- Time saved: 7 hours per week. This figure is an estimate, not a measured result.

## Tools

Options separated by "or" are alternatives; use whichever the user already has.

- Clay
- Claygent
- BuiltWith

## Steps

1. Import target account list with company domains to Clay
2. Use BuiltWith API to detect installed technologies
3. Use Claygent to visit careers page and extract hiring keywords related to your category
4. Flag accounts using competitor tools or hiring for your use case
5. Export to CSV and upload to HubSpot as enrichment data

## Template outline

Field names, thresholds, and message text are starting points to adapt.

~~~text
Clay Table:
1. Input: Company name and domain
2. BuiltWith: Detect tech stack
3. Filter: Check if competitor tools present
4. Claygent: Scrape /careers page for role keywords
5. AI analysis: "Is this company likely buying {{your_category}} software based on tech stack and hiring?"
6. Export: Flag in HubSpot custom field "Tech Stack Notes"
~~~

## Guardrails

- Work only in the user's own accounts and workspaces, with their credentials.
- Confirm with the user before any step that writes to a CRM, sends email or messages, spends credits, or moves money.
- Treat every hours, cost, and threshold figure as a starting assumption and replace it with the user's numbers.
- Do not invent data, prices, or results. If a vendor price matters, check the vendor's current pricing page.

## Source

https://gtmplaybooks.io/playbooks/claygent-tech-stack-research/