Use case
HR process automation for onboarding, leave and hiring paperwork
Onboarding is a checklist somebody copies for every new starter, leave requests arrive by email and get typed into a workbook, and hiring paperwork lives in a folder only one person navigates confidently. AgentCode turns those routines into tools your HR team runs.
No card to start · A person approves every change before it goes live
In short
AgentCode is an AI automation platform for HR teams. Someone in HR describes the routine: what a new starter needs in the first week and who provides it, how a leave request is approved and recorded, which documents a candidate signs before a start date. The agent writes the code for a small web application that carries it out, your team uses it, and the code belongs to your company. The next routine becomes another application in the same way.
The problem
Every process is a document plus a person who remembers the exceptions: an onboarding checklist copied for each new starter, leave tracked in a workbook, and a folder of contracts where the right version is the one with the longest file name.
What AgentCode builds for it
You describe the routine the way you explain it to a new manager: who asks, who approves, what has to be signed, what the deadline is. The agent writes the code for a tool that follows those steps and reminds the right person at the right time, and a human approves the change before your team sees it. A new starter gets the same first week every time, a manager approves leave in one place, and the balance updates without anyone maintaining a workbook. When the policy changes, you describe the change once.
What the agent does while it builds
What HR builds first
HR software is usually bought for the big record keeping job and then works badly for everything around it. The gaps get filled with documents, email threads and a person who follows up. Those gaps are where a small application helps most, because they are specific to your company and nobody sells a product for them.
The first requests tend to look like this, and each one is a page rather than a platform.
- An onboarding tracker that assigns each first week task to the person who owns it and chases it.
- A leave request screen with the approval rules and the balance your policy actually describes.
- A document checklist that shows which signed papers are missing before a start date.
- A probation review reminder that reaches the manager before the date rather than after it.
- A candidate pipeline view built around the stages your hiring managers really use.
- An equipment and access request that reaches IT with everything needed to act on it.
A first week that runs the same way twice
Onboarding is the clearest example of a process that is written down and still goes wrong. The checklist exists, but it is copied by hand, the tasks belong to four different people, and nobody sees the whole picture until the new starter mentions on day three that they still have no laptop.
A small tool fixes this without ceremony. Each task has an owner and a date, the people involved see only their part, and HR sees the whole list. A missed step is visible while there is still time to fix it rather than in a retrospective.
The same shape covers leaving as well as joining, which is the part most companies handle worst. The equipment, the access and the final paperwork become a list with owners instead of a conversation somebody has to remember to start.
Sensitive data that stays where it belongs
HR works with personal information, so the question of where the data sits comes before any discussion of convenience. The applications the agent writes run against your own systems and your own data, and the code goes into your repository where your organisation can read it.
Nothing changes without a person approving it. The agent prepares the work and a human in your organisation reviews and approves it before it affects a live process, which matters when the process decides who sees a salary figure or a medical note. Your policies and your existing access rules stay in force, because the tool sits inside them rather than beside them.
We do not train any model on your data, and the code is plain enough that whoever maintains it later can see exactly what it does with a record.
See it run
From a description to a working app
Pick a task
Plan
- planning
Files changed
Test run
Pull request
You review and merge. AgentCode never merges on its own.
Questions departments ask
What is HR process automation?
It is putting the repeatable HR routines into software: onboarding steps with owners and dates, leave requests with the approval rules applied, document checklists, probation and review reminders. The aim is to remove the copying and the chasing, so the HR team spends its time on the people rather than on the tracking.
Can HR automate a process without asking IT for a project?
Yes. The person who runs the routine describes it in their own words and the agent writes the code for a tool that follows it. A person approves the change before it goes live, and IT can review the code at any point because it sits in your own repository rather than inside somebody else's product.
Does this replace our HR system?
No, and it usually should not. Most teams keep the system of record and build the pieces around it that the system does not cover: the onboarding tracker, the document checklist, the approval screen shaped like your policy. The tool reads and writes the data you already hold.
How is personal data handled?
The applications run against your own systems and the data stays with your company rather than being copied elsewhere. The code lives in your repository where your organisation can read it, every change is approved by a person before it affects a live process, and we do not train any model on your data.
Further reading
HR teams usually read two of these. Internal tools covers the small screens that replace a shared document, and workflow automation covers approvals and the steps that have to happen in order. If you want to see the path from a description to a working page before you start, read how it works.
AgentCode for other departments
Put the next process on rails
Describe the job once and your department gets the application that runs it. See pricing.