What to Actually Research About a Company Before Applying
Most candidates research companies the wrong way. The three research layers — business problem, role challenge, competitive landscape — make your application impossible to ignore.
By Michael Robert · Co-founder
Every hiring manager has read the same cover letter a hundred times: it name-checks the company, quotes the mission statement, and says nothing a competitor's applicant couldn't have said just as easily. The candidates who get callbacks did something different before they opened a laptop. They found the business problem sitting underneath the pitch.
Why does the company research most candidates do not work?
Most candidates research companies the wrong way. They Google the company name, read the "About Us" page, and write something generic. Hiring managers read hundreds of applications like that.
The ones that land come from people who understand the company's actual business problem instead of its elevator pitch.
That kind of research shows in the writing, and an application that reads generic gets skimmed and discarded in seconds.
What are the three research layers, and what does each do?
There are three layers, and they build in order. Each one does separate work in your application, and skipping any single layer leaves a gap that a more prepared candidate will fill.
- What is the company trying to solve in the market? (Not "we make X product" — why does the market need X?)
- Who are the customers? What would success look like for them?
- What's the main competitive threat?
- Why are they hiring for this role right now?
- What's the biggest problem they expect this role to solve?
- What would a win look like in the first 90 days?
- Who are their main competitors?
- What are those competitors doing differently?
- Where is the company losing?
Doing all three layers by hand takes real time. Telosi's free Research Brief handles a version of layers one and two before you sit down to write anything. Layer three, the deeper competitive read, is a more advanced method we will cover in a separate piece.
What does three-layer research look like for a B2B payments startup?
Say you're applying for a product role at a hypothetical Stripe-adjacent B2B payments startup. Here's what each layer surfaces.
| Layer | What you find |
|---|---|
| 1. Business problem | SMBs spend 5-10 hours per month on invoice reconciliation, integrations are fragmented, the success metric is reducing SMB reconciliation time by 30%, and the main threat is embedded finance broadly — competitors like Ramp, Brex, and Intuit bundling lending and card products directly into the SMB workflow. |
| 2. Role's challenge | They just raised a Series B and are expanding beyond invoicing. The role's job is to build the integration layer that locks in SMB customers. The 90-day win is shipping integrations with the top five accounting platforms. |
| 3. Competitive landscape | Bill.com has grown by acquisition (Divvy, Invoice2go, Finmark), and Stripe leads with embedded financial infrastructure. In our view, neither has nailed the native SMB accountant UX yet, which leaves room to lead with "accounts-first" positioning instead of "payments-first." |
What this looks like in your cover letter
✓ "Your reconciliation numbers caught my eye, specifically the fact that you're staying integration-light instead of trying to become a full accounting suite. I built the invoice-matching logic at [previous company] that took our accounting-firm customers from six hours of manual reconciliation a week down to under forty minutes. I'd want to bring that same discipline, solve the narrow problem well before expanding the platform, to the integration layer you're building here."
💡 That kind of specificity sounds like something a real person actually noticed, and it gives the hiring manager a reason to keep reading instead of skimming ahead to the next resume.
Why does business-problem research beat credentials?
Hiring managers rarely care how well you can recite the company's elevator pitch. What they are actually checking for is whether you understand the business problem well enough to contribute quickly.
Layer 03 research is what separates "I want to work here" from "I could actually solve your problem."
Credentials get an application onto the pile worth a second look. What usually moves it off that pile and into a phone screen is whether the candidate seems to understand the business problem. In a pool where everyone already clears the bar on paper, the differentiator tends to be depth of context rather than length of resume.
The elevator pitch is not the business problem
The elevator pitch is what the company says about itself. The business problem is what the company is actually trying to solve in the market. Candidates who have memorized the pitch can usually recite the mission statement, but a lot of them cannot say which customer segment is churning or why. Hiring managers notice the gap quickly, sometimes within the first two sentences of a cover letter.
Private companies require triangulation
Private companies don't publish earnings calls, so triangulate instead: founder interviews on podcasts, customer case studies, funding announcement coverage, cross-functional job postings, and the product changelog all help. What a company actually ships tends to tell you more than what it says it cares about in an interview.
Two to three hours per application is a reasonable bar
This takes real time, which is why most candidates skip it. It is also one of the highest-leverage things you can do if you actually want the role, since almost none of your competition will bother.
What are some practical questions about the research?
Where do I find layer one research about a private company?
Private companies do not publish earnings calls, so you have to piece the picture together from other sources. Founder interviews on podcasts are often more revealing than anything on the company blog, partly because founders tend to relax once they are not being quoted for a press release. Customer case studies on the company's own site show which problems paying customers actually hired the company to solve. A recent funding announcement usually has a paragraph explaining what the new capital is for, and it is worth reading closely. Job postings across different functions are one of the more honest indicators of where a company is actually investing headcount. The product changelog or release notes round it out: what a company ships is usually a better guide to its real priorities than what it says in interviews.
How long does three-layer company research take?
Somewhere around two to three hours per application, if you do it properly. Layer one draws on earnings call transcripts if the company is public, or podcast interviews, customer testimonials, and founder posts if it is not, plus the product changelog and recent press coverage. Layer two means reading the job description closely, then checking the team page and recent hires in the same function. Layer three takes more digging: competitor websites, analyst reports where they exist, and an honest look at which company is actually winning which part of the market. All of it is real work, which is why most candidates skip it. It is also one of the few parts of a job search that is fully within your control, which counts for a lot when everything else about the process feels arbitrary.
What is the most common mistake in company research?
Confusing the elevator pitch with the business problem. The elevator pitch is what the company says about itself; the business problem is what the company is actually trying to solve in the market. Candidates who have the elevator pitch memorized can usually recite the mission statement on cue, but a lot of them cannot say which customer segment is churning or which competitor is taking share. Hiring managers pick up on that gap almost immediately, and it is a fast way to land in the reject pile with an otherwise decent resume. The fix is to spend your research time on the problem the company is solving for its customers, rather than the story it tells about itself.