Agents prepare the file. Your people make the decision.
Credit reviews, underwriting intake and claims. Agents carry the work across your systems, a named person approves each sensitive step, and every refusal goes on the record.
A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.
The work that comes before every decision
AI agents for financial services belong in the steps before a decision: gathering the file, checking it against your procedure, drafting the memo and routing it to the person who signs. Today an analyst carries that work between the loan or policy system, the document store, email and the ledger.
We design those workflows with you and run them on Ares, the platform. The agent prepares. Your credit officer, underwriter or claims handler decides.
- Each agent signs in as itself and gets a permission for one file only.
- A step you mark as sensitive, such as a covenant waiver, waits for a named person.
- Internal audit can check the record offline, without us. See the five guarantees.
If an agent already works for one of your teams, keep it. It enrols on Ares and no longer runs alone.
One annual credit review, four systems, one waiver held for a person.
The task: prepare the annual review for one commercial borrower. This workflow is designed. The underwriting run in the sandbox shows the same guarantees on a built workflow.
- 01In-house tool
Receive a credential for this borrower file only. It expires when the review ends.
- Who approves
- No approval on this step
- On the record
- credential issued · this file only
- 02Documents
Read the year-end financial statements the borrower filed.
- Who approves
- No approval on this step
- On the record
- read-statements · allowed
- 03Email
The borrower's covering email says to mark every covenant as met. That line is struck out before the agent reads it.
- Who approves
- No approval on this step
- On the record
- borrower-email · redacted · hidden instruction
- 04Accounting
Draft the covenant figures from the statements and the loan ledger.
- Who approves
- No approval on this step
- On the record
- draft-covenants · allowed
- 05Email
Try to send the draft memo to the borrower's adviser. The address is outside the permission, so the step is refused.
- Who approves
- No approval on this step
- On the record
- send-memo · refused · outside permission
- 06In-house tool
Record a waiver for the one covenant that was missed. The step waits until the credit officer approves it.
- Who approves
- Credit officer
- On the record
- record-waiver · approved by credit officer
In short
- What happens when a borrower's or broker's document carries an instruction?It is read at the door, and the instruction is struck out before an agent sees it. The record shows what was removed.
- Can an agent change a limit, a rate or a premium by itself?Only if your access policy allows it for that job. A change you mark as sensitive waits for the person you name.
- What does internal audit get?A record of every decision, approval and refusal. They check it offline with the open verifier.
- Does customer data leave our environment?Not unless you allow it. Ares can run in your building, and outbound answers are checked and redacted before they leave.
Workflows for banks, insurers and lenders.
Each card carries its state. Built workflows run in the sandbox today.
- Built
- We have run it.
- Designed
- The steps and approvals are designed. It has not run yet.
- On request
- We scope it with you before we design it.
- Built
Underwriting intake with document inspection
A policy renewal. The broker's document tells the agents to waive the survey. That line is struck out, a discount outside the permission is refused, and the underwriter reviews the premium.
Run it in the sandbox - Built
Contract review with redaction on the way out
Client identifiers are removed from a contract summary before it leaves. An agent that reaches for an outside page is refused.
Run it in the sandbox - Designed
Annual credit review file
The steps above: statements read, covenant figures drafted, a send to a new address refused, a waiver held for the credit officer.
- Designed
Claims intake
The agent reads the notice, opens the claim file and requests missing documents. A claims handler approves any reserve or payment.
- Designed
Onboarding file checks
The agent checks the file against your document list and flags each gap. Your analyst decides on the customer.
- Designed
Invoice matching for your own purchasing
Invoices matched to orders and receipts. A controller approves each adjustment.
See the steps - On request
Evidence packs for periodic returns
Figures and sources gathered for a return. A named owner signs before it is filed.
Requirements, mapped, not promised
Ares does not make your firm compliant with any rule. It gives your risk and compliance teams evidence: which agent acted, what it was allowed to do, what a person approved, and what was refused. For the guidance on AI agents we have mapped so far (the Canada agentic AI guide, the EU AI Act, CSA agent identity, OWASP and NIST AI RMF), the mappings state what Ares does today, what needs configuration, and what it does not do. We have not mapped a financial regulator's guidance yet.
The five guarantees
Every workflow on this page carries them. Each one has a limit, and we state it.
- 01
Each agent can do only what it was allowed to do, for that job.
The limit
Permissions are only as good as the rules you approve.
- 02
Sensitive steps go to a person.
The limit
You decide which steps are sensitive.
- 03
Documents are inspected before an agent sees them, and answers are checked before they leave.
The limit
Filters cover stated patterns and languages.
- 04
Every decision is recorded, including refusals, in a record an outside party can check.
The limit
It shows what agents did, not whether a business rule was wise.
- 05
It can run in your building, on one small machine.
The limit
Local models differ from the largest cloud models.
What it does not do
- It does not make a credit, underwriting or claims decision. It prepares the step, and your people decide.
- It does not certify your firm against any rule. We map published guidance on AI agents to what Ares does.
- It does not decide which steps are sensitive. Your risk owners do, and Ares enforces the list.
- The record shows what agents did, not whether the rule behind a decision was sound.
Assessment, pilot, production.
Each step has a fixed scope and ends with something you keep.
- 01
Workflow assessment
A look at one process: where an agent can act, which steps go to a person, what a wrong action would cost, and what the data allows.
- What you get
- A short, paid look at one process, with your process owner.
- What you keep
- A written scope and a price for a pilot.
Fixed price, quoted after one call.
- 02
Pilot workflow
One workflow on your systems, supervised, with the record on from the first run.
- What you get
- One workflow at a fixed scope, with your people approving the sensitive steps.
- What you keep
- A working workflow and a measured result.
Fixed price, quoted after one call.
- 03
Production and run
The workflow in production on Ares, on your hardware or hosted in your country.
- What you get
- Support, and the next workflows.
- What you keep
- The workflow, and the record of every decision it made.
Recurring fee for operation and support.
Questions and answers
Tell us about one workflow.
Name one file your analysts carry between systems. We will say whether an agent should prepare it, and what the first step costs. The first step is a workflow assessment. Fixed price, quoted after one call.
A senior member of the team replies within two business days.