Potential partners in Asia: choosing companies to approach and recording what remains unknown
Prepare a list of candidates in Korea, Japan or China by role and application, with sources, reasons for fit and open questions.
Article language: English

In this article
A spreadsheet with 100 rows does not necessarily contain 100 reasons to start a conversation. A list of potential partners in Korea, Japan or China should show fit, confirmed information and open questions. Begin with the role you need and the selection criteria. Gather names afterwards. Otherwise, it is easy to produce an impressive directory of organizations whose main common feature is that a search engine returned them for the same query.
“Potential partner” does not mean that a company has agreed to cooperate or that its assessment is complete. Preserve that distinction in file names and statuses. This exercise concerns preparing and accepting a list for further investigation. It does not replace the technical, commercial or legal assessment a particular project may require. The examples illustrate the method and do not describe real companies.
Name the role you need
A partner might be a customer, distributor, integrator, component supplier or a company with which to develop a solution. Each role calls for different criteria. A manufacturer using similar technology is not automatically a distributor ready to add your product to its range. A trading company may help build a channel even if it cannot meet the requirements of a project needing its own production facilities. Do not put all these tasks in one ranking.
Describe the intended role in two sentences: what the company would do and why it matters to the plan. The division of responsibilities is central when choosing between a distributor and direct sales in Asia. The guide to distribution models (in Polish) discusses this distinction. Use the same distinction when building your list. If you cannot explain the purpose of a conversation with a particular organization, the record remains a lead, not a ready recommendation to make contact.
Turn the project objective into inclusion criteria
Choose several criteria that can be checked or explicitly marked unknown. They might concern the application, type of customer served, technical capability, area of operation or way of working. Separate essential conditions from helpful features. An easy-to-read English website may make research easier, but it does not prove technical fit. Otherwise the list will reward the best-described companies instead of those that meet the need.
Test your definitions against a few profiles before collecting data at scale. If the criteria do not clearly distinguish a manufacturer from an intermediary, revise them. The guide to B2B market segmentation in East Asia (in Polish) helps identify the group the list is meant to cover. A market-research brief should also set out acceptance criteria and the limits of the search. The guide to preparing a research brief (in Polish) explains how to define that scope. Record count alone cannot be the measure of a commission's quality.
Assess fit and identity separately
Fit asks whether the activity described may meet the task. Identity helps establish which entity the information concerns. Do not combine these assessments into one “verified” status. A record with a confirmed identifier may not fit the project. Conversely, a profile that describes the required technology well may still require clarification of its relationship with a manufacturer, group or local entity. Each case needs a different next check.
The Japanese NTA Corporate Number Publication Site publishes the corporate numbers of organizations assigned one, and English names and addresses for organizations that have registered those indications in English. It is a source of specific identification data. It does not confirm an ability to fulfil an order or a willingness to talk. No result for an English name does not establish that a company does not exist. Consider the language version's scope and use an identity check suited to the country and type of entity.
Keep the original name and available identifier
A trade name, product brand and company name may appear in different materials. Record them separately when the relationship can be established. Do not discard the original spelling just because the team works in Polish. It may be the shortest route back to a document. Record the domain, source and date accessed too. Keep transliteration as an aid, not the only key for joining records.
If AI connects this information, check the type of relationship between the entity and the brand and the source supporting it (in Polish) before adding it to a candidate record.
The FSS OpenDART guide describes a corporate-code file containing a code, name and date of the latest change for entities covered by and registered in the disclosure system. This is an identifier used in that system. Do not treat it as interchangeable with every other number assigned to a business. Nor is the system a complete directory of all Korean companies. When combining material, apply rules for deduplicating Asian company records, as described in the company database guide (in Polish). Mark uncertain cases for clarification instead of forcing a match to a similar name.
Show evidence or an unknown for each criterion
Write a short observation in the record and identify the document behind it. “The company describes a service processing a particular material” is a checkable statement about the source. “The company is suitable for our order” requires further assessment. Keep them separate. If you inferred a point indirectly from a project description, say that it is an inference. Do not turn missing information into a positive answer merely to make a record look complete.
For an essential criterion, use statuses such as confirmed within a stated scope, contradicted and to be checked. For a helpful feature, add a comment about its relevance to the project. Ten scoring levels are unnecessary when evidence is sparse. Analysis of competitors in the Korean market (in Polish) likewise separates a public offer from the analyst's interpretation. Here the aim is to choose conversations, not to give companies a supposedly objective quality score.
Match sources to the company's role
An industry directory, exhibitor profile, manufacturer's website and disclosure document can provide different information. Do not expect one source to cover every criterion. An exhibitor profile can provide a lead and a description of declared activity. A product page may show an application. An identification document helps establish the entity. Every source has a scope; an official source does not answer questions it was not designed to answer.
For Japan, J-GoodTech can be used to explore profiles and cooperation hypotheses (in Polish). Do not treat its listings as a complete picture of the country. Record the channels used and areas omitted from your search. This helps explain the limits of the result. If all firms came from one event, the recommendation concerns the group explored, not the entire industry in Japan, Korea or China. In Korea, a map of industrial complexes (in Polish) can suggest an area for further research, but a plant's location alone does not confirm its application or a need to buy your solution.

Build a record someone else can assess
A minimum record should connect identity with the reason for interest. Add the proposed role, application, source for the observation and a question for a later conversation. When important information is missing, record how it could be checked. Do not write only “to verify” if you know what is missing. An unknown identity, unconfirmed service and lack of application data each call for a different next step.
Useful fields include:
- Entity, original name and available identifier from the appropriate source.
- Role considered for the project and its rationale.
- Essential criterion, supporting material and scope of confirmation.
- Main unknown and the question that could clarify it.
- Last checked date, record owner and proposed next action.
This need not require an elaborate system. A spreadsheet is enough if it preserves sources and the history of important changes. Decide who may change criteria, however, so the list does not expand each time another record is hard to find. Filling a requested number of rows is a poor reason to relax requirements without changing the project objective.
Test the list on three different candidates
In this exercise, the first company describes the needed technical capability, but it is unknown whether it accepts similar projects. The second serves the right industry but acts only as a seller. The third has a broad offer and clear materials, but no evidence for the specific application. These are three different states. They should not all receive the label “good partner” merely because each has a complete website.
For the first, prepare a question about the projects it accepts. Consider the second for a channel task if such a channel is needed. Keep the third as a lead requiring an application check. If you have no reason to pursue a direction, set the record aside with an explanation. A well-documented rejection can be more useful than adding another company to a contact list without a purpose for the conversation.
Then ask a second person to assess the same profiles against the recorded criteria. Compare the reasons. A difference may reveal an unclear definition of the role or an inference that goes too far. Fix the rule before expanding the list. The trial tests the method; it is not a contest of intuition. Intuition helps find leads, but accepting a list also calls for sources and clear criteria.
Order conversations by the question to resolve
The largest company need not come first. Start with the entity best placed to help test an important assumption: how a sample is assessed, the scope of an integration or an intermediary's responsibilities. Write down what you want to learn and how the answer would change the plan. In the invitation, name the purpose: understanding a process or discussing a specific proposal. The recipient should know how you intend to use the answer.
Before contact, distinguish readiness for a conversation from preparation for a specific transaction. Verifying a partner in Korea, Japan or China may require a different scope from an initial list. The partner verification guide (in Polish) explains the distinction. For a technical enquiry, prepare the information using an RFQ exercise (in Polish). Good selection criteria cannot fix a message in which the recipient cannot identify the task or the scope of the question.
Decide when to set a record aside
Record reasons to stop investigating: no required application, the wrong role, a connection to another record or insufficient information within the agreed search scope. Distinguish a lack of confirmation from confirmed absence of a feature. Do not erase the history merely to make a database look clean. A company set aside today may fit another task in a future project, and the explanation can prevent the same work being repeated.
If a recipient answers a question, update the scope of your knowledge rather than the entire assessment with one click. Confirmation that samples are accepted does not yet prove that every project condition is met. Define a separate scope of checks in your sample assessment plan. The guide to planning sample assessment (in Polish) can help. A candidate list is an entry point to further work. Develop it as evidence arrives instead of treating it as final after the first response.
Compare the scope of list commissions before their size
Imagine two research proposals. One collects company names from directories and assigns industries. The other checks a defined role, records a source for each criterion and describes unknowns. Both can be useful, but they deliver different results. Do not compare them only by the number of records. Decide what the material must support: further searching, selection of conversations or preparation for another assessment.
Ask for an example record structure and how the provider handles a company that cannot be classified unambiguously. Does it enter a separate group? Does the researcher seek another source? Is it excluded with a reason? Such questions reveal the method better than a general promise of very thorough research. Also agree what happens if the defined search does not yield the expected number of entities meeting the conditions.
It can help to agree on a small sample for assessing the criteria before the whole list is built. This is not a request for free work; it is a planned stage with a clear scope. The team can then adjust the role definition and the way evidence is recorded. If conditions change after this trial, record the change. The later list should answer the agreed question, rather than merely resemble the result initially imagined in conversation.
Accept the list by testing whether each choice can be explained
Work backwards through several records: from the recommended action to the criterion, observation and source. If the chain ends at a general industry description, clarify the rationale or change the status. Acceptance should also cover rejected leads and limits of scope. The client can then understand what the list covers and how to extend it, without treating absent companies as automatically unsuitable.
For a conversation about Aeneia Oriens, prepare the intended partner role, product application and essential conditions. A useful result should explain why the next conversation makes sense and what remains unconfirmed, even if the company found is not yet a partner.









