A first-call brief for sales

The first five minutes are the product

A first sales call is lost or saved before the deck. The buyer can tell whether you know who they are — which person, which seat, which public problem they have already described — or whether you scraped a title and hoped. The brief for that call is a one-page orientation: confirmed identity, current role, company context you can defend, one public artifact you actually opened. It is not a life story and it is not a list of direct dials.

Most reps already “research.” They open LinkedIn, Google, the company homepage, a news tab, a podcast tab, a notes doc, and then the Zoom wait room. Twenty minutes later they have a pile and still open with “tell me about your role.” The pile failed because it was not a brief and because it often mixed two people who share a name.

This page is the sales version of confirm-first public-web research. The generic write-up lives in write a first-call brief. The product version is a sourced page after you pick the person, with follow-ups attached so you do not start a second search in the lobby. See people search, without a dossier dump for the shared method.

Twelve tabs vs one page

The same ten minutes can produce a tab pile or a page. The tab pile feels like work. The page is the artifact you can reopen at 8:55 a.m. without picking a new Alex Chen.

In the tab pile, Google returns a news hit about a different Maria Garcia in the same industry. LinkedIn shows a close namesake at a customer you do not have. GitHub belongs to the engineer, not the VP. Your notes merge them because you were late. On a call, you cite the news hit. She has never been in that article. The call is now about your research, not her problem.

On one page, confirm is a gate. The brief cannot start until you pick a card. Follow-up questions stay on that card. If the public web is thin, the page is thin, and you walk in with questions instead of a fake news citation. Thin is professional. Merged is not.

What the ten minutes cost

Reps do not lose deals because they failed to find a mobile number in a directory. They lose hours to unstructured lookup, then show up with nothing they can cite. Do the arithmetic on your own week before you add another browser extension.

If you do eight first-call lookups a week at eighteen minutes of tab-hopping, that is a couple of hours you will not get back — and the output is still a pile. A sourced brief does not replace discovery. It replaces the part of “research” that is really disambiguation plus a hunt for one citable sentence. Your wage is yours to apply; the slider is only there so the cost is visible.

The calculator is not a promise that a product is cheaper than skill. A practiced rep with a good CRM already spends less than eighteen minutes. The people who need the page are the ones who spend eighteen minutes and still brief the wrong Maria. Time is the symptom. Confirm is the fix.

Confirm the buyer — the name on the calendar is a collision set

Calendar holds lie. “Alex Chen, VP, Thursday” is not a person. It is a string that matches a VP of engineering, a VP of sales, and a founder who uses VP as a courtesy title. Your AE-to-AE Slack (“Chen at the payments company”) is better, and still not unique.

Confirm with three signals before you write an opener: employer as of a page you opened, seat (function, not just “VP”), and one unique artifact (a talk, a byline, a filing, a product page that names them). If the hold came from an SDR who booked the wrong Chen, the brief should catch it. That is a win. A polished opener on the wrong VP is a loss you will blame on “personalization.”

Common-name collisions are the working condition, not an edge case. Use the same card discipline as confirm the right person and common-name collisions. If two cards still fit, email the assistant or the SDR: “Want to make sure I have Alex Chen, payments, the one who spoke on latency — is that Thursday?” Do not guess to protect your pride.

Worked example: Alex Chen, inbound demo

An inbound form says Alex Chen, work email at a payments company, “interested in observability.” You have a demo tomorrow. You also have three public Alex Chens in payments. The form did not include a title.

Start from the email domain, not the name

Open the company site and the team or engineering page. Search Chen. If you find one Alex, you have a candidate card. If you find none, the inbound may be a practitioner who is not on the marketing site — still confirm via the email domain plus a public artifact, not via a directory home address. If you find two, you need the artifact: the observability interest, a talk, a repo, a LinkedIn-public headline the SDR already attached.

Do not brief the loud engineer by default

The SF staff engineer with a latency talk is easy to fall in love with. He might be your inbound. He might be a namesake. The form said observability, not latency. If the talk is about API tail latency and your product is observability, you may still cite it — after you confirm it is the same human. If you cannot confirm, your opener is “you wrote that you were interested in observability” — the form they submitted — not “loved the latency talk.”

The five-minute brief

• Confirmed: Alex Chen, this email domain, this team-page title (date).
• Company context: what the company sells, in one sentence from their site, not from a data vendor’s firmographic blur.
• Public artifact: talk, post, or job they posted, opened, dated.
• Question you will actually ask: tied to that artifact or to the form.
• Off the page: mobile numbers, personal social photos, “likely leaving.”

If the team page is empty and the web is quiet, the brief is the form plus the company homepage. That is enough to run a decent discovery call. Padding it with a directory is how you get a wrong city into your opener.

Worked example: Maria Garcia, outbound to a city vendor

You sell to vendors that sit in municipal data. A list says Maria Garcia, director of partnerships, Denver-area vendor. Lists lie about titles and they mash people. Treat the list as a rumor.

Open the vendor site. Find Maria. Confirm director of partnerships — or discover she is director of data, or that she left, or that the partnerships lead is a different person. Conference programs from this year are the next check. A Tuesday municipal-data panel with her name and this employer is a unique artifact. A news hit about a Maria Garcia in Denver politics is not her unless the article names the vendor.

Outbound opener, if confirmed: you sell X, you saw the panel (or you saw the team page if there was no panel), you work with vendors who sit in the same procurement cycle, you want twenty minutes on Y. Outbound opener, if not confirmed: do not send. Fix the list. A wrong-Maria email to a city vendor is how you get remembered as noise.

If you only have the list and a quiet site, your job is not a people-search dump. Your job is to find one public page that ties this Maria to this employer this year. No page, no sequence. That rule saves more reputation than it costs in pipeline theater.

Worked example: Daniel Kim, calendar VP

The hold says “Daniel Kim, VP, Thursday.” The SDR note says the company name and nothing else. That string matches a VP of engineering, a VP of sales, and a Daniel Kim who is a founder and uses VP as a courtesy title at a similarly named company. Your first-call brief has to pick one.

Confirm from the invite domain and the function, not from “VP” plus the brand. Open the company team or leadership page. Find every Daniel Kim. If you find an eng VP and a sales VP, you need the SDR or the inbound form: who booked Thursday? If you find none, the hold may still be a practitioner — confirm via the email domain plus a public artifact (a talk, a hiring post they opened, a filing). Do not default to the loudest Daniel Kim in the industry Slack.

Five-minute brief after confirm: title as of the team page (dated), one sentence from their site about what they sell, one artifact if it is theirs, one question. If you cannot tell eng VP from sales VP, your opener is a confirm question, not a personalized deck. Daniel is a calendar-collision, not an inbound-form Alex or a list-Maria.

What you are allowed to cite on the call

Cite what they put in the world to be read as professionals: a talk, a blog post, a job listing they opened, a podcast, a patent or filing that is clearly theirs, a product announcement that names them. Cite it as a question. “You said on the panel that procurement cycles were the bottleneck — is that still the constraint?” One citation. Then listen.

Do not cite: a public social photo, a family detail, a directory age, a political donation unless your counsel and your market make that a deliberate part of the motion (for almost all B2B sales, it is not), a leaked org chart, a colleague’s gossip. If you would not be comfortable with them knowing you used the source, it is not a first-call source.

Do not cite a news article until you have opened it and seen their name next to this employer or this unique artifact. Homonyms in trade press are normal. The research brief is stricter about this because writers publish. Sales should be almost as strict, because you have to sit in the room with the mistake.

Not a contact waterfall

Apollo-class tools are good at a different job: find a contact, enrich a sequence, put a person in a cadence. That is not a first-call brief. A waterfall can be right and still brief you on the wrong human if the match key was a common name plus a fuzzy title. Do not ask a sequencing tool to be your research memo. See OneSearch vs Apollo.

Use the waterfall when the job is “I need a way to ask for time.” Use the brief when the job is “I already have time.” If you have neither a confirm nor a meeting, you do not have a people-search problem yet. You have a list problem. Mixing the two is how directory attributes land in a call script.

LinkedIn remains the place you message and inspect a public profile if you need the graph. Google remains the place you go when you already have the talk title. OneSearch is the confirm-then-brief step when the name is the only solid object and the call is tomorrow. LinkedIn and Google comparisons exist so you do not force one tab to win every job.

Discovery that does not start at zero

A good brief does not replace discovery. It keeps discovery from wasting the first five minutes on facts you could have opened last night. You still ask what they own, what “good” means this quarter, who else is in the decision, what they already tried. You skip “so what does your company do?” when the homepage is clear. You skip “I saw you went to…” because that is performance.

If the brief is thin, discovery starts earlier and that is fine. Thin means you ask cleaner questions. Invented means you spend the call recovering from a wrong citation. Prefer thin.

Multi-thread with the same discipline. The economic buyer and the champion are two tickets, two confirms, two pages. Do not copy Alex’s brief onto Maria because they share a domain. Shared domain is not shared identity.

After the call

Add what they said to your CRM in your words, as a conversation note. Do not back-port those notes into a people-search product and call them sources. Do not file public-web research as a reason to credit-check a buyer or to decide whether their company is “good for” a contract. Commercial underwriting and consumer reporting are other processes. If your org uses people-search output like a credit file, stop and read FCRA and legal use and the FTC credit reporting guidance. This is not legal advice; it is a boundary.

Reopen the same brief before the second call. Ask follow-ups against it (“they mentioned a migration — is there a public talk about that migration?”). If you start a new name search, you will reintroduce the namesake.

A desk method

You can run a first-call brief in a notes file. OneSearch compresses it when you have a stack of first calls and common names. The order does not change.

1. Write the ticket: name, company, call time, inbound or outbound, “this is not a credit or hiring decision.”
2. Confirm from the strongest breadcrumb you have (email domain, team page, form, SDR note). Name-alone search is last, not first.
3. If two cards fit, stop and ask a human. Do not personalize a coin flip.
4. Open the company homepage, the team page, and one primary artifact. Date them.
5. Write four lines and one question. Close extra tabs. Do not open a directory “for completeness.”
6. On the call, cite at most one artifact, then discover. Do not perform the brief.
7. After the call, CRM notes are yours. Sources stay public URLs. Do not merge the two into a fake report.

Founders running the same confirm-first pass before an investor meeting should use the founder brief — same gate, different questions. Recruiters writing a first note rather than a call script should use the recruiting brief. Writers who need a citation trail rather than a call script should use sourced people research. For the product sequence, how it works is name, confirm, sources, brief, ask.