Skip to content
InovagioInovagio

Scoreboard

Every result and every dollar, measured the same way.

The measures every customer sees, how each is counted, and the method behind the work. Your finance and security teams can check all of it.

Task record · invoice INV-2041

Chain verified

  1. 09:14:02Intake workerRead vendor invoiceintake.read · first entry → #d635
  2. 09:14:09Match workerMatched purchase order and receiptpolicy.check · #d635 → #d4a2
  3. 09:14:11Policy engineAbove approval limitapproval.required · #d4a2 → #d30f
  4. 10:02:47ControllerApproved paymenthuman.approve · #d30f → #d17c
  5. 10:02:48LedgerTask closed · cost recordedledger.seal · #d17c → #cfe9
A task record: every step, its rule and its cost (example company)

The measures

What every customer sees, defined.

MeasureWhat it countsWhy it matters
Time to first correct taskDays from the signed charter to the first task done correctly on live work, every delay includedHow long it takes to start, every delay counted
Cost to first correct taskOur delivery cost plus your team’s time, estimated from logged approval sessions and labeled as an estimateThe setup cost, honestly counted
Delays, by causeDays lost to audit review, legal, access, competing priorities, absent experts and our own defectsWhere the time really goes
Cost per correct taskThe AI and the services it calls, the platform’s share, and every minute your people spend on the work (reviewing, deciding exceptions, checking the audit sample and fixing what was wrong) at your rates for each role, plus the cost of errors that got through, divided by the tasks done correctly; monthly, against today’s cost counted the same wayThe headline number, trending
First-pass successShare of tasks done correctly without a personHow much work it takes on
Needs-a-person rateShare of tasks sent to a person, and the share that became an approved rule within 30 daysThe rulebook’s growth
Rules approvedCount, and the median days from draft to approvalWhether the interviews work
Stop drillsDate and time taken to stop each Virtual Employee and each departmentThe security team’s number
Model familyThe open-model family each role runs onWhere the model came from, answered up front

We publish the method, never your data.

  • The interview method

    How our agents interview your people about the work, and who approves what they write down.

  • The rule format

    What a rule contains, how it is versioned, and how a correction becomes one.

  • Shadow mode and go-live

    How a Virtual Employee moves from working beside your team to the routine queue, one kind of case at a time, and takes on more as its results hold up, through approved rule changes. Each customer sets its own go-live bar.

  • The security model

    Identity, the gateway, checked plans, approvals and your rules, in plain words.

Every task leaves a receipt.

Each task records who did it, the checked plan, the model, the cost, the time, the rules it ran under, what it touched and the outcome. The record is tamper-evident, and the scoreboard is a view of the same data your own screen shows.

  • Your numbers, unadjusted

    Results come from the task records with your own rates, de-identified, and never adjusted by hand. A missing or bad number is flagged.

  • Published with consent

    Results are published only with your written consent, under your industry and size, never your name unless you choose.

  • Better models, shown

    When a role moves to a newer model, cost per correct task and first-pass success are shown before and after, on the same rulebook.

See these numbers for one of your workflows.

We work out what the work costs today, set the measures in the charter your sponsor signs, and report them every month.