• claymation
  • Posts
  • Finding a Company's Tech Stack w/ Clay

Finding a Company's Tech Stack w/ Clay

11 sources you can mine & 3 company examples

May 06, 2024 • Estimated Reading Time: 5 minutes

A vibrant and playful clay scene depicting a large computer with exposed colorful clay components such as wires, motherboards, and processors. A cute green clay monster is intensely examining these components through a large clay magnifying glass, highlighting its curiosity. The monster's eyes are detailed, focused through the lens of the magnifying glass, giving a sense of detailed inspection. It holds the magnifying glass in one hand, while the other hand appears to be adjusting or tinkering with the technology. The background is simple to focus attention on the intricate, engaging interaction between the monster and the tech.

👋 Hey, Claymaker!

Glad you’ve joined me on this journey to master Clay together. I’m a GTM Engineer at Clay. We do a combination of solution engineering, consulting, teaching, and selling.

My goal is to share what I’m learning to help you master & unlock creativity with Clay.

Importance of technographics

Looking back, I hate to think how many hours, weeks, months that have added up trying to figure out a company’s tech stack.

There just wasn’t a good way to do this manual research at scale.

However, it’s super important for some companies to:

  1. Prioritize the right accounts (best fit, highest potential, most likely to convert)

  2. Disqualify accounts

  3. Personalize value prop

Builtwith is one datasource that you can use

Let’s dive into some creative ways of using Clay to mine a company’s tech stack.

Claygent - your AI agent

You can give Claygent missions and point it to a number of different sources that it can use to learn from, search for keywords, and summarize information.

Think of it as your assistant that can go off and execute the manual research for you.

Example: Finding a company’s documentation page

This is what the results look like for some tech companies I plugged in.

Technology in documentation

Now we can use it to go to the documentation page to learn about what technologies are documented:

And get the following lists:

Helpful? Share with someone on your team;

Additional sources to mine

The same thing can be applied to a list of different resources where you can mind tech stacks:

  1. Developer portals

  2. Api documentation

  3. Readme files

  4. Getting started guides

  5. Implementation guides

  6. Deployment guide

  7. Public GitHub pages

  8. Engineering blogs

  9. Third party data subprocessors

  10. Job postings

  11. Linkedin Profiles

Company examples

The following are some interesting ones. (I used to work at Chainguard. You can learn more about Auth0’s use case on the 20Growth podcast. And, know a bit about API security from working in cyber for 5 years.

  • Chainguard’s ideal customers are those that deploy their software via containers into their customer’s environment. Claygent can automate the manual research of going to each deployment guide to figure that out.

  • Auth0’s ideal customers are those that are migrating from one technology stack to another. They could use Claygent to compare keywords in Linkedin profiles to keywords in job postings.

  • Traceable AI, an API security company, I suspect prefer companies who have an external facing API.

✌️That’s it for now.

Let’s connect on Linkedin or email me ([email protected]) if you need help with Clay.

Reply

or to participate.