How to research someone before a meeting (in about 10 minutes)

DeepSearch Name is public-web research — not a background check and not FCRA-compliant. Use it for professional context with sources you can verify; use a regulated consumer reporting agency for employment, housing, or credit decisions. Read the full distinction.

Good pre-meeting research makes you specific without making you creepy. In about ten minutes you can confirm identity, scan public work, and prepare two intelligent questions — using open web sources only. This is professional preparation, not an FCRA background check and not a contact-dossier rabbit hole. If your real goal is employment, housing, or credit eligibility, stop and use a regulated process — see not a background check.

The habit matters more than the tools: lock the person, skim one real artifact, verify what you will say out loud. DeepSearch Name can compress the tab stack; it cannot replace judgment in the room.

The 10-minute checklist

1. Minute 0–2: Lock identity — name + company/city; reject namesakes.
2. Minute 2–5: Current role reality — employer page, LinkedIn, or recent announcement.
3. Minute 5–8: Public work skim — one talk, post, paper, launch, or interview.
4. Minute 8–10: Talking points + verify — two questions, one compliment tied to a source you opened.

Longer playbook: pre-meeting people research. Use that guide when the meeting is high-stakes or the name is ambiguous; use this article when you need a repeatable ten-minute ritual.

Minute 0–2: Confirm you have the right person

Wrong-person prep is worse than no prep. If the name is common, do not trust the first profile photo that “looks right.” Match employer, location, or email domain. Write the clues you already have on a sticky note before you search — that reduces motivated matching. DeepSearch Name forces candidate confirmation before a brief for this reason — or practice manually with common name disambiguation.

Fast rejects: wrong city with a strong local signal in the invite; wrong industry when the agenda is domain-specific; a Wikipedia celebrity dominating results when your calendar says “Series A founder.” Exclude noise with operators when needed — Google advanced search for people.

Minute 2–5: Establish current professional context

• What is their current role and employer?
• Did they join recently? Ship something public?
• What audience do they usually speak to (customers, developers, investors)?
• Is there an obvious shared context (mutual company, event, portfolio company)?

Prefer primary sources (company site, their own writing) over recycled bios. LinkedIn is useful; it is not the only surface — see vs LinkedIn. If the company site and LinkedIn disagree on title, note the conflict and prefer the more recent primary page — or avoid stating the title until you know.

Minute 5–8: Skim one piece of public work

Depth beats breadth. One solid artifact — a podcast, keynote clip, product launch post, or GitHub README — gives you more conversational fuel than twenty shallow tabs. Note:

• A problem they care about
• A phrase or framework they use
• A recent win you can congratulate sincerely
• A risk or open question they have already named publicly

Avoid “I read everything you ever posted” energy. One specific, accurate reference beats a parade of half-remembered headlines. If you cannot find public work in three minutes, switch to company-level context (recent launch, hiring page themes) rather than inventing a personal angle.

Minute 8–10: Prepare questions and verify

Write two questions that could only be asked of this person (not “So, how’s business?”). Open the source behind any fact you plan to mention. If sources conflict on title or affiliation, resolve the conflict or avoid the claim. Run a quick pass on the checklist:

Full verification guide: verify public web identity.

What to research (and what to skip)

A useful rule: if you would feel weird mentioning it in the first five minutes, do not dig for it in the last five minutes of prep.

By meeting type

Sales / prospect calls

Focus on their mandate, recent initiatives, and language from public posts. Personalization should sound human, not scraped. Mirror vocabulary from a launch post or earnings-adjacent blog, not from a directory scrape. More: for sales.

Fundraising / investor meetings

Map the partner’s stated thesis and portfolio patterns from public posts and firm pages. Know one relevant portfolio company story and one question about how they evaluate your stage. Founders: for founders. Investors researching operators: for investors.

Hiring conversations (not screening)

Public work helps conversation quality — portfolios, talks, open-source. Formal employment screening is a separate, regulated process — do not blur them, and do not file research notes into a “background” folder. Read not a background check. Recruiters prepping outreach: for recruiters.

Press and partnerships

Prioritize on-the-record bios, prior quotes, and affiliation accuracy. Get the spelling and title right before you put them in a brief or pitch. Journalists: for journalists.

Customer and partner QBRs

Skim their latest public product or hiring signals so your questions match their current quarter, not last year’s deck. Confirm the attendee list identities when names are common — the “Alex from Acme” on the invite may not be the Alex your AE researched last month.

Using a sourced brief without outsourcing judgment

An AI brief from DeepSearch Name can compress the first six minutes: candidates, narrative, links. Your job remains human — click sources, discard weak claims, and choose talking points that fit the meeting’s goal. Treat the brief as a map. Details: source-linked profiles.

After the brief, chat can help you probe gaps without rebuilding search tabs. Example prompts you can adapt:

Still open the underlying links. A fluent answer with a weak citation is a hypothesis, not a talking point. Lookups stay private — see private people search — so preparation does not notify the other party.

Note-taking that survives the meeting

Capture three lines max: (1) identity anchors (employer, role), (2) one public artifact with URL, (3) two questions. Put source URLs in the note so a teammate can re-verify. Avoid pasting speculative commentary into a shared CRM field labeled as fact. If your company has a research retention policy, follow it — public does not mean “store forever.”

Privacy and etiquette in the room

• Reference public professional work, not obscure personal facts
• Do not surprise people with information they would not expect you to know
• If you used private lookup tooling, you still do not need to announce a dossier
• Never imply you ran a background check when you only read public pages
• If you got something wrong, correct it quickly and move on — do not double down

When ten minutes is not enough

High-stakes diligence, contested facts, or investigative work need more time and often more than open web skim. Escalate methods carefully; keep illegal access and FCRA misuse off the table. Multi-party meetings deserve a pass on each named attendee, not only the host. For tool choice across categories, see best people search tools. End-to-end product flow: how it works.

A simple pre-meeting script

1. Paste name + company into search (or DeepSearch Name).
2. Confirm candidate; reject near-misses.
3. Open employer page + one artifact.
4. Write two questions; delete anything you did not verify.
5. Walk in ready to listen — research supports curiosity, it does not replace it.

Common pre-meeting failure modes

Over-preparing the wrong person

You spent twenty minutes on a polished profile that belongs to a namesake. The fix is front-loading identity: employer, email domain, or a mutual connection’s public mention. Never invest in talking points until the candidate is locked.

Reciting a dossier

Listing five obscure facts in the first minute signals surveillance, not care. Pick one public professional detail and ask a real question. Leave the rest in your notes as context for listening.

Treating LinkedIn as ground truth

Headlines lag, inflate, or belong to someone else. Corroborate with an employer page or recent primary source before you congratulate someone on a title you have not verified.

Skipping re-checks for delayed meetings

If the meeting slipped six weeks, skim once more for role changes. Public context is not static. A two-minute refresh beats walking in with last month’s org chart.

Confusing prep with screening

Reading public pages before an interview is normal. Filing that research as a “background check” in an HR packet is a category error. Keep artifacts and language separate — people search vs background check.

Multi-attendee meetings

When three people join from the other side, run a lightweight pass on each named attendee — at least identity + role — even if you go deep on only the decision-maker. Wrong-person assumptions about a silent VP on the call are how awkward moments start. Budget roughly three minutes per additional name for confirmation, plus deeper skim only for the person you will primarily address.

Shared calendars often show partial names (“Alex M.”). Expand them before research. If you cannot expand, ask your champion for full names and companies in the agenda email. That request is normal and beats guessing.

After the meeting: close the loop

Update your note with what you learned that was not public, mark speculative fields as confirmed or wrong, and attach any new primary URLs the person mentioned (“we just published X”). Good research compounds; stale CRM fiction compounds too. If a claim from prep was wrong, correct it the same day so the next teammate does not repeat it.

Templates for talking points (public only)

• “I saw your [talk/post] on [topic] — how are you thinking about that for [this quarter]?”
• “Congrats on the [launch] — what surprised you most after it shipped?”
• “Your firm’s note on [thesis] resonated — where does our space fit that lens?”

Each template requires a source you opened. If you cannot fill the brackets from a real page, delete the line. Empty curiosity (“What are you focused on lately?”) beats a fake-specific compliment every time. Save winning questions that land well so your future prep gets faster without getting creepier.

Handing prep to a teammate

If someone else will join the call, share a short prep note with identity evidence, one public work item, two questions, and open conflicts — not a dump of every tab. Label the note as public-web meeting prep. Do not paste it into a hiring packet or call it a background check. When the name was ambiguous, include the candidate confirmation step so they do not “helpfully” merge a namesake overnight. For disambiguation patterns, see common name disambiguation.

Bottom line

Research someone before a meeting by confirming identity, skimming real public work, and verifying the facts you will say out loud. Ten focused minutes beat an hour of unstructured tab-hopping. Start a name-first search above when you want a sourced brief, or keep a manual operator habit with Google advanced search. Either way, leave the background-check framing out of the room.