Something in you resists an unclear answer the same way it resists a bug report that just says "it sometimes breaks." Your instinct is to make it precise: add logging, narrow the condition, name the exact case before you move on. That instinct is why you were able to build the product you're now trying to sell. On a sales call it works against you, because a buyer describing their problem out loud is not filing a ticket, and answering them like one is the mistake, not a small one.

The buyer is thinking out loud, not reporting a defect

Someone says, "we sort of have a workaround for that already." An engineer hears an incomplete spec and reaches to complete it: asks three clarifying questions in a row, or worse, jumps straight to explaining why your version of the workaround is better. Both moves shut the sentence down before the buyer finished thinking it. What they actually said, underneath the vague wording, is closer to: I have a problem, I have patched around it badly, and I haven't fully admitted that to myself yet. That takes a few more sentences to arrive at, and it only arrives if you don't interrupt the process with a fix.

The fix is not a new personality. It's one habit: when an answer is vague, ask the buyer to say more about it, rather than resolving the vagueness yourself. "Tell me about the workaround" gets you the real story. "Ah, so you're doing X" gets you a nod and a closed topic, because you've just done their thinking for them and it's easier to agree than correct you.

Silence is not a null pointer

You have been trained for years that a gap in output means something failed. On a call, a gap in speech usually means someone is deciding whether to tell you something. Jump in at second two and you get the safe version of their answer. Wait until second five and you often get the real one, because most people fill a silence with truth before they fill it with a pitch.

Time it once, honestly. A 30-minute call is 1,800 seconds. If you talk for 20 of those 30 minutes, you have used 67 percent of the room, and you can check that on any call by literally watching the clock. The habit worth building is not "talk less" as a vibe, it's noticing, in the moment, that you are about to fill a silence that isn't yours to fill, and letting it sit for a count of five instead.

You already know how to run this meeting — you've just never called it that

Compare a sales call to an incident review, a format you've run or sat through many times without dread. An incident review has a stated purpose at the top, a walk through what happened, a decision about what changes, an owner for that decision, and a date to check it. Nobody in that room is charming anyone. It works because the structure carries the meeting instead of the personality in the room.

Run the sales call the same way and most of the anxiety about "not being a salesperson" goes away, because you're not performing a role, you're running a format you already trust:

  • State the purpose in one sentence before you say anything else: "I want to understand what you're dealing with and see if there's a fit — if there isn't, I'd rather find that out today than waste your March."
  • Ask before you explain anything about your product. Every question you ask before pitching is a question you don't have to guess the answer to later.
  • When you do explain something, explain the one part that answers what they just told you, not the part you're proudest of building.
  • End with a specific next step and a specific date, not "sounds good, I'll follow up."

None of that requires charisma. It requires running the meeting like a review instead of running it like a pitch, which is a format switch, not a personality transplant.

The correct answer is often the wrong thing to say

A buyer asks, "does it handle multi-location?" The honest, complete, technically precise answer is a paragraph about current architecture, an edge case, and a roadmap item with a caveat about timing. You will give that paragraph, because it's true and you built the thing and precision is your default setting. The buyer wanted a yes or a no, plus what happens if it's a soft yes. That's a specific, learnable failure: correct is not the same as useful. Before you answer a direct question on a call, decide first whether it's a yes, a no, or a "yes, with a real caveat," say that in one sentence, and only then add the technical detail if they ask for it. The caveat is allowed. The paragraph that arrives before the caveat is what loses the room.

What actually changes on the next call

Nobody needs a new personality to run a better call. They need four habits stacked on top of the ones that already work in every other room they run: ask before explaining, let five seconds of silence sit before you fill it, lead every direct answer with the one-word version before the caveat, and close on a specific date instead of a vague one. Try it on the next call you have booked, on purpose, and notice how much of it was already familiar from a room you run comfortably every week.

Where the tool helps, and where it flatly does not

Be clear-eyed about the boundary here, because it's easy to want software to solve a room problem. Rocketship will get the call onto your calendar and send the reminder that keeps it from becoming a no-show. Afterward, the call sits in your record as a recording and a transcript instead of a memory you're reconstructing three days later, which turns out to matter more than founders expect — most misremember which objection came up on which call within a week. None of that touches the forty minutes between hello and goodbye. That part is still entirely you, on purpose. A company where the software does the founder's talking is not a company anyone should want to be a customer of.

What the record does buy you is a way to check your own instincts against what actually happened, rather than against what you remember happening, which on a bad week are not the same call.