Case study SaaS ~90 employees, profitable growth

An AI agent that assigns the right CSM to every new campaign

A fundraising platform runs hundreds of client campaigns, and every new campaign needs the right customer success manager assigned fast. We built an AI agent that makes the assignment, posts it to Slack for a one-click human confirmation, and only then touches the CRM.

Client A SaaS fundraising platform, ~90 employees
AI agent
assigns a CSM to every new campaign using deal-level logic
1 click
human confirmation in Slack before anything touches the CRM
0
downstream automations triggered before a manager validates
Auto
renewal reminders for tax-receipt processing clients

The starting point

CSM assignment was manual and inconsistent. The logic lives at the campaign-deal level, not the account level, which is exactly the kind of nuance a plain HubSpot workflow can't handle: who managed this client's last campaign, what's the campaign's revenue, which time zone does it run in. Assignments lagged, and campaigns sat unowned at their most critical moment.

The engagement

We’re the on-call HubSpot and automation expert for this client: multiple stakeholders across CS, finance, and operations bring problems, we design and ship solutions. The CSM assignment agent is the flagship build.

What we built

The assignment agent

The agent evaluates every new campaign deal and decides who should own it. The default rule: a client’s new campaign goes to the account manager who already knows them. Revenue is read from the right field (gross booking, not the aspirational goal amount), time zone is mandatory so assignments respect working hours, and fields that added noise were cut from the logic entirely.

Human in the loop, by design

This is the part we insist on with every AI build: the agent posts its assignment to a dedicated Slack channel, and a manager confirms before anything updates in HubSpot. Crucially, automated assignments are blocked from triggering downstream deal-stage automation until validation happens, so a wrong guess can’t cascade. Full automation comes after the agent earns trust, not before.

CS email operations that respect the plan limits

CSM bulk client communications moved from individual mailboxes to HubSpot marketing emails with list-based segmentation and required exclusion lists. Marketing-contact capacity is managed deliberately: eligible active customers in, excluded contacts out, so the CS team can email clients without blowing through the plan’s contact cap.

Small automations with outsized value

An automated renewal reminder flow for tax-receipt processing clients, so a compliance-critical renewal stops depending on someone’s calendar memory. Survey distribution workflows updated to exclude the campaign types where a survey would land badly.

What this looks like day to day

A new campaign closes, the agent proposes the right CSM in Slack within moments, a manager taps confirm, and the CRM updates itself. The team keeps the judgment; the agent does the remembering.

Stack

HubSpotClaudeSlack

What we did

AI agent developmentCS operationsWorkflow automationEmail operations

Run this playbook for your team

Facing something similar?
We'll scope it to your stack and timeline.

Let's talk →