Architecture is validated beforehand
Connections, data flows, environments, service accounts and logging are described and accepted before deployment. An architecture discovered in production is not an architecture.
Partner integrator
Deploying under control, and proving it
Prepare and deploy solutions under BLA control: connections, architecture, security, data, acceptance testing, training, adoption, local support and reversibility. It is the most demanding of the four tracks, because it is the only one where the partner reaches into the client's information system.
The scope of this track
What you may do
- bring us a client's need
- receive an assignment from BLA
- deploy under BLA's supervision
What lies outside the track
- claim to be certified without active proof of certification
- deploy outside the perimeter entrusted to you
Who this is for
Companies that connect, deploy and maintain information systems on behalf of their clients: IT services firms, business-software integrators, managed-service providers, technical consultancies. What they have in common is not size: it is the ability to describe an architecture before building it, and to prove it afterwards.
The track allows you to apply, be assessed, be accepted, receive an assignment and deploy under our control. Every deployment carries a named perimeter — connections, environments, types of data, sometimes a sector — and it is within that perimeter that the integrator works.
The track's scope, in practice
The track allows the following:
bring us a client's need, receive an assignment from BLA and deploy under BLA's supervision
And it excludes the following:
claim to be certified without active proof of certification and deploy outside the perimeter entrusted to you
The second exclusion deserves reading twice. Deploying beyond the named perimeter means working without a net and committing the client to coverage they believe they have. The perimeter is not paperwork: it is what deploying under control means.
What "under Blue Lemon Agent control" means
The phrase is not a turn of speech. It describes a precise division, set out before the first workshop rather than reconstructed after an incident.
Data has a framework
What goes into an agent, what comes out, what is retained and for how long all fall under a written framework. An integrator neither improvises it nor widens it on their own initiative.
Acceptance testing is adversarial
Go-live is decided on agreed test cases, not on a general impression. What fails is named and reworked; what has not been tested is declared untested.
Reversibility is planned from the outset
A client must be able to recover their data and change provider. A deployment that makes leaving expensive is not a technical success: it is a debt created for them without their knowledge.
Evidence before announcement
Compatibility is announced neither on the strength of a vendor's documentation nor on a test that worked once: it takes evidence tied to named versions, on both sides.
This requirement is tedious, and it is what separates a deployment from a demonstration. An announcement unpicked six months later, because a version moved, costs the client far more than waiting for evidence would have.
Bringing a deal, receiving an assignment
An integrator may also bring a need forward. The referral commission then applies: 10% of the eligible BLA recurring subscription, excluding tax, actually collected, over 24 months from the first eligible recurring collection. The base, its exclusions and the duration of deal protection are published on the conditions page.
In the other direction, a deployment assignment may be entrusted to you. What decides the suggestion made to the client is these criteria: competence in the need expressed, certification, where the need requires it, geographical proximity, the client's working language, experience of the sector, stated availability, security guarantees, insurance cover, verifiable references, measured satisfaction of previous clients, recorded incidents and absence of conflicts of interest — never these: the fee we would earn, the expected remuneration and how long the partner contract has run. Up-to-date compliance documents and the absence of open incidents weigh more, in that decision, than the volume of deals brought in.
Questions
The questions we are asked
What does applying allow?
To be assessed, accepted, and to receive deployment assignments. Your application follows declared states: draft, submitted, under review, awaiting further information, approved, rejected and withdrawn. What is assessed is the environments you know how to connect and the sectors you have already worked in, on real work rather than on a file.
My client's need does not fit any agent in the catalogue.
Use the prescribed wording, without adding an estimate: If the BLA catalogue does not properly cover your need, BLA can study a custom agent. This possibility remains subject to validation of its architecture, feasibility, compliance and pricing. A lead time, a capability or a price announced before that validation binds whoever announced it.
Who is responsible if a connection breaks in production?
The integrator for their deployment work, Blue Lemon Agent for the agent and its operation. That is why the architecture is validated beforehand, why acceptance testing is adversarial and why versions are named: without those three things, the question becomes impossible to settle at the moment it arises.
Who does the client contract with?
With Blue Lemon Agent for the agents and their operation, and with you for your deployment work. These are two distinct contractual relationships, and the client knows which one carries what.
My company is not established in France.
The programme is open in France. A translated page does not open a country: eight checks must be met first — language, support, pricing, connectors, data protection, sector compliance, tax and VAT and capacity to go live. French law, subject to the mandatory rules and overriding provisions applicable locally.
Apply as an integrator
Describe the environments you know how to connect and the sectors you have already worked in: that is what will be assessed, not the size of your organisation.