Follow-ups that actually know what you talked about

You've earned
the meeting.
Make the
follow-up count.

Scurry reads the transcript of the call you just had and drafts the follow-up sequence from it: the objection they raised, the number they mentioned, the person who has to sign it off. Every email lands in your queue as a draft you can rewrite, reschedule or cancel, and sending goes through your own Gmail or Outlook, as you. Connect Pipedrive and a sequence can check the deal before a send.

Join the waitlist See an example
Early access by waitlist Your inbox, your rules From $49.99 per seat billed annually
▸ TRANSCRIPT.TXT ILLUSTRATIVE EXAMPLE
Davis:Our CRM's too heavy. Team's drowning in it.
You:What breaks first at your size?
Davis:Reporting. CFO wants a weekly report I can't pull. Budget's approved.
Scurry writes the email
Scurry mascot holding marker
every highlight = a line
from the call above
Emails from your inbox via OAuth
Review, edit or cancel from your queue
Acorns roll over
Keep the notetaker you already use

What Scurry is, and who it's for.

What it is

AI sales follow-up software. Scurry reads your sales meeting transcripts and drafts multi-touch follow-up email sequences from what was actually said, queued to send from your own Gmail or Outlook.

Who it's for

People who already have the meetings. Established businesses, lean sales teams running back-to-back calls, and consultants and coaches whose bottleneck sits after the call rather than before it.

What it replaces

Re-reading the transcript, pasting it into a chatbot, generic templates, and sending tools that know nothing about what was said on the call.

Illustrative example

Same call. Two follow-ups.

One written from memory at six in the evening. One written from the transcript after the call, while it is still fresh. The call below is a made-up sample, not a customer's.

The sample callIllustrative
Davis:Our CRM is too heavy. Team is drowning in it.
You:What breaks first at your size?
Davis:Reporting. CFO wants a weekly report I cannot pull. Budget is approved.
Written from memory18:40, third call of the day
Great speaking today

Hi Davis,

Great speaking with you today. As discussed, I think our platform could be a great fit for what your team is trying to achieve.

Let me know if you have any questions and I would be happy to jump on another call. Just circling back so this does not slip.

Looking forward to hearing from you.

Nothing in it he could not have received from anyone
Written from the transcriptReady after the call
The weekly report your CFO wants, done

Davis, good call today.

You mentioned your CFO wants a weekly pipeline report you cannot pull yet, and that the team is drowning in the CRM you have. from the call: "CFO wants a weekly report I cannot pull"

That is usually the point where a team outgrows its reporting.

You also said budget is already approved, so if it is useful I will put together the numbers for your size of team. from the call: "Budget is approved"

Every specific claim traces to a line in the sample above

Both take you the same amount of time to send. Only one of them proves you were listening. Every email sits in your queue, where you can rewrite, reschedule or cancel it.

Illustrative example

A sequence written from one call.

Three made-up sample calls, with one email from each drafted sequence. Every highlighted phrase traces back to a line in the transcript beside it. These are illustrations of the output, not screenshots of the product or a customer's results.

Inputtranscript.txt
Raw
You:...and that's the pipeline-by-rep view. Every field here you can customize.
Priya:Hold on, can this sync live with Pipedrive? Our whole pipeline lives there, I don't want another source of truth.
You:Native Pipedrive connection. Scurry reads deal stage, custom fields and activities before a send.
Priya:That's the holy grail. Right now my ops team spends Friday afternoons stitching Pipedrive exports with Stripe data manually. So this kills that ritual entirely?
You:For your stack, yes. What's your timeline to move off the manual process?
Priya:Pilot in 6 weeks, full rollout by Q3 board review. Budget's $85k approved.
, 6 of ~210 lines shown · full transcript processed
Outputsample draft
Illustrative

Illustrative example. The sample calls and the people in them are invented for this page; nothing here is a customer, a result or a screenshot of the product.

Where it fits

Where Scurry fits.

Your notetaker summarises the call. Your sending tool sends what you give it. Someone still has to write the emails. That is the step Scurry takes: transcript in, a drafted sequence out, into the inbox you already send from. Keep the tool that records your calls.

The way it gets done today

By hand, after the call

  • Re-read the transcript, or trust your memory at six in the evening
  • Paste it into a chatbot, re-prompt until the tone is right
  • Write touches two and three, or never get to them
  • Set your own reminders and remember to stop when they reply
With Scurry

Drafted from the transcript

  • The sequence is drafted from the call, with the lines it came from
  • Your tone rules are applied for you, once, everywhere
  • First email and the follow-ups arrive together, already spaced
  • Each one is scheduled in a queue you can rewrite, move or cancel

Not a replacement for your notetaker or your CRM. The step between them.

Illustrated bar chart showing follow-up work adding up
External benchmarks

The work after the call adds up.

Independent research measures the follow-up tax that sits between a good conversation and a useful next message.

10–20 min post-call admin per meeting
5–8 hrs reported by some reps each week
18–20 min spent recalling context for a reply

These are external benchmarks, not Scurry customer results. Read the source, method and caveats in The Follow-Up Study, Finding 01 →

Your rules, always

You stay in charge of what goes out.

Three layers of control. The AI drafts; you set the rails and can change or stop anything in the queue.

01
Control layer one
✓Always use "we" not "I"
✓Never use exclamation marks
✓Sign off with first name only
Reference our case study when asked

Universal Prompts

Set your brand voice, required elements and formatting once, and every new sequence starts from the same rules instead of whatever the model felt like that day.

02
Control layer two
IF budget mentioned
THEN proceed with proposal flow
IF deal stage ≠ "qualified"
HOLD nothing goes out

AI Filters

Define conditions like "only send if budget was discussed" or "skip if the deal has moved past this stage." If the conversation does not match, the sequence holds instead of going out.

03
Control layer three
Queued · sends in 2h 14m
✎ Rewrite ⏱ Reschedule ✕ Kill
Scheduled to send from your own inbox.

Edit Before Send

Every email sits in a queue with its scheduled send time. Rewrite it, move it, or cancel it. Sending goes through your own inbox, under your signature.

Three steps

Transcript in. Sequence out. You stay in the loop.

1

Connect your tools

A transcript source and your email account. Gmail and Outlook connect by OAuth, so we never touch your password. Pipedrive is optional.

set up once
2

Set your rules

Brand voice, sequence length, AI filters. Set them once and new sequences start from the same rules.

set once · reused after that
3

Scurry drafts.

A transcript arrives, a sequence is drafted, and the emails land in your queue with their send times. Rewrite, move or cancel any of them.

no copy-paste
Don't record your meetings yet? Tools like Fireflies and Otter are free to start. Get set up, then come back.
OptionalConnect Pipedrive for deal-stage checks before a send, filtering and conditional logic.
Works with your stack

Works with the stack you already have.

Three things to connect: where the transcript comes from, where the email sends from, and your CRM if you use one. A transcript source and Gmail or Outlook are required. Pipedrive is optional.

Live

Pipedrive CRM

Native connection. Deal-stage checks before a send, filtering and conditional logic. Optional.

Fireflies.ai AI Notetaker

Connect your Fireflies account once and new transcripts come through on their own.

Gmail Send

OAuth-based sending from your own inbox. Threads stay intact.

Outlook Send

Same as Gmail. Microsoft identities supported.

In development

HubSpot In development

Not available yet. On the roadmap, with no date promised.

Connects through the transcript endpoint

Zoom
Google Meet
Microsoft Teams
Gong
Otter.ai
Chorus
Fathom
tl;dv
Read.ai

Tools we have not integrated directly can post a transcript to our endpoint. We send you the format and the URL when you connect.

Transcript endpoint

For anything we have not integrated directly.

One HTTP call per transcript. We send you the exact URL and payload format when you connect.

transcript in → sequence back
See all integrations →
What's in the box

The rest of the toolkit.

The supporting pieces behind the sequences. Anything still in development is labelled as such.

Set up once

Connect your tools once and a sequence is drafted for each transcript that arrives. You open the queue when you want to look at one.

AI Filtering

Write conditions in plain English. "Only proceed if budget was discussed": checked against the transcript, not guessed.

Real subject lines

Pulled from the actual conversation. No "Following up" or "Touching base." Nobody has to guess what the email is about.

Pipedrive-native

Deal stage checks run at send time, not queue time. Pre-send logic keeps sequences aligned with where the deal actually is.

Your own inbox

Gmail or Outlook via OAuth. Replies land where you expect and threads stay intact, because the mail leaves your account rather than a relay.

Edit anything, anytime

Open any draft in the queue and rewrite it, move its send time, or cancel it outright.

See all features →
Important: we don't record

Record your meetings.
We handle what comes after.

Scurry doesn't sit in on your calls or listen to audio. We take the transcripts your existing tools already produce, including Fireflies, Fathom and Granola, and turn them into follow-up sequences written from what was said.

If your meeting tool produces a text transcript, it can reach Scurry — through a product connection where available, or through the account intake endpoint.

Zoom Meet Teams
Your meeting tool
Fireflies, Fathom, Granola + other transcript tools…
records
↓
Transcript
Auto-delivered to Scurry
webhook
↓
Scurry
Sequence generated
you
Trust layer

Built for people who don't trust easily.

OAuth everywhere. Your data stays yours. If we disappeared tomorrow, your sent history still lives in your inbox.

Emails through YOUR inbox

Sent via your own Gmail or Outlook. We never send from our servers.

We never see your password

Secure OAuth, credentials stay with Google or Microsoft.

Acorns roll over

AI credits roll over while you are subscribed. No use-it-or-lose-it gotchas.

Prices are published

Both plans, their Acorn allowances and the trial terms are on the pricing page. No quote required.

FAQ

Questions we get all the time.

Does Scurry record my meetings?+
No. Scurry doesn't record or transcribe. You use your existing tools, Fireflies, Otter, Zoom, Gong, Fathom, whatever, and we pick up from the transcript. Your recording setup stays exactly as it is.
Will the AI emails sound generic?+
Every email references specific details from your actual conversation: pain points, budget, names, next steps. You also set brand voice with Universal Prompts, and you can review, edit or cancel every email.
Do I need a CRM?+
No. The core product runs on a transcript source + email account (Gmail or Outlook). Pipedrive is optional, it adds conditional logic, deal stage checks, and smart filtering. HubSpot integration is in development.
How is this different from Outreach or Apollo?+
Those tools are built to send sequences you have written. Scurry drafts the sequence from the meeting itself, then queues it for your own inbox. If you already run Outreach or Apollo, the overlap is the writing, not the sending.
I already paste transcripts into ChatGPT. Why switch?+
Pasting a transcript into a chatbot gets you one email, when you remember to do it. Scurry runs the same job end to end: the transcript arrives, a full sequence is drafted with its spacing, each email is queued with a send time, a connected CRM can be checked before a send, and the rest of the sequence stops when a reply comes in. No copying, no re-prompting.
What are Acorns? Do they expire?+
Acorns fuel your AI: sequences, summaries, edits. Both plans include them and unused ones roll over. Need more? Grab a top-up anytime.
Is my data safe?+
Emails send through your own Gmail or Outlook via OAuth. We never see your credentials and never send from our servers. Even if we disappeared tomorrow, your sent history lives in your inbox.
Will this burn my domain?+
This is not cold outbound. It is a handful of emails to one person who was on a call with you, sent from the mailbox you already send from, at human volume. No new domains, no warmup, no inbox rotation, no sending relay. Because Scurry sends through Gmail and Outlook's own APIs as you, SPF, DKIM and DMARC align by construction, rather than a third-party sender putting your address on someone else's server.
Doesn't Fireflies already draft a follow-up?+
A notetaker summary is one email, written for your team. Scurry drafts the whole sequence for the buyer and queues it in your own mailbox. Keep the notetaker you have; Scurry reads what it produces.
What if it writes something wrong?+
Every specific claim in a draft shows the line of the transcript it came from. If the line is not there, the claim is not in the email. Drafts wait in your queue, so reviewing one is a couple of minutes of reading instead of fifteen of writing.
One last thing

Your meetings already happen.
Make the follow-up count.

Waitlist access No card to join Review queue
Join the waitlist

Not ready? See an example sequence first, or read the plans and trial terms.