Draft — not for publication. Every figure is an unfilled placeholder. The argument is
publishable; the numbers are not, until each carries a source and a date.
The transition nobody plans for
A pilot is judged on whether the output looks impressive. A production system is judged on what
happens on a bad day. Almost every difficulty in moving from one to the other comes from that
change of question, and almost no pilot budget accounts for it.
What a production budget contains that a pilot budget does not
Evaluation. A held-out set of real cases with known-correct outcomes, maintained as the
business changes. Without it there is no way to tell whether a prompt change helped.
Human review, permanently. A standing share of outputs read by a person. This is a running
cost, not a launch cost, and it is the first line cut when the system appears to be working.
Monitoring and a rollback path. Traces of what was retrieved and decided, alerts on
distribution shifts, and a way to revert to the manual process within the hour.
Corpus maintenance. Documentation, rubrics and policies go stale. Whoever owns them needs the
time to own them.
Access and audit. Least-privilege credentials, retention rules for run logs, and an answer to
"who saw this data" that survives an audit. Typical share of total cost across these lines: [PLACEHOLDER — verify before publishing]
Why the second workflow is cheaper than the first
The first production workflow pays for the whole platform: identity, logging, evaluation
harness, review tooling, deployment. The second pays for itself only. Teams that budget the
second like the first conclude that automation is expensive; teams that budget the first like the
second run out of money before launch. Observed ratio between first and subsequent workflow cost:
[PLACEHOLDER — verify before publishing]
How to phase it
- Pick a workflow with a measurable current cost. If you cannot measure it now, measure it for
a month before building anything.
- Build the evaluation set before the workflow.
- Shadow-run against the manual process and compare, rather than cutting over.
- Cut over on one segment, keep the manual path warm.
- Only then treat the platform pieces as reusable and start the second workflow.
The question to ask before funding
Not "what will this save" but "what will we do differently when it is wrong". A budget with no
answer to the second question is a pilot budget wearing a production label, whatever the figure
at the bottom of it.