Skip to content
← Processes

Brief every cold call before it starts

A cold calling script opener for every account on the list, written from a dated signal and the lead's public words, saved on the record before anyone dials.

HubSpot→TheirStack→Apify→Serper
Starts
New call list
Steps
5
Checks and gates
0
A person decides
Never, runs alone

Trigger · Event

New call list

A newly built call list starts the run, so briefs are waiting before anyone picks up a phone.

HubSpot

Claude runs the rest autonomously

  1. 1

    AI surfaces any prior contact.

    HubSpot

    HubSpot

    Any earlier conversation on the account record is found before outside research, and the note leads with it when there is one.

  2. 2

    AI finds a dated company signal.

    TheirStack

    TheirStack

    Recent hiring, technology or public news comes back ranked by recency, each with its source link, or the note says plainly that none was found.

    Apify

    Apify

  3. 3

    AI quotes the lead's own public words.

    Serper

    Serper

    What the person has said publicly is kept separate from anything their company said.

  4. 4

    AI writes one opener for the call.

    A single line under twenty-five words that names the signal and connects it to the reason for the call.

  5. 5

    AI saves the brief on the record.

    HubSpot

    HubSpot

    The brief sits on the account record, where the rep is already looking when they dial.

Cold calling well takes about ten minutes of preparation per account, which is why almost nobody does it. A rep with forty calls to make has four hundred minutes of research in front of them and an afternoon to make the calls in, so the research collapses into a glance at the company website and an opener that could have been used on any of the forty.

The preparation is not hard work, though. It is a handful of lookups that always run in the same order against sources that are already public: who they are hiring, what they run, what the person has said out loud. Every one of those is an API call, and none of them needs judgement until the last step, which makes cold call preparation a good job for an AI agent.

What you get

A short briefing note on the CRM record of every account due to be called, with the signal, the person's own public words, and one opener a rep can read straight off the screen.

What goes into each cold call brief

The run starts when a new call list is built in HubSpot, so the briefs are waiting before anyone picks up a phone. For every account on the list, the agent works through the same sources in the same order:

  • The account record. Past interactions, earlier call notes, who owns the account, and whether anyone there has already been contacted.
  • A dated company signal. Current job postings, especially for the function you sell into; technologies the company runs or is hiring for; recent public activity such as a funding round, an office opening, a product launch or a press mention. These come from TheirStack and Apify.
  • The lead's own public words. A conference talk, a podcast, a post, a quote in a trade publication, found by searching the person by name and company with Serper.

Signals are ranked by how recent and how specific they are. A posting from last week beats a funding round from last year. A posting is dated, public, and probably approved by the person who answers the phone. Every signal keeps its URL, because the note is worthless if the rep cannot check it when the prospect pushes back.

What makes AI cold call prep worth reading

The note goes back onto the CRM record rather than into a chat message or a document. It sounds like a trivial delivery detail. It decides whether the brief gets read. The rep already has the record open at the moment they dial, and anything living somewhere else has to be hunted down while a phone is ringing.

Reading the CRM before searching externally catches the failure that embarrasses people. An account that a colleague already spoke to six weeks ago does not need an opener about their hiring, it needs a sentence about where that conversation stopped. Doing the external research first and the internal check second produces a beautifully researched call to someone who has already said no. When the record shows a prior conversation, the note says so at the top.

A brief that pads an empty result with a line about industry trends teaches the rep that the notes are decorative, and after the third one they stop reading any of them, including the good ones. Saying "no dated signal found, open on the problem" costs nothing and keeps the other thirty-nine worth reading.

The lead's words and the company's words stay apart. A press release is the company talking, and the note labels it that way. Only a talk, a post or a quote from the person themselves is presented as their own, since getting that wrong on a call is worse than having nothing.

One opener, under twenty-five words

A cold call opener has about eight seconds to earn the next thirty. The brief carries a single line, under twenty-five words, that names the specific signal and connects it to the reason for the call, written so the rep can read it aloud without sounding like they are reading. Underneath it sits the raw signal, so the rep can improvise when the call goes somewhere else. Three variants would be less useful: a rep scanning options on a screen while a phone rings picks none of them.

Each note follows one structure: the signal and its date, the source URL, what the person has said publicly, the opener, and one line on anything the CRM already knew.

Where it applies

The note is an ordinary call note on the account record, and the prior-contact check is an ordinary read, so the process runs the same way on any connected CRM. At the end of a run it reports how many accounts were briefed, how many had a dated signal, how many had nothing and were flagged as such, and how many already had prior contact worth knowing about.

The prompt

The real prompt behind the steps above, detailed enough that an agent with the same tools can run it as written. The Run buttons copy the full version, which also carries the steps for connecting those tools.

# Brief every cold call before it starts

You have access to a CRM, a hiring and technology signal source, a
scraping tool, and web search. Run this for **[the list of accounts
due to be called]**.


## 1. Surface any prior contact

Before searching anything externally, read the account record: past
interactions, any previous call notes, who owns it, and whether
anyone has already been contacted there. A rep opening a call blind to
a colleague's conversation from six weeks ago is worse than not
calling at all.

If the record shows a prior conversation, the brief's job changes from
finding an opener to summarising where that conversation stopped. Say
so at the top of the note.

## 2. Find a dated company signal

Look for something that happened, with a date attached:

- Current job postings, especially for the function you sell into. A
  posting is dated, public, and the person answering the phone
  probably approved it.
- Technologies the company runs or is hiring for, where you integrate
  with or replace one.
- Recent public activity: a funding round, an office opening, a
  product launch, a press mention.

Rank these by how recent and how specific they are. A posting from
last week beats a funding round from last year. Keep the URL against
every signal, because the note is worthless if the rep cannot check it
when the prospect pushes back.

If nothing dated turns up, say so explicitly in the note. A brief that
admits it found nothing is more useful than one that pads with
generic industry commentary, because the rep then knows to open on the
problem rather than on the company.

## 3. Quote the lead's own public words

Search for the specific lead by name and company. What you want is
their own words: a conference talk, a podcast, a post, a quote in a
trade publication, a comment on someone else's work.

Never attribute to a person something their company said. A press
release is the company talking. Distinguish the two in the note, and
where you only have the company's words, label them as the company's.

## 4. Write one opener for the call, and only one

Write a single opening line, under 25 words, that names the specific
signal and connects it to the reason for the call. It has to be
something the rep can read aloud without sounding like they are
reading.

Do not write three variants. A rep scanning three options on a screen
while a phone rings picks none of them. One opener, plus the raw
signal underneath it so they can improvise if the call goes elsewhere.

## 5. Save the brief on the record

Post the note to the account record as a call note, structured as:
the signal and its date, the source URL, what the person has said
publicly, the opener, and one line on anything the CRM already knew.

Write it back rather than sending it somewhere. The rep opens the
record when they dial; a note in a chat message is a note they will
not find at the moment they need it.

## Output

Report: how many accounts were briefed, how many had a dated signal
found, how many had nothing and were flagged as such, and how many
already had prior contact worth knowing about.

Why run it with Tulina

A prompt helps one person. A process moves a team.

Pasted into a chat, the prompt above works once, for whoever pasted it. In Tulina, "Brief every cold call before it starts" becomes a process the team shares, that keeps its history, runs on its own, and stays inside the same security perimeter as the tools it calls.

  • The whole team works on the same one

    PersonalTeamOrganisation

    A process lives where it belongs: yours, your team's or the whole organisation's. Whoever runs it can improve it, and everyone starts from the best version instead of explaining the job again.

  • Every edit is a version

    v1v2v3

    Each change is a new version with the previous one kept, so a bad edit is undone by restoring an earlier one. Every run records the version it followed, and what a run teaches goes back into the process.

  • It runs without you

    schedulewebhookon demand

    A hosted agent runs the process on Tulina's own infrastructure, on a schedule or when an event arrives, and keeps going when you close the chat. Nothing to host. Every run is tracked to its outcome.

  • Inside the same security perimeter

    vaultrolesrun log

    Credentials stay in the vault, never in the prompt. Roles decide who may run what, every call is logged, and a step a person has to approve waits for that person.

Questions about cold call preparation with AI

Yes. An agent with access to the CRM, a hiring and technology signal source, a scraping tool and web search can read the account record, find a dated signal about the company, look up what the lead has said publicly, and save a short note with one opener on the record before the rep dials.

It can when the opener is tied to something specific and dated. The line stays under twenty-five words, names the signal and connects it to the reason for the call, with the raw signal underneath so the rep can improvise. It writes one opener, since a rep scanning three options while a phone rings picks none of them.

The note says so explicitly instead of padding with generic industry commentary. That is useful information for the rep, who then knows to open on the problem rather than on the company, instead of reading out a line that sounds researched and is not.

The two are kept apart in the note. A press release is labelled as the company talking; only a talk, post or quote from the person themselves is presented as their own words. Getting that wrong on a call is worse than having nothing.

Other processes that run mainly on HubSpot. The tools they share with this one are lit.

See Tulina in a 30-minute demo.

Book a demo