Who Can Turn Interest into a Decision?

An encouraging meeting can be entirely sincere and still produce no purchase. The person who recognises the problem may have no budget. The person with budget may need evidence that nobody has yet agreed to produce. A prospective local partner may like the technology while remaining unsure who would maintain it.

Our view is that progress becomes easier to assess when a conversation is connected to a decision, its owner and the evidence needed to make it. This also makes follow-up more respectful: the other party receives a manageable request instead of repeated pressure to confirm vague enthusiasm.

Map responsibilities before interpreting behaviour

Five roles are worth distinguishing: the user experiencing the problem, the advocate willing to mobilise colleagues, the budget owner allocating resources, the approver accepting the commitment and the person accountable for delivery. One individual may hold several roles. A large organisation may divide a single role across regional and country teams.

Singapore’s published government procurement process offers a concrete example of separation: it distinguishes evaluation, approval of award and contract management. This is a public-sector process, not a template for every private company. Singapore Ministry of Finance, Procurement processes.

The commercial lesson we draw is to ask what each participant can decide. A regional innovation leader might authorise a test while an operating subsidiary controls production spending. An equipment buyer might fund hardware while a plant manager determines when installation is possible. A senior title gives context; it does not answer either question.

Local advocates face a real cost when introducing an unfamiliar supplier internally. They must explain why colleagues should spend time reviewing it, and may become the first person asked for an explanation when something fails. Supporting them means providing usable evidence and a credible delivery boundary.

Diagnose silence with competing explanations

Silence after a meeting is ambiguous. The initiative may have lost priority. The recipient may be waiting for another team’s view. The proposal may require more adaptation than the supplier recognises. The organisation may simply have decided against it without closing the loop.

Cross-cultural communication belongs among the possible explanations. It should not become the default explanation attached to a nationality. Before drawing a conclusion, inspect the request itself. Was a specific decision requested? Could the recipient make it? Was there enough information? Was the expected timing discussed?

A useful follow-up reduces one uncertainty. “Would a short discussion with the workflow owner help establish the evaluation criteria?” is more actionable than “Any update on our partnership?” It also gives the recipient an honest route to say that the initiative has no current owner or budget. A clear pause can save both organisations further effort.

A hypothetical meeting that produces the wrong next step

Imagine an overseas AI supplier meeting a Singapore regional operations team. This is a hypothetical illustration, not a reported engagement. The demonstration is well received, and the supplier sends a broad regional rollout proposal. The operations contact stops replying.

One explanation is that a rollout proposal asks for a decision that the meeting never prepared. The contact may only have authority to investigate one workflow. The supplier has increased the internal burden: colleagues must now assess deployment locations, costs and responsibilities before the initial usefulness question is answered.

A better next step would be to agree a limited evaluation question and identify who can answer it. The supplier provides a short statement of the workflow, proposed evidence and support required. The local team confirms whether a business owner can participate. If nobody can, the opportunity should remain exploratory rather than becoming a forecasted deal.

Record a decision chain and observable signals

The following tool is our recommended working record. It should be jointly corrected rather than treated as an intelligence file about people. Names and authority can change; the important point is agreement about responsibilities.

Scroll the table horizontally, or focus it and use the arrow keys.

These signals indicate movement, not a guarantee of purchase. A document request can reflect routine diligence. Access to a senior person may be exploratory. Stronger evidence connects an action to a decision: someone explains how the requested material will be reviewed and what may follow.

Help the counterpart carry the decision internally

A useful meeting record states what was understood, what remains open, who will contribute the next piece of evidence and when the position will be reviewed. It should also state what has not been agreed, particularly where a test could otherwise be mistaken for a wider commitment.

The entrant needs a realistic path to revenue. The local counterpart needs room to coordinate without making promises beyond their authority. Both benefit from a smaller, explicit next decision. When budget, sponsorship or delivery ownership changes, revisit the chain rather than assuming that earlier enthusiasm still carries the same meaning.

Sources

• Singapore Ministry of Finance: Procurement processes — official illustration of separated public procurement responsibilities; private organisations must be assessed individually.