Review the new supplier contracts.Read 12 contracts. 3 clauses flagged.Summary sent to legal.
An example of an agent at work
What is an AI agent?
An AI agent is software that carries out a whole task, not one step. It reads the material, decides within rules you set, acts inside the systems you allow, and writes up the result. It can take over repeatable work such as contract review, month-end preparation and inbox triage, while a person signs off on outputs that matter.
You hand it a job in plain words. It does the job, checks its own work, and shows you the record.
A single AI step answers a question or drafts a paragraph. An agent strings many steps together: it opens the documents, works out what is missing, sends the request, files the reply and tells the right person. It can only touch the systems you allow, and every action is written to a record you can read afterwards.
You hand it the jobIn plain words
It works inside allowed systemsOnly what you permit
It checks firstBefore it confirms an action
A person signs offOn outputs that matter
Record writtenEvery action logged
Is an agent the right fit?
We will say so when an idea is not worth building. These are the signs we look for.
It fits when
The job has many steps across several documents or systems, and someone does it the same way each time.
You can write down what a good result looks like, and what the agent may and may not do.
A named person can review the result before anything irreversible happens.
The job happens often enough, and takes enough hours, to be worth building for.
You want a record of every step, for your own review or for an examiner.
It is the wrong tool when
The job happens twice a year, so the build would cost more than the hours it saves.
The rules change every time, so nobody can write down what a good result is.
A person must exercise judgment at every step, and the steps are not the slow part.
An off the shelf tool already does the job well enough.
Nobody at the firm is willing to review what the agent produces.
What can you build for a firm like ours?
These ten examples show the kind of whole job an agent can take. They are illustrations of what we can build, not client work. The real builds are further down.
CPA and accounting firms
Example
Chasing missing client documents before a tax deadline
Today
A staff member compares each client's checklist with what has arrived, then writes reminder emails one by one.
The build
The agent reads the checklist and the shared folder, lists what is missing for each client, and drafts a reminder naming those items. It updates the tracker when documents arrive.
A person still decides
The engagement manager approves each batch of reminders before they go out.
Example
First draft of an engagement letter
Today
A manager copies an old letter, edits the scope and fees by hand, and checks it against the intake notes.
The build
The agent reads the intake notes and fills the firm's template, choosing the scope paragraphs that apply. It lists every point it could not find in the notes.
A person still decides
The partner edits and signs the letter before it is sent.
Investment advisers and asset managers
Example
Assembling a quarterly client review pack
Today
An associate gathers statements, performance pages and meeting notes for each client, then builds the pack by hand.
The build
The agent collects the quarter's documents for each client, builds the pack in the firm's layout and notes anything missing or inconsistent between sources.
A person still decides
The adviser reviews the pack and decides what to say to the client.
Example
Watching a regulator's site for new guidance
Today
Someone checks the regulator's pages from time to time and forwards what looks relevant.
The build
The agent checks the chosen pages on a schedule, reads anything new, writes a short plain summary with a link to the original and files it in a log.
A person still decides
The chief compliance officer decides whether anything changes in the firm's practice.
Law firms
Example
First pass review of incoming contracts
Today
A lawyer reads each contract end to end looking for the clauses the firm always checks.
The build
The agent reads each contract against the firm's clause playbook, marks where a clause differs from the preferred wording and writes a summary with page references.
A person still decides
The responsible lawyer reads the flagged clauses and decides what to advise.
Example
Conflict check preparation at matter intake
Today
Staff pull party names from the intake form and search the firm's records by hand, name by name.
The build
The agent extracts every party and related name from the intake form, searches the firm's records for each, and assembles the possible matches on one page.
A person still decides
The conflicts partner decides whether a conflict exists.
Mortgage and lending
Example
Chasing outstanding loan conditions
Today
A processor reads the underwriter's conditions, emails borrowers and brokers, and updates the file as items come back.
The build
The agent reads the conditions list, asks for each open item, matches incoming documents to the condition they satisfy and updates the file.
A person still decides
The processor confirms a condition is met before the file moves on.
Example
Completeness check on a loan file before submission
Today
Someone walks through a checklist and opens each document to see that it is present, signed and current.
The build
The agent opens each document in the file, checks it against the checklist, and returns a list of anything missing, unsigned or out of date.
A person still decides
The loan officer decides when the file is ready to submit.
Operations-heavy businesses
Example
A daily exceptions digest for dispatch
Today
A dispatcher scans the schedule, the job notes and the inbox each morning to find what has gone wrong.
The build
The agent reads the day's jobs and messages, finds late, unassigned or conflicting jobs, and sends a short digest ordered by urgency.
A person still decides
The dispatcher decides how to reassign or reschedule.
Example
Drafting follow-ups on overdue customer invoices
Today
Someone reviews the open invoices and writes a different reminder to each customer.
The build
The agent reads the open invoices and recent correspondence, then drafts a reminder suited to each customer and the age of the invoice.
A person still decides
The office manager approves each reminder, or holds it, before it is sent.
Have a job you would hand to a colleague if you had one?
It reads a customer's weekly remittance and applies the payments to the right invoices. It runs as a Claude skill in the company's own Claude workspace.
A person still decides
There are two approval gates, and no payment is saved until both are passed.
It answers questions about prices, service area and policies, so the front desk has one place to look. It runs in the company's own Claude workspace and was in daily use from the first day.
It sweeps AI regulation sources every week and drafts a newsletter.
Built and running
Content engine
In use at DoubleChecked
What it does
It drafts and schedules posts.
A person still decides
Posts are scheduled for approval.
Client work is anonymized at client request. Reference calls available under NDA.
How does a build work?
Step 1ScopeOne working session. A plan and a fixed price.
Step 2BuildWorking agent early and often, on your own systems.
Step 3LaunchYour people trained on their real work.
Step 4RunHosted, watched, improved.
The plan sets the timeline. For a larger build you can start with a scoping sprint: two weeks and a working prototype on your own documents. The price is fixed after one working session. For an agent, the steps look like this.
Write down the job as a colleague would do it, including where they stop and ask someone.
Agree which systems the agent may read, which it may change, and which it may never touch.
Collect real examples of the job, good and bad, from your own files.
Build the agent and test it against those examples, with the checks it runs before it confirms any action.
Review the exceptions together and set the approval points where a named person decides.
Train the people who will use it, on their real work.
Switch it on with the record running, then watch and improve it.
What do you get at handover?
Working software
Running in your own environment, on your own systems.
The record
An append-only record of every action the agent took.
Written rules
What the agent may do, what it may not, and where a person decides.
Training
The people who use it, taught on their real work.
A security review
A named review of the build before it goes into use.
Someone to call
We run it for you: hosted, watched and improved.
How is our data handled?
The agent runs in a private environment that your company controls, and client data does not go to public AI services. DoubleChecked contracts directly with Anthropic under commercial terms and a data processing agreement, with no reseller in between. Zero data retention is available through the API, not the chat interface. Read the security page
Inside your environment
Your documentsThe AI modelThe record
Outside
Public AI servicesResellers
Company data does not go to public AI services.
What does it connect to?
Accounting and general ledger
Document management
Email and calendar
CRM
Bank and card feeds
Spreadsheets
File shares
Line of business systems
Public websites you name
Questions buyers ask
How long does it take?
The plan sets the timeline. After one working session you have a plan and a fixed price. You then see working software early and often during the build, so you are never waiting for a single reveal.
What does it cost?
Every project gets a fixed price after one working session, so you know the number before we build. A scoping sprint is an optional first step for larger builds: two weeks and a working prototype on your own documents.
Where does our data go?
The software runs in a private, client-controlled environment. Client data does not go to public AI services. DoubleChecked contracts directly with Anthropic under commercial terms and a data processing agreement, with no reseller in between.
Who checks the output?
The software checks before it confirms an action and keeps an append-only record of what it did. A person at your firm reviews and signs off on outputs that matter. Each build gets a security review before launch.
What happens when the agent gets something wrong?
The checks before each action catch many errors, and approval points put a named person in front of the rest. The record shows what the agent did, so the cause can be found and the rules corrected.
What do you need from us?
A person who knows the job, examples from your own files, a decision on which systems the agent may use, and a named reviewer. Your people are trained on their real work at launch.
Can an agent act without anyone approving it?
That is a rule you set. Where an action is hard to undo, such as saving a payment, we put approval gates in front of it. Every action is recorded either way.