People search, without a dossier dump

The job is a brief, not a dump

Most “people search” products hand you a pile: possible phones, possible addresses, possible relatives, a map pin, and three people mashed into one record. That pile is useful if your job is to find a phone number. It is the wrong artifact if your job is to walk into a room and not sound like you Googled someone in the hallway.

The useful output is a brief: a short page about one confirmed person, built from pages you can open, with the original URLs still attached. Role. Company. What they have said in public. What they have shipped or written. Dates. That is enough for a first conversation. A dump of consumer attributes is not a brief, and treating it like one is how you brief the wrong Alex Chen.

OneSearch is that brief. You type a name, you confirm the person, you get one sourced page, then you ask follow-ups against the same sources. The person is not notified. Nothing behind a login wall is fetched. If the public web is thin, the page stays thin. You can run the method below in a browser without the product.

Pick the tool before you search

People-search fails when you pick a tool by habit. You open LinkedIn because that is where names live. You open Google because that is where pages live. You open a directory because a friend used it to find a landlord. Those are three different jobs. Mixing them is how a first-call brief becomes a consumer report you were not licensed to run.

Decide the job in one sentence before you type the name. “I need to message them” is LinkedIn. “I need this one PDF” is Google. “I need to walk in oriented, and I must not merge two people” is a sourced brief. “I need to decide hire / no-hire, tenant, credit, or insurance” is a consumer reporting agency — stop, do not use a people-search product.

One winner per job. Google finds a page. LinkedIn is a network and a mailbox. Apollo-class tools sell contacts and sequences. Directories sell consumer attributes. A CRA runs a regulated screen. OneSearch writes a sourced brief after you confirm. If you need two jobs, use two tools.

A recruiter who needs a conversation still belongs on LinkedIn for the message. A founder who already has the talk URL and only needs to re-read it belongs in Google for that one page. The brief is for the gap in between: you have a name, you are not sure which person it is, and you have to speak in twelve minutes.

Confirm is a gate — a name is not a person

A first-and-last name is a collision set, not an identity. “Alex Chen” is a staff engineer in San Francisco, a principal in New York, a founder in Austin, and several hundred other people. If you generate a paragraph before you pick a card, you will eventually quote the wrong person’s talk in a room with the right person. That is not a research error you can laugh off. It is a professional error.

Confirmation is a gate, not a nicety. No brief until one card is chosen. A card needs three agreeing signals before it is safe: a role or company, a place or org, and one unique public artifact (a talk title, a repo org, a byline, a faculty PDF with a middle initial). Two signals that almost fit are not enough. “Works in tech, West Coast” describes a crowd. Write breadcrumbs before you search — name, company, city, title, event. Searching the bare name first trains you to pick the most famous card.

If two cards still fit after every breadcrumb you already have, stop. Do not merge them. Ask for one more artifact, or accept that you cannot brief this meeting from the public web. The confirm-the-right-person method is the gate. Everything after a wrong confirm is fiction with citations.

Worked example: Alex Chen

A colleague DMs you: “Can you talk to Alex Chen before Thursday? Payments, I think. Spoke on latency last year.” That is a complete research ticket. It is also a trap if you type the name and grab the first hit.

Start with what you already know, not with the open web. You have: Alex Chen. Payments company (maybe). A public talk on latency (last year). You do not have a city, a title, or a URL. Do not invent San Francisco because most latency talks you remember were there.

Build three cards before you write a sentence

• Card A — Staff engineer, payments company, San Francisco. GitHub org commits. Conference talk titled something you can open: a slide deck or a YouTube page with the same face and the same employer on the bumper.
• Card B — Principal, quantitative shop, New York. A faculty page and a PDF with a different middle initial. The paper is about latency in a different sense (market data, not product APIs). Easy to mash if you only read the word “latency.”
• Card C — Founder, logistics startup, Austin. A podcast last month. Different face, different company. The host says “Alex” a lot. The show notes say Chen. That is enough to waste ten minutes if you skip the face and the employer.

The referral said payments and a latency talk. Card A is the only card where company, topic, and artifact agree. Card B has latency and a serious resume; it is still the wrong person. Card C is a confident podcast and still wrong. Confirm A. Only then write the brief.

What the brief is allowed to say

After confirm, open the talk page and the company team page. Write: current role as stated on the team page (date the snapshot). Talk title, event, year. One sentence they actually said, with the URL. Public repos that sit under the same org name as the employer, if the commits are theirs and not a namesake. Stop. Do not add a directory address, a phone, or “probably thinking about leaving.” If Thursday is a hiring screen, this is conversation prep only — see FCRA and legal use.

Worked example: Maria Garcia

You met someone at a Denver conference. The badge said Maria Garcia. You remember a panel on municipal data, not the employer. Your notes say “Garcia — data — Denver.” That is less than the Alex Chen ticket, and it is the more common failure.

Search “Maria Garcia” alone and you will get journalists, physicians, teachers, engineers, and elected officials. Adding Denver helps and is still not unique. Adding “municipal data” or the panel title — if you wrote it down — is the first unique artifact. If you did not write the panel title down, look up the conference program by date and city, then search the program PDF for Garcia. That is still public-web research. It is slower than a product, and it prevents you from briefing a Denver school-board Maria as if she ran the data panel.

What “still N cards” means

After name + city + event, you may still have two Marias on the program — a moderator and a speaker, or two speakers on different days. Open both bios on the conference site. Compare the employer line and the headshot. If you cannot tell which one handed you the badge, you do not have a brief. You have a polite email: “I want to make sure I have the right Maria from the municipal data panel — are you at [org]?” That email is better than a confident wrong page.

Once one Maria is confirmed — say, director of data at a city vendor, speaker on Tuesday, bio on the vendor’s team page — the brief is: employer, title as of the team page, panel title and date, any public writing under that byline. If her name is on a press hit about a different Maria Garcia in the same city, leave it off. Homonyms in press are a default assumption, not a rare edge case. Writers and analysts hit this weekly; treat it as the normal path.

Worked example: Wei Zhang

A PI emails: “Wei Zhang, the systems person — sketch a brief before the visiting-talk coffee.” University directories are full of Wei Zhangs. Two of them can share a campus and a first-page search hit.

Card A — associate professor, computer science, distributed systems. A lab page with a photo, a recent systems paper, a middle initial on the PDF. Card B — associate professor, materials science, same university system, a different college site, papers on battery systems. Searching “Wei Zhang systems” hits both. The word “systems” is not a confirm.

Confirm from the paper title the PI already used, or from the lab URL, not from the surname plus the campus. If the PI did not give a paper, ask for one sentence of the talk topic before you write. The brief, once confirmed, is: current appointment as of the lab page (dated), paper title and year, one claim from the PDF you opened. Leave the other Wei’s citations off. Academic homonyms are a third collision class — not the industry talk (Alex) and not the conference badge (Maria).

What belongs on the page

A brief is a document you would still send yourself on the morning of the call. It is not a biography and it is not a credit file. If a line would not survive “can I open the URL?”, it does not belong.

Keep

• Full name as it appears on the confirmed public pages, plus a middle initial if that is how collisions die.
• Current role and employer, dated, from a company page, speaker bio, or other open page — not from a directory that does not show its source.
• Prior roles only when a public page states them (About, LinkedIn-public, author bio). Mark them as stated, not as verified employment history.
• Talks, podcasts, papers, and posts you opened. Title, venue, year, one quote max.
• Public code, public writing, public filings that are clearly the same person.
• Press that names the same employer or a unique artifact. Discard the rest.

Leave off

• Phones, personal emails, and home addresses pulled from people directories.
• Family members, age guesses, and “possible relatives.”
• Anything that would change a hire, lease, credit, or insurance decision.
• Inferences (“seems unhappy,” “likely fundraising”) that are not on a page.
• Pay, immigration status, health, or other attributes you do not have from the subject in a professional setting.

Thin beats invented. A twelve-line brief with four URLs is a better professional object than a three-page dossier that silently merged two people. If you are embarrassed by how short the page is, you are using it correctly.

Public web only

“Public web” means a page you can open without impersonating someone, bypassing a login, or buying a consumer file. Company team pages. Talk pages and slide decks. Bylines. Public social and developer profiles. Press. Court or government pages that are already public and clearly about this person — used as context, never as a screen.

It does not mean scraped inboxes, leaked databases, or a forwarded background check. If you cannot hand the URL to counsel, the sentence does not belong. Dates matter more than tone: a 2019 speaker bio is not a current role. When two public pages disagree, write both with dates.

When the web is quiet

Some people barely exist online. Operators at quiet companies, researchers who publish under a lab name, people who share a name with a much louder person. A quiet result is a result. It is not a prompt to buy a dossier.

First, add a breadcrumb you skipped: company, city, title, event. Search the company team page directly. Search the event program. Search a publication’s staff page. If those are empty, write “public web is quiet as of [date]” and go to the meeting with questions instead of facts. Questions are honest. Invented facts are not.

Do not “complete” a quiet page with directory filler so it looks like the loud pages you are used to. That is how quiet people get a wrong address and a wrong age attached to their name in your notes. The quiet-web guide is the stop line, not a consolation prize.

Not a consumer report

OneSearch is not a consumer reporting agency. It is not FCRA-compliant. It must not be used to decide employment, tenant, credit, or insurance eligibility. A sourced brief is conversation prep: what to ask, what to cite, what tone fits. The moment the same paragraph would be used like a background check — “we passed because the brief was clean,” “we declined because of a public post we found here” — you are in the wrong product. Use a CRA and your counsel’s process. The label on the tab does not save you. Read FCRA and legal use and people search is not a background check. The statute itself is on the FTC Fair Credit Reporting Act page. This site is not legal advice.

A method you can run by hand

If you do not want a product, use twelve minutes and a notes file. The order matters more than the tools.

1. Write the ticket in one line: name, breadcrumbs you already have, the decision this brief is not allowed to make.
2. Search name + strongest breadcrumb (usually company or event), not the name alone.
3. List candidate cards. Each card needs role/company, place or org, and one unique artifact. If you cannot fill those three, the card is not a card.
4. Confirm one card or stop. Never merge.
5. Open sources in a stack: company or team page, talks and bylines, public social or code, then press. Write only what you opened.
6. Date every claim. When pages disagree, keep both lines.
7. Ask two follow-up questions you will actually use in the room. If you cannot name them, you do not need more sources — you need a better ticket.

That is the same sequence OneSearch runs, with confirm as a hard gate. The product compresses the tab pile and keeps follow-ups on the same page. It does not waive the gate, and it does not fill silence.

Follow-ups stay attached

After the brief exists, the next questions should hit the same person and the same sources. “What did they say about latency in that talk?” “Is the team-page title newer than the speaker bio?” “Who did they publish with?” A new Google tab for each question is how Card B sneaks back in.

OneSearch keeps the thread on the confirmed brief. By hand: one notes file per confirmed person, confirmation artifact at the top. Reopen that file in the morning. Do not re-search the bare name at 8:55 a.m. and pick a new card under time pressure.

When to use something else

Use Google when you already have the URL shape — a talk title, a docket number, a paper. Use LinkedIn when the job is a conversation or a mutual. Use an Apollo-class tool when the job is a contact and a sequence. Use a directory only if you understand you are buying consumer attributes, not a research brief. Use a CRA when the decision is regulated.

Use a sourced people search when the job is: confirm this name, walk in briefed, keep citations, stay off the eligibility line. Same gate for recruiting, founders, sales, and research — different questions on the page. Sequence without the copy: how it works.