The talk-ratio myth: why most engineers talk too much on client calls

The number that surprises people

On a healthy discovery call, the client should be talking about sixty percent of the time. You get forty.

Most technical people react to that number the same way: that can't be right. You are the one with the answers. You are the one who prepared. If you only talk for forty percent of the call, what exactly are you being paid for?

Here is the uncomfortable version. The client did not book the call to hear what you know. They booked it to find out whether you understand what they need. Those are different meetings, and only one of them ends in a next step.

Why engineers over-talk

It is rarely ego. It is almost always one of three reflexes.

Competence signalling. You were promoted into client-facing work because you are good at the technical part. So under pressure you do more of the thing that got you here — you explain. Depth feels like value. On a call, past a point, it reads as not listening.

Silence feels like failure. Three seconds of quiet on a video call feels like thirty. So you fill it. The client was assembling a thought, and you took the pen out of their hand.

The demo reflex. A question about one feature becomes a tour of the architecture. You answered a question they did not ask, and buried the one they did.

What the client actually hears

When you take seventy percent of the airtime, the client does not think "thorough." They think one of these:

• They are pitching a solution before they understand my problem.
• I have not been able to say the thing I actually called about.
• This will be what every meeting with this vendor is like.

None of those objections get said out loud. They get said after the call, to someone else, when your proposal comes up.

Four fixes that work immediately

1. Ask, then stop

Ask your question and close your mouth. Fully. Count to three in your head if you need a mechanism. The first answer is the polite one; the useful answer lives in the silence right after it, and you only get it if you leave the space open.

2. Answer in one breath, then check

Give the short answer, then hand control back: "That's the short version — do you want the detail, or is that enough to move on?" You have now made depth their choice instead of your assumption. Half the time they say it's enough, and you just bought back four minutes.

3. Replace the filler with a pause

The goal was never zero "um." The goal is that the gap between your thoughts is silence instead of noise. A pause before a number or a commitment reads as consideration. "Um" before the same sentence reads as guessing.

4. Let them finish the sentence you already know

You can predict how the sentence ends. Let them say it anyway. Finishing a client's sentence saves four seconds and costs you the thing they were going to add at the end — which is usually the constraint that actually decides the deal.

How to actually change this

Reading about talk ratio does not move it. You cannot feel your own airtime in real time — that is precisely the problem. You need to see the number while the conversation is still happening, and you need to run the same conversation more than once.

That is the loop PitchDawn is built around. Talk ratio is measured live during the call, so the balance shifts while you can still do something about it, and it shows up again in the debrief under Pace & Delivery — one of the five pillars every session is scored on. Run a discovery call against a skeptical CTO, watch where your forty percent went, and run it again tomorrow.

The number moves faster than you would expect. What takes longer is trusting the silence.