Five-Step AI Workflow with Human Oversight
Each step shows the workspace, what the AI completed, and what still needs human review.
Steps 3 and 5 need a person. Step 3 is waiting for approval right now. Click it to open the full walkthrough.
Estimates are directional and based on stated assumptions. All names, organizations, and identifying details have been anonymized in accordance with our confidentiality agreements.
How a Growth-Stage Technology Company Built Data Entry That Learns from Each Day's Corrections
Every document that reaches operations, from the moment it arrives to the moment its record sits confirmed in the ERP or the CRM. The agents sort, read, enter, check and post; a person sees only the fields the agents doubted and the rules that would change how tomorrow's documents get read. Five stations, run as a loop: the corrections station 5 counts today change how station 2 reads and station 1 holds tomorrow.
What Was Broken
What We Built
Five stations and 10 subagents. Each subagent carries its own tasks and its own refusal.
How It Runs
Document Intake
Nobody is asked anything hereAgents collect every document off every route, name what each one is from its own pages, merge the ones that arrived twice, and hold anything that cannot be read or trusted. Nothing waits on a person here. A held file is never guessed at and never deleted; it waits, named, until somebody frees it.
Data Entry
Nobody is asked anything hereAgents read every page, tables and handwriting included, fill each field of the record with a confidence score on it, and leave honestly blank any field the pages never state. Nothing waits on a person here. A blank field with a reason beats an invented value that survives into the ERP.
Record Checking
A person answers hereAgents run every record through its checks: totals against line items, required fields, the match against the order. What passes moves on; what the agents doubted waits here for a person, with its page marked. This is where a person works. Everything else exists so that twelve fields, not two hundred documents, reach this screen.
System Posting
Nobody is asked anything hereAgents match each cleared record onto the fields the ERP or the CRM actually has, post it, and write the target's own confirmation number back onto the record. A record the target has no place for is held, not forced. Nothing waits on a person here. A record is posted when the target system says so, never when the export script finishes.
Daily Close
A person answers hereAgents check every document that arrived today against where it ended, keep the trail behind each one, and propose the reading and checking rules that would have stopped today's corrections. A person accepts or rejects each rule. A person decides here. How a document gets read and what counts as a passing check is not something an agent changes quietly.
Where a Person Decides
Operating Model
This changes how work flows through the team.
What Transfers, What Must Be True
Failure Modes
What breaks this pattern:
When nothing holds a locked or unreadable file, the agent skips it and moves on. The invoice inside was never recorded, so nobody knows to ask where it went.
When nothing refuses to fill a field the pages do not state, the agent fills it with its best guess. The guess posts to the ERP and nobody can tell it from a value a person typed.
When nobody waits for the target system to confirm, the export script's clean exit becomes the proof. A record can be marked posted, missing from the ERP, and closed everywhere anyone would look.
When nothing flags a document that is neither posted nor held, it can end the day in no queue and on no report. The gap surfaces weeks later as a payment nobody made.
Directional Outcomes
What the agent counts, and the station that counts it.
These counts are the tallies from one monitored run of the agents. They are not monthly or annual totals.
What Runs Where
Every step names the subagent that does the work, the record it writes, the thing that raises a question for a person, and what it is allowed to touch. This is drawn from the source, not from a diagram somebody kept in sync by hand.
doc-arrivalsdocs/arrivals/<doc-id>.jsonhold-unreadable-filedocs/arrivals/**, docs/held/**, the mailbox and upload folder read-onlyread-and-filldocs/records/<doc-id>.jsonfield-below-confidencedocs/records/**, docs/arrivals/** read-onlycheck-and-queuedocs/checked/<doc-id>.json, review/queue/<doc-id>.jsonawait-your-readdocs/checked/**, review/**, everything else read-onlymap-and-postexport/posted/<doc-id>.jsonhold-unmapped-fieldexport/**, docs/checked/** read-onlyclose-and-learnrules/proposed/<rule-id>.json, reports/docs-<date>.jsonaccept-rule-changerules/proposed/**, reports/**, the day's records read-onlyStack
Every system this agent reads or writes.