Almanac Blog

Real-Time AI Sales Call Assistant: How to Choose One in 2026

Wed, 17 Jun 2026 00:00:00 GMT

A real-time AI sales call assistant is software that listens to a live sales call and surfaces guidance on the rep's screen while the conversation is still happening: the answer to a question just asked, the right proof point, a nudge when the rep has been talking too long, a reminder of a stakeholder still missing from the deal. The point is to change the outcome of the call in progress, not to score it afterward. When you evaluate one in 2026, the decision is not which tool has the most features. It is which tool intervenes the least while still catching the few moments that decide a call. This guide explains what these assistants actually do live, how they differ from the post-call category most teams already own, and the specific criteria that separate a useful one from an expensive distraction.

A real-time AI sales call assistant belongs to the live layer of the call, the subject of our complete guide to real-time sales coaching. Everything below assumes that framing: the value is in the moment, or it is not there at all.

What does a real-time AI sales call assistant actually do?

It does three things during a live call: it recognizes the moment guidance would help, it retrieves the relevant information, and it surfaces that information quietly enough that the rep can use it without losing the buyer. Those three steps, moment-detection, retrieval, and restrained delivery, are the whole product. Everything else a vendor lists is packaging.

In practice, the help falls into a few concrete categories:

Answer surfacing. A buyer asks a pricing, technical, or security question; the assistant puts a vetted answer on screen before the silence gets awkward. This directly attacks a known failure: Allego found that reps cannot answer 40% of the product questions buyers ask.
Behavioral nudges. A talk-time meter that flags when the rep has held the floor too long, a simple guardrail against the monologue that quietly sinks discovery calls.
Context recall. Surfacing the relevant case study, the buyer's prior objection, or the next agreed step, so the rep does not have to hold it all in working memory.
Stakeholder prompts. A reminder, mid-call, that the economic buyer has not been engaged and that asking for the introduction should be a call objective.

The common thread is that all of it is timed to the live conversation. A case study delivered after the call is content; the same case study surfaced the second the buyer raises the exact concern it addresses is coaching.

How is it different from post-call conversation intelligence?

Most teams already own a post-call tool that records, transcribes, and scores conversations after they end, and many assume that covers them. It does not. Conversation intelligence is conversation intelligence: it analyzes the past. A real-time assistant acts in the present, on a deal you can still change. Buying the first and expecting the second is the most common mistake in this category.

Capability	Real-time AI assistant	Post-call conversation intelligence
When it acts	During the live call	After the call ends
What it changes	This deal's outcome	The next call's behavior
Core job	Surface the right thing, now	Analyze what happened
Risk if done poorly	Distracts the rep mid-call	Generates reports nobody opens
Buyer for it	The rep on the call	The manager reviewing later

The two are complements, and a mature stack runs both: real-time to win the call, post-call to improve the team over time. The deeper comparison, including why the live layer is the harder and less crowded problem to solve, is in the real-time sales coaching hub. For this guide, the operative point is narrow: do not let a post-call tool you already pay for talk you out of evaluating the live one, because they do not do the same job.

What criteria actually matter when choosing one?

The criterion almost nobody weighs heavily enough is restraint. A real-time assistant that surfaces ten prompts a minute makes calls worse, not better, because the rep reads the screen instead of the buyer and the talk ratio degrades. The best assistant is the one that stays silent until a moment genuinely calls for it. Lead your evaluation with that, then work through the rest.

Restraint and signal quality. Does it intervene rarely and accurately, or does it fire on every keyword? Watch a real call in the demo, not a scripted one, and count the interruptions. Fewer and right beats many and noisy, every time.
Latency. Guidance that arrives after the moment has passed is worse than none, because it pulls attention backward. The answer to a question has a useful life of a few seconds. Test it on a live connection, not a recording.
Answer accuracy and sourcing. When it surfaces an answer, is it drawn from your vetted material, and can the rep see where it came from? An assistant that confidently surfaces a wrong number is a liability with a UI.
Unobtrusive delivery. Can the rep absorb a prompt with a glance, or does using it visibly break eye contact and rhythm? The interface is not cosmetic here; it determines whether the tool helps or hurts in the only setting that matters.
It closes the loop with prep and follow-up. The live moment is one of three. An assistant that also draws on the pre-call brief and feeds an instant debrief is worth more than a standalone widget, because the same context flows through all three stages.
Privacy and consent posture. Live call listening carries real compliance weight. Confirm how recording consent is handled across the regions you sell into before anything else gets signed.

Notice what is not on the list: a long feature matrix. In this category, more features usually means more interruptions, and more interruptions means a worse call. Evaluate for judgment, not surface area.

Should you build the practice or buy the tool first?

Build the practice first. A real-time AI sales call assistant amplifies a live-coaching habit; it does not create one. Teams that buy the software before they have any practice of in-the-moment guidance end up with a tool reps mute by the second week, because nobody decided what a useful intervention even looks like. The software is worth buying precisely when you already know which live moments keep costing you deals.

The reason build-first works is leverage. Reps already spend a shrinking share of their week in live conversations, so the few calls they get carry outsized weight, and more than half of buyer meetings are wasted before any tooling enters the picture, per RAIN Group's finding that 58% of seller meetings provide no value. Fix the practice and you raise the floor on every call for free. Then add an assistant to catch what discipline alone misses: the question outside the rep's depth, the monologue the rep does not notice, the stakeholder nobody asked for. For the question-you-cannot-answer moment specifically, the manual technique is worth mastering before you automate it, and we cover it in what to do when you don't know the answer on a sales call.

This sequencing also makes the buying decision sharper. A team that has run live ride-alongs knows the three or four interventions it actually wants, which turns a vague "evaluate AI sales tools" project into a concrete test: does this assistant nail those specific moments, quietly? That is a question a demo can answer in twenty minutes.

Doing this with Almanac

Almanac is built for the live layer. During the call it runs a quiet sidebar that surfaces an answer when a question is asked, the proof point matched to the buyer's situation, and a nudge when the talk ratio drifts, designed to intervene rarely so you stay with the buyer rather than the screen. It draws on the pre-call brief it assembled before you joined and feeds an instant debrief after you hang up, so the same context carries across preparation, the live call, and follow-up.

Frequently asked questions

What is a real-time AI sales call assistant?

It is software that listens to a live sales call and surfaces guidance on the rep's screen while the conversation is happening, such as the answer to a question just asked, a relevant proof point, or a nudge that the rep is talking too much. Its purpose is to improve the outcome of the call in progress, which distinguishes it from post-call tools that only analyze the conversation after it ends.

How is it different from a tool like a post-call recorder?

A post-call recorder transcribes and scores conversations after they end, to help managers review and spot trends. A real-time assistant acts during the live call, on a deal you can still change. They solve different problems and a strong stack uses both, but do not assume a recording-and-scoring tool gives you live guidance, because it does not.

Will a live AI assistant distract reps on the call?

It can, and that is the main risk to evaluate. An assistant that fires constant prompts pulls the rep's attention off the buyer and worsens the call. The good ones are restrained by design, surfacing something only on the few moments that genuinely matter. When evaluating, watch a live call and count the interruptions: fewer and accurate is the goal.

Do I need one if I already have a pre-call research tool?

They cover different stages. Pre-call tools prepare you before the call; a real-time assistant helps during it. The strongest setup connects both, plus an instant debrief afterward, so the same context flows through all three. If you have to choose, fix the stage where deals actually slip, which for most teams is the live conversation itself.

What to Do When You Don't Know the Answer on a Sales Call

Tue, 16 Jun 2026 00:00:00 GMT

When you don't know the answer on a sales call, say so plainly, write the question down in front of the buyer, and commit to a specific follow-up time: "Good question, and I don't want to guess at it. Let me confirm with our team and get you an exact answer by tomorrow afternoon." That is the entire move, and it builds more trust than any improvised answer. Buyers do not expect a rep to know everything. They do expect honesty, and they can tell when you are bluffing. The instinct to fill the silence with a confident-sounding guess is the actual mistake, because a wrong answer surfaced later costs you the deal and the relationship. This guide gives you the exact four-step response, the phrasing to use and avoid, and how to turn the gap into a follow-up that moves the deal forward instead of stalling it.

Handling the question you cannot answer is one of the decisive moments covered in our guide to real-time sales coaching, and it is the one that most directly defines whether a buyer decides you are trustworthy.

Why is admitting you don't know actually the stronger move?

Because the buyer is evaluating your honesty more than your knowledge, and a clean "I'll confirm that" reads as confidence while a bluff reads as risk. Buyers assume no single rep holds every technical and contractual detail. What they cannot assess is whether they can trust what you tell them, and a guess that later proves wrong answers that question in the worst way.

The data says reps get caught far more often than they would like to admit. Allego's research found that, on average, sellers cannot answer 40% of the product questions buyers ask, and that roughly 70% of companies say their reps frequently stray off message. So the question is not whether you will be stumped. It is whether your team has a disciplined way to handle being stumped, or whether each rep improvises, and improvisation under pressure is how wrong information enters a deal.

There is also a relationship cost to bluffing that compounds. A buyer who catches one fabricated answer re-examines every other answer you have given, and the burden of proof on your honest claims goes up for the rest of the deal. Reps win deals by being seen as a trusted advisor, not as a walking spec sheet, and trusted advisors are the ones who say "I don't know, let me find out" without flinching.

The 4-step move when you're stumped

The reliable response is four steps run in order: acknowledge, capture, commit, redirect. It takes about fifteen seconds, it works for any kind of question, and its real value is that it is a routine, so you are not inventing a reaction while your pulse is up. A routine is what keeps a stumped moment from becoming a credibility moment.

Step	What you do	Why it works
1. Acknowledge	Affirm it is a fair question and that you will not guess	Signals honesty and respect, defuses your own panic
2. Capture	Write it down visibly, ideally repeating it back	Shows you take it seriously and pins down the exact ask
3. Commit	Name a specific person and a specific deadline for the answer	Converts a gap into a concrete next step you control
4. Redirect	Move the conversation forward without dwelling	Keeps the call's momentum and your composure intact

1. Acknowledge without apologizing your way into a hole

Name the question as legitimate and state plainly that you will get the exact answer rather than guess. Keep it short and unbothered. "That's an important one, and I want to give you the precise answer, not my best guess." What you are avoiding is the spiral of over-apology ("oh gosh, I'm so sorry, I really should know this") that turns a normal gap into a visible loss of footing. One calm sentence, then move to capturing it.

2. Capture it where the buyer can see

Repeat the question back in your own words and write it down, on camera if you are on video. This does two jobs: it proves the question will not be forgotten, and it forces precision, because pinning the exact ask often reveals that the buyer's real concern is narrower or different than your first read. "So you want to know whether the data stays in-region for EU customers, specifically, not just where the company is headquartered, is that right?" Now you are answering the question they actually have.

3. Commit to a who and a when

Vague promises ("I'll look into that") are where credibility quietly leaks out, because they sound like the thing reps say to move past a question they will never revisit. Replace it with a named owner and a deadline: "I'll confirm this with our security lead and send you the documented answer by end of day tomorrow." The specificity is the trust signal. It tells the buyer you have a real process behind you and that the follow-up is a commitment, not a brush-off.

4. Redirect to keep momentum

Once captured and committed, do not linger in the discomfort. Bridge cleanly back to the thread you were on, or hand the floor back with a question. "While I get that confirmed, can you tell me more about how your current process handles that case today?" The redirect signals that an unknown is a normal part of a thorough conversation, not a wound to nurse, and it keeps the call advancing.

What phrasing should you avoid?

Avoid anything that bluffs, minimizes, or over-apologizes. The wrong phrasing does more damage than the gap itself, because it converts "the rep didn't know one thing" into "I'm not sure I can trust this rep." A short table of swaps:

Don't say	Say instead
"I think it's probably around..."	"I won't guess on numbers. I'll confirm the exact figure and send it."
"I'm so sorry, I really should know that"	"Fair question. Let me get you the precise answer."
"I'll look into that" (and move on)	"I'll confirm with [name] and have it to you by [time]."
"Yes, definitely" (when unsure)	"I believe so, but I'd rather confirm than have you act on a maybe."

The "yes, definitely" reflex is the most dangerous one, because it feels helpful in the moment and creates the worst outcome later: a buyer who made a decision on information you guessed at. A confident wrong answer is the only response on this list that can lose you the deal after the call is over.

How preparation shrinks the problem before it starts

Most stumped moments are predictable, which means most of them are preventable. The questions that catch reps are rarely exotic; they cluster around pricing edge cases, security and data handling, integrations, and contract terms. If you know the buyer and the call type, you can anticipate which of these is coming and have the answer ready, which turns a real-time scramble into a prepared response.

This is where the live moment connects back to the work before the call. Solid pre-call research tells you a security-minded evaluator is in the room, so you load the data-residency answer in advance. Knowing the buying committee tells you the CFO will press on payback period, so that number is at your fingertips, not in a guess. Preparation does not eliminate the unknown question, but it shrinks the category to the genuinely novel ones, which are the only ones you should be improvising a process for.

For the questions you still cannot fully anticipate, a real-time assist closes the remaining gap. An assistant that surfaces a vetted answer the instant a known question is asked, or a manager whisper-coaching a high-stakes call, means the four-step move above is your fallback rather than your only option. The full picture of how that live layer works is in the real-time sales coaching guide.

Turning the unknown into a follow-up that advances the deal

A captured question is a gift, because it gives you a legitimate, buyer-requested reason to make contact again with something of value. Most follow-ups are "just checking in," which buyers ignore. "Here is the documented answer to the data-residency question you raised, plus the relevant compliance page" is a follow-up the buyer is waiting for and will open. Handled well, the question you could not answer becomes the strongest next step in the deal.

To make it land, deliver early against the deadline you set, put the answer in writing so it can be forwarded to stakeholders who were not on the call, and use the moment to confirm the next step. The rep who promised an answer by tomorrow and sent a clear one by this afternoon has demonstrated, concretely, what working with them will be like. That is worth more than having known the answer cold, because reliability under a real commitment is harder to fake than knowledge.

Doing this with Almanac

Almanac helps on both sides of the stumped moment. Before the call, its brief flags the likely hard questions from who is attending and how the deal is progressing, so fewer of them catch you cold. During the call, its quiet sidebar can surface a vetted answer the moment a known question lands, and after you hang up, its instant debrief captures the open questions you committed to, so the follow-up actually happens on time.

Frequently asked questions

Is it bad to say "I don't know" on a sales call?

No. Said well, it builds trust, because buyers value honesty over a rep who knows every detail. The full move is to acknowledge the question, write it down, and commit to a specific follow-up time. What damages credibility is not the gap itself but bluffing a confident wrong answer, which a buyer may catch later and which then calls everything else you said into question.

How do you handle a technical question you can't answer in sales?

Use the four-step move: acknowledge it is a fair question, capture it precisely by repeating it back, commit to a named expert and a deadline ("I'll confirm with our security lead by tomorrow"), then redirect to keep the call moving. Technical questions are also the most predictable, so anticipate the likely ones from your pre-call research and load those answers before you join.

What should you never do when stumped on a sales call?

Never guess and present it as fact, especially with a confident "yes, definitely." A wrong answer the buyer acts on is the one mistake here that can lose the deal after the call ends. Also avoid the vague "I'll look into that" with no owner or deadline, which reads as a brush-off, and the over-apology spiral, which turns a normal gap into a visible loss of composure.

How do you follow up on a question you couldn't answer live?

Deliver the answer early against the deadline you set, in writing so it can be forwarded to stakeholders who missed the call, and use it to confirm the next step. A buyer-requested answer is a far stronger reason to re-engage than a generic check-in, so a well-handled unknown often becomes the most productive follow-up in the entire deal.

What to Research Before a Sales Call: The 6-Point Checklist

Fri, 12 Jun 2026 00:00:00 GMT

Wondering what to research before a sales call? Six things, in this order: company fundamentals and recent news, the people who will be on the call, the org structure around your buyer, trigger events and buying signals, the prospect's tech stack and current vendors, and every past interaction logged in your CRM. Cover those six and you can open with a relevant point of view instead of "so, tell me about your business." The full sweep takes about 15 minutes once you have a routine, and the checklist below assigns a time budget to each item so you never spend 45 minutes researching a 30-minute call.

Why do most reps still walk in blind?

Most reps skip research because nothing immediately punishes them for it. The buyer punishes them later, silently, by not booking the next meeting. Buyers say 58% of their meetings with sellers don't provide value, according to RAIN Group's Center for Sales Research. Those are meetings the buyer agreed to take, and more than half were a waste of their time.

The cost of showing up unprepared is just as well documented. LinkedIn's State of Sales research found that 77% of decision makers won't engage with salespeople who don't have insights or knowledge of their business. You don't get a warning. The buyer answers politely, says "send me some information," and disappears.

The fix is not heroic effort. It is a repeatable checklist, the backbone of any serious approach to sales call preparation, with hard time limits per item.

The 6-point pre-call research checklist

A pre-call research checklist is a fixed list of information sources you review, in the same order and within set time budgets, before every scheduled sales call. The fixed order matters as much as the content: it stops you from rabbit-holing on LinkedIn for 25 minutes and never opening the CRM.

Here is the full checklist with time budgets for a standard discovery or first call:

#	Research item	Primary sources	Time budget
1	Company fundamentals and recent news	Website, newsroom, Google News	3 min
2	The people on the call	LinkedIn profiles, company bio pages	4 min
3	Org structure and decision dynamics	LinkedIn org browsing, job postings	2 min
4	Trigger events and buying signals	Funding news, hiring pages, press	2 min
5	Tech stack and current vendors	Job postings, review sites, careers page	2 min
6	Past interactions in your CRM	CRM activity log, email threads	2 min
	Total		15 min

If you only have five minutes, do items 2, 6, and 1, in that order. Knowing the people and your own history with the account beats knowing their funding round.

The budgets assume you do this daily and have your tabs and saved searches ready. If you are building the habit from scratch, start with a repeatable pre-call research routine and expect each item to take roughly double at first.

1. What company fundamentals should you check first?

Start with four facts: what the company sells, who they sell it to, roughly how big they are, and what has changed in the last 90 days. That last part is where most reps stop short. Static facts make you sound informed; recent changes give you something to actually talk about.

In your three minutes, hit:

Homepage and product pages. How do they describe themselves? Mirror their language on the call.
Newsroom or blog. Skim the last quarter's headlines for launches, hires, or new markets.
A news search on the company name, past three months: funding, layoffs, acquisitions, executive changes.
Revenue and headcount estimates, so you can calibrate which customer stories will land.

Write down one sentence: "Company X does Y for Z, and the most notable recent thing is W." If you cannot fill in W, you have not finished this step.

2. Who exactly is on the call, and what do they care about?

Research every confirmed attendee, not just the person who booked. This is the highest-value item on the list, which is why it gets the biggest budget. Spend about two minutes per attendee on LinkedIn and note:

Role and tenure. Someone six weeks into a VP job is shopping for early wins. Someone six years in is protecting a system they built.
Career path. A VP of Operations who came up through finance will ask cost questions. One who came up through the warehouse floor will ask workflow questions.
Recent activity. Posts, comments, or shared articles tell you the topics already on their mind.
Mutual connections. A genuine shared contact is the fastest trust shortcut available.

One caution: reference what you learned naturally, not performatively. Reciting someone's resume back to them is unsettling.

3. How does the org structure shape the deal?

Your goal in two minutes is a sketch, not a census: who does your contact report to, who reports to them, and which adjacent teams touch the problem you solve. That sketch tells you whether you are talking to the economic buyer, a champion who must sell internally, or a researcher gathering options for someone else.

Browse the company's people on LinkedIn filtered by department. Look for the layer above your contact (the likely budget holder), peers who would feel the impact of a change, and any role like "RevOps" or "Procurement" that signals a formal buying process.

A first call only needs the rough shape. You can build the full committee view later with a proper approach to mapping deal stakeholders once multiple people are involved.

4. Which trigger events and buying signals matter?

A trigger event is a change inside the prospect's business that creates new pressure to act: a funding round, an executive hire, an expansion, a regulation. Triggers explain why now. A prospect with a live trigger has a deadline; one without is comparison shopping.

In two minutes, check for:

Funding or financial events. New capital means growth targets and budget.
Leadership changes. New executives typically review vendors in their first two quarters.
Hiring surges or freezes. Postings signal investment; a freeze signals do-more-with-less pressure, which is its own trigger.
Expansion or contraction. New offices, markets, or product lines, or closures and layoffs.

If you find a trigger, build a question around it rather than a statement. A question does far more work than congratulations.

5. What can the tech stack and current vendors tell you?

The tools a prospect already runs tell you how mature their process is, what they are used to paying for, and who you are actually displacing. Most deals are not against a competitor in the room. They are against the current way of doing things, and you should know what that is before you dial in.

Fastest sources, in order:

Job postings. Listings name required tools with remarkable honesty. "Experience with NetSuite and a homegrown TMS" is a competitive briefing in one line.
Review sites. Search the company name to see what their employees have reviewed.
Careers and engineering pages. Many companies list their stack outright.

If they use a direct competitor, prepare for "how are you different" without bashing anyone. If they run on spreadsheets and email, your competition is inertia, and your discovery questions should quantify its cost.

6. What should you pull from your own CRM?

Check your CRM last, but never skip it, because nothing torches credibility faster than ignorance of your own company's history with the account. Two minutes covers it: previous opportunities and why they closed or died, every contact your company has touched, recent marketing engagement, and how this meeting came to exist.

That last point deserves special attention. A prospect who requested a demo after reading your pricing page is in a completely different conversation than one a colleague cold-called. Also check whether anyone at the account used your product at a previous job. Former users are the warmest path into any account, and they are routinely missed because nobody looked.

Turning research into three call-ready talking points

Research only pays off if it compresses into something you can use live. Reps who do this well end their prep by writing exactly three talking points: one insight, one hypothesis, and one relevant proof point. This matches what buyers reward; RAIN Group found that content customized to their specific situation influences 67% of buyers to engage.

Here is a worked example. The call: a 30-minute discovery with Dana Reyes, VP of Operations at Meridian Freight, a 200-person regional logistics company. Fifteen minutes of research surfaced a new Dallas cross-dock facility announced in April, Dana's promotion from Director eight months ago, four open "operations analyst" postings that all mention Excel and a legacy TMS, and a colleague's dead 2024 opportunity lost to "no decision."

The three talking points:

Insight (from triggers and stack): "Most regional carriers we work with hit a wall on manual exception handling somewhere between two and four facilities. With Dallas coming online, where is that load landing today?"
Hypothesis (from the people and org research): "Given you stepped into the VP seat recently and you're hiring four analysts, my guess is you're trying to build reporting muscle before peak season. Is that close?"
Proof point (matched to their size): "A 250-person carrier we work with cut exception resolution from two days to four hours. Happy to share how, if it's relevant."

Plus one honest opener from the CRM: "I know our teams spoke in 2024 and the timing wasn't right. I'd rather start from what's changed than re-run that conversation."

Manual research vs an automated pre-call brief

Everything above is doable by hand, and you should do it by hand long enough to know what good looks like. The cost is 15 minutes per call, which across five or six daily calls eats real selling time, plus the consistency problem: on busy days, research is the first thing reps cut.

This is the gap pre-call intelligence tools are built to close. Almanac, for example, assembles a brief before you join: who is on the call and their roles and tenure, recent company news, a map of the likely buying committee, how the prospect found you, and your relevant talk tracks preloaded. The checklist stays the same; the gathering stops being manual. Whether you build the brief yourself or have it built for you, the standard holds: never join a call without one.

Frequently asked questions

How long should pre-call research take?

About 15 minutes for a first call with a new prospect, using fixed time budgets per source. For later-stage calls with familiar accounts, a five-minute refresh (new news, new attendees, CRM activity since last touch) is usually enough. If research regularly takes 30+ minutes, you are collecting information you won't use on the call.

What is the most important thing to research before a sales call?

The people on the call, by a wide margin. Company facts are table stakes, but calls are won person to person. Knowing each attendee's role, tenure, and background lets you calibrate your questions, examples, and proof points to what they personally care about. Your own CRM history with the account is a close second.

What should you research for a follow-up call versus a first call?

For a follow-up, shift from external research to internal review: re-read your notes from the last call, confirm the agreed next steps, and check the invite for new attendees, who get the full person-level treatment from item 2. Then do a two-minute external refresh for news published since you last spoke.

Can you over-research a prospect?

Yes, in two ways. You can spend selling time gathering facts that never affect the conversation, and you can use personal details in ways that feel invasive. Stick to professional, public, business-relevant information, time-box the work, and remember the goal is three usable talking points, not a dossier.

The 10-Minute Pre-Call Research Routine for Busy Reps

Thu, 11 Jun 2026 00:00:00 GMT

If you want to know how to research a prospect before a call without losing your morning to it, the answer is a timed routine: two minutes on the company, three on the people, two on org context, two on triggers and timing, and one writing three talking points. That is the whole system. A pre-call research routine is a fixed sequence of sources you check in a fixed order, with a hard stop, so every call gets the same baseline of preparation no matter how slammed your calendar is. Below is the exact 10-minute version, with one real-feeling example carried through every step, plus a 60-second fallback for the days when even ten minutes is a fantasy.

Why is 10 minutes the right budget (not 45, not zero)?

Ten minutes is the right budget because it is long enough to find everything that changes how you open a call, and short enough that you will actually do it before every call. Forty-five minutes of research produces maybe two more usable facts than ten. Zero minutes produces a call that sounds like every other vendor's call.

The data backs the discipline. In LinkedIn's State of Sales research, 82% of top performers say they always research prospects before reaching out, compared with just 49% of everyone else. Consistency, not depth, is what separates them. Meanwhile, buyers report that 58% of their meetings with sellers provide no value, according to RAIN Group. Most of that gap is preparation, not product.

The routine below sits inside a broader system for sales call preparation, but it stands alone. The core principle: ruthless prioritization. You are not building a dossier. You are looking for three things you can say in the first five minutes that prove you did your homework.

Just as important is what you deliberately skip:

The full 10-K. Unless you sell to the CFO, skim the one-paragraph business summary and move on.
Press releases older than six months. Stale news makes you sound stale.
The prospect's entire LinkedIn history. You need their current role, tenure, and one recent signal. Not their 2014 job change.
Glassdoor rabbit holes, podcast back catalogs, conference talks. Interesting, rarely actionable in a first call.

The 10-minute routine at a glance

Here is the full sequence in one table. Each block has a source, a hard time cap, and a specific extraction target, because "look at their website" is not a step, it is a way to lose eleven minutes.

Minutes	Source	What you're extracting
0-2	Company site + one news search	What they sell, to whom, and one recent change
2-5	LinkedIn profiles of attendees	Role, tenure, one personal signal per person
5-7	LinkedIn company page + org clues	Team size, who your contact reports to, likely approvers
7-9	Funding, hiring, leadership news	The trigger that explains "why now"
9-10	Your notes	Three talking points, written down

For the rest of this post, we will run the routine on a single example: you have a 2 p.m. discovery call with Dana Okafor, VP of Operations at Meridian Freight, a 400-person logistics company, plus one unknown second attendee on the invite.

Minutes 0-2: the company in two searches

The first two minutes answer one question: what does this company do, and what changed recently? Open the homepage and read the hero section and the customer logos. Then run a single news search for the company name filtered to the last six months. That is it. Two searches, two minutes.

From Meridian Freight's homepage you learn they do refrigerated freight for grocery chains, and the logo bar shows two big regional supermarket brands. The news search surfaces one item: they opened a third distribution hub in Reno four months ago.

That is already an opener: "I saw the Reno hub announcement. Expansion like that usually puts pressure on ops tooling. Is that part of why we're talking?" Notice what you skipped: the leadership page, the careers page essay, the blog. If a fact does not change your first five minutes, it does not earn time in this block.

Minutes 2-5: the people on the invite

Minutes two through five go to the humans, because people buy, companies do not. For each attendee, you want exactly three things: current title and scope, tenure in the role, and one recent signal, a post, a job change, a shared connection. Cap yourself at 90 seconds per person.

Dana Okafor: VP of Operations, 14 months in role, previously a director at a larger 3PL. She posted three weeks ago about "the hidden cost of manual dock scheduling." That post is gold; it tells you the pain in her own words.

The mystery second attendee resolves to Priya Shah, Senior Manager of IT. Her presence on a first call usually means security and integration questions will come early. Note it and move on. Do not read either person's full activity feed. Tenure plus one signal is the extraction target; everything else is curiosity dressed up as diligence. If you want the exhaustive version of what is worth gathering, keep a full pre-call research checklist bookmarked for high-stakes calls, and resist using it for routine ones.

Minutes 5-7: org context and likely decision path

This block answers: who else will touch this decision? You are not building a complete org chart in two minutes. You are forming a hypothesis about the buying committee that you will test on the call itself.

Check the LinkedIn company page for headcount and the rough size of the relevant department. Search for Dana's likely boss: at a 400-person company, a VP of Operations probably reports to a COO or directly to the CEO. Meridian has a COO, Marcus Lin, who joined eight months ago. New executive plus new hub equals someone with a mandate to fix things, which is very good news for you.

So the hypothesis: Dana is the champion, Marcus is the economic buyer, Priya owns technical sign-off. Write it down as a question to validate, not a fact. Getting this map right early is the difference between a deal that moves and one that dies in "let me check with my boss." A proper stakeholder mapping approach takes this much further, but on a 10-minute budget, a three-name hypothesis is the deliverable.

Minutes 7-9: triggers, timing, and why now

Minutes seven through nine hunt for the trigger: the event that made this company take a meeting this month instead of last year. Triggers cluster into a few types: funding, leadership changes, expansion, hiring spikes, regulatory pressure, and public incidents. You usually only need to find one.

For Meridian, you already have two from earlier blocks: the Reno hub and the new COO. A 60-second scan of their open roles adds a third: they are hiring four dispatch coordinators, which suggests volume is outrunning their current process. You do not need a fourth.

Triggers matter because they convert your questions from generic to specific. "What are your priorities this year?" is a question anyone could ask. "You're adding a third hub and four dispatchers at the same time. What breaks first if nothing changes?" is a question only a prepared rep can ask. RAIN Group's buyer research finds that 96% of buyers say a seller's focus on the value they can deliver influences their purchase decision; you cannot speak to value until you know why now.

Minutes 9-10: write your three talking points

The final minute converts research into something usable mid-call, because findings you cannot retrieve under pressure might as well not exist. Write exactly three lines, each one a fact plus the question it sets up. Keep them visible during the call.

For the Meridian call:

Reno hub, four months old. "Is the new hub what's stressing the current scheduling process?"
Dana's post on manual dock scheduling. "You wrote about hidden costs of manual scheduling. What prompted that?"
New COO, eight months in. "Is Marcus driving an ops overhaul, and how does this fit his priorities?"

Three is the limit. Five talking points means you will be reading notes instead of listening. One means a single thread that can dead-end. Three gives you an opener, a pain probe, and a decision-path probe, which is the skeleton of a good discovery call.

What should you do with 60 seconds, not 10 minutes?

When a call gets dropped on your calendar with no warning, run the 60-second version: one look at the company homepage hero, one look at the primary attendee's LinkedIn headline and tenure, and one honest opening line. That is genuinely enough to avoid the worst outcome, which is opening with "so, tell me about Meridian."

The 60-second hierarchy, in order, dropping from the bottom as time runs out:

What the company sells, in one sentence
Your contact's title and tenure
One recent company event

And the honest opener works better than reps expect: "This came together quickly, so I did a fast pass on Meridian rather than my usual prep. Can I ask you to fill in the gaps?" Buyers forgive limited research. They do not forgive pretended research.

When the routine becomes automatic

After a few weeks, the 10-minute routine stops feeling like a checklist and starts feeling like instinct. The next bottleneck is volume: running it well at 9 a.m. is easy, running it well before your sixth call of the day is not. That is the problem we are building Almanac to solve. It assembles the same brief this routine produces by hand: who is on the call and their roles and tenure, recent company news, a map of the likely buying committee, how the prospect found you, with your own talk tracks preloaded, so the ten minutes you do spend goes to thinking rather than tab-switching. The routine teaches you what a good brief looks like; the tooling keeps the standard from slipping on busy days.

FAQ

How long should pre-call research take?

Ten minutes for a standard discovery or first call, with a hard stop. Reserve 30 to 45 minutes for late-stage calls with executives or multi-stakeholder demos where the stakes justify it. The biggest gains come from doing consistent light research on every call, not deep research on a few.

What is the single most important thing to research before a sales call?

The trigger: the recent event that explains why this company is taking meetings now. Funding, a new executive, an expansion, or a hiring spike will shape your questions more than any product or company fact. If you can only find one thing, find that.

Should I research every attendee on the call invite?

Yes, briefly. Ninety seconds per person gets you title, tenure, and one recent signal, which is enough to address each person credibly. An unexpected attendee's role often predicts the call's direction, like an IT manager signaling early security questions, so never skip the names you do not recognize.

What should I skip when researching a prospect?

Skip annual report deep dives, press releases older than six months, the prospect's full LinkedIn history, and Glassdoor reviews. Apply one test to every source: could this fact change what I say in the first five minutes of the call? If not, close the tab.

Stakeholder Mapping in Sales: Know the Buying Committee Before You Dial In

Wed, 10 Jun 2026 00:00:00 GMT

Stakeholder mapping in sales is the practice of identifying everyone who influences a purchase decision, charting their role, influence, and stance, and updating that picture as the deal moves. You do it because the person on your calendar is almost never the person who signs. Gartner finds that a typical complex B2B purchase now involves six to ten decision makers, each gathering their own independent research before the group converges on a choice. Map the committee before the first call, validate the map during it, and you stop pitching one person while five invisible people decide your fate. This guide covers the five roles to find, how to map them before you dial in, and the questions that surface the rest.

What is stakeholder mapping in sales?

Stakeholder mapping is the process of documenting every person who can influence, approve, or block a deal, then plotting each one by role, level of influence, and current disposition toward you. The output is not a wall chart for its own sake. It is a working document that tells you who to talk to next, what each person cares about, and where the deal is exposed.

A useful map answers four questions for every name on it:

What is their formal role in this decision?
How much actual influence do they have, regardless of title?
Where do they stand today: advocate, neutral, or skeptic?
Have we talked to them, or do we only know them secondhand?

That last question matters most. A stakeholder you have never spoken to is a guess wearing a name tag. The map exists to turn guesses into contacts, and it starts before the first call, as part of your broader sales call preparation work rather than something you reconstruct in a panic at the proposal stage.

Why do single-threaded deals die?

Single-threaded deals die because one contact cannot carry a committee decision alone. If your only relationship changes jobs, loses an internal fight, or simply gets busy, the deal has no other heartbeat. The structural reason is committee size, and it is worth taking seriously.

Gartner finds that a complex B2B purchase typically involves six to ten decision makers, each arriving with four or five pieces of independently gathered research that the group then has to reconcile. A single thread into a group that large is a single point of failure: it has to carry your message to people you never meet and survive the internal debate without you in the room. Deals that close are simply wired into more of that committee than deals that stall, which tells you multithreading works in both directions, more of your people connected to more of theirs.

Timing matters too. Going over your contact's head to an executive on day one tends to backfire; executive involvement lands far better once a champion is established and can frame the conversation, usually a few touchpoints in. Multithreading is not "go over your contact's head on day one." It is building a deliberate sequence of relationships, and you cannot sequence what you have not mapped.

The five roles on every buying committee

Every buying committee, whatever its size, contains five functional roles: the champion, the economic buyer, the technical evaluator, the end user, and the blocker. One person can hold two roles, and large committees may have several people per role, but if you cannot name a person for each, the gap is a risk.

Role	How to spot them	What they care about
Champion	Brings energy, asks "how do we get this done," shares internal context unprompted, recruits colleagues to calls	Looking good internally, solving their team's pain, having ammunition to sell on your behalf
Economic buyer	Owns the budget line, talks in outcomes and tradeoffs, often joins late and asks about cost vs. alternatives	ROI, risk, opportunity cost, how this purchase reflects on their judgment
Technical evaluator	Asks about security, architecture, integrations, and admin overhead; sends questionnaires	Whether it works, whether it breaks anything, whether they will be stuck maintaining it
End user	Asks workflow-level questions ("where does this live day to day?"), focuses on usability	Whether the tool makes their job easier or just adds another login
Blocker	Goes quiet in meetings, raises late objections, champions the status quo or a rival option	Protecting an existing investment, workload, budget, or a competing internal agenda

Two cautions. First, the champion is not automatically your main contact; a champion is proven by action, like getting you a meeting with the economic buyer, not by enthusiasm on calls. Second, the blocker is rarely hostile. Most blockers are people with a rational stake in the status quo who nobody bothered to involve early. Mapping them is the first step to converting them.

How do you map stakeholders before the first call?

You map stakeholders before the first call by combining three sources: the attendee list, the org chart, and the deal's origin story. Twenty minutes of structured work gets you a draft map that the call itself will correct.

Work through it in this order:

Start with who booked and who is attending. Look up each attendee's title, tenure, and reporting line. A director of revenue operations who has been there nine years reads very differently from one who started last quarter. This sits naturally inside the research you already do; our checklist of what to research before a call covers the person-level and company-level passes in detail.
Sketch the org around them. From LinkedIn and the company site, identify the attendee's manager, the likely budget owner one or two levels up, and adjacent teams your product touches. You are drafting hypotheses: "economic buyer is probably the VP of Sales, technical evaluator probably sits in IT."
Read the origin story. How did this deal start? An inbound demo request from a manager suggests a champion-led motion with the economic buyer still unaware. An RFP suggests a committee that already exists and has opinions. A referral from an exec means you may have economic-buyer access early, which you should use carefully rather than immediately, for the sequencing reason above.
Mark the gaps. For each of the five roles, write a name or write "unknown." The unknowns become your discovery objectives for the call.

If you run a timeboxed prep ritual, this slots straight into it; the mapping pass is one block in a 10-minute pre-call research routine rather than a separate project. The point is not a perfect map. It is walking in with informed hypotheses so your questions sound like diligence, not a census.

Which questions reveal the decision process without interrogating?

The questions that reveal the decision process are the ones framed around the buyer's success rather than your forecast. "Who is the decision maker?" makes people defensive and often gets a polite lie. Process-framed questions get the same information without the sting.

Use these on early calls:

"When your team bought something like this last time, what did the path to a signature look like?" (Reveals the real process, including procurement and legal.)
"If we get to a yes, whose budget does this typically come out of?" (Locates the economic buyer without asking "are you the decision maker?")
"Who would actually live in this tool every day?" (Surfaces end users you have not met.)
"Who else would want a say before this moves forward? I would rather hear their concerns now than at the end." (Invites the blocker into the open and signals confidence.)
"Is there anyone who looked at solving this before and decided not to?" (Finds the history, and often the skeptic, behind the project.)
"What would your security or IT team need from us to feel good about this?" (Activates the technical evaluator early, on your timeline.)

Listen for pronouns in the answers. "I'll get this approved" and "we'd need to discuss it" describe two different committees. And when a contact says "I'm the decision maker," believe their sincerity but verify the claim gently; in a ten-person buying group, very few individuals can sign alone.

How do you keep the map alive as the deal moves?

You keep a stakeholder map alive by treating it as a deliverable of every call, not an artifact of the first one. Committees change: a sponsor leaves, finance adds a reviewer, a parallel project competes for the same budget. A map that is three calls old is fiction.

Make three habits routine:

Update after every touchpoint. New name mentioned on a call? Add it within the hour, with role hypothesis and source. CC'd on an email from someone new? Same.
Re-score stance, not just presence. A technical evaluator who was neutral and is now responding within minutes has moved. A champion who stops replying has too. Direction of travel predicts the deal better than any single snapshot.
Audit threading before every stage change. Before you move a deal to proposal, count single points of failure. If the economic buyer has never been in a room with you, fix that before sending pricing, not after.

A practical bar: by mid-funnel on any deal over $50K, you should have spoken with at least three people, and every one of the five roles should have a confirmed name. If you cannot meet that bar, the map is telling you the deal is thinner than the pipeline says.

Mapping the committee with an AI pre-call brief

Most of the mechanical work above, looking up attendees, charting reporting lines, tracking who has appeared on which call, is exactly what software should do for you. Almanac builds a pre-call brief that includes who is joining the call, their roles and tenure, an org and buying-committee map, recent company news, and how the prospect found you, so you walk in with the draft map already drawn. During the call, its silent sidebar can suggest follow-up questions when a new name surfaces, and the instant debrief afterward captures every stakeholder mentioned into CRM-ready notes. You still do the human part, reading stances and building champions, but the census takes care of itself.

Frequently asked questions

What is the difference between a stakeholder map and an org chart?

An org chart shows formal reporting lines; a stakeholder map shows influence on one specific decision. They overlap but rarely match. A senior architect with no direct reports may hold veto power over your deal, while a VP on the chart may have delegated the whole decision. Start from the org chart, then overlay role, influence, and stance for this purchase specifically.

How many stakeholders should I expect in a B2B deal?

Plan for more than you can see. Gartner finds a typical complex B2B purchase involves six to ten decision makers, and large strategic deals can run well beyond that. You will not meet all of them, but your champion will, so equip that person to sell to the people you never see.

What is multithreading in sales?

Multithreading is building relationships with multiple stakeholders in the same account instead of relying on a single contact. It protects deals against champion turnover and stalled internal handoffs, and it directly addresses the reality that a typical complex B2B purchase is decided by six to ten people, not one. Stakeholder mapping is the prerequisite: you cannot multithread a committee you have not identified.

How do I handle a blocker once I find one?

Engage them early and treat their objection as legitimate, because it usually is. Ask what a good outcome looks like from their seat, and look for ways your proposal reduces their workload or protects their existing investment. A blocker converted into a neutral is a major win; a blocker ignored until the final stage is the most common cause of late-deal collapse.