Total Cost of Ownership (TCO)

Total Cost of Ownership is what a purchase actually costs an organization across its full life, not just the price on the invoice for a single unit. Applied to identity verification, TCO is the honest question a buyer comparing vendors should be asking instead of Cost Per Verification alone: not "what does one check cost," but "what does verifying this population of users cost over the period we'll actually be doing it", onboarding checks and every mandated refresh included, not just the first one.

Where it comes from

Gartner analyst Bill Kirwin coined Total Cost of Ownership in 1987, originally to argue that a personal computer's purchase price was a small piece of what it actually cost a business to own and run, support calls, downtime, training, and administration added up to far more than the sticker price implied. The same logic, sticker price is not total price, generalizes cleanly to any recurring-cost vendor relationship, identity verification included, and that's the only sense in which this entry uses "TCO": the general method, not a Gartner-branded product Solidus has any relationship with.

The worked example, done honestly

Take Solidus's own published, illustrative figures at face value: a first KYC Level 2 check at $5.00, and a reuse event at $0.05 (the low end of its own reuse-pricing band), against an incumbent charging a flat $1.50 per check regardless of whether it's the first or the fifth. Solidus's cumulative cost after the first check plus n reuse events is 5.00 + 0.05n; the incumbent's cumulative cost for the same n + 1 total checks is 1.50 × (n + 1). Setting them equal and solving: the two lines cross at n ≈ 2.4, meaning Solidus's running total drops below the incumbent's somewhere between the person's third and fourth total identity check, assuming every reuse event after the first actually reuses the credential instead of re-scanning.

That's the real crossover, not a rounded-up marketing number, and it comes with three honest qualifiers a TCO comparison has to carry or it's dishonest. First, these are Solidus's own draft, non-final prices, not a signed contract with anyone. Second, the crossover assumes a functioning reuse loop, see Credential Reuse Rate, which has not been demonstrated in production with a real relying party. Third, it compares only the per-event fee line; it doesn't include integration cost, switching cost, or the value of certifications (SOC 2, ISO 27001) that some incumbents hold and Solidus does not, which a real procurement TCO would have to weigh alongside the per-check math.

What a real buyer TCO should also include

The per-event crossover above is the easy half of a real TCO analysis. The harder half, integration engineering time, vendor switching cost (see Vendor Lock-In), compliance and certification gaps a buyer's own auditors will ask about, and the uncertainty premium of relying on a testnet-stage, unaudited, no-paying-customer vendor versus an incumbent with thousands of customers and a decade of production history, isn't captured in a per-event formula at all, and no honest TCO comparison should pretend otherwise.

See also

Cost Per Verification and Re-verification Cost are the two inputs to the worked example above. Credential Reuse Rate is the unproven assumption the crossover depends on. Vendor Lock-In names the switching-cost half of TCO this entry doesn't quantify.