Financial Model Review with Claude Code: API Runtime Pattern
A production playbook for financial model review in cross-industry operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Finance and strategy teams
The problem
Finance and strategy teams need financial model review to run repeatedly against spreadsheets, assumptions, source docs, and board materials. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the financial model review instructions as a skill, send spreadsheets, assumptions, source docs, and board materials as run-scoped inputs, execute with Claude Code, poll terminal status, and consume argo.result.v1 instead of parsing a transcript.
Tradeoffs and failure modes
The API boundary forces the workflow to define inputs, terminal states, and result shape before customers depend on it. For financial model review, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Run request
POST /api/skills/<skill_id>/run
provider=claude-code
workflow=financial-model-review
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo