Resources · 70

Digital services: compare total cost and cost per outcome

Include migration, operation, quality, support and exit in an explicit comparison.

· 3 min

Empty intelligence archive with dossiers and maps AI-generated editorial illustration

What this guide helps achieve

  • Define a useful unit
  • List cost components
  • Compare scenarios
  • Include exit and reconcile

Quick check

  • Is the useful outcome defined consistently?
  • Which costs remain unknown?
  • Does the scenario include commitments and exit?

Step-by-step method

  1. 01

    Define a useful unit

    Choose a service-related unit: completed order, handled case or active user. Describe required quality and availability. Cheap requests can conceal unnecessary calls and manual recovery.

    Deliverable: business-unit definition.

  2. 02

    List cost components

    Separate initial, recurring and variable costs. Include integration, migration, training, monitoring, support, storage, transfers and maintenance. Record source and date for assumptions without inventing universal prices.

    Deliverable: cost register.

  3. 03

    Compare scenarios

    Calculate a baseline, increased volume and reduced demand on the same horizon. Review minimum commitments and tiers. Retain unknown components instead of silently treating them as zero.

    Deliverable: scenarios and sensitivity.

  4. 04

    Include exit and reconcile

    Estimate export, replacement, transition and necessary retention. Compare assumptions with invoices and actual service volume. Explain differences by volume, price, quality or scope, then reassess the decision.

    Deliverable: reconciliation and dated decision.

Acceptance case to reproduce

Fictional example: these inputs describe no customer or observed result.

View case inputs
{
    "currency": "EUR",
    "period_months": 12,
    "costs": {
        "service": 80,
        "integration": 20,
        "operations": 30,
        "exit": 10
    },
    "accepted_outcomes": 70,
    "total": 140,
    "cost_per_accepted_outcome": 2
}

Expected decision

The scenario costs EUR 140, or EUR 2 per accepted outcome; retain the period and assumptions.

Fictional variations to test

190 EUR funds 100 runs, but only 95 are accepted.

Cost per accepted result is 190/95 = 2 EUR. Dividing by 100 gives 1.90 EUR per attempted run.

300 EUR fixed plus 1 EUR per use: volume doubles.

At 100 uses, unit cost is 4 EUR; at 200, 2.50 EUR. This decrease comes from volume, without a price discount.

Two teams each count the entire shared cost.

Define an allocation rule. The shares must sum to the shared cost without counting the same expense twice.

Evidence to retain

  • Period, currency and accepted-result definition.
  • Fixed costs, variable costs and scenario volumes.
  • Allocation rule and shared-cost reconciliation.

Verification procedure

  1. Fix period, currency and accepted-outcome definition.
  2. Add integration, operations and exit costs.
  3. Keep assumptions and the accepted-outcome denominator.

FinOps Foundation — Unit Economics

Reusable worksheet

Complete with your authorised observations. These fields are a working template, not observed results.

FieldInformation to record
UnitUseful outcome, quality and period
ComponentFixed or variable, source, date and assumption
ScenarioVolume, commitment, exit and unknowns

Worked example

Illustrative situation

Fictional example: a service charges little per request but often requires manual recovery.

Decision and expected evidence

The team measures cost per correctly completed case, includes recovery time and tests a volume scenario before committing.

Distinguish the mechanisms

MechanismPurposeCheck or limitation
Advertised priceUnderstand a billing unitMay exclude integration and operation
Total costCompare services on a common horizonDepends on explicit components and assumptions

Management indicators

IndicatorWhat it measuresFirst action
Cost per useful outcomeIncluded costs divided by conforming outcomesDocument numerator and denominator
Forecast/actual differenceCost difference on comparable scopeExplain volume, price and recovery

Common pitfalls

  • Treat unknown costs as zero
  • Compare offers on different horizons

Frequently asked questions

Is there a standard cost per user?

No: scope, volume, availability and the user definition change the calculation. Use documented components.

Does an unknown cost equal zero?

No. Record the unknown, an owner and, where useful, a justified range.

Is unit cost enough to choose?

No. Compare quality, risk, continuity and exit capability: services may deliver different outcomes.

Official references

References consulted: . The method and worksheet propose checks to adapt to your context; they do not constitute certification.