Jason says you may be recommended as a vendor less often than you think because different LLMs have different memories, context, and data access. He recommends a bank of ten third-party agents to ask weekly what they would use in your category, then attack answers where you lose.
Jason says Muse gives you a virtual machine, an embedded browser, and scheduled tasks, so it can run competitor tracking or AEO audits daily. He used it to find sponsor clips and schedule a two-week A/B test in five minutes; it is an extra layer for tasks they do not want to build in 10k.
Jason says early AI outbound emails lacked first-party data and leaned on basic web scraping or Salesforce records. Once agents know SaaS-specific history—such as prior sponsorships and lead ROI—the emails get much better than Amelia's self-built prospector. That first-party context makes agent emails feel informed rather than generic.
The agent researches an inbound lead, writes a custom introduction, picks relevant packages, and generates a unique prospectus link plus meeting booker. Amelia shows Base44, where this flow helped a real lead book a meeting within ten minutes. This replaces the usual quick reply and hope.
Amelia says the agent sends the prospect a version of the research, then if they book, it sends her a brief ten minutes before the call. This prevents her from forgetting account details like Wix owning Base44; she no longer manually checks each call for context.
Jason says their No. 1 outbound motion is feeding an agent a list of all historical customers and asking for each customer's top three or four competitors plus domains. Then their outbound agents relentlessly target those competitor and lookalike accounts. He calls it a perfect use case for starting outbound.
Amelia says agents do not care about images or design; they care about verifiable facts like public pricing, renewal rates, and logos repeated year over year. Muse can help create robots.txt or llms.txt so agents read standardized facts. Testimonials only go so far because agents do not treat them as facts.
Amelia says with 21 agents and 3 humans, inbound emails, outbound from four tools, renewals, and support were falling through cracks. They built Prospector as one queue so an agent can filter, route, and follow up until each item reaches its goal, preventing handoffs from silently dropping.
Jason explains their four outbound platforms each send autonomously, but Prospector pulls replies through APIs into one queue and starts a timer. It is not unifying initial sends; it unifies responses. The agent drafts follow-ups and reminds them when to ping again or try another contact.
Jason advises picking one outbound or CX agent, pushing it as far as possible on a subset of work, then adding another only when gaps appear. He warns against buying every tool in their stack, says best-of-breed still matters, and admits they broke their own add-one-remove-one rule.
Amelia frames agent-led growth two ways: using AI agents like 10k to run GTM, and positioning so other agents recommend SaaStr when users ask for events or tools. The second path is now gaining traction, and she says getting picked by agents is purposeful in how they have done it.
Amelia asked Muse to look at SaaStr's sites and prompt different LLMs cold, logged out, with its own questions to see whether SaaStr surfaced. This avoids biased results from your own agent and reveals confusing facts across event years; she warns many social AEO tips come from agencies selling products.
