Six Minutes of Prep Per Account: What to Look Up Before You Dial (and What to Skip)

Two things kill a calling block before the first dial. The first is dialing blind — pulling a list, hitting the top of it, and opening with a sentence that would work equally well on any of the two hundred names below. The second is the opposite: opening the annual report, reading the risk factors section, clicking into three podcast appearances, and looking up ninety minutes later having made no calls at all. Both feel like work. Only one of them is avoidable by being lazier.

I have watched reps do both, and the second is more dangerous because it looks virtuous. Nobody gets coached out of over-researching. Your manager sees a rep with eleven tabs open and assumes diligence. What is actually happening is that research has become a socially acceptable way to not pick up the phone.

So here is the fix I use and teach: six minutes per account, timed, with a hard stop. Two minutes on the company. Two minutes on the person. Two minutes writing one sentence of relevance you can say out loud without reading it. When the timer goes, you dial with whatever you have. That constraint is the whole point. Cold call research before dialing is not a knowledge-gathering exercise — it is a sentence-production exercise, and everything that does not produce the sentence is waste.

Why six minutes and not sixteen

The honest reason is arithmetic. If you are running a real calling block, you are working through a list, and every minute of prep per account comes directly out of dial volume. Twenty minutes of research per account means you are making a handful of calls a day and each one carries the weight of your entire pipeline. That is a terrible way to live. You get precious about calls. You avoid the ones you researched hardest because you cannot bear to burn them.

Six minutes is short enough that you stay loose. You can prep a block of accounts in under an hour, dial all of them, and treat each one as cheap. Cheap calls are better calls. You experiment more. You hang up faster on the dead ones. You are willing to burn a name to test a line.

The other reason is that the marginal value of research falls off a cliff almost immediately. The first thing you find about a company is usually the thing that matters. The eighth thing you find is trivia. Trivia does not make you credible on a cold call — it makes you sound like a stalker with a browser. Nobody has ever booked a meeting because the rep knew where the CFO went to university.

What actually earns you the next thirty seconds is a single line that proves you know what this specific company is dealing with right now, and that you called them on purpose. That line takes six minutes to build. It does not take sixty.

Minutes one and two: the company

Set a timer. Two minutes. You are looking for exactly one thing: a change. Not a description of the business — a change in it.

Static facts are useless on a cold call. "You're a mid-market logistics provider with four distribution centres" tells the person nothing they do not know and gives them no reason to talk. Changes are different. Changes create problems, and problems create budget and urgency. Your job in these two minutes is to find the most recent change you can name out loud.

The four places a change shows up

Hiring. This is the highest-signal, lowest-effort source and most reps skip it entirely. Open the careers page or the jobs tab on their LinkedIn company page. You are not reading the job descriptions. You are looking at the shape of the hiring. Are they hiring for a function they clearly did not have before? Are five of the twelve open roles in one department? Are they hiring in a city they were not in last year? Hiring is a company telling you, in public and in detail, where it has decided to spend money and where it is currently short-handed. If a manufacturer has four open maintenance technician roles at one plant, that plant has a staffing problem right now, and the plant manager knows it better than anyone.

Expansion or contraction. New site, new facility, new region, new product line. Or the reverse — a closure, a consolidation, an exit from a market. Both create work for whoever owns the affected function.

Incidents. A breach, a recall, an outage, a lawsuit, a regulatory notice, a safety event. These are uncomfortable to reference and enormously powerful when referenced correctly. Not "I saw you got breached" — that is a taunt. More on how to say it below.

Filings and public disclosures. If they are public, the press release page and the most recent earnings call summary tell you what leadership is publicly committed to this year. You are not reading the 10-K. You are reading the headline of the last four press releases, which takes about forty seconds.

That is the whole company block. Careers page, news search on the company name sorted by date, press release page. If nothing jumps out in two minutes, nothing was going to. Write "no trigger" in your notes and move on — a no-trigger account is not a bad account, it just means your opener leans on the industry instead of the company, and that is a perfectly good opener.

Minutes three and four: the person

Reset the timer. Two minutes on the human being who is going to pick up.

You are answering three questions, and none of them is "what are they interested in."

What does the title actually cover here?

Titles do not mean the same thing at every company, and this is where most reps guess wrong. A VP of Operations at a two-hundred-person manufacturer runs the floor. A VP of Operations at a five-thousand-person one runs a spreadsheet about the people who run the floor. A Director of Security might own the SOC or might own compliance paperwork and have no operational authority at all.

The fastest way to work this out is to look at who else has a similar title at the same company. If there are six directors of security, yours owns a slice, and you need to know which slice before you open with something outside it. If there is one, they own everything, which means they are busy and your call has to be shorter.

Also check the reporting line if you can infer it. Someone who reports to the CIO has a different set of pressures than someone who reports to the COO, even with the same title on the door.

How long have they been there?

Tenure changes the entire call. Somebody who has been in the seat a few months is still building their plan, still allowed to say the previous approach was not working, and still meeting vendors to figure out the landscape. Somebody who has been in the seat for nine years built the current stack and will hear your pitch as a criticism of their own decisions.

This is not a reason to skip the long-tenured person. It is a reason to change the frame. With the new person you can ask what they inherited. With the long-tenured person you ask what they have not been able to get funded, which is a much better question anyway and usually gets a real answer.

What would get them fired?

This is the one that matters and the one nobody writes down. Every operational leader has one or two outcomes they are personally accountable for, and everything else is noise to them. A plant manager gets fired for downtime and safety incidents. A SOC leader gets fired for a breach that goes undetected or an audit that goes badly. A VP of Sales gets fired for missing the number two quarters running. A practice leader in professional services gets fired for utilisation falling off a cliff or a marquee client leaving.

Write the answer down as a phrase, not a paragraph. "Unplanned downtime." "Missed detection." "Two quarters of miss." That phrase is the gravitational centre of the call. Everything you say should visibly orbit it, and anything that does not is a reason for them to hang up.

You will not always be right. That is fine — being roughly right about someone's accountability is dramatically better than being precisely right about their company's Series B.

Minutes five and six: write the sentence

Last two minutes. You are producing one written sentence. Not a script, not bullets — one sentence you will say out loud in the first fifteen seconds of the call.

The shape I use is: change plus consequence plus check.

The change is what you found in minutes one and two. The consequence is what that change usually creates for someone with this person's accountability. The check is a short question that invites them to correct you.

Say you found three open maintenance technician roles at one site. The sentence is something like: "I saw you're trying to fill a few maintenance roles at the Toledo plant — usually when that happens the existing crew is running hot and PM schedules start slipping. Is that where you are, or have you got it covered?"

Or on the security side, if the change is a new compliance obligation: "You've picked up a new audit requirement this year, and the teams I talk to end up pulling analysts off detection work to produce evidence. Is your team feeling that yet?"

Three things are happening in that sentence. You are proving the call is not random. You are demonstrating you understand the mechanics of their job, not just their industry. And you are handing them the easiest possible response — a correction. People love correcting you. A correction is a conversation.

Say it out loud before you dial

This is the step people skip and it is the reason the other four minutes were worth spending. Read the sentence out loud once. If it is longer than a breath, cut it. If it contains a phrase you would never say to a friend — "leveraging," "solutions," "in the space" — cut it. If you stumble on it, the wording is wrong, not your delivery.

A sentence that reads well and speaks badly is worse than no research at all, because you will end up reading it, and everybody can hear reading.

The anti-list: what to skip

Equally important is what you refuse to look at, because these are the four things reps burn twenty minutes on and never use.

Funding rounds. "Congratulations on the raise" is the single most transparent opener in cold calling. Everyone who called them last week said it. It also tells you nothing operational — a raise means money exists somewhere in the building, not that this person has any of it or any authority to spend it. Skip funding unless the round is tied to a specific stated use that maps to your buyer's accountability, and even then, reference the use, never the round.

Their LinkedIn posts. Almost every post from a mid-level operational leader is either a repost of a company announcement, a congratulations to a colleague, or something they were asked to share by marketing. Referencing it makes you sound like you have been reading their diary, and it signals that you found nothing better. The exception is a post where they describe a problem in their own words — that is gold, and it is rare. If you find one in your two minutes, use it. If you do not, do not go looking.

Their product pages. This is the trap for reps who confuse research about the account with research about the account's marketing. Reading their solutions page teaches you their positioning, which is the language they use with their customers and almost never the language they use internally. Repeat it back and you sound like a brochure reading itself aloud. The plant manager does not describe his plant the way the website does.

Anything longer than a page. The 10-K, the analyst report, the founder's hour-long podcast. There may be something extraordinary in there. You will not find it in six minutes, and you should not spend sixty looking. If an account is genuinely strategic and worth an hour, that is a separate activity done at a separate time, not something you do mid-block with a dial queue open.

Where the six minutes actually gets used

The output plugs straight into whatever opener you run, and this is the part that makes the routine worth doing rather than just feeling thorough.

If you are dialing operations leaders, the change-plus-consequence sentence slots directly into the front of the manufacturing cold call script, where the whole premise is that a plant manager gives you thirty seconds to prove you understand what runs his floor. The hiring signal is the highest-value thing you can bring to that call, because staffing and downtime are the same conversation.

Dialing security leaders, the research feeds the opener in the cybersecurity cold call script — where the trigger you want is almost never a funding round and almost always a compliance change, a tooling change visible in their job postings, or an incident in their sector rather than their own building. Referencing a peer's incident rather than theirs is usually the better move, and it takes the same two minutes to find.

Software leaders are different again. When you run the SaaS cold call script for CROs and RevOps leaders, the useful signal is usually headcount shape — who they are hiring on the sales side, whether they are adding enablement or cutting it — because that tells you what the number looks like and what they have already tried. And in professional services, the change worth finding is a new practice area or a senior hire, because both mean somebody has been handed a target they do not yet know how to hit.

Same six minutes. Different sentence, because the accountability is different.

Run it as a block, not per call

One last mechanical point. Do not research one account, dial it, then research the next. Context-switching between reading mode and talking mode is exhausting and it slows both down.

Prep in a block. Sit down with your list and run the six-minute loop on eight or ten accounts back to back, writing each sentence into a column next to the name. Then close every tab, stand up, and dial the whole set with nothing in front of you but the names and the sentences. You will be surprised how much faster the calls go when you are not reading a browser during them.

And when the six minutes produces nothing — no trigger, no clear accountability, nothing to say — dial anyway with a straight industry opener. A generic call made is worth more than a researched call that never happens.

If you want to get sharp at saying that sentence rather than just writing it, the next step is reps against the clock. That is what we built DrillCall for — you practise the fifteen-second opener out loud against an AI prospect who interrupts, pushes back, and does not care how good your research was if you deliver it badly. I would take the six-minute routine, write ten sentences for ten real accounts on your list, and run each one through a drill before you dial it for real. The wording problems show up in about two attempts.