All case studiesThe droid that runs inbound lead response

Inbound leads, answered in minutes.

A droid that works the top of the funnel the moment a lead lands: it researches the account, writes it into the CRM, replies and books the meeting while it’s still warm, and loops in an AE only for the deals worth their time — remembering every account so the next touch is never cold.

< 5 min
from form fill to a researched, personal reply — day or night
100%
of inbound leads worked — none left aging in a queue
Every lead
in the CRM, enriched, before a rep opens it
Does
Researches, replies to & books inbound leads
Where
B2B SaaS, ~15-person go-to-market team
Reaches people on
Email, Slack
Works inside
HubSpot, Gmail, Google Calendar
Runs
On every inbound lead · 24/7
The situation

The leads you answer first are the ones you win.

Inbound was the team’s best channel, but the leads that converted were the ones they answered first. After hours and over weekends, demo requests sat untouched until someone was back at a desk — and by then the prospect had often booked with whoever replied fastest.

Even in the working day, reps burned the first ten minutes of every lead researching the company and typing it into the CRM before they could say a word. The easy 90% — the lookups, the data entry, the “thanks, here are some times” — quietly ate the hours that were supposed to go to actual selling.

Isometric inbound-sales scene: a lead funnel feeding a CRM, with a calendar and an outreach reply
How it works

How the droid took it on.

Rather than ask reps to babysit the inbox, the team handed first-touch over. The moment a lead lands the droid researches it, writes it into the CRM, replies and books while it’s still warm, and loops in an AE only for the deals worth their time.

TASK#207Inbound lead responsestanding
trigger
Any inbound lead — form, email, or booking
also
An end-of-day pipeline digest
scope
Every new lead · 24/7
runs as
A contained droid action per lead — research, reply, book…
memory
Per-account rolling summary, carried touch to touch

Set up once, in plain language — “whenever a lead comes in, research it, reply and book while it's warm, and only bring us in for the big ones.” The droid turned that into a standing job: no round-robin to babysit, no leads aging out over a weekend.

Every new lead trips the same loop:

Ongoing handling

How it ran, lead after lead.

Here’s a day of inbound as it actually unfolded — lead by lead, down to how it reached for each app. Only the strategic deals ever made it to a rep.

  1. 9:02amdemo · Acme
    • HubSpot
    • Gmail

    Inbound demo request — researched the account, wrote it to the CRM, and replied with times in under five minutes.

  2. 9:14ambooked · Acme
    • Google Calendar
    • HubSpot

    Answered a pre-meeting question and booked the call while the lead was still warm.

  3. 9:20ambrief · Acme
    • Slack

    Posted a pre-call brief so the rep walks in prepared, not cold.

  4. 10:05amself-serve
    • Gmail

    A student inquiry — pointed them to the free tier and skipped the deal, keeping the pipeline honest.

  5. 11:30amenterprise · Northwindescalated
    • HubSpot
    • Slack

    A 2,000-seat enterprise eval — did the research, flagged it high-value, and handed an AE a draft reply.

  6. 2:40pmfollow-ups
    • Gmail
    • HubSpot

    Nudged two leads from yesterday that had gone quiet, using what it already knew about each.

  7. 5:00pmdaily digest

    The day reconciled — every lead researched, enriched and staged. Digest posted: 9 worked, 4 booked, 1 escalated, 0 dropped.

See it in action

One morning, lead by lead.

Inbound leads and prospect replies land on the left. Watch the droid pick up each one and work it end to end across the CRM, inbox and calendar — looping in a human only for the deals that warrant it.

We didn't bolt on a chatbot — we handed off first-touch. A lead comes in and it's already researched, in the CRM, and answered before anyone's looked. The reps only ever see the deals that are actually worth their time, and they walk in already briefed.
Priya M.Head of Growth, B2B SaaS

An illustrative workflow based on real product mechanics. Tool names and behaviour reflect how a droid actually triggers on events and calls connected apps; figures are directional.

Try it with your droid

Run this workflow yourself.

Copy the brief below and paste it to your droid. It’ll walk you through the prerequisites, connect what it needs, and stand the workflow up with you.

Workflow brief
I run growth at a small B2B SaaS company, and inbound is our best channel — but the leads that convert are the ones we answer first. After hours and on weekends they sit until someone's back; even in the day, reps burn the first ten minutes researching each company and typing it into the CRM before they can reply. The easy 90% eats the hours that should go to actual selling.

Own inbound lead response. Apps/channels: HubSpot (CRM — contacts, companies, deals, stages), Gmail (first-touch and follow-up replies), Google Calendar (booking meetings), Slack #revenue (pre-call briefs and escalations). Use the web to research each company.

Run whenever a new lead comes in — a website demo request, an inbound email, or a booking — plus an end-of-day digest. For each lead:
1. Identify the person and company, and research them on the web (what they do, size, recent news, likely fit).
2. Create or update the CRM record with the enriched details and the lead source.
3. Reply in their channel within minutes — a tailored note that answers the obvious questions and offers times.
4. When they're a fit, book the meeting and advance the deal stage; for off-fit or tiny inquiries, point them to self-serve and skip the deal so the pipeline stays clean.
5. Before any booked call, post a pre-call brief to #revenue — who they are, why they reached out, and what to cover.

Carry context between touches (everything we know about the account, what's been said) so no reply starts cold. Only loop in an AE for the strategic or high-value deals.

What would a droid take off your desk?

Tell us the job that never gets done before close. We'll wire up a droid on a call and you can watch it work.

Try now — freeBook a walkthrough