What if the company is already talking to micro1 or another buyer?

If a company is already speaking with micro1 or another buyer, pause new outreach until the owner clarifies the current discussion, its scope and who is authorized to communicate. Do not contact the same company through a second route simply because the first conversation appears slow or limited.

An existing conversation may cover one dataset, one recipient, a specific evaluation or an early inquiry. It does not necessarily cover every business unit, use or future opportunity. But that uncertainty belongs to the company and the parties already involved to resolve. A second intermediary should not infer permission to step in.

How can you check an existing buyer discussion privately?

The first check can be non-identifying: “Is there an active conversation relevant to this proposed scope, and may we continue?” If the answer is yes, record the company-approved counterparty, subject, status and permitted next action. Do not request confidential terms unless the company is authorized and willing to share them.

The company can choose to pause, continue with its existing contact, ask for a limited comparison, or authorize a separate adviser to review a different scope. Each choice should be explicit and documented. A message, NDA or job title is not automatically a mandate to represent the company or disclose its data.

Map the scope before deciding whether there is overlap

Record what is known about the discussion: data category, period, intended use, rights requested, recipient entities, exclusivity or options, and whether a sample or company identity has already been shared. Mark unknown items rather than filling them with assumptions. If two parties are discussing related but distinct material, the owner should decide whether to proceed separately after reviewing rights and contract restrictions.

Use a narrow existing-counterparty list under the owner's control. It can record names and scope privately so partners avoid duplicate contact. It should not become a public lead directory or a shared list distributed without permission. Access should be limited to people who need it for the authorized work.

Does an existing adviser or programme limit the next approach?

If an adviser or referrer is already involved, establish whether their authority is exclusive, what subject it covers, when it expires and how conflicts are handled. Do not tell the company that one party has a right to a fee or representation unless the relevant agreement supports that statement. Where the documents are unclear, have counsel review them before anyone promises a referral payment or contacts the buyer.

The same care applies if the company has already submitted information through a provider's public process. A public intake process may state what that provider does, but it does not make a new intermediary the owner of the resulting relationship or grant access to the company's submission. Ask the company what it wishes to do and what permissions it has given.

Keep any status record factual and dated. “The owner reports an active conversation about support records” is different from “the provider is evaluating the dataset.” Record what the owner actually said, whether the company authorized you to know it, and when to check again. Do not copy private terms into a general pipeline or infer whether the conversation succeeded.

Could a separate engineering proposal overlap the support discussion?

Consider a fictional software company already discussing an evaluation of support workflow data with one counterparty. A potential second discussion concerns engineering review records. The categories might be distinct, but they could share customer details, employees, systems, contracts or exclusivity restrictions. Before any outreach, the owner should examine the agreements and decide whether a separate scope is permitted. Similar subject matter alone cannot settle the question.

What should happen before another party contacts the buyer?

1. Stop duplicate outreach until the company confirms the status.
2. Ask whether it authorizes a conversation about this specific scope.
3. Record counterparties, scope, permissions and restrictions in a private log.
4. Check existing agreements and any exclusivity, option or confidentiality terms.
5. Agree who communicates, what may be disclosed, and who receives updates.
6. If the company wants another route, document the distinct scope and mandate.

This protocol protects the company's control and makes attribution more intelligible. It does not guarantee that counterparties will agree, that a second route is available, or that the company should pursue one.

Avelence provides advisory and research support and, under a written mandate, can support specified discussions or identify opportunities the owner closes. Before any approach, the company controls whether its identity or information is shared and which recipient may receive it. If there is already a conversation, confirm its scope first.

A current provider page can be recorded as a self-description, not independent validation: micro1 describes a data-partnership intake and review workflow. Separately, the W3C PROV model can help document who supplied or changed information as a status request moves between parties. Neither source establishes the status of a specific company opportunity.