HomeBuilds by Use Case
Builds by Use Case

Pick the job. The build follows.

Nine families of work cover most of what revenue teams ask for. Each one below is a pattern with production mileage behind it, not a concept waiting for its first deployment.

Use Case 01

Pipeline Generation

Outbound that researches and writes per lead instead of mail-merging, with a human gate before anything sends. Signal clusters decide the timing: a leadership change, a funding round, a competitor stumble.

What a Build Includes

AI SDR pipeline

Lists resolved against your CRM, persona sequences written per lead, staged for review, pushed to the sequencer, stamped back to the CRM.

LinkedIn outbound

Connection accepted? A researched, personalized follow-up fires within the minute, written in the rep's voice from a copywriting skill.

Signal plays

Closed-lost re-engagement, micro-campaigns, and displacement plays from the play library, firing on stacked signals.

Reply handling

Every reply classified and answered with a drafted response grounded in what was actually sent. Drafts only.

Typical Tools
ClaudeClayHubSpotLemlistHeyReachSumble
Use Case 02

Lead Qualification & Routing

Every inbound lead scored the moment it lands, routed by rules your team agreed on, and kept clean so downstream agents never choke on junk.

What a Build Includes

ICP fit scoring

A multi-dimension rubric scored by AI, with compliance checks like sanctions and export controls layered in where the business needs them.

Fast-track routing

High-value leads skip the queue and land directly with sales leadership, with the rationale attached.

CRM hygiene

Low-score leads updated automatically against an agreed ruleset, so nobody maintains fields by hand.

Typical Tools
ClaudeMakeSalesforceHubSpot
Use Case 03

Account Intelligence & Planning

The research a great rep would do if they had three spare hours per account, done automatically and delivered where the team already works.

What a Build Includes

Pre-call briefs

Company snapshot, contact context, competitive landscape, talking points, and likely objections, delivered 30 minutes before the call.

Account plans

CRM data, a year of call transcripts, and cited public research cross-referenced into a 2 to 3 page plan, rendered per role and refreshed without overwriting human edits.

Named-account briefs

Fit, intent, relationship, and engagement scored per target account, with a verdict and the evidence behind it.

Champion tracking

A relationship graph that watches job changes, promotions, and investor overlap, then drafts the right warm ask.

Typical Tools
ClaudeSalesforceGongUserGemsThe SwarmWord
Use Case 04

Competitive Intelligence

Battlecards that update themselves and intel that arrives before the deal needs it, not after the loss report.

What a Build Includes

Weekly competitor scans

A scanner per competitor runs in parallel, findings deduplicate against prior briefs, and the team gets one ranked document plus a Slack post.

Living battlecards

Approved findings merge into battlecards, kill sheets, and objection guides on a publish cadence, so enablement never goes stale.

Just-in-time kill sheets

A competitor mention on a sales call triggers a tailored kill sheet to the rep before the next conversation.

Typical Tools
ClaudeFirecrawlG2SlackWord
Use Case 05

Rep Productivity

The admin tax on sellers goes to the agents: notes, prep, and call archaeology. Reps keep the conversations.

What a Build Includes

After-call notes

Call recordings become structured notes for rep approval in Slack, then write back to the CRM, with methodology variants like SPICED per team.

Per-rep call tools

Each rep gets their own call-archive access and a personalized prep skill: every prior call on the account, summarized before the next meeting.

Coaching routers

A rep posts a deal link in Slack, the scenario gets classified, and the right coaching doc plus a summary comes back.

Typical Tools
ClaudeGongMakeZapierSlackSalesforce
Use Case 06

Customer Success & Retention

Accounts flagged before they churn and expansion spotted before the QBR, because an agent reads the signals every day.

What a Build Includes

Account watchers

Daily, weekly, and monthly scans per account: regulatory actions, leadership changes, funding, hiring, review sentiment, competitive intent.

Renewal and expansion briefs

CRM, call history, and success-platform data consolidated into a per-account artifact for renewal conversations.

Living account plans

Plans refresh on demand with a dated update block, preserving every human edit underneath.

Typical Tools
ClaudeSalesforceGongWeb ResearchSlack
Use Case 07

Content & Brand Operations

Brand-voice content with the author in the loop, from LinkedIn presence to full launch asset packs. The voice work happens once, in a skill, and every surface inherits it.

What a Build Includes

Content OS

A research-fed content operation that drafts in the author's voice, grades posts against what performs, and keeps a weekly digest cadence.

Role-specific writing skills

One brand voice encoded as maintained skill files per discipline, powering outbound, executive posts, and content from the same source.

LinkedIn engagement

Engagement-worthy posts surfaced daily, comments drafted in the executive's voice, approved, posted. Presence that compounds.

Ad and asset engines

Multi-channel ad copy and launch asset packs generated against brand guardrails, with a QA pass before anything ships.

Typical Tools
Claude CodeCustom SkillsNotionApifyPhantomBuster
Use Case 08

Research Ops

Standing research that used to be an intern project or a quarterly scramble, running continuously with citations attached.

What a Build Includes

Named-account research

Public snapshots, regulatory pressure, buying signals, and stack detection per account, compiled into one-page briefs where the team works.

Opportunity scanning

Sector scanners sweep procurement portals, foundations, and funding sources on a schedule, score against your criteria, and compile a weekly digest.

Greenfield enrichment

Corporate-family research with citations, schema validation in waves, and field-level CRM reconciliation with human-reviewable verdicts.

Typical Tools
ClaudePerplexityFirecrawlSupabaseExcel
Use Case 09

Reporting & the Executive Layer

The aggregation layer above the agents: daily pulses, weekly rollups, and a chief-of-staff pattern for the executive chair. Usually the last layer built, because it rides on everything underneath.

What a Build Includes

Daily executive pulse

One screen each morning: inbound counts, scores, fast-tracked accounts, outbound activity, and the accounts to watch, with rationale.

Weekly reporting

Hours, deliverables, pipeline movement, and next steps compiled into one pass: a doc, a Slack post, and an executive email.

Chief-of-staff pattern

Morning briefs with a recommendation and the dissent, pre-loaded meeting agendas, decision logs, and an action tracker that chases with approval.

Custom dashboards

A flat data layer on Supabase and Pinecone that agents can query, with dashboards on secure hosting answering questions reports never could.

Typical Tools
ClaudeCoworkSlackSupabasePineconeVercel
FAQ

Choosing your starting point.

Which use case should we start with?

Wherever the pain is sharpest and the value shows up weekly. After-call notes, a weekly report, or a single outbound persona are the classic first builds because they prove value within days and create the template for everything after.

Can use cases combine?

They stack by design. Qualification feeds outbound, call notes feed account planning, watchers feed renewal briefs, and the executive layer rides on all of it. The strongest portfolios stop needing new agents and start adding skills on top of existing ones.

Do I need all the tools listed?

No. The tool chains shown are typical, not required. Your stack is the starting point, and most patterns adapt to whatever CRM, sequencer, and call recorder you already run. The full tool grid is on the homepage stack.

What does the AI decide versus the humans?

Agents research, draft, score, and route. People approve anything customer-facing and own every system. A human gate before sends is an operating principle here, not a feature flag.

Know the job you need done? Start there.