OneSearch vs LinkedIn — different jobs

Recruiters, founders, and operators collapse two questions into one click: “Who is this?” and “How do I reach them on LinkedIn?” Those are different jobs. LinkedIn wins the second one completely — messaging, the graph, InMail, Recruiter projects, Sales Navigator, the thread that already lives there. OneSearch does not send InMail, does not show mutuals, and does not keep you inside LinkedIn. If the work is a conversation on that network, start on LinkedIn. Official product help is LinkedIn Help. This page will say that in every section that needs it.

OneSearch wins a narrower job: you have a name, you must confirm the right person, and you want one sourced page built from the public web — company sites, talks, bylines, public social and code, press — without notifying them. That is people search, not a dossier and not a contact waterfall. Read the table, then the cases where LinkedIn is the correct tool.

Side by side

Which tool is this hour?

If the outcome is “send the note” or “see who we both know,” the picker should send you to LinkedIn. If the outcome is “walk in briefed,” it should send you to a sourced page. If the outcome is eligibility, it should send you to a CRA — not either of these products.

When LinkedIn wins

LinkedIn wins whenever the work has to happen on LinkedIn. That is not a slogan. It is a constraint of how recruiting, business development, and a lot of sales actually run. OneSearch cannot close those loops.

Messaging and InMail

If you need to write to Alex Chen on the platform, LinkedIn is the product. InMail, open profiles, connection notes, and Recruiter InMail credits live there. A sourced brief can make the first sentence specific — a talk, a repo, a byline — but it will not deliver the message. Do not open OneSearch hoping it grew an inbox. It did not.

The graph

Mutuals, shared groups, “how you are connected,” and the path through a colleague are LinkedIn objects. Founders asking “does anyone on the team know Maria Garcia?” should stay on LinkedIn or in their own CRM, not in a public-web brief. OneSearch does not map your network. It does not see your connections. It will not tell you that your series A lead already knows the person.

Staying inside LinkedIn

Some workflows are native to the site: a Recruiter project, a Sales Navigator list, a hiring-manager comment on a profile, a conversation that already has six messages. Pulling that work into another tool just to feel “researched” is waste. Stay. Use the brief only when you need sources that are not on that one About section — or when you cannot afford a profile view yet.

Slate search, not a name

Boolean strings, title filters, and “people at this company with this skill” are LinkedIn (or LinkedIn-adjacent) jobs. OneSearch starts from a name you already have. If you do not have a name yet, you are sourcing, not briefing. Source on LinkedIn. Brief later.

Recruiter, Sales Navigator, and the free profile

These are still LinkedIn. Recruiter is a slate and InMail machine. Sales Navigator is a territory and account machine. The free profile is how most first conversations still start. OneSearch does not unlock Open Profile, does not share InMail credits, and does not replace a seat your team already pays for. If your complaint is “I cannot see the full profile without Premium,” that is a LinkedIn packaging problem. A public-web brief may surface a talk or a team page the locked profile hid; it will not reconstruct their connection count or their Featured carousel.

The person only exists there, and the next step is a connect

Plenty of operators have a public LinkedIn and almost nothing else. If your next action is still “connect” or “InMail,” LinkedIn remains the right surface even if a brief would come back thin. A thin OneSearch page is honest; it is not a messaging client.

When OneSearch wins

OneSearch wins when the output you need is a brief, not a thread. Confirm first. Public pages only. Citations attached. They are not notified. That is the whole product. See how it works.

Confirm before you write

Common names collide. LinkedIn search returns a stack of Alex Chens. People click the first card that looks close, then write a message to the wrong engineer. OneSearch treats confirm as a gate: no brief until you pick a card. The method is confirm the right person and common-name collisions. You can do this manually on LinkedIn too — the point is that a brief product that skips confirm is dangerous, and we do not skip it.

Sources that are not the LinkedIn About section

A LinkedIn profile is one artifact. The public web is several: a company team page that still lists them, a conference talk, a podcast, a GitHub org, a journal byline, a local news quote. Recruiters who only read LinkedIn miss the talk that would have made the InMail specific. Founders who only read LinkedIn miss the interview where the investor already stated a thesis. The brief’s job is to put those open pages on one document. It will not invent a talk that is not there.

Private lookup

LinkedIn often notifies. Profile views, InMail, and connection requests change the relationship before you are ready. OneSearch does not send the subject an alert. That matters for passive candidates and for discreet partner research. It does not make the research a secret police file. It means the first time they hear from you can still be the moment you choose.

Follow-ups on one page

After confirm, you ask against the same sources: last role, recent talks, who they published with. You do not open a second Google tab and lose the thread. That is the “twelve tabs versus one page” problem, covered in OneSearch vs Google. LinkedIn chat is a conversation with the person. OneSearch chat is a conversation with the brief.

Worked example: Alex Chen, twenty minutes before outreach

You are a recruiter. A hiring manager said “talk to Alex Chen, the backend person who presented at that Rust meetup.” You do not have a URL. LinkedIn search for Alex Chen plus Rust still returns multiple people — one in Berlin, one in Austin, one who left the industry. If you InMail the Austin card because the photo looked right, you have burned a credit and notified the wrong person.

The LinkedIn-winning move, if you already have the exact profile open and the next action is InMail: stay on LinkedIn. Write the note. Use Recruiter if that is your seat. Do not detour.

The brief-winning move, if you only have the name and the meetup breadcrumb: confirm first. Add company or city if you have it. Pick the card that matches the talk, not the first handsome headshot. Read the sourced page. Open the meetup link. Then — and this is the honest split — go back to LinkedIn to send the message. OneSearch does not replace that last step. Recruiting detail lives on people search for recruiting.

If the hiring manager actually wants you to decide whether Alex is eligible to hire based on a compilation of web hits, that is not a LinkedIn job and not a OneSearch job. That is a regulated screen. Stop. Read people search is not a background check.

Worked example: Jordan Okonkwo, messaging vs a brief

Slack: “Jordan Okonkwo — backend, used to be at the marketplace company, wrote about queueing. Might chat.” Marketplace alumni are a collision set. There is a Jordan Okonkwo who shipped consumer-marketplace infra and posted an engineering-blog piece on delayed jobs. There is another Jordan Okonkwo who is a product manager at a different company and writes essays about “the marketplace opportunity.” LinkedIn search for the name plus marketplace still returns both. If you InMail the PM because the headline was louder, you have burned a credit and notified the wrong person.

The LinkedIn-winning move, if you already have the engineer’s exact profile open and the next action is InMail: stay on LinkedIn. Write the note. Quote the queueing post if you opened it. Do not detour through a brief to feel researched. Messaging is the job.

The brief-winning move, if you only have the name and “the queueing piece”: confirm first. Pick the card that matches the delayed-jobs byline, not the first marketplace essay. Read the sourced page. Then go back to LinkedIn to send the message. OneSearch does not replace that last step. The graph and the InMail live on the network. Same split as Alex Chen before outreach and Maria Garcia when someone asks who on the team already knows her.

If someone wants you to decide whether either Jordan is eligible to hire from a LinkedIn scrape plus a directory address, that is not a LinkedIn job and not a OneSearch job. That is a regulated screen. Stop.

What each surface actually contains

A LinkedIn profile, when you can see it, is a self-authored document: headline, About, Experience, Featured, recommendations, activity. It is excellent for how they want to be reached professionally. It is weak on anything they did not post — a conference talk hosted elsewhere, a company team page that still lists them, a repo, a journal byline, a local interview. Those live on the public web. That is why a brief can complement a profile you already have open.

A OneSearch brief is not a second LinkedIn. It will not show “open to work,” mutuals, or the last six posts in the feed. If the only public artifact is the LinkedIn itself, the brief may cite that page and stay short. That is correct. Do not expect us to scrape a login wall to fatten the About section. Do not expect LinkedIn to cite a PDF they never uploaded.

Locked-down profiles are a common reason people bounce to directories. A missing mobile number is not a reason to buy a household report. If you cannot see the profile and you cannot confirm the person from other open pages, you do not yet have a brief or a message — you have a collision. Stay in confirm. Common-name collisions is the method when two cards still fit.

Who gets notified

LinkedIn’s social features are the product. Views, follows, InMails, and connection requests are designed to be seen. Privacy settings change the details; they do not change the default. Plan for “they might know you looked.”

OneSearch lookups are private to your account. The subject is not emailed, not shown a “someone researched you” card, and not added to a public view list. History is so you can reopen the brief the morning of the call. See privacy for data handling. Private is not the same as “use this to stalk.” Acceptable use still applies; terms and FCRA and legal use are the lines.

Using both in one hour

A clean split for a first conversation — recruiting, founder, or sales — looks like this. None of these steps require celebrity names. Alex Chen, Maria Garcia, and Jordan Okonkwo are enough.

1. Write down the name and the one breadcrumb you already have (company, city, talk, repo).
2. If you do not have a unique LinkedIn URL, confirm the person on a brief or with a disciplined Google pass. Do not merge two cards. Method: confirm the right person.
3. Read public artifacts you would actually cite in a room. If OneSearch is thin, believe the thinness. When the public web is quiet is the stop, not a prompt to invent.
4. Switch to LinkedIn for the graph and the message. Quote a public talk, not a guess about their personality. Write a first-call brief if the meeting is already booked and the note is not the job.
5. Do not paste the brief into an ATS as if it were a background check. Do not ask OneSearch for emails. If you need emails and a sequence, that is Apollo’s job, not ours.

Founders doing partner or investor prep use the same hour without the InMail step: brief, then walk in. That page is people research for founders. Salespeople who already have the meeting on the calendar should not open Recruiter to feel busy; they need pre-call people research, then LinkedIn only if the follow-up lives there.

Neither product is a background check

LinkedIn is a professional network. OneSearch is public-web research. Neither is a consumer reporting agency. Neither is FCRA-compliant screening. You must not use a LinkedIn scrape or a OneSearch brief to decide hire / no-hire, tenant, credit, or insurance eligibility as if it were a consumer report. If that is the decision, use a CRA and your counsel’s process. We are not your counsel. The trust page is FCRA and legal use. The method page is people search is not a background check.

A practical test: if you would have to send an adverse-action letter after using the document, you are in the wrong product. Close the brief. Close the LinkedIn tab. Open the vendor your HR team already contracted.

Cost, time, and what you are paying for

LinkedIn’s free tier is enough for many messages. Recruiter and Sales Navigator are priced for list work and InMail volume. You are paying to stay in the graph. That is rational when messaging is the job.

OneSearch is priced as a research desk — weekly, monthly, quarterly, yearly on pricing — because the job is a handful of confirmed briefs, not a ten-thousand-person extract. If you run eight manual LinkedIn-plus-Google tab piles a week, the time cost is the hidden invoice. Sibling compare: pages vs a brief. Directory compare, if someone on your team is shopping Spokeo-class reports instead: OneSearch vs people directories.

What OneSearch will not become at any price: an InMail client, an email waterfall, a consumer-report stand-in, or a way to browse someone who opted out. Opt out is public. About states the same limits without a comparison table.

If you came here hoping one product would replace the other, keep LinkedIn for the conversation and use a sourced brief only when the name is unconfirmed or the public web has more than one profile can hold. That is the honest split. The cluster index is how OneSearch compares.