Why the first sales call wastes time on basics, and how to fix it

The first sales call wastes time on basics because both sides arrive empty-handed. The buyer has not seen the product, so the rep spends the opening explaining it. The rep knows a name, a company and a few form fields, so the next stretch is questions the buyer could have answered in advance. Neither side did anything wrong. The call is just the first place either gets to learn. The fix is to move those two jobs before the call: let the buyer see the product and collect the standard questions, so the call can start at the buyer's real problem.

We have no data on how many minutes a typical first call loses to basics, and we will not invent a figure. This post argues from how the call works and marks the judgement. The one thing we measured is how companies set the call up, in a crawl of 198 B2B SaaS homepages.

What counts as basics on a first call?

A basic is anything where the question, or the answer, is the same for every buyer. There are two kinds, one on each side of the call.

• Orientation, owed to the buyer. What the product is, who it is for, what it looks like doing the job, roughly how it is bought and how long it takes to set up.
• Qualifying questions, owed to the rep. Role, team size, what they use today, why now, who else is involved. The answers differ by buyer, but the questions are the same every time.

Neither is discovery, which is finding out what this buyer is trying to achieve and what would have to be true for them to change. That is the part of the call that needs a person. A test for any question on a first call: would you ask it of every buyer? If yes, it is a basic and probably does not need live time.

What should a prospect know before the first call?

Five things. If the buyer can say all five, the call can skip the overview.

1. What it is and who it is for, in a sentence they could repeat to a colleague.
2. What it looks like doing their job. The one workflow they came for, seen on screen rather than described.
3. The shape of the commitment. How it is priced or licensed, roughly how long setup takes, and what it has to connect to.
4. Whether it clears their deal-breakers. The security, integration or team-size constraint that would end the evaluation, found early rather than in minute forty.
5. What the call is for. What they will get from the thirty minutes, and what they should bring.

A website can show most of these. The second usually needs the product itself, and is the one most often missing.

What should the rep know about the buyer before dialing?

Also five. These let the first question be about the buyer instead of the company.

1. Who they are. Role, team and company size, and whether they decide or influence.
2. The problem in their words, and why it matters now.
3. What they have seen. Which parts of the product, in what order, and what they skipped.
4. What they asked, and which questions are still open.
5. Constraints and company. Integrations, security needs, timeline and who else is involved.

A form can capture the first, the second and part of the fifth. The third and fourth are different: they exist only if the buyer used the product or talked to something before the call. Order matters too: a buyer who went straight to integrations is signaling a technical gate that a value-proposition opener will miss.

Why does the first call start from zero on both sides?

Part of the answer is how companies set the call up. In our crawl of 198 B2B SaaS homepages on 2 October 2026, 99 (50%) led with a sales-led ask (book, request or get a demo, or talk to us) as the primary button, and only 11 (6%) linked to an interactive demo or tour in the hero or main navigation. Method and data are here. The sample is early-stage, technical and English-language, and counts only what a homepage offers first, so a video or demo deeper in a site is missed. It says nothing about what happens after the click. But where the first door is a call, the call is where orientation happens by default.

The rest is judgement. Buyers research from what you published, and if that is a headline and a button they arrive with a headline. The rep's side is a smaller version of the same problem. Where we could follow the button, the median demo-request form had five fields (we found 49 forms). Five fields tell a rep who and where, not what the buyer has seen. And a form's fields are what the rep receives, not necessarily what the buyer knows: someone can fill in all five and have no idea what the product does. What to use instead of a book-a-demo form covers the trade-off.

How do you move the basics before the call?

Three ways, in rising order of effort. Start with the cheapest.

• A good form and a good pre-call email. Ask the few questions that change how the rep prepares, and use the confirmation email to carry the basics: a short walkthrough of the one workflow, a plain statement of how the product is priced, and what the call will cover. It is cheap and works for buyers who read it. You cannot tell whether they did.
• A self-serve product path. An interactive demo or recorded tour before the booking step. The buyer sees the product, which covers orientation. But a fixed path asks nothing, and unless it reports back, the rep still knows nothing new. What an interactive demo is covers the kinds.
• A conversation before the call. The buyer sees the product and answers the qualifying questions in the same sitting, and the answers and the path go to the rep. It can cover both checklists and takes the most setup.

We make the third kind, so weigh this accordingly. Inkly is an AI demo agent: it chats with each visitor, runs a guided demo of the part of the product that fits, answers questions inline and hands sales a brief of what the visitor asked and explored, which we call buyer intelligence. It does not replace the call or decide who is qualified. Your team defines what the signals mean.

Two sibling posts cover the mechanics: how to qualify a buyer without a form and how to qualify leads in a demo. This post is about what has to be settled before anyone dials.

What does a pre-call path look like in practice?

A concrete run, using Inkly. A visitor opens the agent and is asked their role and what they are trying to get done. It shows the workflow that matches, answers questions along the way, including pricing and integrations, and when they are ready offers a next step such as a call. The call is booked by someone who has already seen the product.

Qualification and buyer intelligence are on Pro and above. Pro starts at $150 a month ($120 billed yearly) for 150 active visitors, and the pricing page has the table.

Here is the kind of handoff note a rep might get at the end. It is an illustration we wrote, not a real session or customer, built from what a session can capture: what the visitor said about themselves, their questions, the workflows they explored and their objections.

• Who: Head of RevOps at a 40-person software company, evaluating for the sales team. Said the VP of Sales signs off.
• Why now: reps spend the first call explaining the product.
• Saw: the CRM handoff workflow first, then permissions. Skipped the analytics screens.
• Asked: how permissions work by role (answered in the demo); whether it connects to their CRM (needs a specific check).
• Open: whether single sign-on is a requirement.
• Suggested first question: "You looked at permissions before anything else. What are you trying to protect?"

The note leaves out a verdict on purpose. Knowing what a buyer clicked is not knowing why, and a rep who opens with conclusions from session data will get corrected. It gives the rep a better first question, not the answer.

What does the first call look like once the basics are done?

It opens on the buyer's problem, not on an introduction to the company. The rep's first question comes from the note, discovery becomes confirmation rather than excavation, and the buyer skips an overview they have already seen. It may not be shorter. In our judgement, thirty minutes with twenty-five on the buyer's problem builds more trust than an hour with forty of overview, because relevance builds trust and length does not.

What if buyers will not look before the call?

Some will not, and that is fine. The aim is to shift the mix, not abolish the uninformed first call. Some buyers prefer to talk first, so keep the booking button visible, and give the rep a short orientation to run on purpose when the buyer arrives having seen nothing.

FAQ

What should a prospect know before a first sales call?

Five things: what the product is and who it is for, what it looks like doing their job, the shape of the commitment, whether it clears their deal-breakers, and what the call is for.

Can a form and a pre-call email do this without an AI agent?

Partly, and for many teams that is enough. A short form plus an email with a walkthrough and a plain statement of how the product is priced moves a lot of basics earlier. It cannot show what the buyer looked at or asked.

Will asking qualifying questions before the call cost me bookings?

It can, and we have no figure for how much. Ask only what changes how the rep prepares, ask after the buyer has seen something useful, keep a visible booking path, and compare your booking rate before and after.

What should you do this week?

Take your last five first calls and mark every stretch that was a basic. Sort each into orientation, a standard qualifying question or real discovery. Move the biggest basic before the call, using whichever of the three methods fits your volume, then compare how your next five calls open. That gives you your own number, which is worth more than anyone's benchmark, including ours.

Sales teams use Inkly to send a live demo instead of scheduling another call.