DeskFerry Logo

Your best BD intelligence is in calls nobody wrote down

A client mentions two roles coming in September, a restructure in the new year, and that their incumbent supplier is struggling. None of it reaches the CRM, because logging a call takes ten minutes and you have another one at three.

Client calls · week to 8 Aug

14 calls

Calls
14
Logged
3
Lost
11
  • Alan Brightwell — Wexley Group

    Two platform roles signed off for September

    Tue

    22 min

    Nowhere
  • Priti Nandy — Calder Rail

    Restructure in Q1, whole team may move

    Wed

    35 min

    Nowhere
  • Marcus Hale — Northgate

    Offer accepted, asked about contract cover

    Wed

    12 min

    In CRM
  • Ines Duarte — Ellery Partners

    Unhappy with incumbent agency — openly said so

    Thu

    41 min

    Nowhere

Eleven of fourteen exist only in somebody's memory. When that consultant leaves, so does the pipeline they were building.

Works with

  • Zoom
  • Fireflies
  • Google Meet
  • HubSpot
  • Pipedrive
  • Gmail

It works from calls you already record. Zoom publishes eleven triggers including new cloud recordings, and Fireflies publishes transcription-complete, so this route genuinely reacts rather than sweeping. HubSpot and Pipedrive both accept notes, tasks and activity, so the write-back lands where your BD actually lives.

The chore

How this goes right now

  1. A recruitment CRM is usually a good record of what was invoiced and a poor record of what was said. The transactional layer is fine — placements, fees, contacts. The layer that actually predicts next quarter's revenue is a set of things clients mentioned on calls, and almost none of it is written anywhere, because a consultant who has just finished a call has another one booked and logging takes ten minutes they don't have.

  2. The things lost are specifically the valuable ones. A client saying two roles are signed off for September is a forecastable pipeline. A client mentioning a Q1 restructure is a warning and an opportunity at once. A client complaining about their incumbent supplier is the single most actionable sentence in business development, and it routinely reaches nobody, because the person who heard it was already thinking about their next call.

  3. Then it compounds in a way that only shows up later. Your forecast is built from opportunities somebody remembered to create, so it is systematically short. Two consultants call the same client in a fortnight because neither could see the other's conversation. And when someone resigns, their pipeline resigns with them — you inherit a contact list and lose every piece of context that made it worth anything, which is why a desk changing hands takes six months to recover.

The difference

Same conversations, actually captured

Nothing changes about how you sell. What changes is that the intelligence in those calls survives the week, and the person who has it isn't the only person who has it.

Logging calls by hand
Logged from the recording
Ten minutes per call, against a diary with no ten minutes in it
Every recorded call logged as activity against the right company
Three of fourteen calls logged in a normal week
Roles and timings surfaced as draft opportunities, not lost asides
Roles mentioned in passing that never become opportunities
Commitments you made turned into tasks with dates on them
Two consultants calling the same client a fortnight apart
Shared context, so the desk can see the account rather than the invoices
A resignation that takes the pipeline with it
A forecast built on what clients said, not on what got typed in

Try it

Walk through it yourself

This is the actual shape of the workflow — the same trigger, the same steps, the same draft waiting for your say-so. Click through it.

Log client calls into the CRM

TriggerZoom

Cloud recording ready — Wexley Group

Zoom publishes a new-cloud-recording trigger, so this starts as soon as the recording is processed. It works only from calls you already record; it never joins a meeting and never starts recording anything.

What it does

  1. Read the recording and match it to an account

    22-minute call with Alan Brightwell. Matched to Wexley Group in HubSpot from the calendar entry and his email domain.

    Zoom
  2. Check what the CRM already knows about this account

    Two open deals, both from July. No activity logged since 14 June. Last note is a placement confirmation, not a conversation.

    HubSpot
  3. Pull out what's commercially material

    2 roles signed off for September. Budget confirmed at £80–90k. He asked for contractor rates by Friday. A restructure was mentioned but not dated.

    HubSpot
  4. Draft the activity, the opportunities and the follow-ups

    1 call note, 2 draft opportunities with September timing, 1 task dated Friday for the rate card. Nothing written until approved.

    HubSpot

Draft list — nothing has been sent

Wexley Group — from the call on 6 August

  • 2 roles signed off — September start

    Platform Engineer and a second not yet titled. Budget stated as £80–90k. Drafted as two opportunities with September close dates.

    New pipeline
  • Contractor rate card — due Friday

    You committed to sending it by end of week. Drafted as a task assigned to you, dated Friday. This is the one that gets forgotten.

    You committed
  • Restructure mentioned, not dated

    Said in passing, no timing given. Logged as a note rather than an opportunity, because a vague mention isn't a forecast.

    Context
  • Account had no activity since 14 June

    Seven weeks of silence in the CRM against an account you've spoken to twice. Worth knowing how far the record had drifted.

    Gap closed

Log the call, create 2 opportunities and the Friday task?

Opportunities are the ones worth a look — a client saying something is signed off and it actually being signed off are different things, and you know which this was. Most desks approve the note and the task without reading and take a second over the pipeline entries.

Once you approveHubSpot

In the CRM, under your name

The note, opportunities and task are written to HubSpot or Pipedrive as your user, so the audit trail is intact. The rate card task appears on your list dated Friday. Nothing goes to the client, and nothing about the call is shared outside your own CRM.

The pipeline nobody was typing in.

Drafted from the call, written to the CRM only when you approve it.

Start free

How it works

What it's actually doing

Taking the commercially material parts of a conversation and putting them where the rest of the business can see them.

  1. 1
    • ZoZoom
    • FiFireflies
    • GoGoogle Meet

    Starts from a recording you already made

    Zoom, Fireflies or Meet. It never joins a call, never dials in and never initiates a recording — consent and policy are settled before it's involved.

  2. 2
    • HubSpot
    • PiPipedrive

    Matches the call to the right account

    From the calendar entry and the attendee domains, so activity lands on the company record without anyone filing it.

  3. 3
    • HubSpot
    • PiPipedrive

    Separates pipeline from context

    A signed-off role with a budget is a draft opportunity. A restructure mentioned vaguely is a note. Treating those the same is how forecasts become fiction.

  4. 4
    • HubSpot
    • PiPipedrive
    • Gmail

    Turns your commitments into dated tasks

    What you said you'd send, and by when. This is the highest-value output and the thing consultants most reliably forget between one call and the next.

You stay in control

It logs what was said. It doesn't decide what a deal is worth.

A CRM full of optimistic opportunities is worse than an empty one, because people plan against it. So the discipline is conservative: something becomes pipeline when a client said it was happening, and everything softer stays a note.

  1. Step one

    It drafts

  2. Step two — you

    You read it and approve

  3. Step three

    Only then does it send

Nothing is written without approval

Notes, opportunities and tasks are all proposals. Forecast data that arrives unreviewed stops being trusted within a month.

It won't inflate a vague mention into pipeline

"We might need someone in the new year" is a note. "Two roles signed off for September" is an opportunity. The gap between those is where CRM credibility lives.

It puts no value on a deal

Where a client stated a budget, that's recorded as what they said. It doesn't estimate fees, probabilities or close dates beyond timing that was actually given.

Client calls only

Candidate conversations aren't BD activity and don't belong in a commercial CRM record. Those go through interview notes, which is a different task with different rules.

Setup

What setting this up involves

  1. 1

    Connect

    • Zoom, Fireflies or Google Meet — wherever client calls are recorded
    • HubSpot or Pipedrive, whichever holds your BD
    • Google Calendar, so calls match to the right company
    • Gmail or Outlook, for follow-ups that need an email rather than a task
  2. 2

    Tell it how you work

    • Which calls are client calls — usually by domain or calendar category
    • What counts as an opportunity versus a note, in your language
    • Your deal stages, so drafts land in the right place
    • Who owns which account, so activity is attributed correctly
    • Whether to create tasks automatically or list them for you to pick
  3. 3

    Then it runs

    About 40 minutes, once

    Most of it is defining the opportunity threshold, which is worth doing carefully — set it loose and the CRM fills with wishful pipeline, which is the exact failure this is meant to fix.

Edge cases

Where it's careful, and what it won't do

What it handles

  • A call that's half BD and half catch-up

    Twenty minutes about a mutual contact and four minutes about two live roles. The four minutes become the record; the rest doesn't clutter the account.

  • A client who mentions a role but not a timeline

    Logged as a note with the wording used, not as an opportunity with an invented close date. Vague pipeline is worse than none because people plan with it.

  • Several people from one client on the call

    Activity is logged against the company with each contact associated, rather than attributed to whoever happened to speak most.

  • A commitment made in passing

    "I'll get you those rates by Friday" said once, mid-sentence, becomes a dated task. It's the single most commonly dropped thing on a BD desk.

What it does not do

  • Record or join calls

    It reads recordings that already exist because you chose to make them. Consent and notice happen before this is involved at all.

  • Create pipeline you haven't approved

    Every opportunity is a draft. An unreviewed forecast is one people stop believing, at which point the CRM is decoration.

  • Estimate deal values or probabilities

    It records the budget a client stated. It doesn't guess fees, weight probabilities or invent close dates.

  • Send anything to the client

    This writes to your CRM and nowhere else. Follow-up emails are drafted for you where you asked for them, never sent automatically.

Time back

Five to eight hours a week, and a forecast you can believe

Time back
5–8 hrs a week
Spent on
More calls, properly captured
What it costs
$49 / monthGrowthplan — see what’s included

How that’s worked out: Based on twelve to eighteen client calls a week per consultant at around ten minutes to log properly — time that mostly isn't spent, which is why the CRM is thin rather than why anyone is busy. The real return is pipeline that would otherwise never have been recorded, and continuity when a desk changes hands.

Fair questions

The questions agency owners ask first

Our consultants would object to their calls being processed like this.

That's a conversation worth having before you turn it on, and it usually lands better than expected because of what this specifically doesn't do. It doesn't score calls, doesn't measure talk time, doesn't evaluate how anyone sold, and produces nothing a manager could use to rank a team. It writes down what a client said. If your consultants suspect it's a performance-monitoring tool wearing a CRM costume, they'll work around it — so being explicit about that limit is the thing that makes it work.

We already have call recording with AI summaries built in.

Then you have the summary and probably still have the gap, because the summary sits in the recording tool and the CRM is where decisions get made. What matters is that a role mentioned on Tuesday becomes an opportunity someone can forecast against and a commitment becomes a dated task. If your existing tool writes structured records into HubSpot or Pipedrive already, you're covered — most of them stop at producing a summary you still have to read and re-enter.

How do we stop the CRM filling with rubbish opportunities?

By setting the threshold deliberately and keeping the approval step, which is why both exist. Something becomes an opportunity when a client said it was happening with some indication of timing; everything softer is a note. And because you approve each one, the drafts that don't match reality get rejected rather than accumulating. If anything, most desks find the threshold wants tightening after a fortnight, and that's an easy change.

FAQ

Questions worth answering properly

Does it record the calls?

No. It works from recordings that already exist because you record client calls today. It never joins a meeting, never dials in and never starts a recording. Consent, notice and your policy on recording are all settled before this is involved.

Which CRMs does it write to?

HubSpot and Pipedrive. Both accept notes, tasks and deal records, and both publish event triggers, so the integration works in each direction. Records are written under your own user so the audit trail stays intact.

What stops it creating opportunities that aren't real?

A deliberately conservative threshold plus your approval. Something becomes an opportunity when a client indicated it was happening with some timing attached; anything vaguer stays a note with the wording used. Every draft waits for you, so wishful pipeline gets rejected rather than accumulating.

Does it work on candidate calls too?

No, deliberately. Candidate conversations aren't business development and don't belong in a commercial CRM record. Those are covered by interview notes, which has its own rules — including that it forms no view about the person.

Can managers use this to monitor consultants?

Not in any meaningful way, and that's by design. It doesn't score calls, measure talk time, rate how anyone sold or produce comparative metrics about people. It extracts what a client said. A tool that doubles as surveillance gets worked around, and then it captures nothing.

What happens to the recordings and transcripts?

They stay in whichever tool made them, under the retention settings you already have there. What lands in your CRM is the structured record — the note, the opportunity, the task — not the transcript itself, unless you choose to attach it.

Stop losing next quarter's pipeline to a busy Tuesday

Connect the tool that records your client calls and your CRM. The next call logs itself for you to approve.

Start free