UK-based independent AI efficiency projectEvidence before claims ยท 2026

Cost per Verified Job: The Denominator Comes First

EVIDENCE GAP ยท COST RESULT UNKNOWN

Cost per Verified Job: The Denominator Comes First

A long-scroll visual companion to the article. It summarizes the articleโ€™s evidence boundary and method; it does not extend the underlying result.

At a glance

Cost per Verified Job: The Denominator Comes FirstFour-step visual: MATCH BILLING WINDOW; CAPTURE FULL USAGE; COUNT ACCEPTED JOBS; CALCULATE OR UNKNOWN. Account-wide activity and the complete accepted-job denominator are not established. Synthetic harness outcomes do not establish production usage.EVIDENCE GAP ยท COST RESULT UNKNOWN1MATCH BILLING WINDOW2CAPTURE FULL USAGE3COUNT ACCEPTED JOBS4CALCULATE OR UNKNOWNEvidence labels and limits travel with the visual.
A plan charge divided by one observed local result is not a defensible per-job cost when periods and denominator are incomplete.

Evidence in scope

  • ยฃ89: user-recorded on 2026-10-02
  • Billing window: UNKNOWN
  • Complete account-period job denominator: UNKNOWN

Evidence boundary: Account-wide activity and the complete accepted-job denominator are not established. Synthetic harness outcomes do not establish production usage.

How to use the diagram

Match invoice period, account-wide usage, retries, independently accepted jobs, service costs, and human time before dividing.

What this visual explains: A plan charge divided by one observed local result is not a defensible per-job cost when periods and denominator are incomplete.

What it does not establish

Allowance burn, total account jobs, 5-vs-8 comparison, cost/job, and plan value remain unknown.

โ† View article ยท Return to source article