Build, buy or SaaS en 2026: decide without underestimating the total cost

The topic “Build, buy or SaaS” must lead to proof, not just deployment: the expected effect must be measurable and reversible.
Frame the “Define Capability” point, control the “Measure Differentiator” point, then decide with an explicit baseline measure.

1. Key figures

These benchmarks limit the decision to the build, buy or SaaS decision; 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 perimeter is authentic.

When an arbitrage is contested, exceptions are logged: for this topic, the first source leads to the following operational reading: “The purchase price is not enough to compare two technology 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

In the presence of a third party, the stopping rule is known: a source is useful when a reader simultaneously understands what it asserts, 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 build, buy or SaaS decision”, 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 “Define capacity” 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 compromise appears clearly.

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 decision can be reviewed.

2.3. Bench 3

FinOps Foundation — FinOps for SaaS documents “allocated 100 %”. The exact range is shown in the previous table; keep it when comparing this data to your own operations, populations and periods. The measurement precedes arbitrage.

2.4. Benchmark 4

FinOps Foundation — Technology Categories provides the hint “90 %” here. This information informs a choice; it does not, by itself, demonstrate that the same effect will appear in your context. The roles are distinct.

2.5. Bench 5

The NIST CSF reference 2.0 — Informative references publishes “ID.AM-04”. Before making a decision, check the date, the population covered and the possibility of replicating the measure locally. These mistakes are costly.

3. Reusable citation sheet

Because the context evolves, the next deadline is planned: a robust citation must be able to be used 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.

4. Introduction: framework the primary risk

The SaaS seems rapide, the tailor-made seems differentiating and the purchase of license seems manageable. However, each option hides a different type of cost. Comparison often stops before data, exploitation and output. Build does not mean complete ownership if the critical bricks remain external. SaaS does not mean absence of organizational maintenance.

The British Service Standard emphasizes total cost and ability to change. A good decision minimizes the cost of the wrong choice as much as the price of the right scenario. Control remains human.

5. Actors and responsibilities

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. Nuance matters here.

6. Definition: build, buy or SaaS decision

The build-buy-SaaS decision compares a developed capacity, an acquired product and an operated service according to differentiation, total cost, time, risk, data, skills and reversibility.

During the review, the local verification can be reproduced: 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. Each step leaves a trace.

7. Why the subject becomes structuring

The sources converge on three terminals: 4 obligations, 1 discovery phase and 100 % allocated. They do not describe a universal average; they specify thresholds, obligations or operating conditions. In the present case, the third source leads to the following operational reading: “A license without an owner or economic unit becomes rapily invisible waste. »

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 build, buy or SaaS decision, this responsibility conditions the desired effect. The discrepancy deserves an explanation.

8. Compare four levels of engagement

Regarding the build, buy or SaaS decision, the comparison does not indicate 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 “Measure the differentiator” and the concrete possibility of repeating “Evaluate the options”. Deferred cost exists.

9. Recommended methodology: seven verifiable steps

Applied to the build, buy or SaaS decision, the following method is 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. Set capacity

The work consists first of describing the business result without presupposing the product. Do not retain an ideal demonstration or an overall average: observe the truly open decision and the value that justifies it. The useful deliverable is a memo cadrage which names the decision, the limit and the person responsible.

9.2. Measure the differentiator

At this stage, we must separate convenience, specific process and competitive advantage. Involve the person who handles the exceptions, then compare the result to the initial situation and its variations between segments. You must be able to provide an initial measurement, dated and broken down by useful segment, to a decision-maker absent from the project.

9.3. Encrypt the life cycle

Here the action is to include integration, support, security, data, migration and exit. Run the check on a normal case and a degraded case, keeping the exceptions encountered by the teams operating the device as a criterion. The concrete output takes the form of a map of exceptions, dependencies and owners.

9.4. Evaluate the options

This step transforms intent into control: compare build, buy, SaaS and hybrid with same scenarios. Measure what actually changes in boundaries, action rights, and rollback ability, including human takeovers. Document everything in a control matrix that makes cost and reversibility visible.

9.5. Test the actual product

To move forward without hiding the deferred cost, you must use representative data, roles, volumes, and exceptions. Compare before and after on the nominal behavior, the failure caused and the quality of the recovery, then have an account of the nominal scenario, the failure and the human recovery reread by an actor who did not design the test.

9.6. Negotiating reversibility

Expected action: Fix export, API, notice, exit assist and delete. Start on a perimeter where the team can still get back. The expected proof relates to the discrepancy between the initial promise and the recorded facts; record it in a file of logs, deviations and decisions that can be read by a third party.

9.7. Decide with review date

The work consists first of documenting hypotheses and triggers for re-examination. Do not retain an ideal demonstration or an overall average: observe the threshold that triggers a correction, an extension or a stop. The useful deliverable is a review rule with correction and stopping thresholds.

10. Logik tips: proof, mastery and reversibility

Our priority concerns the following risk: the ancrage on the initial price or on the preference of the service provider. Start where this fragility already produces an expectation, a loss, or a contested decision; the prestigious perimeter can wait.

Between two reviews, the initial value remains accessible: 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 “Define Capacity” as a documented decision. A manager, a hypothesis, a limit and a review date are better than an adjustment whose origin no one knows.

Experience “Encrypt the Lifecycle” with “Evaluate Options” 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 “Measuring the differentiator” remains controllable by a person outside the project.

In this file, the recommendations express a judgment of sequence: make the risk observable, test the hypothesis relating to “Encrypt the life cycle”, then commit the resources. Sophistication comes after the demonstration of the announced effect; it does not replace it. This border matters.

11. Decision grid

The grid does not automatically produce the arbitrage on the build, buy or SaaS decision. On the other hand, it forces teams to show their assumptions about “Define Capacity”, their thresholds and their responsibilities; a disagreement is then explicit and can be resolved. The calendar serves as proof.

12. Frequent errors

12.1. Consolidate activation and result

Enabling “Set Capacity” 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

As long as doubt remains, the threshold has an owner: a convenient proxy can advance while the decisive measure deteriorates. Link each signal to a decision and a guardrail.

12.3. Ignore exceptions

If the measurement diverges, the sample remains representative: the nominal path often masks 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 “Measuring the differentiator” 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 “Encrypt the life cycle” without correcting the system produces facade compliance. The record must show a check performed and its result.

12.6. Extend without exit rule

If “Evaluate Options” does not make a decision, the pilot continues through 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.

When a dependency changes, the trace remains auditable: 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.

Faced with a gap, the residual risk is accepted: 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.

Once the baseline has been established, the incident is subject to a review: 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 build, buy or SaaS decision?

This is a decision framework applied to the build, buy or SaaS decision. The approach links “Define Capacity” to the “Costume Lifecycle” and “Evaluate Options” controls, with a baseline metric, responsible parties and an exit rule.

14.2. What to start with?

Without a designated owner, the scope remains explicit: start with an actual decision, a baseline measurement and an already observed manifestation of the main risk. The tool comes after this cadrage.

14.3. What budget should be retained?

On the critical path, the source date is checked: 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 “Encrypt the life cycle”. Its duration derives from this observation, not from an arbitrary standard.

14.5. When to scale?

Scale up when progress remains stable, “Evaluate Options” is controlled, and responsibilities, costs, and exit conditions are documented.

15. Conclusion

At the next milestone, the convincing element remains linked to the decision: 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 project “the build, buy or SaaS decision” must no longer be a project to be delivered, but a capacity to govern to produce the announced effect. The outing is prepared early.

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.
• FinOps Foundation — FinOps for SaaS — accessed 11 July 2026 — expenditure governance SaaS.
• FinOps Foundation — Technology Categories — 2026 — international community FinOps.
• NIST CSF 2.0 — Informative references — accessed on 11 July 2026 — asset management and suppliers.