Write a first-call brief

What a first-call brief is

A first-call brief is a one-page note you can read twice before you join. It answers four questions: who you are talking to, what they have said in public about their work, which open pages those claims come from, and what you will ask in the first ten minutes. It is not a biography. It is not a contact waterfall. It is not a background check. If a sentence will not change how you open, listen, or follow up, it does not belong on the page.

The job of the brief is to keep you from inventing a person from a name. Recruiters write one before a screen. Founders write one before a partner or investor conversation. Sales writes one before a discovery call. Researchers write one before quoting someone. The audience changes; the page does not. You still start with a name, you still confirm the person, and you still stop when the public web is quiet.

OneSearch is built for this page: type a name, confirm a card, read a sourced brief, ask follow-ups that stay attached. You can run the same method in a notes doc. See people search for the confirm-first workflow without assembling the tabs yourself.

The twelve-minute clock

Twelve minutes is enough if you refuse to chase completeness. Set a timer. You are not writing a profile for a wiki. You are collecting enough public signal to walk in without guessing the last role or mis-attributing a talk. If you routinely spend forty minutes, you are either merging two people or filling gaps the web never published. Both are errors. The operator guide can shorten the hunt; it cannot invent a trail.

Split the clock on purpose. Two minutes to write the confirm line (name, company or city, one unique public artifact). Six minutes on the source stack — company site, talks or bylines, public social or code, press — opening pages, not titles in a results list. Two minutes to write three questions you will actually ask. Two minutes to cut anything you cannot click. When the timer ends, the brief is done, even if it is thin.

Thin is a finding. A departmental bio from 2019 and a PDF program from a campus talk is a complete brief if that is all the open web holds. Do not pad it with a guessed title or a city you inferred from a namesake. How to sit with that silence is its own method: when the public web is quiet.

Confirm before you write

A first-call brief on the wrong Alex Chen is worse than no brief. Common names collide across companies, cities, and decades. If you were told “Alex Chen, the San Francisco engineer who spoke on latency last year,” you still have to pick that card and reject the quant in New York and the founder in Austin. The method lives in common-name collisions. The rule for this page is simpler: no paragraph exists until the confirm line exists.

The confirm line has three parts you can defend in the room. (1) The name as it appears on an open page, not a nickname you invented. (2) A breadcrumb you already had — employer, city, talk title, repo, byline — not a breadcrumb you scraped after the fact and reverse- fitted. (3) One unique public artifact that would not fit the lookalikes. If two cards still fit after that, stop. Do not merge people. Do not write “probably the SF one.”

Confirmation is a gate in how OneSearch works: name, confirm, sources, brief, ask. Manual research should copy the gate. Opening ten tabs before you have a card is how you brief the wrong person with high confidence.

Brief anatomy

Click each part. If a section has no open URL behind it, it is not part of the brief yet.

Confirm is the match you picked. Role, city, one artifact. If this is wrong, everything below is a different person and should not exist. Summary is a short narrative from open pages. Every load-bearing sentence should be clickable. “Works in payments” is load-bearing; “seems thoughtful” is not research. Work is roles as they appear on company sites, talks, and bylines, dated when the source is dated. Do not upgrade “spoke at” into “leads.” Ask is follow-ups that stay on this person’s sources. A new name is a new brief.

Write the four parts in that order. People who start with work history often discover halfway through that they have two employers on two people. Anatomy is a writing order, not a design flourish.

Twelve tabs vs one page

The same ten minutes can produce a tab pile or a page. The tab pile feels like research because you touched LinkedIn, Google, GitHub, and a news clip. It is easy to brief the wrong Alex, and it is easy to lose the URL that actually supported a claim. The page forces you to choose.

If you stay in tabs, paste the URL under every sentence as you go. Do not trust memory after the call. If you use OneSearch, the citations stay on the brief and follow-ups stay attached — that is the product difference versus a general Google search or a LinkedIn tab. Neither of those tools is wrong for their job. Google finds a page. LinkedIn is a network and a message channel. The first-call brief is a different job: one sourced document you can reopen the morning of the call.

Apollo-class tools and people directories are a third job — contact data, sequences, consumer attributes. Do not import a phone number or household field into a first-call brief. If the job is a consumer report, stop and read FCRA and legal use.

What to collect

Collect only from indexed, publicly accessible pages. Company team pages and speaker bios are usually the cleanest role signal. Talks, podcasts, and bylines tell you how they describe their own work. Public social or code can confirm a stack or a community, not a personality. Press can confirm a date or a launch; treat it as secondary until you open the original page and check that the article is about the person you confirmed.

For each source, write four fields in your notes: URL, date on the page (or “undated”), the claim in the source’s words, and whether the page uniquely identifies your person (company + role, or a face/talk that matches). If you cannot fill those four fields, the source is a maybe. Maybes do not go in the summary. They can sit in a “parked” list at the bottom so you do not lose them, and so you do not launder them into facts.

Prefer first-party pages. A company engineering blog that names Alex Chen as the author of a latency post is stronger than a roundup that mentions “an engineer named Alex.” A conference program PDF that lists Maria Garcia with a departmental affiliation is stronger than a social post that tags a common name. Secondary pages are how collisions enter the brief. Collect and verify are two passes, not one.

Date everything you can. “Staff engineer, 2023 talk” is usable. “Staff engineer” with an undated snippet is a maybe. A 2019 departmental bio is a 2019 fact, not a 2026 title. If the only dated page is old, say so: “Last dated public page: 2019 campus talk. Current employer not confirmed.”

What to leave out

Leave out anything you will not use in the first conversation and anything the open web did not publish. Family, home address, estimated net worth, “three children,” political guesses, and health inferences are not first-call research. OneSearch does not sell that file. Your notes doc should not grow one.

Leave out contact waterfalls. Email patterns and mobile numbers belong in a sequencer, not in a brief you will reread for tone. Leave out character judgments. “Seems like a culture fit” is not a sourced claim. If a podcast host asked a sharp question and they answered it, quote the answer and link the episode.

Leave out eligibility language. A first-call brief is prep for a conversation. It is not hire/no-hire, tenant yes/no, credit, or insurance. If someone on your team wants to use the page that way, they need a consumer reporting agency and a compliant process — not a public-web note. That boundary is not a slogan; it is the difference between research and a regulated report. Details: FCRA and legal use.

Worked example: Alex Chen, first sales call

You have a Tuesday discovery call. The inbound form says Alex Chen, payments company, San Francisco. You do not have a LinkedIn URL. You have twelve minutes.

Confirm line: “Alex Chen — staff engineer, payments company, San Francisco. Unique artifact: 2025 conference talk on payment-latency tail cases, slides on the company engineering site.” You rejected a New York quant with a different middle initial on a faculty PDF and an Austin founder whose podcast shows a different face. If you cannot reject those cards, you do not write the brief. You write a question for the AE: “Which Alex — SF payments talk, or someone else?”

Summary (four sentences, each with a URL): current role as stated on the company team page; the latency talk and the year on the program; one engineering-blog post under that name on the same domain; no dated press that names this Alex at this company after 2024. That last sentence is a finding. It keeps you from opening with “loved the TechCrunch piece” that was about a different Alex Chen.

Work: staff engineer, payments, SF, dated from the team page and the talk. Do not promote them to “leads infrastructure” because the talk was confident. Ask: (1) “Your 2025 talk treated p99 as a product problem — is that still the frame internally?” (2) “The blog post walked through queue isolation — is that still in production?” (3) “What broke after the talk that the slides do not show?” Those questions are usable because they are attached to pages. “What’s your vision for payments?” is not a brief; it is a blank.

You will not collect a mobile number. You will not estimate tenure from a photo. You will not mention the Austin founder in the room. If the web had been quiet — team page gone, talk not online — the brief would be the inbound form plus “no dated public trail confirmed,” and the questions would be about their problem, not their biography. That is still a first-call brief.

Worked example: Maria Garcia, recruiting screen

A referral says “Maria Garcia, research-adjacent, spoke on campus around 2019, might be in Austin.” That sentence is a collision factory. High-frequency name, stale year, soft city. Before you write outreach, you need a confirm line or you need to go back to the referrer.

You find a 2019 departmental bio and a PDF program from a campus talk. You do not find a current employer on an open page that also carries a unique artifact. The honest brief is two pages and a gap. Summary: “Public trail is a 2019 bio and a campus program PDF. Current role not confirmed. Do not invent a 2024 title.” Questions for the screen, if it still happens: ask what they are working on now, and ask how the 2019 talk topic aged. Questions you do not ask from invented context: “How’s the VP role in Austin?”

If a second Maria Garcia appears — same field, different campus, a 2023 byline — you now have two cards. Do not merge the byline onto the 2019 bio because the story would be nicer. Send the referrer both cards. “Which Maria — 2019 campus program, or 2023 byline at X?” That email is the brief until someone answers. Recruiting outreach written on a merge is how you burn a referral and look like you did not read.

This is also the FCRA line in recruiting. A public-web brief can change how you open a conversation. It cannot be the file you use as a consumer report for hire, promote, or housing. If your process requires a background check, use a CRA. OneSearch will not become that file for you. The legal page is here; the product page for this workflow is people search.

Worked example: Priya Nair, first partner call

A vendor invite says Priya Nair, design systems, Bengaluru, 30 minutes. Purpose: you are deciding whether their token-pipeline work is even the right conversation. You have twelve minutes. This is not a recruiting screen and not a diligence file.

Confirm line: “Priya Nair — design-systems lead, Bengaluru product company. Unique artifact: 2024 conference talk on design-token pipelines, slides on the company design blog.” You rejected a Boston public-health researcher named Priya Nair (journal byline, different face, different city) and a London PM whose headline also says “design systems” with no talk match. If you cannot reject those cards, you do not write the brief. You write a question for the organizer: “Which Priya — Bengaluru token talk, or someone else?”

Summary (four sentences, each with a URL): current role as stated on the team page; the 2024 talk and the year on the program; one design-blog post under that name on the same domain; no dated press that names this Priya at this company after 2024. Work: design-systems lead, Bengaluru, dated from the team page and the talk. Do not promote them to “head of design” because the slides were confident.

Ask: (1) “Your 2024 talk treated tokens as a pipeline, not a Figma file — is that still the frame?” (2) “The blog post walked through theming breakage — is that still the incident you would start with?” (3) “What broke after the talk that the slides do not show?” You will not mention the Boston journal paper. You will not collect a mobile number. If the web had been quiet, the brief would be the invite plus “no dated public trail confirmed,” and the questions would be about their problem, not their biography.

Questions you will actually ask

Write questions that require the brief. If you could ask the same three questions to any stranger in that job title, you did not need a brief. Good questions point at a page: a talk, a byline, a repo, a launch note, a dated role. They invite correction. “If I misread the 2025 slides, stop me” is a better opener than a summary of their career they did not ask for.

Cap yourself at three questions from the brief. The rest of the call is their problem, not your research. The brief is a floor so you do not waste the first five minutes on “so what do you do?” It is not a script.

Park questions the sources cannot support. “Why did you leave Company X?” is not a public-web question unless they said so on an open page. “Are you happy?” is never a research question. “Who else should we involve?” can wait until they have talked. The brief should make you more specific, not more intrusive.

Hand the brief to a teammate

If someone else is taking the call, the brief has to survive without you. That means URLs in the note, dates on claims, and a confirm line at the top. “Alex Chen, payments, SF, latency talk 2025, here’s the program PDF” can be handed off. “Seemed senior, interesting background” cannot.

Label confidence. Confirmed means you opened the page and the identity markers match. Parked means you found a maybe. Absent means you looked and the web was quiet. Do not let a teammate upgrade parked to confirmed because the call is in an hour. Do not paste the brief into a hiring packet as if it were screening. Treat it as dated meeting prep. Re-open the sources the morning of the call.

Stop line

Stop writing when you cannot confirm the person, when two cards still fit, or when the remaining questions are about eligibility rather than conversation. Stop inventing when the stack is quiet. Stop collecting household or contact fields that do not belong on a public-web page. Those stop lines are the product: confirm-first, thin-beats-invented, not a consumer report.

If you want the page assembled after you pick a card, start at people search. If you want the collision method, read common-name collisions. If you need to check a sentence before you say it in the room, use source verification. If the trail is two old PDFs, sit with a quiet web instead of padding the note.