How to run a first call with a client: a fifteen-minute plan

How to run a first call with a client: a fifteen-minute plan

A conversation with no plan drifts into detail and ends with "we will think about it", after which nobody comes back. Below is a fifteen-minute script: five stages with timings, what to ask at each and how to close so that what comes out is a scheduled next step.

A conversation with no plan drifts into detail and ends with "we will think about it", after which nobody comes back. Below is a fifteen-minute script: five stages with timings, what to ask at each and how to close so that what comes out is a scheduled next step.

The call is booked, and that is worse than a refusal

The exchange went fine. The client agreed to a call. And that is when it hits: what am I going to say to him for fifteen minutes?

The fear is understandable. In writing there is time to think, rewrite, ask advice. On a call you either lead the conversation or it is led for you — and the second ends with "thank you, we will think about it".

A beginner's typical first call looks like this: nervous, says hello and starts talking about himself and what he can do. Seven minutes later the client knows which tools you use and does not know whether you understood his task. Then the price question, a vague answer, and that is that.

In my survey the barrier is phrased as "I am afraid I will take a job and not manage it". But behind that sentence very often sits something else: not "I will not manage the work" but "I do not know what to say to him".

That is not cured by courage. It is cured by a plan sitting in front of you.

How I came to this

Over a thousand hours on stage and a best speaker award — and I still prepare for a client call in advance and keep the plan open in the next window. Not because I cannot remember it but because in conversation your attention goes to the person rather than the structure.

Below is a real plan for a real call. The client is Zakhar Fomin, a dental clinic, type: a Controller with elements of drive. I did not write the plan myself: I asked the sales assistant to draw up a fifteen-minute script for that type, and it laid out the stages with specific phrases.

I then placed that tab neatly beside the call window so I could always see where I was.

Why a plan matters more than confidence

The root cause of failure on a first call: the conversation has no structure, and the client starts supplying one. And a client supplies one structure by default — "tell me about yourself, and how much does it cost". You lose in that one, because you have neither information about the task nor grounds for a price.

The misconception: "I need to make an impression". You do not. An impression is made not by talking about yourself but by precise questions: somebody who asks to the point reads as somebody who has done this before.

And a psychological mechanism worth understanding. When in the first minute you say how long the conversation will take and what parts it consists of, a Controller sees that the process is structured and safe. And he hands you the lead in the dialogue himself — because he sees you managing it. With other types it works less strongly, but it hinders nobody.

The script by stage

Stage 1. Entry and setting the ground rules

Purpose: take the initiative, show respect for his time, establish yourself as an expert partner rather than an applicant.

The phrasing:

"Zakhar, hello. As agreed, we will keep to 15–20 minutes and stick to the essentials. The plan is this: I will ask three or four questions about the current situation at the clinic, to understand where we can get the most efficiency. Then I will show you a live example on screen. And at the end we will discuss the format of the work and a price range."

Note the last four words. You announce the price conversation yourself — and thereby remove the tension on both sides. The client does not have to find a moment to ask, and you do not have to brace for the blow.

Stage 2. Rapid diagnosis, 3–4 minutes

Purpose: uncover where he is losing money. A Controller buys once he has understood the scale of the problem himself.

Open problem questions only, no "does this interest you?":

Native selling is already happening here: the question about people going to competitors makes the person count his losses.

Your job at this stage is to listen and record pain markers. Keep a separate document open and write down everything he runs into. That is the raw material for the quote, for the presentation and for the whole conversation onwards.

Stage 3. Demonstrating the solution through a metaphor

Purpose: show the value without technical tedium.

You start screen sharing and say: "Look, so as not to burden you with code, let me explain it simply."

Then a running metaphor — mine is a restaurant:

"A patient writes at night: how much is an implant. The live administrator is asleep. The agent goes instantly to the store cupboard, takes the price list — and does not simply spit out a figure. It qualifies the patient, asks about contraindications, addresses the fear and books a slot in the CRM on a free chair itself."

The metaphor works because the person completes the picture himself. He has seen a restaurant; he has not seen the architecture of an AI agent.

The rule: one metaphor for the whole conversation. Started with a restaurant, keep the restaurant to the end rather than swapping it for a factory and pipes.

Stage 4. The economic argument

A short block, but without it none of the preceding converts.

A live employee is a salary, taxes, sick leave, holidays, the human factor and burnout. An agent works around the clock, 365 days a year, does not get the script wrong and steadily carries a person along the funnel.

The full phrasing: "we take your content, your site and your traffic and turn them into an autonomous conveyor of first enquiries".

Stage 5. Closing

Purpose: come out with a next step rather than with "we will think about it".

"Zakhar, for your tasks a turnkey build of a system like this will take such-and-such. To produce a precise quote and architecture, a detailed technical audit of your current funnel is needed. I am ready to take that on. The audit with an architecture map costs such-and-such. Let us draw up an agreement for the audit and start."

Two branches follow, and both work.

A paid audit. An agreement for the audit, a modest sum, and you are already working and already paid.

A free audit. Also fine — especially if it takes half an hour with AI. But then fix the feedback point without fail: "within half an hour I will send you the full picture, look at it today or in the morning and give me an answer". A free audit with no agreed response date turns into a gift somebody forgot about.

Three rules on top of the script

Keep the proportion: the client talks more than you. The guide is 60–70% him, 30–40% you. A beginner does the opposite: gets nervous and pours out everything he can do in five minutes. After that the client knows about your tools and does not know whether you understood the task. A simple technique for holding the proportion: for every statement of yours, ask one question.

Do not argue with an objection immediately. If the client says "I am afraid it will not work", the first move is not to persuade but to clarify: what exactly he fears and whether there was already a bad experience. Half of objections dissolve after a clarifying question, because the person says them aloud and hears them himself.

Finish earlier than promised. You said "15–20 minutes" — keep to fifteen. That is the only way to prove you meet deadlines before the work has even started. For a Controller that weighs more than any words about deadlines.

How to rehearse before a live client

The most valuable thing here is not the script but the chance to run it in advance.

Ask the assistant to take the client's role — with his type, his objections, his manner — and hold the call in writing. It will haggle, go quiet and ask awkward questions. A mistake in a simulation costs nothing.

The AI sales assistant that writes the plan and plays the client is one of 200+ AI assistants across 14 categories: sales, marketing, legal, HR, analytics, creative, engineers. Alongside is the ten-lesson “Sales” course covering what does not fit into a script: rejections, objections, burnout, shaping an offer to demand.

Registration is free and opens three days of full Basic access — the sales module, all the assistants, the prompt texts and six foundational express courses.

Before your next call do two things. Draw up a plan against the five stages above and open it in the next window. And run the conversation once in simulation — not to practise your delivery but to hear the questions you are not ready for.

Fifteen minutes to a plan give more than an hour without one.

If you know somebody who avoids calls and prefers writing, forward this to them. It is not shyness.

The SPIN structure: four steps of the conversation

The fifteen-minute script above is the general frame. Inside it works a specific structure for uncovering the need, and it has been tested on real calls.

Situation. What is bothering you, how long, where.

Problem. What gets in the way most.

Implication. No scaremongering — only what the person already feels.

Need-payoff. A positive frame rather than a loss frame.

The mechanic that matters more than the questions themselves: one question — pause — listen.

The proportion of the conversation: the client speaks 60–70%, you 30–40%. If it is the other way round, you are not finding out but presenting, and the decision will be made without you.

Two branches of one script

The block structure is common; the timing and focus differ.

Branch A — a short contact. 7–12 minutes, formal address, SPIN in a lightened form. The goal is to agree a next step rather than to sell.

Branch B — getting acquainted. 30 minutes, full SPIN. The goal is to remove the main barrier rather than to diagnose the task.

Common to both: a question bank, an objection bank, the close and a separate "what to do after the call" block.

Red lines

What must not be broken in either branch: no false deadlines and fake scarcity · no pressure and no promises of gold · no guarantees of results.

That is not only about ethics — it is what separates a conversation people come back after from a conversation people block you after.

What to run it on and how to protect yourself

And one thing to do before the call rather than after. Agree to a recording. You will be reviewing it afterwards, and a recording made without warning must not be reviewed.

A ready script and a simulator for it

The express course Freelance 2.0, prompt №46 "A selling call script" — the structure of the conversation for your product. And immediately №47 "A selling call simulator": the model plays the client, asks awkward questions and does not yield. Basic plan.

Fifteen minutes is frightening the first time. The second time it is not — and the second time can be done for free.

Who else helps, Basic plan, the catalogue: AI Sergey Molokov — a trainer built on sales lecture transcripts. Inside Sales Representative — preparation for a specific call.

What determines the course of the conversation more than the script. The “Sales” course, the lesson “4 types of people. How to sell to anyone”, Basic plan — the type of the person opposite. A Controller needs figures and clear meeting rules, a Driver scale and speed, an Analyst data and time to think after the call. Fifteen minutes is only enough if you speak his language from the first minute.

What to take on the platform for this task

The series: one deal step by step

Eight pieces about one real deal — from a listing in a chat to payment received. The client, Zakhar Fomin, owner of a dental clinic, agreed to be named along with the figures.

What to read next

"How much does it cost" — what to say — how you get to a call in the first place.

Reviewing a recorded conversation — what to do with the recording afterwards.

Four client types — how the type changes the script.

A commercial proposal in ten minutes — what follows the call.

n8n and Make automation templates — the full guide to automations.

Also on AI SKILLS