Originally written in French. Translated by AI — the meaning has been preserved, not the prose.
Short definition
Everything needed around the core of the product so that a given customer can actually buy it, deploy it and operate it.
Full definition
The notion is classic in technology product marketing, where it describes the gap between what a vendor sells and what a buyer needs in order to get something out of it.
In the articles on this blog, it is understood through one sentence: these elements don't create the value, they let the value enter the company. SSO, forwarding events to the customer's SIEM, data residency, delegating rights to its IAM have no effect on the business problem — and the absence of any one of them can stop a sale.
Its content isn't universal: it depends on the customers you have chosen to serve. This isn't a checklist of "good enterprise software", it is the concrete answer to the question of what has to be added so that this particular segment can buy.
Usage in the field
Used to arbitrate a roadmap when non-functional requirements compete with features, and to bound the extent of technology support.
Synonyms and variants
"complete product". "Conditions of market access" when the emphasis falls on the commercial effect.
Not to be confused with
- Core product — what carries the value. The whole product surrounds it and never substitutes for it.
- feature catalogue — a list of what the product can do. The whole product is defined by a market, not by exhaustiveness.
- BYO — one possible answer among others to a demand for control, therefore a possible element of the whole product, not its synonym.
Examples
For a vendor targeting large accounts built around Microsoft, supporting Azure and SQL Server belongs to the whole product; supporting Oracle and GCP, which nobody in the segment asks for, does not.
Ambiguities / debates
The notion can justify anything if the segment isn't defined: with no chosen market, every customer request looks like it belongs to the whole product.