The four-phase brief behind every sales call

"Felt like the right time." That's the answer you get when you ask a rep why they rang that particular customer on that particular day. The owner on the other end works it out before you do: a call that starts from a hunch announces itself in the first sentence, and three minutes later it's over.

The four-phase brief exists to take the hunch out of it. Prepare, Discovery, Objections and Close are four distinct moments inside one conversation, each with a job, all anchored to something that is true about that account and carries a date.

Prepare: open with a fact, not a feeling

Suppose the lead generation co-worker sees port 445 reachable from the internet on an SME in your base, and next to that line sits the day it was seen. To an engineer it's a scan result. To your rep, as written, it's useless: unreadable over the phone, and no help at all with whatever the customer asks next.

The brief translates it. Port 445 is how office computers share folders and printers between themselves; if it answers from the public internet, the company's shared drive is reachable from outside, and it's one of the first doors ransomware crews try. So the sentence the rep brings to the call sounds roughly like this: "I noticed your shared office drive is answering directly from the internet. I wanted to check whether that's deliberate or whether it was left open after some maintenance."

No acronyms, no scare, a real question. The detection date travels with the sentence, because the date is what turns a phone call into news rather than an opinion. Customers argue with opinions. Give the thing a date and they mostly just ask what to do about it.

That's all Prepare is: what you need to know before you dial. Who the company is, what changed since last time, which signal deserves the call, and how to say it in plain language.

Discovery: questions that qualify, not questions that interrogate

Holding a technical finding makes you want to use it to prove you're right, which is the quickest route to putting the only person who can sign on the defensive. Discovery questions do the opposite job. They get the customer to describe what breaks when that thing breaks, so the risk stops being an IT topic and becomes a line in their own numbers.

• "Who works off that shared drive, and what stops if it isn't there tomorrow morning?" It moves the conversation to the cost of a day of downtime, which the owner can price better than you can.
• "Has any of your customers sent you a security questionnaire lately, or written one into a contract?" Fastest way to find out whether the supply chain is already pushing, and NIS2 almost always reaches an SME through a buyer rather than through a statute book.
• "Who decides on this sort of thing, you or whoever looks after your IT?" Tells the rep whether they're talking to the decision maker and who else has to be in the room at proposal time.
• "If you were down for three days, what would that do to the orders you owe your own customers?"

The brief holds those questions in your brand's tone and the customer's language, because the sales framework governs how things get said and never what's true. Facts stay with the signals.

Objections: the answer comes from that customer's own data

There aren't many objections an SME will throw at you on security, and the same ones come round again and again; anyone who works that base can recite them before dialling. What separates an answer that holds from one that collapses isn't eloquence, it's provenance: a slide about the general state of the market collapses, a scan line from that customer's own domain with a date on it holds. "We're too small" is answered badly with a market statistic and well with a fact nobody else in the room can dispute.

Then there's the more interesting case, the one where the co-worker refuses to answer. When the customer asks "and what would it cost me if it happened", the pull towards a large impressive figure is enormous, and a generic deck reaches for one every time. Not here. Where there's no number that can be backed up, the brief says so: no number here, because we only show amounts we can prove.

It looks like leaving money on the table. It's the thing holding up everything else. A rep who knows every figure in the brief is defensible reads those figures without flinching, and customers can hear a flinch.

Close: a service, not a recommendation

Plenty of good calls die in the gap between "you really should look at this" and "here's what I'm proposing." The rep did the work, the customer agreed there's a problem, and then the quote has to route through somebody who can pick the right service and price it, and two weeks evaporate.

Close exists to remove that gap. Every risk found is already mapped to a service in your catalogue at your price, and the proposal builds from there. The document left behind on the customer's desk carries your brand and not ours, so what they bought, they bought from you, and at renewal they call you.

Why four phases rather than a script

A script gets learned once and recited identically to everyone, and customers spot it inside two minutes. A brief gets rebuilt per account, because what sits underneath is that account's signals rather than a template. When the customer's posture shifts, the conversation to have shifts with it, and the rep sees that by opening the page instead of finding out three months later.

The four phases aren't a new methodology to teach your sales force. They're the order a decent commercial conversation already follows, except the preparation no longer waits for the one person in the company who knows how to do it.

Every call starts from a fact with a date attached. The rest of the brief is there so that fact doesn't go to waste.