Named-account research for sales teams
Named-account research begins with a company your team already cares about. The job is to build a dated, source-backed view of the business, explain which current changes matter to your sales thesis, identify people worth investigating, and record what remains unknown. The result should guide a next step without pretending public evidence reveals the full buying process.
When the account is known but the reading is missing
A target-account list can tell a team where it wants to sell. It cannot tell a rep what is happening inside each company, whether the original thesis is still sound, or which person is relevant now.
That gap is especially costly in strategic sales. Generic company summaries and copied profile fields do not prepare a seller for an account-specific decision. The work requires a reading: what the company appears to be changing, why that change bears on the problem you solve, who may be involved, what evidence supports the conclusion, and what question should come next.
Named-account research is useful when:
- the company is already part of a territory, target list, or active opportunity;
- the sale requires more depth than a database record can provide;
- multiple people or functions could be involved;
- the research must be checked by an account owner or manager;
- the account view needs to stay useful beyond a single meeting.
What should an account brief contain?
A practical brief is compact enough to use and specific enough to challenge.
Account thesis
Explain why the company belongs in scope and which conditions would make it relevant now. Include the team's requirements and exclusions, not only a general company description.
Current company view
Summarize what the company does only to the extent needed for the decision. Add the operating context, changes, or constraints that bear on the team's thesis.
Material observations
List the most decision-relevant public observations with their event dates and sources. Separate original sources from articles or posts that merely repeat the same announcement.
Interpretation
Explain why each observation strengthens, weakens, or leaves the thesis unchanged. This is an inference, so make the logic visible.
Relevant people
Identify people whose public roles, responsibilities, or activity make them relevant to investigate. Do not label the result a complete buying committee unless the company has confirmed it.
What remains uncertain and disconfirming evidence
Name what the research cannot establish: internal ownership, budget, timeline, project status, current vendor commitments, or private priorities. Include facts that lower confidence.
Next move and review date
Recommend the next question or action, record who reviewed the brief, and show when the account should be revisited.
How to research a named account
1. Start with the domain and a research focus
Use the company domain to resolve the correct entity. Then state the decision the research must support. “Tell me about this company” produces a broad summary; “Assess whether expansion in this function creates a relevant operating problem, and identify the leaders closest to it” creates a usable brief.
2. Define the team's account thesis
Write the company conditions, problems, people, triggers, and exclusions that matter. Include what would cause the team to lower the account's priority. A thesis that cannot be disproven is not a useful research standard.
3. Collect evidence with dates
Review company-controlled sources, public announcements, job postings, relevant professional activity, and other inspectable records. For every observation, preserve:
- the source URL;
- the subject it concerns;
- the date of the event, when known;
- the date the source was checked;
- whether the source is original or derivative.
Do not use source count as a substitute for coverage or quality.
4. Build the company reading
Group facts by the questions they answer, not by the tabs where they were found. Explain what appears to be changing, how it bears on the account thesis, and what alternative explanation could also fit.
5. Map relevant people
Look for people connected to the problem, the affected workflow, executive sponsorship, implementation, or day-to-day use. Role titles are a starting point. Current responsibilities and public evidence determine whether a person is worth investigating.
For each person, record:
- why the role may matter;
- the evidence connecting the person to the thesis;
- the date and source;
- what remains unknown about influence or ownership;
- the next question that would validate the hypothesis.
6. Review the judgment
Let the account owner inspect the original evidence and correct what the research cannot know. Accept, reject, revise, or defer the brief. Preserve that decision so the next update starts from the team's actual view.
A reusable named-account checklist
Identity and scope
- Correct company entity and domain
- Research question stated in one sentence
- Team criteria and exclusions recorded
- Account thesis can be proven wrong
Company evidence
- Material observations have sources and dates
- Original sources are distinguished from repetition
- Current changes are separated from static company facts
- Disconfirming facts are included
- Research has a visible as-of date
People map
- Relevant people are tied to roles or evidence, not title guesses alone
- Identity matches are checked
- Influence, authority, and project membership remain unknown unless validated
- No “complete buying committee” claim is made from public data
Decision
- Observation and inference are visibly separate
- The next move is proportionate to the evidence
- A reviewer can inspect and revise the result
- The next review date or reopening condition is recorded
A hypothetical named-account brief
The following example demonstrates the structure; it is not a customer result.
Research focus: determine whether a logistics-software company is standardizing a workflow that the seller's product supports, and identify the people closest to that effort.
Observed: the company published two roles connected to the workflow, and an operations leader publicly described inconsistency across regional teams. The original sources show dates and responsibilities.
Inferred: standardization appears to be an active operating concern. The operations leader and the executive responsible for the function are reasonable people to research further.
Still unconfirmed: public evidence does not show whether a software project exists, who controls budget, whether an incumbent vendor is involved, or whether the company intends to solve the issue through hiring alone.
Disconfirming check: an older announcement describes an existing transformation program. The account owner should determine whether that program already addresses the problem before raising priority.
Next move: verify the current program, inspect the job descriptions, and prepare a question about how the company is standardizing the workflow. Keep the account in review until the conflict is resolved.
The brief helps the seller learn. It does not manufacture certainty.
How do you keep account research fresh?
Show both the event date and the research as-of date. Recheck facts according to how quickly they can change. A person's role or public activity may need review sooner than a durable company description.
When new evidence appears, compare it with the previous thesis:
- Did the observation strengthen the reason?
- Did it weaken or contradict the reason?
- Did the relevant people change?
- Did a source expire or become unavailable?
- Does the next move still follow?
Continuous account research is a maintained judgment, not an endless stream of alerts. Read the practical guide to continuous account research.
How Lumnis supports named-account research
Lumnis Account Intelligence starts with a company your team already cares about. Enter the domain, choose a research focus, and create a dated company report. Lumnis can also surface people who may be relevant to a possible purchase, with public evidence available for review.
The output is not a guaranteed map of an internal buying committee. It is a source-backed account view and a set of people hypotheses that a seller can inspect, correct, and act on proportionately.
Use People Intelligence when the company is not known and the search begins with a description of the people and organizations you want to find.
Named-account research questions
What is the difference between account research and account planning?
Account research establishes the evidence and current reading: what is happening, why it may matter, who appears relevant, and what remains unknown. Account planning uses that reading to coordinate goals, relationships, activity, and strategy. Research should inform the plan without pretending to replace account-owner knowledge.
Can named-account research identify the buying committee?
It can identify people whose public roles and evidence make them reasonable stakeholders to investigate. It cannot reliably prove private influence, decision rights, budget ownership, or current project membership without validation from the account.
How much research is enough?
Stop when the evidence is sufficient for the decision at hand and the important uncertainty is explicit. Early prioritization may need a compact thesis and a few strong sources. A consequential executive meeting may justify deeper research. More pages do not automatically create a better judgment.
Should sellers research every account at the same depth?
No. Match depth to account value, uncertainty, decision stage, and seller capacity. Use a lighter first pass to decide which accounts deserve deeper work, then preserve the research so it does not need to be rebuilt.
Start with the company you care about
Create a dated account view, inspect the sources, and identify the people worth investigating—without turning public evidence into a private-intent claim.