☎ +33 (0)1 87 66 00 65 · Monday to Friday, 9am–6pm Discuss your project

Track 04 / Alliances

Building an alliance that proves itself

Software publisher, supplier, network or institution: let’s move forward from a concrete pilot, verified interoperability or a documented sector need.

Defined roles, published commitments

Two specialists check an interoperability setup

Two paths

Choose your starting point

The conversation starts with the result to deliver together, suited to your organisation.

Publisher or supplier

Test a connection, demonstrate interoperability and document the versions concerned.

PilotInteroperabilityVersioned evidence

Present a solution

Institution or network

Bring out a shared need, a sector pilot or an event based on verified facts.

Sector accessTrialEvent

Present an organisation

Before communicating

Evidence tied to the right versions

Each demonstration adds to a results sheet: versions, context and tests carried out give your communications a precise framework.

Pilot sheet

Validated results and next steps

Versions of both solutions, environment, test cases, observed result and limits: this sheet is the basis for any joint communication.

Use the official logos within the agreed communication arrangement.

Sample sheet — proposed format

Interoperability pilot

  • Named versions

    Solution A vX.Y · Blue Lemon Agent agent vX.Y

  • Scope tested

    Reading a file, human approval, logging.

  • Next validations

    Writing and scaling up: assessments still to be run to extend the validated scope.

Collaboration steps

From use case to accurate communication

  1. Step 01

    Propose

    A need and a pilot goal.

  2. Step 02

    Frame

    A scope, versions and responsibilities.

  3. Step 03

    Test

    Recorded, jointly checked results.

  4. Step 04

    Publish

    Communication faithful to the validated results and scope.

Useful questions

The answers before you start

Is an alliance remunerated?

No. The track's rights are limited to proposing a pilot and communicating jointly; no commission is attached to it, in any direction. An organisation wishing to recommend Blue Lemon Agent and be paid for it applies on the referral track, whose rules are published separately.

When will we be able to announce our integration?

When it is proven on named versions, on both sides. This is not a scheduling formality: an announcement made before the evidence rebounds at the first version change.

Can you display our logo, and we yours?

Yes, with an official source on both sides: a written agreement stating which logo, on which materials and for how long. Without that source, no logo is displayed — displaying one without agreement is exactly what the track excludes.

Our need falls outside the catalogue. Can you build something for us?

The answer comes in a sentence we do not alter: If the Blue Lemon Agent catalogue does not properly cover your need, Blue Lemon Agent can study a custom agent. This possibility remains subject to validation of its architecture, feasibility, compliance and pricing. No lead time, capability or price is announced before that validation, and a pilot is not a commitment to bring something to market.

Our organisation is established outside France.

The terms of your track are supplied to you before any signature, whatever your country of residence. French law, subject to the mandatory rules and overriding provisions applicable locally.

How is an alliance application assessed?

Like the others, through declared states: draft, submitted, under review, awaiting further information, approved, rejected and withdrawn. We ask for a named contact on each side and a first concrete objective — a pilot, an interoperability check, an event. An alliance with no concrete objective remains an intention, and an intention is not something we publish.

The next step

What pilot could we build?

Present a concrete situation, the solutions involved and the result to demonstrate.

Propose an alliance