New starters set up with the access their role needs. A person confirms every grant.
The agent reads the signed offer, prepares the accounts and groups for the role and drafts the first-day email. Personal details are struck out at the door by rules you set, and every step goes on a record you can check.
A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.
AI agents for HR teams take on the setup work between a signed offer and a person's first morning. Today someone copies the start date into the HR system, asks IT for accounts, chases the manager for the access list and writes the welcome email. Each copy is a chance to grant the wrong access, or to send a home address where it should not go. The agent does the copying and the chasing. Your people keep every decision about who works here.
What changes for your HR team
- A new starter's tasks move as one job, from the signed offer to the first day.
- The hiring manager confirms one access list, built from the role, instead of answering a chain of emails.
- Bank details, home addresses and ID numbers are struck out before the agent reads a document. You choose the fields.
An agent here makes no hiring, firing, pay or promotion decision. It starts only after a person has signed the offer. The grant itself follows the same path as any IT access request.
One new starter, from the signed offer to the first-day email.
We have set out these steps but not run them yet. They show where personal data is struck out, where the agent is refused, and where the hiring manager decides.
- 01Ticketing
Take the new-starter task when HR marks the offer as signed. Receive a credential for this one hire. It expires when onboarding closes.
- Who approves
- No approval on this step
- On the record
- credential issued · one hire
- 02Documents
Read the signed offer pack. The home address, the bank details and the national ID number are struck out at the door, by the rules your HR lead set, before the agent reads the pack.
- Who approves
- No approval on this step
- On the record
- offer-pack · redacted · personal data
- 03In-house tool
Read the job title, the start date, the manager and the site from the HR record.
- Who approves
- No approval on this step
- On the record
- read-hr-record · allowed
- 04In-house tool
Try to read the salary field to complete a setup form. Pay data is outside the permission for this job, so the step is refused.
- Who approves
- No approval on this step
- On the record
- read-salary · refused · outside permission
- 05Ticketing
Draft the access request for the groups the role template lists.
- Who approves
- No approval on this step
- On the record
- draft-access-request · allowed
- 06In-house tool
Create the accounts and add the role's groups. The step waits until the hiring manager confirms the list.
- Who approves
- Hiring manager
- On the record
- grant-access · approved by hiring manager
- 07Email
Draft the first-day email to the new starter: the time, the place and who meets them.
- Who approves
- No approval on this step
- On the record
- first-day-email · allowed
- 08Ticketing
Mark each onboarding task done in the ticket, with who confirmed what.
- Who approves
- No approval on this step
- On the record
- close-onboarding · allowed
In short
- Does the agent decide who we hire or let go?No. Hiring, firing, pay and promotion stay with people. The agent starts after a person has signed the offer, and it prepares setup work only.
- Who sees a new starter's personal details?Documents are read at the door before the agent sees them. The fields you list are struck out first, and the record shows each strike and the rule behind it.
- What if the agent grants more access than the role needs?It asks only for the groups in the role template, and the hiring manager confirms the list. A group outside the template is refused and recorded.
- Where does employee data stay?Ares can run on one small machine in your building. Nothing leaves unless you allow it, and the record shows what did.
People workflows, and the state of each.
One related check runs in the sandbox today. The others have their steps set out, or we scope them with you.
- 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.
- Designed
Employee onboarding and access
The offer read with personal data struck out, the accounts prepared from the role, and the grant confirmed by the hiring manager.
See the steps - Designed
Access request for a named role
The ticket, the directory lookup and the policy check. The system owner approves each grant.
See the steps - Built
Personal details taken out on the way out
A document summary leaves with names, account numbers and addresses removed, and a fetch to an outside page is refused.
Run it in the sandbox - Designed
Role change
When a person moves to a new role, the agent lists the groups the new role needs and the groups the old role leaves behind. The system owner approves each change.
- Designed
Leaver access removal
On the leaving date the agent lists every account and group the person holds and prepares the removal. It runs after the manager confirms the date.
- Designed
Policy acknowledgements
The agent sends each new policy to the people it covers, tracks who has confirmed it and reminds the rest. Your HR lead closes the round.
- On request
Equipment and desk requests for a new starter
- On request
Training due dates and reminders
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 makes no hiring, firing, pay or promotion decision. A person makes each one.
- It does not screen, score or rank candidates.
- It strikes out the fields and patterns you list, in the languages we state. A detail you do not list reaches the agent.
- It does not replace your HR system, your payroll or your privacy lead.
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 the people process your HR team copies by hand most often. We will say whether an agent should take it, and what the first step costs. Fixed price, quoted after one call.
A senior member of the team replies within two business days.