Why local relationships are not just contact lists

For international teams entering a new market, it is common to ask for “local contacts.”

A supplier contact.
A government contact.
A university contact.
A community contact.
A potential partner contact.

But in Indonesia, a useful local relationship is rarely just a name, phone number, or email address. A contact list may tell you who exists. It does not always explain who matters, who is relevant, who can respond, who has authority, who understands the project, and who should be approached first.

That difference matters.

A project can have many contacts and still have no clear path forward. On the other hand, a small number of well-mapped relationships can help a team understand the local situation, ask better questions, and move with more care.

A contact is not the same as a stakeholder

A contact is someone you can reach.

A stakeholder is someone whose role, interest, position, or influence may affect the project.

Those are different things.

For example, a company may have a list of possible suppliers, institutions, or local partners. But before reaching out, it is useful to understand:

• Why is this person or organization relevant?
• What role could they play?
• Are they a decision-maker, introducer, user, advisor, vendor, regulator, or observer?
• What information should be prepared before contacting them?
• Is the timing appropriate?
• Is this the right first conversation?

Without this context, outreach can become noisy. People may receive unclear requests. Meetings may happen without clear objectives. Follow-up may become difficult.

Stakeholder mapping helps turn scattered contacts into a more organized picture.

Local relevance needs interpretation

Indonesia is not one uniform business environment. Local conditions can vary by sector, city, region, institution, community, and timing.

A contact that looks important from outside Indonesia may not be the most practical starting point. Another contact that looks small on paper may be more useful because they understand the local situation, can explain field realities, or know which questions should be asked first.

This is why relationship mapping is not only about “who do we know?” It is also about:

• What does this stakeholder understand?
• What can they realistically contribute?
• What risks or limitations should be considered?
• What should not be assumed from one conversation?
• What is the right way to approach the next step?

NRC’s own service positioning is built around this practical layer: mapping relevant business partners, institutions, communities, suppliers, and other stakeholders for client review, while supporting local coordination and decision-ready documentation.

Good relationships require clear communication

Many cross-border projects become difficult not because the idea is weak, but because the communication is unclear.

A local stakeholder may ask:

• What is the project actually about?
• Who is behind it?
• What decision is being made?
• What is expected from this meeting?
• Is this a commercial discussion, research discussion, institutional visit, pilot project, event, or early exploration?
• Is there any commitment, or is this only a first conversation?

If those questions are not clear, the relationship can start with confusion.

Before contacting local stakeholders, international teams should prepare a simple explanation of the project: who they are, what they are exploring, what they need to understand, and what kind of conversation they are requesting.

This does not need to be overly formal. It just needs to be clear.

A meeting is not a commitment

One common mistake is assuming that a meeting means alignment.

In practice, a meeting may only mean that someone is willing to listen. It may not mean they have authority, interest, budget, approval, or operational capacity.

This is why follow-up matters.

After a meeting, the team should document:

• Who attended
• What was discussed
• What was confirmed
• What remains unclear
• What the stakeholder can or cannot do
• What follow-up is appropriate
• Whether the relationship should continue, pause, or be redirected

Without this record, the team may overread a conversation or lose track of important details.

For NRC, this is especially important because internal project-risk work has already emphasized that NRCshould remain clearly positioned as a project support provider: coordination, research, stakeholder engagement, administrative support, site support, and reporting — not as an agent, seller, recruiter, customs broker, or party guaranteeing approvals or public commitments.

Relationships also need boundaries

A good local relationship is not only about access. It is also about boundaries.

International projects may involve sensitive expectations: introductions, public-sector meetings, pilot activities, event support, reimbursement, documentation, or partner discussions. These situations need careful handling.

A local support partner should help clarify what can be done, what should be documented, and what should not be promised.

This is important because unclear relationship-building can create risk. A company may accidentally sound like it is offering a guarantee, representing another entity, or securing an approval. That kind of language should be avoided.

Better language is simple and careful:

• We are exploring.
• We would like to understand.
• We are preparing a review.
• We are mapping relevant stakeholders.
• We are requesting a discussion.
• We are not making any commitment at this stage.

This protects both the client and the local relationship.

The value of stakeholder mapping

A useful stakeholder map should not be a spreadsheet full of names only.

It should help the client understand:

• Who the relevant parties are
• Why they are relevant
• What role they may play
• What level of confidence exists
• What information is still missing
• What communication should happen next
• What risks or limitations should be noted

This allows international teams to move with more discipline.

They can avoid contacting too many people too early. They can prepare better meeting materials. They can understand which relationships are strategic, which are operational, and which are only informational.

Local relationships take structure

Some relationships begin with a formal introduction. Others begin with a field discussion, a community conversation, a supplier call, an institutional visit, or a small meeting.

The format may differ, but the principle is the same: relationships become useful when they are connected to a clear project objective.

Before building local relationships in Indonesia, teams should clarify:

• What are we trying to understand?
• Who do we need to speak with first?
• What should we prepare before reaching out?
• What should be documented after the conversation?
• What should be avoided in our wording?
• What decision will this relationship help inform?

These questions keep the work practical.

Final note

Local relationships are not shortcuts. They are part of the work.

A contact list may open the first door, but it does not replace context, preparation, communication, documentation, and careful follow-up.

For international teams working in Indonesia, the goal is not to know everyone. The goal is to understand the right people, approach them properly, and build enough clarity to make better decisions.

That is where stakeholder mapping becomes valuable.