LinkedIn and 3rd parties use essential and non-essential cookies to provide, secure, analyze and improve our Services, and to show you relevant ads (including professional and job ads) on and off LinkedIn. Learn more in our Cookie Policy.
Select Accept to consent or Reject to decline non-essential cookies for this use. You can update your choices at any time in your settings.
To continue celebrating 100+ integrations in Clay this week...
Here's our Head of Education's TOP 5 🖐 use cases with Clay Integrations!
Thanks for the breakdown Yash Tekriwal 🤔!
Check out all 100 and more at clay.com/integrations!
#100ClayIntegrations
Hey, it's Yash, Head of Education over here at Clay. We've got some exciting news. Clay now integrates with over 100 different tools. In light of that, I wanted to take a few seconds to go over five of my favorite use cases that we've seen emerge over the last six months and what they mean for how you should be thinking about what's possible for you to do. And Clay use case number one, clays custom Salesforce package. Part of what I love about this use case is that we're now opening up the power of Clay. Two, SDRS and BDRS. I think something that people get confused on all the time is that they think clay is a tool for salespeople. And what we've actually seen consistently over the last few years be always true is that clay is actually best used on its own in the hand of revoked professionals, sales OPS professionals, or marketing OPS professionals. But that's really tough because a lot of teams aren't natively equipped to just let Rev OPS, Mar OPS, and sales OPS command the entire data workflow. It's much more natural. Have people working in conjunction with each other, and no matter what you do, you're going to need just in time data at the SDR, BDR, or marketer level when you want more information for a custom use case you're going after. So that Salesforce package that we've built is our first step into this foray of enabling that kind of data puzzle solving across the org, built for the roles that matter the most #2 always on AI web scraping. This is a super exciting use case we just started implementing. Recently for a customer that I actually can't name on this video. But what I'm going to say about that is this customer wanted to keep track of all of these evolving things that change rapidly over the course of multiple weeks or months. Think about the total number of articles you might have on your help center. Think about the total number of blog posts you might have updating and informing people about your product. Those are really important signals that traditional data providers don't gather for you. And when that signal reaches a certain threshold or level. You really care about reaching out with your potential solution because now that person has just entered the precipice or threshold for your tool to be as valuable to them as possible. I know I'm being super vague here, so I'm just going to leave it at that and remind you that client is one of the craziest things you can use in Clay, even after 100 plus different integrations. Then we'll move on to use case #3 intent signals. This is just the beginning of what we're doing with Clay, but I'm going to specifically call out job changes and champion. Monitoring here because I think this is a beautiful, beautiful addition to the clay library of integrations. It's such low hanging fruit for your business when someone that you've already turned into a believer at a company or customer that currently uses your product, then leaves and goes to a new company or tool where they should be taking your tool along with them to their next role. Most of the time, these champions want to be advocating for the tools that they're most comfortable using at their company, but they've also got a million things that they have to worry about and starting a new role. If you can proactively reach out to these folks and let them know ahead of time that you're with them for that journey and you're excited to help them advocate or bringing your solution to their new company, it gives them an ally and starting their new role and it gives you a new customer that you can hopefully leverage to continue growing your presence. Use case number four, that's 84 bad e-mail rewriting. This is a little bit selfish. This is one that I'm currently still building internally because I think it's interesting and useful, but you guys probably feel this issue all the time. You get horrible. Cold outreach from people who it seemed like if they just taken a second of time would realize that the copy they wrote for you is absolute trash. Now a lot of you probably know you can be using tools like Clay to actually write better copy for these folks. And So what I've started to prototype and is just really a fun demonstration of what's possible when you use HTTP API, Zapier and make etcetera, is we now have an internal e-mail address that people can forward bad messages too. And then once that e-mail address gets a new message that someone has forwarded to them. We use AI to extract the original text of that message. We then enrich social profiles, and we figure out the score of that message based on all the available data across personalization, relevance, value, prop, and conciseness. And then we give that person a score of all four of those categories and a suggestion on all of the possible personalizations they could have just used automatically with a tool like Clay. And I don't think there's a real practical use case to this beyond reverse selling people who reach out in poor ways to us. But I love how it still touches on the creativity of what's possible. In clay, which leads me to use case #5 personalized meme creation. This is an old but gold use case for clay because it again taps into anything is possible if you know how to turn it into a process with clay. And I love love, love that people are still throwing parties over the ability to create personalized custom AI memes based on people's social profile URLs based on people's past job experiences, thought leadership research. You can really do whatever you want to and a fun bonus fact for this is that. Someone had so much fun with the personalized roasting of people's social profile URLs that in the Clay office now we actually constantly have a stream of different people's LinkedIn profiles being roasted just running across our message board every single day. And it adds a little bit of fun and flair to the company culture. So those are the top five things I'm most excited about with our hundred plus integrations announcement. Curious what other use cases people have seen and what people are most excited for us to continue building into 2025. Thanks, guys.
1 and 2 are my favorites! This is an awesome video, Yash. We're in the very tippy top percentile of Claygent users according to our Clayback.
Honestly the most important thing you said here though is about the optimal end user of Clay. I've seen ops folks absolutely thrive when they start tinkering. It takes time to get great, but if it's in your nature, it's a lot easier. Also let's be honest, it's just a fun way to spend your time 😂.
💻 Short Form Video Services
🌈 Clay Club Midwest host
🦄 Former FinTech Digital Marketing Director
🎯 Signal Based Outbound Led Allbound
📈 B2B/B2C SaaS ABM GTM and Demand Generation Consultant for LTV >$5k
The Salesforce integration unlocks a lot of use cases for larger organizations. It can be a game-changer for SDRs/BDRs out there.
Paired with in-time data, we’ve been able to minimize manual data entry for Sales & Marketing teams for clients at SalesCaptain.
Keep it up Yash & Clay team!
Exciting stuff coming up! For me, the YouTube transcript integration is such a cool feature - still exploring the best use cases, but loving it so far!
I talk about the employee experience 🌟 | Recruiting Ops Advisor | Meditate! 🧘♂️
2dClay aside, the delivery and breakdown of this content was 🔥. How do you prep for these video's Yash Tekriwal 🤔. Super impressed