A research dossier for a target company is an organized report that brings together evidence about a business. It should cover company identity, ownership, products, finances, leadership, competitors, technology, risks, and sources. The purpose is to help someone answer a specific business question using information they can check.
“Target company” means the business you are researching. It does not automatically refer to Target Corporation, the US retailer. You might prepare a dossier before choosing a software vendor, approaching a potential client, considering a partnership, or researching an employer.
A useful dossier also records what remains unknown. That makes it easier to decide which questions need answers before the next meeting or commitment.
Define the Decision Before Collecting Information
Start with one sentence explaining why you need the research. For example: “We need to decide whether this software provider belongs on our vendor shortlist.”
That question determines the depth of each section. A vendor review may require data-handling details and service terms. A sales brief may focus on business priorities, decision-makers, and recent changes. An investment review needs deeper financial analysis and professional judgment.
Also set a research cutoff date and name the intended reader. These small details prevent confusion when someone opens the report months later.
Keep the scope realistic. A public-web dossier can support initial screening, but a major transaction may require confidential records and specialist due diligence.
What to Include in a Research Dossier for Target Company
Use the following sections as a working structure. Expand the areas that affect your decision, and shorten those that add little.
Company Identity and Ownership
Record the legal name, trading names, official website, headquarters, and main operating locations. Where available, add the registration jurisdiction, entity number, parent company, and relevant subsidiaries.
Check that each record belongs to the correct business. Similar names, old websites, and acquired brands can lead researchers to combine unrelated information.
For US businesses, look for the relevant state business registry. Record exactly what its entry establishes. Do not treat a registration record as proof of financial strength, service quality, or regulatory approval.
Separate the brand selling a product from the legal entity that would sign your contract.
Products, Customers, and Revenue Model
Explain what the company sells, who buys it, and how it earns money. Keep this description concrete: subscription software, project fees, product sales, licensing, or another documented model.
For a technology company, identify its main products and the business problems they address. Distinguish features that customers can use now from announcements or future plans.
Capture pricing terms when they matter, including billing periods, usage limits, setup charges, and cancellation conditions. RoyalMagz’s discussion of backtofrontshow pricing offers related reading on examining software plans; confirm any figures against the provider’s current terms before using them.
Treat customer logos carefully. A logo alone does not establish contract size, length, or the customer’s present relationship with the company.
Financial Performance and Funding
Include available revenue, profit or loss, cash flow, cash balances, debt, and funding information. Attach a reporting period, currency, and source to every figure.
The SEC’s explanation of Form 10-K identifies business information, risk disclosures, management discussion, and audited financial statements as useful parts of an annual filing. These sections give researchers a starting point for companies that file the form.
Compare equivalent periods and measures. Annual revenue should not sit beside quarterly revenue without a clear label. Likewise, a funding announcement does not tell you how much cash remains.
If a private company does not disclose financial statements, say so. Identify database estimates as estimates and explain their limits. Avoid filling gaps with unsupported numbers.
Leadership and Operational Capacity
Identify the executives and business contacts relevant to your objective. Record their current roles and the sources supporting them, rather than collecting unrelated personal details.
Then examine how the business operates. Depending on the company, this could include staffing, support coverage, delivery locations, manufacturing partners, or dependence on outside providers.
A hiring advertisement can suggest an area of investment, but it does not prove the company already has that capability. Similarly, an old executive biography may no longer reflect the current leadership team.
Turn these observations into questions for follow-up. When reviewing several providers, an online form builder can help you collect answers to the same vendor questionnaire, making responses easier to compare. If the provider advertises round-the-clock support, ask which channels, response times, and contract terms apply.
Market Position and Competitors
Choose competitors that serve similar customers or solve the same problem. Explain why each comparison belongs in the dossier.
A useful comparison might cover target customers, product scope, published prices, distribution, or switching costs. Apply the same criteria across the companies you compare.
Avoid unsupported claims such as “market leader.” If a source gives market share, record the market definition, geography, measurement period, and method.
Financial news can help identify developments worth checking. RoyalMagz’s review of fintechzoom.com provides context on financial-media coverage and its limits. Trace consequential claims back to company disclosures or other original evidence.
Technology, Security, and Data Handling
For a software or technology supplier, document the capabilities your team actually needs. These may include supported integrations, access controls, data export, backups, and service availability commitments.
Also ask what information the provider stores, which outside services it relies on, and what happens to your data when the contract ends.
NIST’s supplier due diligence guide addresses technology supply-chain assessment through areas including ownership, provenance, resilience, cyber practices, and supplier tiers. Provenance means where a product or component comes from.
Use that perspective to guide questions rather than award an automatic security score. For example, request relevant assurance documents and check their scope, date, and issuing organization.
A security badge or a short website statement should lead to supporting evidence. It cannot answer every question about a supplier’s practices.
Risks, Disputes, and Open Questions
Record risks that could change the decision, including customer concentration, reliance on one supplier, unclear ownership, product discontinuation, or unresolved service issues.
For each concern, explain the evidence, possible consequence, and next verification step. Distinguish a documented event from a possible exposure.
Handle legal matters precisely. Identify the correct entity, source, date, and current status. An allegation is not a finding, and a settlement may not include an admission of wrongdoing.
Avoid presenting the absence of search results as proof that no problems exist. “No relevant result found in the sources checked” describes the research honestly.
Build a Source Log Alongside the Report
A source log connects each important claim to the evidence behind it. Build it while researching, so you do not have to reconstruct your work later.
A spreadsheet can hold the following fields:
| Field | What to record |
|---|---|
| Claim | The specific statement or figure |
| Source | Document title, publisher, and URL or file reference |
| Relevant period | When the information applies |
| Date checked | When you accessed or reviewed it |
| Evidence status | Documented fact, company claim, estimate, or analysis |
| Limitation | Missing context, conflicting evidence, or follow-up needed |
Use precise references. A filing page number or named document section helps another person check a claim faster than a homepage link.
Also separate a source’s authenticity from its independence. A company announcement may reliably show what management announced without independently proving the expected outcome.
If two sources disagree, retain the disagreement until you understand it. Different reporting dates, definitions, currencies, or corporate entities may explain the difference.
Turn Evidence Into a Useful Executive Summary
Write the executive summary after completing the research. Keep it focused on the decision named at the start.
Include the company’s identity, the strongest relevant findings, the main concerns, and the unresolved questions. Finish with a practical next step, such as requesting documents or scheduling a technical review.
Use explicit labels where needed:
- Documented fact: A dated record supports the statement.
- Company claim: The company states something that needs further support.
- Analysis: You explain what the evidence may mean.
- Unknown: Available sources do not resolve the question.
For example, a vendor’s documentation might describe data export. Your analysis could note that export may help with a future move. Whether it preserves every field remains unknown until checked.
This separation lets readers challenge an interpretation without losing sight of the underlying facts.
A Worked Example: Reviewing a Software Provider
Consider a hypothetical business choosing a customer-support platform. Its research question is whether the provider can meet operational needs before a contract discussion.
The dossier records the provider’s legal identity, product documentation, published plan terms, and available security material. It also lists unanswered questions about importing historical tickets and exporting attachments.
Suppose the pricing page quotes a per-user monthly fee. Before estimating total cost, the researcher checks minimum seats, annual billing conditions, storage limits, and paid add-ons.
The report should distinguish three outcomes:
| Finding | Meaning for the review | Next action |
|---|---|---|
| Documentation describes an integration | The provider claims support for a needed connection | Confirm the required functions and plan |
| Contract terms are unavailable publicly | Cancellation obligations remain unclear | Request the proposed agreement |
| Export instructions omit attachments | The available material does not resolve portability | Ask for a demonstration or written clarification |
These are illustrative findings, not claims about a real provider. They show how a dossier can move from collected information to specific questions.
The next step is a focused discussion with the vendor, supported by a record of what still needs checking.
Keep the Dossier Current and Easy to Review
Put a version date, research cutoff, and responsible reviewer near the beginning. Add a short change log when you revise important findings.
Choose update triggers that match the decision. A new financial filing, ownership change, product retirement, or contract revision may justify another review. Recheck prices and service terms before relying on them.
Keep confidential documents separate from material intended for wider circulation. Give colleagues access according to their role and the permissions attached to each source.
Before sharing the dossier, ask someone to trace a few important conclusions back to their evidence. If they cannot follow the path, improve the references or narrow the claim.
Start with the decision, document the facts that matter, and make the unanswered questions visible. A dossier is ready for use when the reader can see what is known, what needs checking, and what to do next.