Reading a Profile — Buyer angle#

Reading a Profile when one has to arbitrate between providers and turn a public declaration into an enforceable contractual piece.

Your stake#

A buyer does not read a Profile in the same posture as a CIO or a CISO. The CIO looks for operational continuity; the CISO qualifies exposure to structural risk. The buyer arbitrates — between two providers at functional equivalence, between an outgoing incumbent and a challenger, between a commercial offer and what it hides. The Profile is the instrument that turns a marketing promise into a contractual piece. A brochure announces longevity; a dated Profile names the mechanisms that make it enforceable — escrow, release-on-trigger, reversibility clauses, quantified notice periods. The manifesto asks the buyer explicitly to align their demand: what you write into your tender documents structures what providers publish. Reading a Profile thus consists in checking that it says enough, and precisely enough, for a lawyer to be able to draw a clause from it.

A 5-minute reading#

Five fields suffice to decide whether a Profile allows a serious arbitration at functional equivalence, or whether it forces the buyer to integrate a risk provision into the price for lack of enforceable elements.

• Domain 5 — Continuity in the event of failure. If the domain limits itself to intentions (“we commit to longevity”), it offers no contractual hold. If it names an escrow, a release-on-trigger clause that can be triggered on specific events, a reversibility procedure with a quantified notice period, then the public declaration can become a signed clause.
• Domain 6 — Governance and capital. Over a three- to five-year procurement, the capital stability of the provider matters as much as its technique. Capital exposed to Italian golden power, to French IEF or to German AWG without readable anti-acquisition clauses signals that a transfer may occur during the procurement, beyond your control.
• Domain 1 — Strategic third-party components. Signing with a provider is to commit in cascade with its own critical providers. If domain 1 names the upstream bricks, you know to whom you are effectively bound; if it hides them, you buy a blind chain.
• Date and version of the Profile. A Profile that is undated or frozen for more than eighteen months no longer describes the current state of the provider. The freshness of the document is itself a purchase criterion.
• Domain 7 — Assumed commitments and limits. A provider that names its limits allows the contract to be calibrated — you know what it refuses to carry, and therefore what you must carry elsewhere or provision. A provider that hides them forces you to assume the worst.

In-depth reading#

Seven domains, seven illuminations from the buyer angle. This section does not rewrite the educational sheets — it says what a buyer draws from them in order to arbitrate and to draft.

Domain 1 — Strategic third-party components#

Domain 1 says to whom your provider is itself bound. For the buyer, this is the downstream chain made readable: if you sign, you inherit in cascade the dependencies found there, and hence the licence flips that they can undergo.

Domain 2 — Contingency plans#

Domain 2 indicates whether the provider has planned to switch over when an upstream brick falls. A theoretical plan does not turn into a clause; a tested plan, with a quantified lead time, can be taken up in a specification document and become a measurable service commitment.

Domain 3 — Supply chain#

The distribution chain says who else operates the same brick, hence how many organisations share the same breaking points. For a public buyer, this is a signal of mutualisation of interests; for a private buyer, this is an indicator of the maturity of the field they are entering.

Domain 4 — Hosting and data#

Domain 4 names the effective jurisdiction of the data — distinct from the declared jurisdiction of the headquarters. For the buyer, this is direct purchase information: depending on the sensitivity of the data processed, the effective jurisdiction conditions the very eligibility of the offer, regardless of price.

Domain 5 — Continuity in the event of failure#

Domain 5 is the heart of the buyer reading. It is here that the part transformable into clauses is lodged: a declared escrow becomes a signed escrow clause; a documented reversibility procedure becomes an enforceable reversibility commitment; a quantified notice period becomes a contractual lead time. A domain 5 that describes intentions without a mechanism gives nothing to take up.

Domain 6 — Governance and capital#

Domain 6 qualifies the stability of the partner over the duration of the procurement. Shareholders’ agreement, blocking rights, exposure to State strategic-divestment regimes: a readable capital allows assessment of whether the signing provider will still be the same operator in three years, or whether a transfer will place it under another execution logic.

Domain 7 — Assumed commitments and limits#

Domain 7 is the Profile’s test of sincerity. A provider that assumes its limits — “we do not carry the disaster recovery plan”, “we do not maintain version N-2 beyond twelve months” — offers you a calibratable contract. A provider that writes only intentions forces you to provision all the worst hypotheses into the price, or to leave them implicit and discover them on incident.

Warning signs#

Five signals that should trigger a request for complement before award or renewal. None on its own suffices to disqualify; their accumulation indicates a Profile that does not support a serious arbitration at functional equivalence.

• Vague non-enforceable commitment. Domain 5 limits itself to formulae of intention (“we commit to the longevity of our service”). Consequence: no contractual clause can rest on it, and the public declaration remains a moral assurance without a mechanism.
• Absence of escrow, of release-on-trigger or of reversibility clause. Domain 5 describes no triggerable mechanism. Consequence: the day the provider closes, is acquired or shifts license, no contractual mechanism activates — the procurement extinguishes with it.
• Foreign capital without anti-acquisition clauses or armoured statutes. Domain 6 remains evasive on the shareholders’ agreement and on the blocking rights. Consequence: a transfer may occur during the procurement and place your incumbent under an operational, jurisdictional or tariff logic that neither the tender documents nor the contract had anticipated — see family 1 — licence flips, in particular Broadcom–VMware or the shifts to BSL and SSPL.
• Profile undated or frozen for more than eighteen months. The chain described is no longer the current chain. Consequence: you arbitrate on the basis of a state of the provider that no longer exists, and the updating of the Profile will become a task the buyer carries in place of the provider.
• Opaque downstream chain. The provider publishes its Profile, but its own critical providers — host, single-vendor bricks, technical subcontractors — do not publish theirs. Consequence: enforceability collapses in cascade. You cannot contractually require of an incumbent what its own incumbents have never documented.

How to act#

Reading a Profile is not enough — it must be written into the procurement process. Four gestures specific to the buyer make the reading operational.

First, integrate the Profile as a piece of the tender documents on the public side, or of the procurement process on the private side. The Profile joins the technical memorandum and the CSR sheet as an expected document, not as an optional bonus — the mirror commitment user-002-integrate-profile-procurement formalises this integration.

Next, arbitrate at equivalence in favour of the most complete Profile. When two offers are equal functionally and in price, the completeness and freshness of the Profile become a discriminating criterion — the commitment user-003-prefer-european-governance anchors this preference in the procurement policy.

Then, turn the declared commitments into enforceable contractual clauses. An escrow described in domain 5 becomes a drafted and signed escrow clause; a published reversibility procedure becomes a contractual reversibility commitment with a deadline and deliverables. The public declaration serves as raw material for the procurement drafter.

Finally, require the Profiles of the entire downstream chain and make renewal conditional on the annual update. A publisher that depends on a host must produce the host’s Profile; an incumbent that depends on a single-vendor brick must document its trajectory — see user-007-require-suppliers-profile. The assumed limits of the device clarify what the Profile claims to carry and what it leaves to the tender documents and to the contract.

Prepare your own declaration#

An organisation that requires a Profile from its providers is itself engaged by its own purchasing practices. The manifesto sets out that aligning one’s demand structures the offer: a public buyer that writes the completeness of the Profile into its criteria, a private buyer that makes it a contractual prerequisite, shift what the market publishes. Publishing your commitments declaration makes this purchasing policy readable and makes it enforceable in turn. The basket below proposes the commitments and domains relevant to this persona, and the full philosophy of the device sets the frame.