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

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

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

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

---

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

The messaging went fine. The client agreed to a call. And now it hits: what am I going to say to them for fifteen minutes?

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

A beginner's typical first call looks like this: nervous, they say hello and start talking about themselves and what they can do. Seven minutes later the client knows which tools they use and does not know whether they understood the task. Then the price question, an unclear answer, and that is that.

In my survey the barrier reads as *"I'm afraid I'll take the job and fail"*. But behind that sentence very often sits something else: not "I can't do the work" but "I don't know what to say to them".

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

How I got to this

More than a thousand hours on stage and a "best speaker of 2025" 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, a Controller with a streak of Driver. I did not write the plan myself: I asked the sales assistant to produce a fifteen-minute script for that type, and it laid out the stages with specific phrasings.

Then I carefully placed that tab next to the call window so I could always see where I was.

Why a plan matters more than confidence

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

The misconception: "I have 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 the psychological mechanism worth understanding. When in the first minute you say how long the conversation will take and what parts it has, a Controller sees the process is structured and safe. And hands you the lead in the conversation themselves — because they can see you are managing it. With other types it works less strongly but bothers nobody.

The script by stage

Stage 1. Making contact and setting the ground rules

The goal: take the initiative, show respect for their time, establish yourself as an expert partner rather than an applicant.

The wording:

> "Zakhar, hello. As agreed, we'll keep this to 15–20 minutes and stick to the substance. The plan: I'll ask three or four questions about the current situation at the clinic so I can see where we can squeeze out the most efficiency. Then I'll show you a live example on screen. And at the end we'll discuss the format and a price range."

Note the last five words. You announce the price conversation yourself — and thereby take the tension out of it for both sides. The client does not have to catch a moment to ask, and you do not have to brace for a blow.

Stage 2. Rapid diagnosis, 3–4 minutes

The goal: expose where they are losing money. A Controller buys once they have worked out the scale of the problem themselves.

Only open, problem-focused questions, no "would that be of interest?":

The selling already happens natively here: the question about people going to competitors makes somebody count their losses.

Your job at this stage is to listen and record markers of pain. Keep a separate document open and write down everything they run into. That is the raw material for the quote, for the deck and for the whole rest of the conversation.

Stage 3. Demonstrating the solution through a metaphor

The goal: show value without technical tedium.

You share your screen and say: "Look, so as not to bury you in code, let me explain it in plain terms."

Then a running metaphor; mine is a restaurant:

"A patient writes at night: how much is an implant. The live receptionist is asleep. The agent goes 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 in a free chair itself."

The metaphor works because the person completes the picture themselves. They have seen a restaurant; they have not seen the architecture of an AI agent.

The rule: one metaphor for the whole conversation. Start with a restaurant and 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 above converts.

A live employee means a salary, taxes, sick leave, holidays, the human factor and burnout. An agent works round the clock, 365 days a year, does not fumble the script and steadily walks somebody through the funnel.

The wording in full: "we take your content, your website and your traffic and turn them into an autonomous pipeline of first enquiries".

Stage 5. Closing

The goal: leave with a next step rather than "we'll think about it".

> "Zakhar, for your tasks a build like this end to end would take such and such. To put together an exact quote and the architecture, I need a detailed technical audit of your current funnel. I'm ready to take that on. The audit with an architecture map costs this much. Shall we do the 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 when AI does it in half an hour. But then fix a time for the feedback without fail: "I'll send you the full picture within half an hour, look at it today or in the morning, and give me an answer." A free audit with no agreed reply date turns into a gift somebody forgot about.

Three rules on top of the script

Hold the proportion: the client talks more than you. The guide is 60–70% them, 30–40% you. A beginner does the reverse: gets nervous and dumps everything they can do in five minutes. After that the client knows about their tools and does not know whether the task was understood. A simple device for holding the proportion: one question for every statement you make.

Do not argue with an objection straight away. If the client says "I'm afraid it won't work", the first move is not to persuade but to clarify: what exactly are they afraid of, and have they had a bad experience already. Half of all objections dissolve after a clarifying question, because the person says them out loud and hears themselves.

Finish earlier than you promised. You said "15–20 minutes" — come in at fifteen. That is the only way to prove you keep to deadlines before the work has begun. For a Controller it 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 their type, their objections, their manner — and run the call in messages. They will haggle, go quiet and ask awkward questions. Getting it wrong in a simulation costs nothing.

The sales assistant that writes the plan and plays the client is one of more than 140 AI assistants across 14 categories: sales, marketing, legal, HR, analytics, creative, engineering. Alongside is the ten-lesson sales module covering what does not fit into a script: rejections, objections, burnout, shaping an offer around 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. Put together a plan across the five stages above and open it in the next window. And run the conversation once in simulation — not to rehearse your delivery but to hear the questions you are not ready for.

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

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

---

The SPIN structure: four steps of the conversation

The fifteen-minute script above is the outer frame. Inside it works a specific structure for drawing things out, and it is proven on real calls.

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

Problem. What gets in the way most.

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

Payoff. A positive frame rather than a frame of loss.

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

The proportion: the client talks 60–70%, you 30–40%. If it is the other way round you are pitching rather than finding out, and the decision will be made without you.

Two branches of one script

The blocks are the same; the timing and the focus differ.

Branch A — a short contact. 7–12 minutes, formal address, SPIN in a lighter 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 diagnose the task.

Common to both: a bank of questions, a bank of objections, the close, and a separate block on what to do after the call.

Red lines

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

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

---

The series: one deal step by step

Eight pieces about one real deal — from a listing in a chat to the payment received. The client, Zakhar Fomin, owner of a dental clinic, gave permission to use his name and the figures.

---

What to read next

[Reviewing a call with AI](/en/blog/call-analysis-with-ai) — what to do with the recording afterwards.

[Four client types](/en/blog/four-client-types) — what to change in the script per person.

["How much does it cost" — what to say](/en/blog/what-to-answer-about-price) — if the price comes up mid-conversation.

[A commercial proposal in ten minutes](/en/blog/proposal-in-ten-minutes) — what gets assembled from the results.

[n8n and Make automation templates](/en/blog/n8n-automation-templates-guide) — the full guide to automations.