The Agents #006: We Run SaaStr AI on 3 Humans and 21+ AI Agents. Here’s Every Agent, Agent by Agent, With the Numbers.

We run SaaStr AI on 3 humans and 21+ AI agents. At SaaStr AI 2026 we did something we’d never done before: we pulled up the back ends of our top agents live, in front of the room, and went through how they really work. Not the demo version. The real version, including the parts that break.

This is that walkthrough, agent by agent, with the numbers and the stack behind each one. A few of these were built on Replit. A few are third-party tools we trained. Collectively they’ve handled multi-millions of interactions. Here’s what each one does, what it runs on, and the lessons that surprised even us.

The single biggest theme across the whole stack: almost none of these started as agents. They started as a dashboard, a project management tool, a website. They became agents because we kept showing up to work with them every day.

Welcome to The Agents Episode #006. Live from SaaStr AI 2026!

10K: Our AI VP of Marketing

10K runs our marketing. He owns the number, tracks daily revenue across all of go-to-market, handles forecasting, knows every campaign’s performance in real time, and pushes us our top three marketing ideas every single day.

He did not start that way. In January he was a dashboard. That’s it. We were tired of copy-pasting numbers out of Salesforce and Marketo into a Notion doc, so we built a simple dashboard to pull it together. For a few weeks that’s all he was.

The back end:

**Built on:**Replit, first commit January 2026. He’s barely four months old.**Commits:**Close to 1,000. We run 7 to 8 commits a day between the two of us.**APIs wired in:**The most of any agent. This is what “headless Salesforce” means in practice. We hit Salesforce directly through the API without ever logging in. Bizible for ticketing. Marketo for marketing automation. Slack for daily reports. Clerk for auth.

The top three things 10K does for us, in order:

He’s a living dashboard. We talk to him. We ask how many VCs are coming, how many CMOs registered for a summit, which sessions are tracking light so we can move them. The number is just the number, because it’s pulled straight from the API. There’s no argument between sales and marketing about whose figure is right, no one pulling the wrong dates to make a campaign look better than it was.

He forecasts, which matters enormously when you’re selling time-sensitive inventory like event tickets.

He generates ideas. Last week 10K started writing better marketing emails than our humans. When we asked the CEO of Replit how that happened, he didn’t quite know. When we asked their head field engineer, he didn’t quite know either.

One thing worth trying yourself if you do nothing else from this whole post: spin up a Replit, Lovable, or V0 instance, connect it to Salesforce, and tell it to build the dashboard or analysis you can’t get out of Salesforce today. We wanted real-time visibility into ticket sales and attendance every hour. That doesn’t exist natively. It took two APIs and now we can interact with our Salesforce data in ways we never could. You can get 10% of what we do in about an hour. The Salesforce API is genuinely good. Most teams are leaving it on the table.

Top learnings from 10K:

• Start with the boring version. A dashboard that ends the copy-paste tax is a perfectly good day one. The agent grows from there.
• Headless Salesforce is the fastest leverage you can buy. Hit the API directly and build the views Salesforce won’t give you natively.
• Daily reps compound. Seven or eight commits a day is how an agent goes from reading numbers to writing better emails than your team in four months.
• The model underneath matters. The same specs on Replit versus Lovable produced different ideas. Pick the brain that matches the job.

QBee: Our AI VP of Customer Success

QBee handles our sponsors. All ~150 of them, including non-booth sponsors. He’s less than 90 days old.

He started as a project management tool. We had an antiquated, out-of-the-box tool for managing sponsor onboarding, and events are niche and weird enough that nothing off the shelf fit. So it took endless human follow-up: manual emails, manual calls, texting people, chasing assets. We built QBee to save that time and budget.

Now he’s a self-service agent. He intakes logos and websites, answers sponsor questions, remembers everything about every account, and collects the assets that used to be a genuine pain to gather. The better part: he emails all ~150 sponsors with personalized outreach. No human CSM wants 100 accounts. They want five. QBee knows all of them cold, knows their logos, knows what they do, and researches them. He knows more about our sponsors than a lot of the best CSMs know their top customers.

We asked him a question on stage we’d never asked: which sponsors are most at risk of not renewing.

He flagged the ones who never logged in or went dark with him, and got the analysis directionally right. The interesting part: the accounts he flagged were the ones our humans were spending the most time on directly. He saw that one sponsor complained the most in chat, which was true. He noticed two top sponsors never completed their VIP nominations. We’d never run that analysis before. For something we made up on the spot, it landed in the top 15% of CSMs we’ve ever worked with.

The catch: he only has the context he has. He missed the human side, the conversations that happened over email and in person. We’d give it a B. The fix is simple: hook him up to email and the call transcripts. Any source with an API can be wired in, usually in 10 to 15 minutes.

The back end:

**Built on:**Replit.**Top API:**Clerk, for single sign-on. That’s so sponsors can invite their colleagues to interact with QBee and see what others in their org are doing. Auth used to be the hard part. It’s native in Replit now and much easier.**Salesforce:**Here’s the kicker. That risk analysis he ran on stage? He didn’t even have Salesforce data yet. We’re wiring it in next. It only gets better from here.

Top learnings from QBee:

• One agent can own 100+ accounts at a depth no human CSM will. Humans want five accounts. An agent will know all 150 cold, including logos, assets, and history.
• Agents surface what humans hide. A renewal-risk read flagged the accounts our team was over-invested in, and treated a sponsor’s frequent complaints as signal instead of noise.
• Coverage is only as good as the context. QBee missed the human side because he couldn’t see email and call transcripts. The fix is wiring in the source, not lowering the bar.
• You don’t need the full stack to get value. QBee ran a useful risk analysis with no Salesforce data connected at all.

Annie: Our AI Event Producer (and the Prohibited-Email Story)

Annie is SaaStr Annual’s website. Last year it lived on Squarespace, where all you can really do is swap images and videos. That wasn’t enough this year, so we rebuilt a V1 on Replit in November. Once we could make it do anything we wanted, it stopped being a website.

We asked Annie what title she’d give herself. She said “AI event producer hybrid,” part producer, part technical producer, because she runs the website and the agenda. Fair enough. She runs the site, the agenda, and a lot of the attendee newsletters.

She became agentic with the now-famous parking pass app. Getting a parking pass used to require a human to split up a 5,000-page PDF and manually send the right page to the right person. Last year it was a form fill plus a wait. Now you tell Annie if you’re an attendee, sponsor, or speaker, how many days you need, and she sends the right pass automatically. She’s also hooked into our visitor data, so she can see active website visitors and run targeted campaigns based on what they’re doing.

The back end:

**Built on:**Replit, first commit November 2025.**Commits:**The most of any agent, and the highest commits per day.Lines of code:~46,000. Two weeks ago a related app was 18,000 lines at $257 a month. Going from 18K to