How to Run a Weekly Call Review for a Two Rep Sales Team

How do you run a call review when your whole sales team is two people?

Block 45 minutes once a week. Each rep picks one recorded call, good or bad. Both people listen to the key moments together, score them against a short shared scorecard, and agree on one change to try next week. Log that change in the CRM. Small, steady, and honest beats a monthly coaching marathon.

Small B2B teams rarely review calls. There is no sales manager, no enablement team, and every hour feels like it should go to selling. So reps repeat the same discovery mistakes for months, and the founder only notices when win rates slide.

I help B2B teams design the systems behind their go-to-market, and a lightweight call review is one of the cheapest habits I recommend. This tutorial walks through the exact setup for a team of two, step by step, using whatever call recorder you already have.

What do you need before the first review?

You need three things: recorded calls with buyer consent, a one page scorecard both reps agree on, and a recurring 45 minute slot on the calendar. You do not need special software. Any recorder that saves calls and transcripts, plus a shared document, is enough to start this week.

Consent comes first. Recording rules differ by location, so tell buyers at the start of the call that you record, and follow the consent rules that apply to you and your buyer. Most recorders can announce this automatically, but check how yours works in its own documentation.

The scorecard is the heart of the review. Keep it to five or six questions, each answered with a simple yes, partly, or no. Did the rep confirm the problem in the buyer's words? Did they learn who else decides? Did they agree a clear next step with a date? Short scorecards get used. Long ones get skipped.

If you already score cold emails, reuse the same format so the habit feels familiar. I described that approach in how to write a cold email scorecard for your team, and the structure carries over to calls almost unchanged.

How should each rep pick which call to bring?

Each rep brings one call from the past week. Alternate weeks between a call that went well and one that went badly. Good calls show what to repeat. Bad calls show where deals leak. Rotating keeps the review from becoming a weekly trial, which is the fastest way to kill the habit.

Ask each rep to mark two or three timestamps before the meeting. These should be the moments that mattered: the question that opened the buyer up, the objection that stalled things, or the point where the call lost energy. Listening to marked moments takes minutes. Listening to whole calls takes the entire hour.

Prefer discovery calls and first demos over late stage negotiations. Early calls shape the whole deal, and they are where small teams usually have the most room to improve. A sharper discovery question asked on every call is worth more than one rescued negotiation.

How do you structure the 45 minutes?

Spend five minutes on context, fifteen minutes per call on the marked moments and the scorecard, and the last ten minutes agreeing on one change each. The structure matters more than the content. Without it, reviews drift into storytelling about the deal instead of looking at what was actually said.

Start with context. The rep bringing the call explains who the buyer was, what stage the deal is in, and what they want feedback on. Two or three sentences is enough. Then play the first marked moment.

After each moment, pause and let the other rep speak first. Ask what they heard, not what they would have done. Then score the call together on the scorecard. Disagreements are useful. If one rep thinks the next step was clear and the other does not, that gap is worth discussing.

End with commitments. Each rep names one specific thing to do differently on calls next week. Not "ask better questions," but "ask who else signs off before the demo ends." One change, stated plainly, is something you can check next week.

What should you do with what you learn?

Write each week's commitments and patterns in one shared document, and log the scorecard results against the deal in your CRM. Over a month, patterns appear. Those patterns should change your discovery questions, your qualification rules, and sometimes your website and sales materials, not just individual habits.

The shared document can be simple. One heading per week, the two calls reviewed, the scores, and the two commitments. At the next review, start by checking last week's commitments. Did each rep try the change? Did it help? This keeps the review connected from week to week.

Logging scores in the CRM lets you connect call quality to outcomes. In HubSpot or any CRM, a few custom fields on the deal can hold the scorecard answers. After a quarter, you can see whether deals with a confirmed decision process close more often. That turns opinion into evidence.

Patterns should also flow into how you qualify leads. If reviews keep showing calls with buyers who had no real problem, your definition of a qualified lead may be too loose. I wrote about setting that bar in what should count as a qualified lead for a two person team.

How do you keep the review honest without hurting morale?

Score the call, not the person. Keep the scorecard focused on behaviors anyone can change, like asking about the decision process. Make sure good calls get the same airtime as bad ones. And if a founder is one of the two reps, they should bring their own weak calls first.

The founder point matters a lot in small teams. If the founder only reviews the other rep's calls, the review feels like an inspection. If the founder plays their own clumsy discovery call in the first week, it signals that everyone is learning, including the person who started the company.

Language helps too. Saying "the next step here was vague" is about the call. Saying "you are bad at closing" is about the person. Agree on the scorecard language up front, and use it during the review. It keeps feedback specific and easier to hear.

How can AI help without replacing the review?

Use AI to prepare the review, not to run it. A transcript and an assistant like Claude or ChatGPT can summarize a call, pull the buyer's stated problems, and draft a first pass at the scorecard. The two reps still listen to the real moments and decide what to change.

The value of the review is the conversation between two people who sell the same product. An AI summary can point you to the right timestamps faster. It cannot tell you how the buyer's tone changed when price came up, or why a pause felt awkward. Listening together still matters.

If you use AI on transcripts, check what your recorder and AI tool do with call data, and keep sensitive buyer information out of tools that are not approved for it. That is a basic data hygiene rule for any automation that touches customer conversations.

How do you know the review is working?

Track two things for a quarter: scorecard trends and meeting outcomes. If scores on key questions rise, such as confirming the decision process, and more first calls lead to a defined next meeting, the review is working. If scores stay flat after a month, change the scorecard or the format, not the habit.

A clear definition of a good outcome helps here. For outbound, I like to agree in advance what counts as a good first meeting, which I covered in how to define what counts as a good outbound meeting. With that definition, you can see whether better calls actually lead to better meetings.

Also watch whether the review survives busy weeks. A habit that disappears every time the pipeline gets hot was never really a habit. Keep the slot even in busy weeks, and shorten it to one call if you must. Consistency is what builds the skill over time.

What should you do next?

Put a 45 minute weekly slot on both calendars starting this week. Draft a five question scorecard together. Each rep picks one recorded call and marks two or three moments. Run the first review, agree on one change each, and log it. Then repeat for four weeks before you judge it.

After a month, read back through the shared document. Look for the patterns that keep appearing, and decide whether they point to a coaching fix, a qualification fix, or a change to your sales materials. Then adjust the scorecard so it keeps measuring what matters most.

If you want help building the go-to-market systems around habits like this, from scorecard fields in your CRM to reports that link call quality to pipeline, reach out. Helping small teams sell with more structure is a big part of my work. Let's chat.