Hey, GTM Engineers!

I was talking to a customer and asked what was driving their initiative for Clay.

They said the usual (better data, intelligence, and so on), but exclaimed there’s a mandate from the CEO to integrate AI into everything GTM. “We are behind”.

The same day, a good friend of mine, Oscar Moore, Director of CX at Scratchpad showed me how he was using AI internally, specifically for sales building custom GPTs.

We both introduced each other to new ways of using AI and It compelled us to start a newsletter together. There’s gotta be other killer ideas out there for us to surface and we seek to share them on The Augmented Seller.

Our goal is showcase how sellers can use AI effectively to sell more effectively, efficiently, and to beat quota. We’ll also be showcasing tip and tricks from our reader base and networks.

Oscar dropped the first post: Sales Assistant-GPT

Give me a shout if you have a use case you think would be worth sharing.

Primitives & Reusable Components

Many will say “Clay is hard to learn”. Well, so is a Piano if you don’t learn music theory or how to read sheet music.

It’s actually not that hard to learn the basics. Once you start to realize that Clay is really a collection of building blocks, then its just a matter of figuring out who to interconnect everything into a workflow.

As a part of this process, you can start to build your own reusable components that are specific to your business or use cases.

There’s several key reusable components to know:

1. Tables

2. Recipes

3. Prompts

4. Waterfalls

Let’s dive into each one.

1. Tables

Once you setup a table of automations, you can easily share this with others. Create tables and then allow others to use them with their data set.

For example, we do this with our Claybooks. We have a growing suite of tables you can copy over to your workspace.

Check out this one with Typeform, my Integration of the Week: Enrich, classify, and route leads from Typeform submissions

2. Recipes

Recipes are a collection of columns that you can group together and then reuse from table to table.

For example you can create a “Find LinkedIn Profile” Recipe that would include:

1. LinkedIn Profile Waterfall

2. Claygent to find missing Profiles that the Waterfall misses

3. Aggregated column of profiles from # 1 and # 2

Here’s a walkthrough of how to setup a recipe:

Clay also has a library of pre-built recipes: