
SaaStr Runs 4 AI Sales Vendors but Built Its Own ABM Tool
EntrepreneurshipSaaStr may be the most aggressive buyer of AI sales tools in SaaS, and it still built its own tool for the accounts that matter most. The reason is not that the vendors fall short. It is that no vendor can read all the places SaaStr’s customer data lives, and reading that data is about to get more expensive.
What Happened
Jason Lemkin laid out SaaStr’s current AI go-to-market stack in a post on why the company built its own AI account-based marketing tool. Monaco runs cold outbound and booked a meeting with the right buyer at Anthropic on day one. Artisan, detailed in SaaStr’s earlier AI agent playbook, has run warm outbound for over a year and is credited with millions in closed-won revenue. Agentforce runs win-back campaigns with a 72% open rate. Qualified, the inbound agent, has closed more than $2M in the past year.
Next to those four vendors sits an internal pitch generator. A rep types in a company name, and the tool pulls Salesforce history, event attendance, and newsletter engagement to draft a custom sponsorship pitch. That pitch covers how many people from the company attended SaaStr AI Annual, which executives read the newsletters, past sponsorship levels and ROI, and blog and podcast mentions. It grew out of a renewal agent Amelia built in about half a day on top of 10K, SaaStr’s internal AI VP of Marketing, with decks generated through the Gamma API.
Why It Matters
The build decision comes down to data surface area. Most AI SDR vendors read only Salesforce contacts, accounts, and activity. SaaStr’s account picture spans six systems: Salesforce, Bizzabo, Marketing Cloud, WordPress, a podcast archive, and Momentum/Qualified. “We couldn’t get that from third-party services,” Lemkin writes. “It just can’t, today, it can’t be bought.” No vendor is going to build six custom connectors for one customer.
The second factor is cost. Lemkin notes Salesforce plans to meter agent API calls through Flex Credits. 10K already makes about 35,000 Salesforce API calls a day, so every vendor reading the CRM deeply will get more expensive to run. One internal tool reading the data once beats several vendors each paying to read it separately.
The renewal version of this tool produced the result Stack Archive covered in September: silver-tier sponsors replied at higher rates than diamond once they got custom decks. The team went from about 5 custom renewal decks to 20 to 30.
What This Means for Founders
SaaStr’s split is a usable template. Volume goes to vendors: four tools handle cold, warm, win-back, and inbound at scale. Depth stays in-house: the internal tool handles a small set of named accounts where cross-system context wins deals. Two process rules make it work. A human approves the narrative before anything is generated, because fixing a story takes minutes while fixing a finished deck takes far longer. And the first touch stays short, with the detailed pitch saved for the follow-up after the prospect replies.
This also continues SaaStr’s pattern of pruning and specializing its agent fleet, which Stack Archive tracked when it cut from 30 agents to 20.
The So What
The buy-vs-build line for AI sales is not about model quality. It is about how many systems hold your customer context. If the useful signal lives entirely in the CRM, buy. If it is scattered across event, content, and engagement tools no vendor will integrate, build a narrow internal tool for top accounts and let vendors handle the long tail. With CRM API metering coming, that line will keep moving toward build.
Source: SaaStr
Content created with AI assistance and reviewed for accuracy.
Join the conversation
Stack Insiders is our free community for readers who want to go deeper — share resources, ask questions, and connect with others across every vertical we cover.
Join Stack Insiders →