Kai

The BDR that does the research first.

Kai studies the company and the person, writes outreach grounded in what it actually learned, then runs the sequence through your inboxes. You stay in control of conversations and decisions.

Kai is working
Researched
Pulled Workday's homepage, recent press, and Lisa Chen's LinkedIn. Distilled to a one-paragraph brief.
Drafted
Wrote Email 1, the LinkedIn note, and a follow-up. Each opens with a specific observation about Workday's content stack.
In progress
Queueing the sequence in Lemlist, scheduled to start tomorrow at 9am Lisa's time.
How it works

Three steps. One Kai. No generic outreach.

Kai sits between your contact list and your inboxes. Every contact gets the same treatment a careful rep would give them, just at the pace and volume software can sustain.

01 · Research

Read the company, then the person.

For each new contact, Kai crawls the company website, scans recent news, and reads the person's LinkedIn. Claude distills a one paragraph brief on each so the outreach has something specific to lean on.

02 · Personalize

Write outreach grounded in the brief.

Kai drafts the full sequence: three emails, a LinkedIn opener, a LinkedIn follow up, and a call brief for the rep. Every message references something Kai actually learned about the prospect.

03 · Execute

Send through your real inboxes.

Kai injects the sequence into Lemlist, where it runs across warmed up rep inboxes. Replies route automatically: positive leads land in your CRM with full context, off topic replies pause the sequence, hard nos suppress.

Three modes

One Kai. Three ways to put it to work.

Different outreach motions need different shapes. Kai runs three of them, side by side, sharing the same research, writing, and reply logic underneath.

Seasonal

Time-boxed campaigns from a list you bring.

You upload a CSV, paste contacts manually, or pull an existing Lemlist campaign in by ID. Kai picks them up, researches each one, writes the sequence, and runs it. Finite. Has a start and an end.

  • Pull leads from any Lemlist campaign by ID
  • Optional daily sync so newly added leads flow in automatically
  • Same research and personalization as every other mode
Good for: conferences, webinars, partner referrals, curated lists from Sales Navigator.

ABM

Account based outreach with waves and learning.

Point Kai at a single target account. Kai pulls the company info, writes a brief, discovers the buying committee through Lemlist's database, scores candidates against your persona focus, and runs outreach in waves. Each wave learns from the one before it.

  • Above the line plus below the line mix per account
  • Automatic account state machine reacts to replies
  • Kai's read panel synthesizes what the account is signaling
Good for: strategic hit lists. The accounts you'd love to land but can't afford to spray.

24/7

Always on sourcing that paces itself.

Give Kai a vertical and an ICP brief. Kai sources new contacts continuously in the background, scores them against your persona focus, and queues survivors for your review. Never stops. Never floods the queue.

  • Weekly target so Kai paces sourcing sustainably
  • Saturation rule auto-pauses if the review queue gets full
  • Pause and resume whenever you need to focus elsewhere
Good for: steady pipeline. The campaigns you want running in the background while you focus on calls and closes.
What Kai does

Everything that happens before the conversation starts.

The boring research, the tailored writing, the patient sequencing. The parts of BDR work that take real time but reward repetition.

Live prospect research

Every contact gets a fresh research pass before the first email. Company snapshot, news mentions, and a persona read. Cached at the account level so it scales.

Full sequence generation

Three emails, two LinkedIn messages, and a call brief per contact. Each message opens with a specific observation, not a templated hook.

Account based outreach

Point Kai at a target account, like a company you would love to land. Kai discovers the buying committee, runs the outreach in waves, and learns from engagement at the account level.

Reply classification

Every reply gets read and sorted. Interested leads route to your CRM with the full research brief attached. Out of office reschedules. Hard nos suppress for twelve months.

Weekly self review

Every Monday Kai pulls the prior week, compares variants, and proposes adjustments to ICP, opening hooks, or sequence pacing. You approve the ones that make sense.

Always on sourcing

Give Kai a vertical and an ICP brief, and it sources new contacts continuously. Pauses itself when your approval queue gets full so the human side is never buried.

Continuous improvement

Kai gets sharper every week. Grounded in your real data.

Every Monday morning Kai reads its own week. Which subjects opened, which hooks earned replies, which personas converted. It compares variants, isolates what worked, and proposes specific changes you can approve in a single tap.

Monday review · Week 24
06:00 UTC
What worked
"question about [company]" as a subject line earned a 41 percent reply rate on Fintech contacts, double the campaign average.
What underperformed
Email 2 sent on D6 ran 6 percent below average. D5 appears to be the sweet spot in Fintech.
Proposed for next week
Promote the winning subject variant to default for new Fintech sequences. Shift D6 follow ups to D5. Reply APPROVE to apply.
38%Open rate this week, up 4 points vs last
6.1%Reply rate, up from 4.8 last week
14Interested leads handed to the CRM

What Kai handles end to end.

The grindy parts. Research, writing, sequencing, routing, learning. Kai runs the full motion from "new contact added" to "interested reply lands in your CRM."

What stays human.

Kai does not call, close, or decide. Conversations stay with your team. Strategy stays with you. Kai handles the volume so your reps can spend their time on the meetings that matter.

A real example

What Kai writes when it has done the research.

EMAIL 1 · DAY 1
From Sarah Whitfield, growth@growth.example.com
To Lisa Chen, VP Demand Gen at Workday
your team's RFP page is doing the heavy lifting
Lisa, I noticed Workday started gating the new procurement RFP guide behind a content hub instead of a PDF. The engagement data on those is usually three to four times richer than a static download, especially for procurement buyers who tend to share around internally. We work with teams that want that same signal across all their high value content. The clients I think look most like Workday are running between four and seven of these per quarter and using the page level engagement data to score account interest. Worth a fifteen minute look at how they set it up? Sarah
Generated by Kai. The reference to the RFP guide came from Kai's research pass on the Workday content hub three days earlier. The proof points cited are from the campaign brief.
Built on Claude

Every piece of intelligence in Kai, the research distillation, the sequence writing, the reply classification, the weekly self review, runs through Anthropic's Claude. The same model that powers Anthropic's own products. Claude was chosen for one specific reason: its writing reads like a thoughtful person, not a template engine.

Ready to see Kai working?

Sign in to the dashboard. Watch Kai research a contact, write a sequence, and execute the outreach in real time.

Sign in to Kai