The subject “Choose an agency or a tech service provider” must lead to proof, not just to deployment: the expected effect must be measurable and reversible.
Frame the “Describe the service” point, control the “Request evidence” point, then decide with an explicit benchmark measure.
1. Key figures
| Number | What it establishes | Source, date and scope | Reading for you |
|---|---|---|---|
| 4 bonds | The British Service Standard requires you to justify build or buy, calculate the total cost and preserve the ability to change supplier. | GOV.UK — Choose the right tools and technology, consulted on 11 July 2026, public digital services, transposable principles | The purchase price is not enough to compare two technological options |
| 1 discovery phase | GOV.UK recommends not choosing an off-the-shelf product before a discovery phase and testing of options. | GOV.UK — Commercial off-the-shelf products, updated to 2025, purchasing technologies and services | A SaaS should be tested against the actual problem, not against a list of features |
| 6 functions | CSF 2.0 adds Govern to Identify, Protect, Detect, Respond, and Recover. | NIST—Cybersecurity Framework 2.0, 26 February 2024, organizations of all sizes | Cybersecurity must be linked to governance and enterprise risk |
| 3 factors | ANSSI links the cloud choice to the typology of the offer, the state of the threat and the nature of the information system. | ANSSI — Cloud recommendations, accessed on July 11 2026, IaaS, PaaS and SaaS | A SaaS service is not judged only by its functions, but by the data and threats concerned |
| 100 % allocated | The FinOps SaaS framework aims for the complete allocation of expenses to cost centers, products or application owners. | FinOps Foundation — FinOps for SaaS, accessed on July 11 2026, expenditure governance SaaS | A license without an owner or economic unit becomes invisible waste. |
These benchmarks limit the decision on the due diligence of an agency or a technological service provider; they don't take it for you. A published value describes a precise perimeter, a date and sometimes a population different from yours. Read it as a constraint to be tested, not as the promise of an automatic effect. The risk is concrete.
On the critical path, the stopping rule is known: for this subject, the first source leads to the following operational reading: “The purchase price is not enough to compare two technological options. » The second reference in the table must also be compared to your perimeter and a local measurement. This distinction between external reference and local measurement protects the analysis against easy extrapolations.
2. Read the sources without overinterpretation
Outside of the nominal scenario, the next deadline is planned: a source is useful when a reader simultaneously understands what it states, the scope it covers and the limit of extrapolation. The five benchmarks below are therefore reread as decision markers, never as causal promises.
For the scope “the due diligence of an agency or a technological service provider”, external data can only be used to decide if its scope, date, unit and limit are explained. The review should separate what the source establishes, what the team infers, and what a local test still needs to demonstrate.
Concretely, the proof sheet preserves the organism, the title, the URL, the date of consultation, the population, the unit, the method and the reservation of interpretation. It then indicates the decision that the benchmark informs and the local observation capable of contradicting this benchmark. In this file, attach this register to “Describe the service” and entrust its review to “Management”. Data without a documentary owner ages silently; data with a revision condition remains controllable and can be cited without losing its context.
2.1. Benchmark 1
The source GOV.UK — Choose the right tools and technology locates the terminal “4 obligations” in the field “public digital services, transposable principles”. It provides an external reference to the diagnosis; it does not replace either a local reference measurement or the analysis of exceptions. The threshold remains explicit.
2.2. Bench 2
The “1 discovery phase” milestone, published by GOV.UK — Commercial off-the-shelf products, falls under the “purchase of technologies and services” scope. It helps to formulate a testable hypothesis, without transforming an external value into an automatic objective. The average can deceive.
2.3. Bench 3
NIST — Cybersecurity Framework 2.0 documents “6 functions”. The exact range is shown in the previous table; keep it when comparing this data to your own operations, populations and periods. The perimeter is authentic.
2.4. Benchmark 4
ANSSI — Cloud Recommendations provides the indication “3 factors” here. This information informs a choice; it does not, by itself, demonstrate that the same effect will appear in your context. The compromise appears clearly.
2.5. Bench 5
The reference FinOps Foundation — FinOps for SaaS publishes “allocated 100 %”. Before making a decision, check the date, the population covered and the possibility of replicating the measure locally. The decision can be reviewed.
3. Reusable citation sheet
During the audit, the threshold has an owner: a robust citation must be able to be repeated without losing its author, its date, its scope or its limit. The sheet below isolates these elements and links them to a specific decision; it prevents a correct figure from becoming misleading after extraction from its context.
| Field | Content to keep |
|---|---|
| Verifiable assertion | The British Service Standard requires you to justify build or buy, calculate the total cost and preserve the ability to change supplier. |
| Attribution | GOV.UK — Choose the right tools and technology, accessed July 11 2026 |
| Declared scope | public digital services, transposable principles |
| Value or bound | 4 bonds |
| Operational reading | The purchase price is not enough to compare two technological options. |
| Decision concerned | Link “Describe the service” to a local observation before arbitrage |
| Magazine owner | Direction — Naming truly open decisions |
| Condition of revision | Reexamine the citation if the source, scope, or “Test the Method” changes |
4. Introduction: framework the primary risk
The portfolio is attractive, the proposal is precise and the people presented may not be the ones who deliver. References talk about successes, but rarely about incidents, delays or transitions. The contract begins when commercial uncertainty disappears. A customer logo does not prove the scope achieved. A low daily price predicts neither total cost nor management time consumed.
Supplier decisions involve data, continuity and output capacity. Serious trust is built through evidence, difficult scenarios and explicit responsibilities. The measurement precedes arbitrage.
5. Actors and responsibilities
| Actor | Responsibility in the decision | Point of vigilance |
|---|---|---|
| Management | Arbitrage, risk, budget and expected value | Name the truly open decisions |
| Professions and users | Usage constraints, exceptions and adoption | Do not reduce discovery to validation interviews |
| DSI, finance and purchasing | Architecture, total cost, contracts and reversibility | Make deferred costs visible |
| Suppliers and integrators | Implementation, support and documentation | Never delegate the definition of success to them alone |
This distribution avoids confusing execution and responsibility. The first operational responsibility falls to the “Management” function; the “Professionals and users” function provides separate control. The decision is only defensible if each actor knows what it measures, what it authorizes and what it takes back when the accepted limit is crossed. The roles are distinct.
6. Definition: due diligence of an agency or technology service provider
Supplier due diligence verifies, before commitment, the actual capacity to deliver, operate, secure, document and transfer a service within the buyer's constraints.
When faced with a deviation, the exceptions are logged: the definition is therefore operational: it names the components, the desired effect, the indicator and the limit. A reader can quote it without having to reconstruct the meaning from the rest of the page. These mistakes are costly.
7. Why the subject becomes structuring
The sources converge on three terminals: 4 obligations, 1 discovery phase and 6 functions. They do not describe a universal average; they specify thresholds, obligations or operating conditions. In this case, the third source leads to the following operational reading: “Cybersecurity must be linked to governance and enterprise risk. »
This reading transforms the figures into decision questions: what perimeter do they cover, what uncertainty remains and who can act when the measurement goes beyond the accepted threshold? On the due diligence of an agency or a technological service provider, this responsibility determines the desired effect. Control remains human.
8. Compare four levels of engagement
| Level | What it optimizes | Decision criterion | Limit to make visible |
|---|---|---|---|
| Observation without reference measurement | Apparent speed | Describe the service | The result cannot be attributed |
| Narrow-minded pilot | Learning on a flow | Deviation from reference measurement | The tested case may remain too simple |
| Governed deployment | Demonstrated effect on the useful perimeter | The “Check Team” and “Test Method” checks | The recurring cost must remain explicit |
| Reduction or cessation | Control of the main risk | Documented exit threshold | Preserve data, evidence and reversibility |
When it comes to the due diligence of an agency or technology provider, the comparison does not point to a universal winner. It makes visible the cost of an absent proof, an overly simple driver or a premature extension. The right level depends on the criticality of the flow, the quality of “Request evidence” and the concrete possibility of resuming “Test the method”. Nuance matters here.
9. Recommended methodology: seven verifiable steps
Applied to the due diligence of an agency or a technology service provider, the following method is part of good public and operational practice. It is not presented as a proprietary method of Logiks: its value comes from the order of controls and the possibility, for a third party, to verify each deliverable.
9.1. Describe the service
This step transforms intention into control: write result, criticality, data, volumes and expected responsibilities. Measure what actually changes in the truly open decision and the value that justifies it, including human rework. Document everything in a note cadrage which names the decision, the limit and the person responsible.
9.2. Ask for proof
To move forward without hiding the deferred cost, you must review anonymized examples of documentation, testing, incidents and handover. Compare before and after on the initial situation and its variations between segments, then have an initial measurement dated and broken down by useful segment reread by an actor who did not design the test.
9.3. Check the team
Expected action: identify the people actually mobilized, their availability and their replacement. Start on a perimeter where the team can still get back. The expected proof concerns the exceptions encountered by the teams operating the system; record it in a map of exceptions, dependencies and owners.
9.4. Test the method
The work consists first of having the finalists work on a short case with constraints and questions. Do not retain an ideal demonstration or an overall average: observe the limits, the rights of action and the possibility of going back. The useful deliverable is a control matrix that makes cost and reversibility visible.
9.5. Audit the contract
At this stage, ownership, subcontractors, security, SLA, exit and continuity must be addressed. Involve the person who handles the exceptions, then compare the result to the nominal behavior, the failure caused and the quality of the recovery. You must be able to provide a report of the nominal scenario, the failure and the human recovery to a decision-maker absent from the project.
9.6. Talk to references
The action here is to ask customers about the tough times, not just the launch. Run the check on a normal case and a degraded case, keeping the gap between the initial promise and the recorded facts as a criterion. The concrete output takes the form of a file of logs, deviations and decisions readable by a third party.
9.7. Organize the first days 90
This step transforms intention into control: setting onboarding, decisions, indicators and trust review. Measure what actually changes in the threshold that triggers a correction, extension or shutdown, including human rework. Document everything in a review rule with correction and stopping thresholds.
10. Logik tips: proof, mastery and reversibility
Our priority concerns the following risk: a selection based on portfolio, commercial speech and daily price. Start where this fragility already produces an expectation, a loss, or a contested decision; the prestigious perimeter can wait.
From the first test, the scope remains explicit: keep the reference measurement at the level where a team can act. A quarterly average does not replace an observation by course, by cohort or by type of exception; the marker must remain actionable.
Treat “Describe the Service” as a documented decision. A manager, a hypothesis, a limit and a review date are better than an adjustment whose origin no one knows.
Test “Check Team” with “Test Method” and then with a degraded recovery. The test should reveal operation and operating cost, not just confirm that the demonstration holds up.
Only extend the system if the observed facts support the desired effect and if “Request proof” remains controllable by a person outside the project.
In this file, the recommendations express a sequence judgment: make the risk observable, test the hypothesis relating to “Check the team”, then commit the resources. Sophistication comes after the demonstration of the announced effect; it does not replace it. Each step leaves a trace.
11. Decision grid
| State | Signal observed | Expected proof | Cautious decision |
|---|---|---|---|
| To frame | “Describe service” exists without a named result | dated reference measurement | Do not engage the entire perimeter |
| As a pilot | “Request proof” is tested on a real flow | Deviation from starting point | Include a representative exception |
| Governed | “Check Team” has a manager and a review | Stability, cost and incidents | Document degraded mode |
| To expand or stop | “Test the method” allows a decision | Net worth and residual risk | Apply exit rule |
The grid does not automatically produce the arbitrage on the due diligence of an agency or technology provider. On the other hand, it forces teams to show their assumptions about “Describing the service”, their thresholds and their responsibilities; a disagreement is then explicit and can be resolved. The discrepancy deserves an explanation.
12. Frequent errors
12.1. Consolidate activation and result
Enabling “Describe service” does not prove that the expected effect is achieved. This error shifts the debate towards the tool while the decision concerns an observable change.
12.2. Optimize the first available indicator
Depending on the hypothesis chosen, the sample remains representative: a convenient proxy can improve while the decisive measure deteriorates. Link each signal to a decision and a guardrail.
12.3. Ignore exceptions
On the business side, the trace remains auditable: the nominal path often hides the fragility described above. Test a borderline case, a failure and how the team regains control.
12.4. Leave an addiction without an owner
When “Request Evidence” is everyone’s responsibility, no one decides the incident or the cost. Assign the decision before deployment.
12.5. Present risk as a formality
Documenting “Check Team” without patching the system produces facade compliance. The record must show a check performed and its result.
12.6. Extend without exit rule
If “Test the method” does not make it possible to decide, the pilot continues by inertia. Set continuation, correction and termination thresholds in advance.
13. Action Plan 30 / 60 / 90 days
13.1. Days 1 to 30: establishing the starting point
- describe the decision, the scope and the person responsible for it;
- record the initial value of the indicator before any modification;
- inventory dependencies and their exceptions;
- write the main risk and its detection condition.
In current operations, the convincing element remains linked to the decision: the first phase serves to make the disagreement visible. At thirty days, management must know the baseline measurement, the missing data and the specific case on which progress will be judged.
13.2. Days 31 to 60: testing the critical path
- implement primary control over a representative flow;
- test the recovery in a normal then degraded situation;
- record errors, human interventions, delays and costs;
- compare the observations to the initial scenario.
At each check, the date of the source is verified: this pilot does not only seek to demonstrate that the technology works. It must establish whether the system advances the selected indicator without shifting a disproportionate burden towards the operation, users or a supplier.
13.3. Days 61 to 90: decide and organize the continuation
- consolidate the evidence and have its limitations reread;
- assign each recurring control to a named function;
- confirm the next review date and discharge procedure;
- extend only if the facts support the effect initially announced.
In degraded mode, the observed field remains stable: at ninety days, the initial hypothesis must be demonstrated or refuted. Three decisions remain legitimate: extend, correct or stop the perimeter; continuing without a threshold does not constitute a fourth option.
14. FAQ
14.1. How to define the due diligence of an agency or a technological service provider?
This is a decision-making framework applied to the due diligence of an agency or technology provider. The approach links “Describe the service” to the “Check the team” and “Test the method” controls, with a baseline measurement, responsible people and an exit rule.
14.2. What to start with?
Under real constraint, residual risk is accepted: start with a real decision, a reference measurement and an already observed manifestation of the main risk. The tool comes after this cadrage.
14.3. What budget should be retained?
During the cadrage, the incident is subject to a review: add preparation, integration, operation, control, training, incidents and exit. Compare this full cost to the expected value, not just the license or campaign price.
14.4. How long should the test last?
The test must cover a full cycle of the measurement and at least one exception related to “Check Team”. Its duration derives from this observation, not from an arbitrary standard.
14.5. When to scale?
Scale up when progress remains stable, “Test the Method” is controlled, and responsibilities, costs, and exit conditions are documented.
15. Conclusion
When the pilot is launched, the initial value remains accessible: the decision is solid when a common measure links the technical, business and financial choices. The number of options activated is less important than the ability to explain discrepancies, deal with exceptions and reverse a choice that has become costly.
The pivot is simple: the “due diligence of an agency or a technological service provider” must no longer be a project to be delivered, but a capacity to govern to produce the announced effect. Deferred cost exists.
16. Main sources
- GOV.UK — Choose the right tools and technology — consulted on 11 July 2026 — public digital services, transposable principles.
- GOV.UK — Commercial off-the-shelf products — updated to 2025 — purchasing technologies and services.
- NIST—Cybersecurity Framework 2.0 — 26 February 2024 — organizations of all sizes.
- ANSSI — Cloud recommendations — accessed on July 11 2026 — IaaS, PaaS and SaaS.
- FinOps Foundation — FinOps for SaaS — accessed 11 July 2026 — expenditure governance SaaS.