How to Research Someone Publicly Without Using Their Email

Free public profiles show role history, tenure, mutual connections, recent posts, and engagement. Sort posts by "Recent" — that's the single best window into what someone is thinking about right now.

Pay attention to: the last role change (timing tells you onboarding pressure or budget cycle), the company's growth posts (hiring waves signal pain), and which posts they engage with (their influences).

Job posts reveal hiring priorities and pain points faster than any sales-intel database. The "About" page names decision makers. The blog telegraphs strategy. Read the last three blog posts and the three most recent job openings before any outbound.

Funding rounds, board members, and 10-K disclosures tell you budget, priorities, and timing. A Series B six months ago means hiring spend and tooling spend now. A 10-K's "risk factors" section reads like a sales-pitch outline written by the prospect themselves.

Public commits show what stack a person uses, what they care about, how active they are, and which open-source maintainers they collaborate with. Reference a specific pull request in your opener — instant credibility, near-zero competition.

Search "[name] podcast" — most leaders have at least one episode where they explain their worldview in their own words. Transcripts are gold for personalization because they reveal the exact phrases the person uses when not on script.

Recent news = recent context. A funding round, leadership change, product launch, or acquisition is the most reply-worthy opener of any. Set up a Google Alert for the prospect's name and company before reaching out.

For technical or thought-leader prospects, their writing is the fastest path to genuine relevance. A two-sentence reaction to their latest Substack post beats any "circling back" template ever written.

A warm intro converts 10–20× better than cold. LinkedIn's "mutual connections" view, plus checking who's commenting on their posts, surfaces the easiest path in. A 90-second voice memo to a mutual contact almost always outperforms a 200-word cold email.

Anonymous reviews from current and former employees reveal what's actually breaking inside the company — turnover, comp gaps, tooling complaints. Use sparingly and never quote directly; use it to inform your hypothesis.

If the company publishes any code on GitHub, the README, issues, and contributor list expose their internal architecture, hiring brand, and engineering culture better than any "About" page.

SpeakerDeck, Slideshare, conference recordings on YouTube. People reuse decks across talks — the same narrative shows up everywhere. Reference a deck slide and you've done what 99% of senders never do.

archive.org snapshots show how the company's positioning, pricing, and product have changed over time. A "we used to focus on X, now you focus on Y" observation is unusually disarming.

You don't need all twelve sources for every prospect. The winning pattern: pick one recent signal (news, post, podcast, hire) plus one structural signal (funding, stack, headcount) and weave them into a single sentence in your opener. Two signals always beats one; four is overkill.