Managing Conversations with Finalists and Connections on Halo

Last updated: February 11, 2026

Once you move beyond proposal review, conversations may transition off-platform for deeper evaluation, validation, or partnership discussions.This article outlines Halo’s recommended best practices for managing finalist and introduction workflows.

These are Halo recommendations only. Always confirm requirements with your internal legal, procurement, compliance, and finance teams before proceeding.

1. Partner Requests and Finalists

What happens when you select a finalist?

When a Lead selects a finalist:

  • An email is sent to the Lead with the finalist’s contact information.

  • A separate email is sent to the finalist with the Lead’s contact information explaining next steps.

  • The email clearly states that being selected as a finalist does not guarantee a partnership.

  • The email indicates that outreach can begin via Halo messaging or direct email.

Finalist evaluation happens off-platform and does not have a deadline within Halo.

How to initiate outreach

You may:

  • Reach out directly by email using the contact information provided, or

  • Start the conversation in Halo messaging and then move offline if needed.

Both approaches are supported.

We recommend aligning internally on which method you prefer before initiating outreach.

Anonymized Requests

For anonymized requests, your contact information is not automatically shared with the innovator.

If your request was anonymized, consider:

  • Sending a short Halo message introducing yourself before emailing, particularly if you want to reduce the chance of your outreach being missed.

  • Confirming internally what level of disclosure is appropriate before identifying your company.

Always follow your internal confidentiality and disclosure policies.

Confidentiality and NDAs

If you plan to discuss proprietary, technical, or commercially sensitive information:

  • Confirm whether an NDA is required before sharing details.

  • Avoid requesting or sharing confidential information within Halo messaging.

  • Transition to offline channels when deeper confidential discussions are needed.

Halo does not automatically enforce NDAs. These decisions should follow your internal legal processes.

Proof of Concept and Validation Discussions

Depending on the maturity of the technology or solution, next steps may include:

  • Early feasibility or lab-scale testing

  • Application-specific validation or pilot work

  • A defined, time-bound proof of concept

  • Advisory or expert consultations

These activities are managed directly between you and the finalist and may require vendor setup, contracting, or internal approvals.

Engaging Multiple Finalists

If you have selected multiple finalists, such as for a Request for Experts, you may:

  • Engage finalists individually for consulting

  • Host a panel discussion or workshop

  • Compare approaches before narrowing to a single partner

Your internal process may require:

  • Setting finalists up as vendors

  • Defining scope, compensation, and payment terms

  • Executing appropriate agreements

Confirm requirements with procurement and finance teams before proceeding.


2. Discover Introductions

If you request an introduction via Discover:

  • You submit a request form.

  • Halo facilitates the introduction.

  • The connection is created through the Halo messaging system.

We recommend beginning the conversation within Halo messaging and then moving offline if appropriate.


3. PulseChecks

PulseChecks follow a slightly different workflow:

  • You receive a user profile.

  • Initial outreach should occur through the Halo messaging system.

  • Email contact information is not automatically provided at this stage.

If both parties decide to proceed into deeper or confidential discussions, you may transition offline according to your internal policies.


Setting Expectations with Finalists and Connections

Regardless of request type, we recommend:

  • Clarifying that finalist selection is exploratory and not a guarantee of partnership

  • Aligning on timelines and next steps

  • Confirming confidentiality expectations early

  • Documenting agreed next steps internally


Quick Checklist for Request Leads

Use this checklist after selecting finalists or initiating introductions:

Outreach

☐ Review finalist profiles and maturity levels

☐ Confirm whether outreach will begin via Halo messaging, direct email, or both

☐ For anonymized requests, decide whether to introduce yourself in Halo before emailing

Confidentiality

☐ Confirm whether an NDA is required before sharing detailed information

☐ Avoid sharing confidential information in Halo messaging

☐ Move offline when appropriate for sensitive discussions

Engagement Structure

☐ Clarify whether next steps involve PoC testing, validation, consulting, or partnership discussions

☐ If engaging multiple finalists, confirm vendor setup and payment requirements internally

☐ Align on partnership model and benefits you may provide

Platform-Specific Flows

☐ For Discover introductions, continue the conversation in Halo messaging first

☐ For PulseChecks, initiate outreach via Halo messaging before moving offline

Closing the Loop

☐ Set clear timelines and next steps

☐ Document outcomes internally

☐ Contact support@halo.science if assistance is needed