Company Research Before Asking for a Referral: The 15-Minute Checklist

Most referral requests fail before they're sent. The person asking hasn't read the job description carefully. They can't explain why this specific company interests them. They don't know the hiring manager's name. The message they send is interchangeable with one they could send to any company, and the recipient can tell.

The fix takes 15 minutes. Fifteen minutes of focused research transforms a generic "hey, can you refer me?" into a specific, compelling request that your connection can forward directly to the hiring manager. This guide walks through exactly what to research, where to find it, and how to use it in your outreach.

Why research changes the referral equation

When someone refers you, they're spending social capital. They're attaching their name to yours inside their company. If you seem unprepared, you make them look bad. If you seem informed and genuinely interested, you make them look like they have good taste in people.

Think about it from the referrer's perspective. They receive two messages on the same day:

Message A: "Hey, I saw your company has some openings. Would you be able to refer me? I've attached my resume."

Message B: "Hey, I noticed the Senior Product Manager role on the Growth team. I've been following your product-led expansion into SMB since the Series C announcement, and the problems they're solving around activation rates are close to what I did at Amplitude. Would you be open to forwarding my resume to the hiring manager?"

Message B took 15 minutes more to write. It gets forwarded. Message A gets a polite non-response.

The difference isn't writing skill. It's preparation. Message B contains signals that the sender has done real work: they know the specific role, the team, the company's strategy, and how their experience maps to the problem. That preparation gives the referrer confidence and gives the hiring manager a reason to pay attention.

The 15-minute research checklist

Here's the exact sequence. Do this for every company before you send a referral request. It'll feel slow at first. After five or six repetitions, you'll knock it out in 10 minutes.

Minutes 1-3: Read the actual job description

This sounds obvious. Most people skim. Don't skim. Read it word by word. You're looking for three things:

• The core problem the role exists to solve. Every job description, buried under boilerplate requirements, describes a problem. "Drive expansion revenue in our mid-market segment" or "Reduce time-to-value for enterprise onboarding." Find that sentence. It tells you what the hiring manager cares about most.
• Required vs. preferred qualifications. Required qualifications are table stakes. Preferred qualifications reveal what the ideal candidate looks like. If "experience with product-led growth motions" is preferred, the team is either building or scaling a PLG motion. That's intelligence you can use.
• Reporting structure. Who does this role report to? If the listing says "reports to VP of Revenue Operations," you now know the hiring manager's title and can look them up. If it says "reports to the CEO," this is a company building the function for the first time.

Minutes 3-6: Company overview and recent news

Spend three minutes building a mental model of the company's current state. You don't need a thesis. You need enough context to sound informed.

Funding and stage. Check Crunchbase for the latest funding round, total raised, and investor names. A company that raised a $50M Series C six months ago is in growth mode. A bootstrapped company is optimizing for efficiency. These details shape how you position your experience.

Recent news. Google the company name and scan the first page of results. Look for product launches, acquisitions, layoffs, leadership changes, or market expansions from the last 90 days. If they just launched a new product line, the role you're targeting might be tied to that launch. If they recently did layoffs and are now hiring again, they're being selective about headcount.

Product and customers. Visit the company's website. Spend 60 seconds on the homepage and one customer case study. You should be able to describe what the company sells, who buys it, and roughly how the product works. If you can't do this after visiting the site, spend another minute on their "About" page.

Minutes 6-9: The hiring manager and team

This is where most candidates don't bother. That's precisely why it works when you do.

Find the hiring manager. The job description usually names the team or department. Go to LinkedIn, search for people at that company with VP or Director titles in that function. If the role reports to a VP of Marketing, search "[Company name] VP Marketing" on LinkedIn. In most cases, you'll find them in under a minute.

Review their profile. What's their background? Where did they come from? How long have they been in the role? If they joined six months ago, they're building their team. If they've been there four years, they have established processes and are looking for someone who can plug in. Either way, this shapes your positioning.

Check the team composition. Look at the company page on LinkedIn and filter by department. How big is the team? Is this a first hire or backfill? Are they distributed or co-located? A five-person team hiring their sixth member has different needs than a 50-person org adding headcount.

Minutes 9-12: Your connection to this company

Now map your experience to what you've learned. This isn't about writing a cover letter. It's about identifying two or three specific connections between your background and their situation.

• Problem overlap. "They're trying to scale enterprise onboarding. I reduced onboarding time by 40% at my last company."
• Domain overlap. "They sell to mid-market SaaS. I've spent six years selling to that exact segment."
• Stage overlap. "They're post-Series B, 120 employees, building their first revenue ops function. I built RevOps from zero at a similar-stage company."
• Tool or methodology overlap. "The JD mentions Salesforce CPQ and Clari. I've implemented both."

Write down two concrete overlap points. You'll use them in your referral request.

Minutes 12-15: Check your network

Before reaching out to any single connection, check how many paths you have into this company. Use LinkedIn's search operators to find everyone in your network who works there. Check first-degree connections, second-degree connections with strong mutual ties, and alumni.

If you have three first-degree connections at the company, reach out to the one closest to the hiring team. If you only have second-degree connections, ask the strongest mutual contact for an introduction. If you have no connections at all, look for alumni ties or weak ties with shared context.

This step also prevents an embarrassing situation: reaching out to a connection in engineering for a marketing role when you have another connection who sits on the marketing team.

How to use your research in the referral request

You've spent 15 minutes. Now compress what you learned into three sentences that demonstrate your preparation. You're not writing an essay. You're providing just enough signal to separate your request from every generic message in their inbox.

Reference the specific role and team

Name the job title and team. "The Senior PM role on the Growth team" is more compelling than "a product management role at your company." It shows you've identified the exact position and aren't mass-messaging everyone you know.

Show you understand their situation

One sentence that proves you've done homework. "I saw the Series C announcement and the push into mid-market. That expansion is similar to what I helped build at [previous company]." This tells the referrer two things: you understand what the company is doing, and you have relevant experience. Both make them more willing to forward your name.

Connect your experience to their problem

Map one of your overlap points to the role's core problem. "The JD emphasizes reducing time-to-value for enterprise customers. I cut onboarding time by 35% at Amplitude using a similar playbook." Specific. Measurable. Directly relevant. The referrer can paste this into a message to the hiring manager verbatim.

Example: Before and after

Before research:

After 15 minutes of research:

The second message took 15 minutes more to prepare. It gets the interview.

Research shortcuts for high-volume outreach

If you're targeting 15 to 20 companies, spending 15 minutes per company adds up to four to five hours. That's a reasonable investment for roles you care about. But there are ways to speed up the process once you've built the habit.

Build a company research template

Create a simple document or spreadsheet with fields for: company name, stage/funding, recent news, role title, team, hiring manager, core problem, your overlap points, and connections at the company. Fill this in for every target. The template turns unstructured browsing into focused research.

Batch similar companies

If you're targeting mid-market SaaS companies in your city, your research for company two builds on what you learned researching company one. The competitive landscape, common challenges, and industry context carry over. Your third company takes eight minutes instead of fifteen.

Use job alerts to front-load timing

Set up alerts on LinkedIn, Indeed, and any niche job boards for your target titles. When a new role drops, run the 15-minute checklist and send your outreach the same day. Speed matters. A role that hits the job board has already been circulating internally for days or weeks. Being one of the first external candidates through the referral channel puts you ahead of the wave.

What not to do

Don't over-research

Fifteen minutes is the target. If you're spending an hour per company, you're procrastinating. The goal is sufficient context to write a credible referral request, not a competitive analysis. You'll learn the rest during interviews.

Don't reference confidential information

If a connection told you something off the record about the company ("they're about to fire the VP of Sales"), don't reference it in your outreach. Keep your research to publicly available information. Demonstrating insider knowledge that shouldn't be public makes people uncomfortable, not impressed.

Don't make assumptions about the role

Your research gives you context, not certainty. "I noticed you're expanding into enterprise" is a safe observation. "I know you're struggling with enterprise deal cycles" is an assumption that might be wrong and comes across as presumptuous. Frame observations as observations, not diagnoses.

Don't mention competitor intelligence

Even if you have deep knowledge of their competitors from a previous role, save it for the interview. Leading with "I know your competitor's pricing strategy" raises ethical flags for the referrer. They don't want to be associated with someone who might bring IP issues.

The compounding return

Here's what happens when you do 15 minutes of research for every referral request: your hit rate doubles. Instead of sending 20 generic messages and getting two responses, you send 10 researched messages and get four to five responses. Each response is higher quality because the person you're talking to already has confidence in your preparation.

The hiring managers on the receiving end notice too. When a referrer forwards your message and it includes specific, relevant context about the team and role, you've already passed an informal screen. You've demonstrated the same preparation skills that separate strong employees from weak ones.

Fifteen minutes of research. That's the line between a referral request that gets forwarded and one that gets archived. Pick a company from your target list and time yourself. You'll be surprised how much intelligence you can gather before the clock runs out.

Frequently asked questions