A partnership starts with the work.

Partnerships

Partnerships in Energy, Health, Intelligence, and Compute. Scope and responsibilities are agreed separately.

A shared objective before a shared label

A partnership begins with a problem that both parties can describe clearly. Identify the system, the intended outcome, and the capability your organization brings to it. That capability might be a research method, a manufacturing process, a field environment, a data source you are authorized to use, or an operating requirement that gives a program a practical direction. A statement of interest is more useful when it also identifies what needs to be resolved.

The partnership routes on this page organize discussions in Energy, Health, Intelligence, and Compute. They are not a public application for funding, an automatic supplier registration process, or a promise that a particular collaboration is available. Scope, responsibilities, ownership, resources, and any commercial terms are discussed separately with the parties involved.

Define the interfaces

For technical work, explain what each organization would contribute and where the contributions meet. A model may need measurements; equipment may need an operating site; a research protocol may need institutional review; software may need an authorized dataset and an integration boundary. Naming these interfaces helps distinguish a meaningful collaboration from a collection of broad aspirations.

Initial information should be non-confidential and suitable for a public enquiry channel. Do not submit patient records, controlled technical details, non-public market information, credentials, or third-party data you are not authorized to share. If a later discussion requires protected material, first agree on an appropriate channel, the permitted purpose, and the people entitled to receive it.

Plan for evidence and responsibility

An effective proposal explains how the parties would know whether the work is succeeding. State the question, the proposed method, the baseline, and the result that would inform a next decision. Distinguish a research objective from a demonstrated outcome and a technical result from an authorization to deploy. The relevant evidence depends on the application and cannot be replaced by the appearance of a product page.

In health-related discussions, the institution and qualified professionals remain central to ethical review, biosafety, samples, data governance, and any clinical or regulatory pathway. Intelligence discussions should identify authorized sources and uses. Energy and computing proposals should address the operating environment and integration constraints. An initial enquiry can identify these responsibilities without pretending that the full arrangement has already been settled.

Begin with a focused brief

Select the program closest to the work, identify your organization and role, and describe the opportunity in terms that can be routed to the right business. Include the principal constraints and the decision you would like to discuss next. A public reference or a short description of relevant prior work can provide context when you have permission to share it.

Submitting the form does not establish a partnership, exclusivity, an endorsement, a procurement commitment, or a right to use either party’s branding. A partner reference elsewhere on the site should not be treated as an authorization to make those representations. Any relationship that progresses needs its own confirmed scope and terms.