Logging call notes on a 10-rep sales team: 30% of every rep's day
For the executive who decides
One call, two mornings
The same sales call, today and redrawn. Who acts, in three lanes: the buyer, the machine, and the rep.
Today
Estimate. The $16 and the 29 minutes assume 5 calls a rep a day, because the team lead gave no call count; the $210,000 rests only on the team lead's own 30% and US median pay for a sales rep.
Redrawn
Estimate. The minutes and the $12 rest on the same 5 calls a day; the checking time is drawn at 3 minutes and is not known until counted.
- The customer acts
- The machine acts
- A person decides
- Nothing runs
An illustration built from the team lead's numbers: the times are examples, and the minutes a call are an estimate.
- 1The job
Logging call notes and updating the deal in the CRM after every sales call. A sales team of 10 reps; the industry and company size are not stated. The calls are recorded, or can be.
- 2The number today
I lead a sales team of 10. I pay these guys a lot of money to be on the phone closing deals, but they spend at least 30% of their day updating the CRM and logging notes.
That is about 6,240 hours a year across the team, three full-time people's worth. At US median pay for a sales rep ($33.65 an hour) it is about $210,000 a year in wages, about $21,000 a rep, or about $16 of rep time a call. At the median pay of a B2B account executive ($200,000 a year) it would be about $600,000 a year; treat that as a ceiling.Estimate. The $16 a call assumes 5 calls a rep a day, because the team lead gave no count; the $600,000 assumes the reps earn that much, which the post does not state. The team's own call count and pay replace both.
- 3The verdict
Hand over the notes. Keep the deal stage.
- Hand to the machine: recording and transcribing every customer call; writing the notes and next steps on the right deal; and drafting any other change, such as a new contact or a new close date, for the rep to approve.
- Keep with a person: the deal's stage, amount and close date; anything the buyer said loosely, like "maybe Q3"; and any call that matches no deal, or more than one.
- Not yet: filling deal fields from email threads; creating, merging or closing a deal, or adding a contact, on its own.
What the rep is for now: the conversation, and the read on where each deal stands. The machine does the typing. The forecast stays with the rep.
- 4The bill
About $250 a month for the 10 reps, with a call note-taker that writes into the CRM. The CRM's own call tools are the other main route: about $900 a month on a mid-tier sales plan, plus $1,500 to start, or little extra if the team already pays for that plan; the top plan of the largest CRM is about $5,500 a month. Building it is about $170 a month in running costs, plus 20 to 50 euros a month for the software that runs the steps, and then the build and the upkeep. People doing it by hand would cost about $5,400 a month for the three it would take. Checking: for the first two weeks, the rep approves every suggested change, and the team lead reads 10 calls a week against what was written. The check time is not known until it is counted.
Estimate. The build cost assumes about 1,050 calls a month of 30 minutes each.
- 5Owner and off switch
The sales team lead owns it, because the forecast is built on these fields. The off switch: in the note-taker's settings, set the CRM connection from automatic to manual. Notes stop going into the CRM, and reps log calls as they do today. It takes under a minute. Try it once in week one.
- 6The brief to hand your builder
The job: after every recorded customer call, write the notes and next steps on the right deal, and suggest any other change to the deal or its contacts for the rep to approve.
Today: 10 reps spend at least 30% of the day updating the CRM and logging notes. Rules set up in the CRM break on the exceptions.
Done when: for two weeks, every recorded call has notes on the right deal within 15 minutes of ending; no stage, amount or close date changes without a rep's approval; the reps' logging time a call is under a third of what it was the week before switch-on; and reps change fewer than 1 in 20 of the fields it wrote.
It may never, on its own: change a deal's stage, amount or close date; create, merge or close a deal; add a contact; or write anything the buyer did not say.
You get from us: 20 recorded calls with the notes the reps wrote for them, messy ones included; the short list of fields that matter, and which ones feed the forecast; admin access to the CRM for setup.
We own: the CRM, the recordings, the note-taker account and the billing.
We get back: each morning, a list for each rep of every field it wrote and every suggestion waiting, each with the line from the call it came from.
Ask whoever sets it up A good answer A bad answer Which fields will it change without asking us? Only the ones you list. Stage, amount and close date wait for the rep "All of them, automatically" What happens when a call matches no deal, or the wrong one? It goes to a holding list for a person. It never creates a deal on its own "It creates the record for you" How do I see what it changed, and undo it? Every change shows the old value, the new value and the line from the call, and can be reversed "It's very accurate"
For the operator who builds and runs it Paid layer
- 7The working set
- Trigger: a recorded external call or video meeting ends. Internal calls are skipped.
- Steps: transcribe; match the call to the account and open deal by attendee email; if there is no match or more than one, put it on a holding list for the rep; extract a fixed short field list (summary, next step, objections, proposed new contacts, proposed stage, proposed close date, proposed amount); write the low-risk text fields (summary, next step, objections) directly; hold new contacts, stage, amount and close date as suggestions for the rep; attach the transcript line behind every value; write approved changes and log each one.
- Data: one record per call: call ID, rep, date, length, matched account and deal (or "unmatched"), and for each field: old value, new value, the transcript line, status (written, approved, edited, rejected), and minutes from call end to approval.
- Review step: reps clear their waiting suggestions the same day. The team lead reads 10 random calls a week against what was written.
- Alerts: a call with no match; a suggestion waiting more than a day; a write blocked by a CRM validation rule or a broken connection; a mapped field overwritten (it replaces the old value after every call); and the wrong-but-green count, the fields reps changed after it wrote them.
- If it breaks: what you see: notes missing, notes on the wrong deal, or duplicate deals. Check first: the CRM connection is still authorized; the buyer's email on the invite matches the contact in the CRM; the deal is still open (closed deals are skipped). Safe fix: set the sync to manual; reps push each call by hand after reading it.
- Cost per call: about $0.24 with a note-taker at $25 a seat (Fathom Business, annual) over about 1,050 calls a month; about $0.16 in usage if built (Deepgram transcription $0.13, Claude Sonnet $0.03), plus the n8n plan.
- Baseline, before switch-on: one week of: minutes each rep spends logging a call (time it, do not ask), calls a rep a day, share of calls logged the same day, and the number of open deals with no next step.
Estimate. The cost per call assumes 5 calls a rep a day and 30 minutes a call. The baseline week replaces both.
Tools by name: Fathom Business ($25 a user a month annual) or Avoma ($19 plus $29 for two-way field updates); HubSpot Sales Hub Professional ($90 a seat annual, smart data capture with per-property manual review); Salesforce Max ($550 a user); built: Deepgram Nova-3, Claude Sonnet 5.5, n8n, the CRM's API.
The operator's map
The middle is the deal's status: whether the deal moved, what was agreed, and what goes in the forecast. The rep holds it.
The same job as a system. The middle is the deal's status, held by the rep. The call comes in on the left, is matched, written up and turned into suggestions across the top, and anything that changes the forecast drops to the rep on the right. Along the bottom is what it runs on: the switch and the alerts, the counts, and the rules for which fields wait.
- Runs on its own
- A person does it
- The judgment it all depends on
- What it runs on