A process nobody automated is usually a process nobody wrote down. It runs on a Thursday because somebody remembers that it has to, and it breaks the week that somebody takes leave. Executives ask which department to automate first. The useful question is narrower: which of our processes even has the shape that automates?
Manual Document Work
How Do You Automate a Business Process
That Is Still Run by Hand?
One shape automates. How to recognize it in five minutes, and which page settles each workflow you name.
Built from real buyer questions in our sales meetings
Direct Answer
One shape automates, and you can spot it from across the room. A document goes in. A person applies a rule that already exists somewhere — a template, a playbook, an answer approved last quarter. A document comes out. There, an assistant grounded in your own corpus takes over the searching and retyping; the judgment stays with your people. Iternal builds AirgapAI to answer over a selected data set on the machine itself, and states that a Word or PDF template is all the AI needs to populate the content.
The limit: the automation stops at both ends. What gets automated is the finding and the drafting. Iternal is direct that its tooling does not today publish into a customer’s own execution layer or agent library, and that it does not remove the need for a separate data-federation and data-management engagement before any of it runs. The systems work in front and the acting on the output behind both stay yours; a workflow whose cost sits there will not get cheaper here.
Keep the acceptance decision on a named desk. Iternal advocates a human in the loop for a practical reason: generated output gets numbers and chart types wrong. Three things belong on paper before you buy — which of your material a pipeline reads as files, what the preparation work costs, and whose name goes on the output. The questions further down put each in writing.
Testing a workflow and choosing one are different jobs. The four questions below start from a workflow you have already named as the thing eating your week. Where AI applies at all, and which candidate to prove first, is a separate decision. For more information visit the use-case selection page.
Document In, Known Rule, Document Out
Break a hand-run document process into four moves and the economics separate cleanly. Three are index work. The fourth is a decision somebody is accountable for. Software is good at the first three and has no standing to make the fourth.
Step 01
Find the material
The pages already exist somewhere in your estate. Retrieval over a prepared corpus
replaces the hunt.
Automates
Step 02
Pull out what matters
Terms, dates, thresholds, the paragraph that answers the question — with the
source behind it.
Automates
Step 03
Write it into your format
Your own document structure, populated — rather than text stranded in a chat
pane.
Automates
Step 04
Accept it
Somebody reads the draft, owns the number, signs the page. Iternal always wants a
human in the loop.
Stays with a person
Read the diagram as a budget. The saving comes out of steps one to three, where the hours are; step four is why it survives an audit. Automate all four and you buy a quarter of speed for a year of explaining.
Business Process Automation With AI: What It Does and What Goes First
Business process automation with AI applies a language model to the document steps of a process your people run by hand: finding the source material, pulling out what matters, and drafting it into your own template. It automates the searching and the retyping, not the approval, and it starts with work that already produces a document.
What changed is the input, not the ambition. Rule-based automation has always been able to move a record between two systems when the fields line up; the platforms that do that well are mature and worth keeping. What they could never read was the unstructured half of the estate — the specification, the executed agreement, the policy PDF, the last bid response — because there was no field to map. A retrieval layer over your own corpus reads that half, which is why work that was quoted as impossible five years ago is now a scoping question. The step that makes it work is intelligent document processing — turning those raw files into clean, retrievable units before any assistant reads them.
What goes first is decided by three properties, not by department. The process is fed by files rather than a live system call. The rule it applies is already written down somewhere — a template, a playbook, an answer approved last quarter. The thing it produces is a document in a format you control. Where all three hold, the test further down returns a clean automate; where one is missing you get the search back and write the rule down before the drafting follows.
Four document-heavy processes carry most of the hours. Executed agreements nobody can query across are settled on the contract portfolio page. Bid responses assembled from scattered approved language are settled on the proposals and RFP page. Outside requests with a legal deadline are settled on the records and evidence page. Numbers assembled into a dated document — including invoice and accounts payable automation — are settled on the reporting and back-office page. Each one names its own inputs, its own failure mode and the point where a person signs.
Three Complaints That Are One Complaint
Buyers bring this job to us in three tempers. Each blames a different department. Each describes the same missing capability.
The process that has to be run by hand every time. The most frequently raised of the three, and it arrives with an error rate attached. Buyers described an offshore team retyping service requests into a procurement system, and bills of material arriving as a PDF to be retyped into internal templates.
The day spent searching your own documents. Close behind, and expensive because it lands on senior people. An engineer reads a document that references twenty further documents, hunting the mismatches between them. Engineers, one buyer said, have to guess how the content is worded in order to find it.
The same basic questions, answered by hand, all day. Staff walk down the corridor and ask HR or finance something simple; turnover restarts the cycle every quarter. One IT leader named the trap: because his team designed every process, his team became the subject-matter expert desk for the whole company.
What all three share. A person is being used as the index: the answer already sits in a file you own, and a salary is paid to walk somebody to it.
The Five-Minute Test: Automate, Partly, or Leave Alone
Pick the workflow that annoys you most and answer four questions about it. The answers are observable rather than strategic, which is why the test takes five minutes and an offsite takes two days to reach a worse one.
- Does the work start with files? Documents, drawings, forms, exports, attachments. AirgapAI works with files rather than querying databases, so a workflow fed by a live system call is a different project.
- Is the rule already written down? A template, a playbook, a policy, an approved answer. If the rule lives only in one head, you can still automate the finding — the drafting will need that head first.
- Does a document come out, and do you own the format? Hand over the Word or PDF template and the output shape stops being a negotiation.
- Who accepts the result, and what happens when it is wrong? Name the person before you name the tool. Where the output reaches a customer, a regulator or a ledger, that name is what makes the rest defensible.
Automate
Files in, a written rule, a template you own, a named acceptor. Automate steps one to three; staff the read-through.
Partly automate
Findable material, but no written rule or no house format. Take the search off your people now; write the rule down before the drafting follows.
Leave alone
A live system feeds it, or the labor is negotiation and chasing people. Automating the keystrokes leaves the cost where it was.
Two Places the Same Shape Turns Up Away From a Desk
The engineer at the point of work. Somebody pulls a device off the line and has to judge a substituted chip acceptable or not, on the spot. The answer sits inside a technical document several hundred pages long, whose reference points at a second document, which points at a third. The shape holds perfectly — documents in, a written threshold applied, a decision out — but acceptance here is an inspection call made in seconds. Automate the lookup and that engineer gets the afternoon back. Automate the call and you have shipped an unreviewed part.
Traceability and defect work on the plant floor. Every component on a board has to be tracked so a fault can be backtraced, and mapping each one to its certificate of compliance is done by hand today. That half is document work with the shape intact. The other half is not: detecting defects across every site and model type is instrumentation work rather than retrieval. Split the two before you scope anything.
Seven Workflows, and Where Each One Is Settled
The shape is general; the workflows are not. Each row below carries its own inputs, failure mode and limit, and each one is settled in full where it is answered.
| What is eating the week | What it settles | Where it is answered |
|---|---|---|
| Signed agreements nobody can query across — obligations and renewal dates spread over executed files. | What extraction returns, and where the signed page takes over. | the contract portfolio page |
| A bid due and the good paragraphs scattered — cleared language buried in old responses. | Template adherence, export, and how much you still write. | the proposals and RFP page |
| An outside request with a deadline bolted to it — a regulator, a plaintiff or a buyer asking for everything responsive. | Turning a manual dig into search-and-verify, and what nobody certifies. | the records and evidence page |
| Numbers pulled from three systems into a document with a date on it — the close, the quote, the pack. | Which steps assemble themselves and which keep a signature. | the reporting and back-office page |
| Systems still running that nobody can describe — the authors left, the estate did not. | Reading configuration, runbooks and tickets as a corpus, and where intent stops. | the legacy systems and IT operations page |
| A system your sellers feed and never get paid back by — nothing useful returns to the person typing. | What a seller-facing layer must answer back before the keystrokes pay. | the CRM and seller admin page |
| A creative queue with one server — the site, the deck, the campaign, all waiting on capacity. | Where throughput is the constraint, and what the finishing pass catches. | the design and web production page |
Software, Services and Tools: Which Layer Carries Which Part
“Business process automation software” covers four different purchases, and a quote that blurs them is where budgets go wrong. Separate the layers before you compare anything, because a workflow that stalls in one of them is not fixed by buying more of another.
| Layer | What it carries | Where it is read in full |
|---|---|---|
| Corpus preparation | Getting scattered files into one governed, readable set before anything queries them. Paid once, in front of everything else. | the data readiness pages |
| The assistant that reads and drafts | Retrieval over your own material, extraction with the source attached, and the draft written into your template. This is where the hand-run hours go. | the AirgapAI page |
| Workflow and orchestration tooling | Moving the finished output between systems, on a schedule or a trigger. Mature, well-served, and a separate comparison. | the enterprise AI workflow tools comparison |
| Scoping, build and run | Someone to size the candidates, build the pipeline and stay for the second one. Engagement shapes, costs and how to choose a partner. | the AI automation services page |
Sequence beats shopping. Prepare the corpus, prove the finding and the drafting on one named workflow, then connect the output to whatever already moves your records. Teams that buy the orchestration layer first end up automating the one step that was never the expensive part.
What Sits in Front of the Automation, and What Sits Behind It
Every complete estimate carries two lines that are not the software: one paid before the first answer, one after every answer.
In front: getting the material into one governed place. Iternal states plainly that its tooling does not remove the need for a separate data-federation and data-management engagement. Corpora arrive scattered across shares and mailboxes never meant to be read together, and somebody has to govern them first. For more information visit the data readiness pages.
Behind: acting on the output. A drafted document is not an executed one. Iternal is direct that its tooling does not today publish into a customer’s own execution layer or agent library, and that no integrations exist with process-automation platforms such as UiPath or Automation Anywhere. Iternal does describe an agent library as something a customer can build, something Iternal can build as a service, or both. Read both together and the line is clean: finding and drafting are product today; the handoff into your execution stack is scoped work.
Pin it down: questions for your evaluation
-
Which of our repositories can the pipeline read as files on day one, and which need a federation project first?The line item nobody budgets, sized before signature.
-
What does the output publish into today, and what would it take to reach our own execution layer?Whether the last mile is configuration, a services engagement, or roadmap.
-
Who builds and maintains the agent library, and what does Iternal charge to build it or teach our team?Ownership of the asset after the deployment closes.
Answered elsewhere
- Which candidate workflows exist at all, and which one you prove first — see the use-case selection page.
- Worked examples arranged by function and sector — see the industry and department page.
- How good an answer has to be, and how to prove it — see the answer accuracy page.
- Where plant and engineering teams apply the pattern — see the manufacturing and industrial page.
FAQ
FAQ: Taking the Hand-Run Work Off Your People
Those shaped like a document going in, a known rule being applied, and a document coming out. There, an assistant grounded in your own corpus takes over the finding, extracting and drafting into your template, while a named person keeps the acceptance decision. Where a live system feeds the work, no saving appears.
Stop using people as the index. Buyers described engineers having to guess exactly how content was worded in order to find it. Prepare the material as a governed corpus and let retrieval return the passage with its source attached. Iternal builds AirgapAI to answer over a selected data set and reveal each source.
The same shape in different clothes. The answer already sits in a policy or a process document, and a person is paid to walk somebody to it. Point an assistant at that material and the repeat traffic drops. Keep the corpus current, and route anything with legal or financial consequence to a person.
By asking the corpus instead of scrolling it. Buyers described specification files several hundred pages long, references pointing at a second document and then a third, and an agent searching six knowledge bases for one specification. Retrieval collapses that hunt to a question. The inspection call stays with the engineer.
Both ends of it. In front, the material has to be governed first: Iternal states that its tooling does not remove the need for a separate data-federation and data-management engagement. Behind, the draft still has to be acted on. Iternal is direct that its tooling does not today publish into an execution layer or agent library that you own, and that no integrations exist with process-automation platforms such as UiPath or Automation Anywhere.
Answer four questions. Does the work start with files a person could drop in a folder? Is the rule written down as a template, playbook or approved answer? Does a document come out in a format you own? Who accepts the result when it is wrong? Four clear answers means automate the finding and the drafting.
It applies a language model to the document steps of a process people run by hand: finding the material, extracting what matters, drafting into your template. Rule-based platforms already move records between systems where fields line up. The difference is the unstructured half of the estate, which had no field to map and is now readable.
Four layers, bought separately: corpus preparation, an assistant that reads your material and drafts into your format, orchestration tooling that moves the finished output between systems, and the people who scope and build it. Compare the orchestration layer on the enterprise AI workflow tools page; the assistant layer is AirgapAI.
Either works once the shape is confirmed. A team that already runs its own document estate can prove the finding and the drafting on one workflow alone. Bring in help when the corpus needs federating first, when the candidates need sizing against each other, or when the second workflow has to land while the first stays running. For more information visit the AI automation services page.
Name the Shape Before You Name the Tool
Run the four questions against the workflow that annoys you most, decide who signs the output, and the rest is routing. Every workflow above is settled in full, with its own limits stated in the open.