Wednesday: the sales rep has three discovery calls scheduled. First is a mid-market company evaluating the product for the first time. Second is someone from that same company's finance team — they need to know the pricing model and what compliance certifications are in place. Third is a smaller company where the decision-maker is also doing the technical evaluation.
Three different conversations. Three different goals for each buyer. Three different pain points. Three different timelines. By the end of the day, three recordings sit on the Mac. Three transcripts. Three different summaries. Each one a record of what that specific buyer actually said they needed.
What makes discovery calls inefficient isn't the calls themselves. It is remembering, on the phone with a prospect, what the last prospect said about their timeline or their budget or their integration priority. It is writing a proposal and realizing you're not sure whether the buyer said "we need it by Q4" or "we want it by Q4." It is the moment the deal moves to a manager who didn't take the call, and you're trying to explain what the buyer said without the actual words.
8:30am — preparing for three different conversations
Before the first call, the rep reviews what's known about each prospect. First company: 500-person SaaS startup, likely need is for recording customer calls. Second call: the finance person from the same company. Third: smaller company, under 100 people, looking to record internal meetings.
The prep isn't new — it's the same prep before any discovery call. What's different is that notes from the call will be sitting on the Mac within minutes, not reconstructed from memory at the end of the day. The rep doesn't have to choose between listening fully and taking notes while listening. The recording does the notes.
9:00am — the first prospect: mid-market company, the product champion
The first call is with someone who asked for the demo after reading a comparison article. They're a product operations manager who's been frustrated with their current tool not capturing calls cleanly. They know what problem they're solving for. What they don't know is whether this product solves it better than the three others they're looking at.
The rep goes through the demo. Shows the recording and transcription. Plays a sample minute summary. The prospect asks questions about compliance and about setup — can their team deploy it without an IT ticket? By the end of the call, the rep knows this is someone who can move fast if the product is right. The prospect knows this could be the tool they were looking for, but they want to check with their security team first.
That last sentence is the moment that matters. What exactly did they say they need security to check? Did they say security approval is required or that they want to loop security in first? Those are different timelines. Without a recording, the rep is working from a vague memory. With a recording, the rep has the exact quote and the exact context.
- 00:26:14ProspectWe need our security team to approve the data handling before we commit. That's non-negotiable for us.
- 00:26:22Sales repHow long do security reviews usually take in your process?
- 00:26:29ProspectTwo weeks if they have what they need, four weeks if they need to ask for more info.
- 00:26:37Sales repSo best case, a decision in fourteen days if we send the right documentation now?
- 00:26:44ProspectThat's right. And I can push them to prioritize if they see we're moving.
10:00am — after the first call, before the second
The rep has ten minutes before the second prospect joins. That second person is the finance person from the same company. What should the rep know? The first conversation was about product fit. This one will be about pricing, contracts, and compliance. But the rep also knows from the first call that this company is serious — they're going to loop in security — which means the finance conversation is happening because they think the product might work.
The rep pulls up the summary from the first call. It has the key points: security review needed, two-week timeline, key value is better recording quality. Before this call starts, the rep reads the one-paragraph recap and knows the context. No guessing about what the first person said. It's right there.
10:00am — the second prospect: the finance person from the same company
The second prospect is the finance person who needs to understand pricing and contract terms. The product person already approved the features. Now finance wants to know: annual or monthly? Volume discounts? Is there a minimum? What's included in support?
These are the questions that determine whether a deal closes or sits in the pipeline forever. The prospect is professional and direct. They have a budget. They're willing to move if the pricing fits. They also want to know about data handling for compliance purposes — they're the one who makes the decision about which tools the company buys, and they want to make sure whatever comes in satisfies their audit requirements.
The conversation is faster than the product conversation because the questions are simpler. But what the prospect asks for — and when they ask for it — matters for the proposal. The rep needs to know whether they're asking for a discount before the end of the quarter or whether end of year is plenty of time. Without a recording, it's a vague memory: "they wanted to know about volume pricing." With a recording, it's the exact context: they wanted to know what happens if they buy licenses for their whole customer success team.
Decisions
- Pricing model works for their team size; they need a summary of our compliance approach in writing
Actions
- Send MSA template and security questionnaire by tomorrow; loop in sales engineering if they have follow-ups
Open questions
- Do they want to include support tiers in the quote or just discuss verbally?
10:35am — before the third call, comparing what two buyers from the same company said
The rep has three minutes before the third call. Different company, different buyer, different set of needs. But the rep now has two transcripts from the same company, and they answer different questions. The product person said: "We need your security team to approve the data handling." The finance person said: "I need a summary of your compliance approach in writing."
Are those the same ask or different? The transcript shows they're slightly different. Security person wants the review. Finance person wants the written summary. For the proposal to work, both need to happen. The rep now knows to include both in the follow-up plan.
11:00am — the third prospect: smaller company, tight timeline
The third company is much smaller. 85 people. The decision-maker is the head of operations, and they're doing both the product evaluation and the budget decision on the same call. They have a timeline: they want to start recording meetings by the end of the month. That's six weeks.
This prospect is hands-on with the technology side. They want to know about setup. Can they deploy it themselves or does it need engineering? How long does it take to transcribe a meeting? Can they export the recordings? These are different questions than the mid-market company asked.
By the end of this call, the rep knows this company moves faster than the first one. No security review. One decision-maker. Six-week deadline. But they also have a constraint: it has to integrate with Zoom and Google Meet, and the rep needs to confirm both are supported. Without the recording, the rep is hoping they mentioned both. With the recording, the rep knows exactly what they said was supported and exactly what the prospect said would make or break the deal.
- 00:18:43ProspectWe use both Zoom and Google Meet. If you only work with one, it doesn't work for us.
- 00:18:51Sales repWe support both. You can use the same license across both platforms.
- 00:18:58ProspectGreat. And recording starts automatically or do we have to press a button?
- 00:19:05Sales repYou press a button each time. It has to be deliberate, just like recording a Zoom meeting.
11:45am — end of calls, beginning of work
By noon, three calls are done. Three recordings on the Mac. Three transcripts. Three summaries. The rep has the rest of the day to turn these into next steps.
First company: security approval is the blocker. The rep sends the MSA and security questionnaire before lunch. The product person said "I can push them to prioritize if they see we're moving," so the rep also sends a quick email to the product person summarizing what finance needs, asking them to copy the security team.
Second call (the finance person): Finance person asked for a written compliance summary. The rep has a template. Send it within the hour.
Third company: Six-week timeline, both platforms required, recording is manual. The rep knows exactly what to include in the proposal because they know exactly what the prospect said they need.
All three of these follow-ups are more specific because they're based on what the prospects actually said, not what the rep guessed they meant.
Thursday morning — pulling a quote for the first company
Finance person from the first company replies asking for a proposal. The rep pulls up that call's summary and the product person's summary. What does the first company actually need? One license for the product person who championed it? Or licenses for the whole customer success team? The transcript shows: the finance person asked about volume pricing for their customer success team. That's the scope. The proposal is accurate because it's based on the actual conversation, not on what the rep guessed was important.
Thursday afternoon — the technical question about the third company
The third company's decision-maker sends a Slack message: "One more question — if we record with Zoom, can we download the file directly or does it only work through your app?" The rep searches the transcript from yesterday's call. Did they talk about downloading files?
They did. Not in detail, but enough. The prospect asked "Can they export the recordings?" and the rep answered yes. The exact answer is in the transcript. The rep now sends a clear answer based on the call, not a guess.
Friday morning — comparing what you learned
Friday, the rep has three prospects in three different stages. First company has made it through product and finance review, waiting on security. Second company (actually the same company as first, different person) already approved. Third company gets a proposal on Friday and is expected to decide by the middle of next week.
What did the rep learn from all three calls? Three different timelines. Three different decision paths. Three different budget levels. Three different compliance concerns. The rep can now segment these by what matters: which ones need security approval, which ones can move fast, which ones need which documentation.
All of that analysis is based on what the prospects actually said. Not what the rep guessed. Not what the rep's manager thought they said. What they actually said, in their own words, timestamped in the transcripts on the Mac.
Next week — one deal closes because the notes were specific
The third company decides by Wednesday. They move fast. The proposal addressed everything they said they needed. The deal closes.
Why did it close? Not because the product is better — all three companies saw the same demo. It closed because the proposal addressed the specific things that company said they needed, without wasting space on things they didn't mention. That specificity came from the transcript, not from the rep's memory.
Two weeks later — the finance question that could have sunk the deal
The first company's security team approves. Finance comes back with a question: "Your pricing says annual, but we're on a quarterly budget cycle. Can we do quarters?" The rep searches the finance call's transcript. The prospect asked "annual or monthly?" and the rep answered both are possible. That's the opening the rep needs to take them a proposal for quarterly payments.
Without the transcript, the rep is hoping they mentioned quarterly was possible. With the transcript, the rep can point to the exact moment it was discussed and move forward with a real negotiation, not a guess about whether the option was on the table.
The comparison that won the deal
Weeks later, the first company's decision-maker tells the rep: "Honestly, I looked at three other tools before you. Your note-taking just worked better in our trial." What made the notes work better? Not the feature set alone. The rep understood their specific concern — "better recording quality" — and made sure every conversation confirmed that was solved. That focus came from having the actual words from the first call, not from a paraphrase written at the end of a busy day.
What this workflow deliberately doesn't do
Nothing here integrates into Salesforce or any CRM. The recordings don't sync into a shared pipeline, don't contribute to forecasting, and don't get reviewed by a sales manager from a dashboard. Each prospect's transcripts live on the rep's Mac, searchable by them, under their control. A sales organization that runs forecasting through a shared system has reasons to stay there. This workflow is local-first because that's what a sales rep needs in the moment of a call: to listen, to understand, and to have the proof of what was said when the call is over.
The day reps stop paraphrasing deals
The first day of recording calls feels deliberate — remembering to set up the recording, remembering to save each file with the prospect's name. By the third week, a sales manager asking "what did they say they needed?" gets answered with a search, not with "I think they said something about..." By week four, the rep is writing proposals that are more specific and closer to what the prospect asked for, simply because the proposals are based on the actual conversation instead of a reconstructed version of it.
What it costs, what it runs on
Coii AudioNotes is $19, once, covering up to three of your own Macs, with a 30-day trial needing no card and no account. It runs on macOS 13 Ventura or later, Apple Silicon or Intel — the same machine you use for Zoom calls with your prospects. The full case for a sales rep's notetaker covers why this matters in more depth than a single day can, and how to search your old meetings walks through finding what a prospect said weeks later. How to write minutes from a transcript covers turning calls into summaries for your team, and how to ask questions about a past meeting covers the technique of working backward from a prospect's follow-up to find the original conversation that sparked it. The round-up of private meeting recorders covers the wider field of tools that don't upload your conversations to a server, and meeting notes apps without a bot covers the broader category for teams that want local-first recording.