Documents
Reading forms, invoices, and contracts
Fields extracted from documents that are laid out differently every time, low-confidence cases flagged for review, and clean records written into your systems.
AI automation
AI is useful in a company when it removes specific, repetitive work — not as a strategy in itself. Here is what that looks like in practice: the processes it fits, what changes, and roughly what it costs.
What this is
Most "AI for business" material stays abstract. This page is the opposite: the concrete workflows where a language model removes hours of work, what the business feels afterwards, and the cost to expect.
Deciding which processes to automate is its own piece of work — that is AI strategy and automation consulting. Building the connected workflow underneath is business process automation. This page is about what the finished thing does for you.
Where it fits
These are the patterns that resist fixed rules — where a model earns its cost — with a person kept on the consequential decisions.
Documents
Fields extracted from documents that are laid out differently every time, low-confidence cases flagged for review, and clean records written into your systems.
Inbox
Incoming email sorted by intent and urgency, routed to the right person, with a drafted response for the routine cases that a human approves before it sends.
Revenue
Inbound enquiries asked the qualifying questions, enriched, summarised, and routed — so the first real conversation starts informed.
Knowledge
Staff ask in plain language and get an answer with the source passage attached, scoped to what their role is allowed to see.
Back office
Records matched across systems, discrepancies surfaced rather than buried, and the repetitive keying removed.
Leadership
The weekly or monthly write-up assembled from source data into a first draft, so the person owning it edits instead of building from scratch.
What changes
We agree the specific measure and its baseline before the build, so the change is demonstrable rather than asserted.
Time returned to the team by removing reading, keying, chasing, and formatting from a recurring process.
Inbound work acknowledged and progressed without waiting for someone to be at their desk.
Validated inputs and single-source records instead of transcription between systems.
A process that absorbs more volume without adding proportional staff time.
What it costs
A single scoped automation is typically $4,000–$15,000 to build, set by how many systems it touches and how much review the output needs. Running cost is model and API usage — usually tens to low hundreds of dollars a month — plus optional monitoring. The range is fixed in writing after a discovery call.
It does not pay back on low-volume processes, on anything where an error is expensive and cannot be reviewed, or on a task a setting in software you already own would handle. We will tell you when that is the case.
How the work runs
Each phase produces something you can review. Progress is shown in working software, not status updates.
Score candidate processes on volume, variability, handoffs, and consequence of error. Pick the one with the best return for the least risk.
Build against the common path first, test on your real cases, and route the exceptions to a person.
Add error handling, logging, and a human approval step on anything consequential, then connect it to your systems.
Compare against the baseline agreed at the start, then decide what to automate next.
Questions
A single scoped automation is typically $4,000–$15,000 to build, depending on how many systems it touches and how much human review the output needs. Running cost is model and API usage — usually tens to low hundreds of dollars a month — plus optional monitoring. We give a fixed range in writing after a discovery call, not an open-ended hourly arrangement.
Sometimes. It pays back on processes that run often, follow a mostly predictable pattern, and currently consume real staff hours — document handling, inbox triage, lead qualification, routine lookups. It does not pay back on low-volume work, on tasks where an error is expensive and cannot be reviewed, or where a setting in software you already own would do the same job.
Rules-based automation moves information and triggers actions along a fixed path — it is predictable and cheap where the steps never vary. AI automation handles the parts that resist fixed rules: reading a document that is laid out differently every time, drafting a reply, classifying a message by intent. Most real systems use both, with rules doing the deterministic work and a model doing the judgement, behind a review step.
Not always, but it has to be in the scope. If the information a process needs currently lives in someone's head or in an email thread, the first piece of work is building the record the automation will read. That is legitimate work — it just belongs in the estimate rather than being discovered mid-build.
A focused automation is usually two to six weeks from kickoff to production, including testing against your real cases. Larger programmes are split so one process is live and measured before the next one starts.
Not under the configurations we deploy. We use business-tier API access where the provider's terms exclude training on your inputs, and we document exactly which provider handles which data.
Related
Deciding which processes to automate first, and which to leave alone.
Explore this serviceThe connected workflow underneath — moving information and triggering the next step.
Explore this serviceA specific application: answering, booking, and routing calls without missing any.
See how it worksWe will give you an honest read on whether AI automation is the right tool for it, and what a first build would involve.