How it works

The six-week sprint.

One workflow. Two numbers. A first version running inside your environment.

Everything an AI decision needs. In six weeks.

  1. 1 · Find
  2. 2 · Numbers
  3. 3 · Decide
  4. 4 · Build
  5. 5 · Checks
  6. 6 · Readout
  1. Week 1 of 6

    Find the workflow

    Workflow shortlistExample
    WorkflowVolume per monthMinutes eachCandidate
    Invoice exceptions 4,000 11 First
    Support ticket triage 9,000 2 Yes
    Vendor onboarding checks 300 25 No
    Contract clause lookup 150 40 No
    Expense report coding 1,200 3 No

    Example data. Candidate: value at least 3 times run cost, on the calculator's numbers.

    Five candidates on one page. One goes first.

  2. Week 2 of 6

    Put the two numbers on it

    Sample output

    From the calculator

    What it is worth
    $28,600 per month
    What it costs to run each month
    $2,432
    Example: invoice exceptions, 4,000 per month, 11 minutes each Computed by the calculator's own model. Its defaults fill the rest: $65 loaded cost per hour, 60% of the step, 18,000 tokens per run. An estimate, not a quote.

    Value and monthly run cost, from the week 1 row. Before anything is built.

  3. Week 3 of 6

    Decide

    One-page business caseExample

    Workflow

    Invoice exceptions

    Value$28,600per month

    Run cost$2,432per month

    Fund

    Example. The week 2 numbers, on one page. Fund: value at least 3 times run cost. An estimate, not a quote.

    One page. Two numbers. The stamp.

  4. Week 4 of 6

    Build the first version

    Run logExample
    DateItems processedExceptionsCost that dayChecks
    Mon 176 9 $19.01
    Tue 191 12 $20.63
    Wed 184 7 $19.87
    Thu 203 14 $21.92
    Fri 188 8 $20.30
    • Audit trail written
    • Evals passed
    • Data stayed in tenant
    • Exceptions sent to a person

    Example week. Cost that day is tokens at the calculator's defaults.

    Every day logged: items, exceptions, cost. Checks visible.

  5. Week 5 of 6

    Build the first version: the checks

    Handover checklistExample
    • Eval suitehow we know it works, run before and after every change
    • Model cardwhat the system does, what it must not do, and its limits
    • Control mappingeach control traced to the policy or framework it satisfies
    • Rollback planhow to turn it off in minutes without losing data
    • Runbookthe finance or ops team runs it without us
    • Software bill of materialsevery dependency pinned and listed

    The list is real: it ships with every engagement. The ticks are the example.

    Six checks ship with the build. Your team runs them.

  6. Week 6 of 6

    Readout

    Monthly readoutExample
    Value promised
    $28,600
    Value measured
    $26,741

    94% of the promise, on 3,740 items that month.

    Run cost: $2,432 promised, $2,404 measured.

    Example month. Measured figures run the same model on the items that arrived.

    The number the board sees each month: promised against measured.

What you keep

  1. 01 Your data (stays in your tenant)
  2. 02 Governance and audit trail
  3. 03 The workflow build
  4. 04 The two numbers and the model behind them
  5. 05 The monthly readout

All of it is yours. Code, model, figures.

Three shapes

01

AI Review

A CEO or board that has been asked for an AI plan.

  • A business case
  • A run-cost forecast
  • A ranked roadmap
  • A written recommendation on what not to build

Runs: 30 days.

Talk to Korey

02

Fractional Chief AI Officer

A company that needs an AI executive at the table now and is not ready to hire one full time.

  • An AI strategy tied to your P&L
  • The first production system live with its run cost known
  • Governance your board can sign off on
  • A team that can carry it forward without me

Runs: Monthly, reviewed each quarter.

Talk to Korey

03

Diligence Advisory

Boards, investors and operating partners who need an independent read before the money moves.

  • An independent view of an AI plan, a vendor or a portfolio company's claims
  • The diligence questions that separate a working system from a demo
  • A portfolio map of where AI creates value and where it burns cash

Runs: Monthly, with a standing seat at the review.

Talk to Korey

Not sure which shape fits? Bring the workflow you're arguing about and we'll pick in 30 minutes.

Who it's for

Operating partners

  • One view of value and run cost, company by company.
  • Leadership teams in each company that can carry it forward.

Portfolio company CEOs and CFOs

  • A business case with the run cost known before the first invoice.
  • A first version running in your environment, and one number to report each month.

Deal teams in diligence

  • An independent read on an AI plan, a vendor or a company's claims before the money moves.
  • The questions that separate a working system from a demo.

See it on your workflow.