
AI Employee Onboarding
Runs new-hire onboarding checklists, documents and first-week guidance.
Access removal, equipment return and exit surveys run automatically the moment a last day is confirmed.
When someone leaves, the real risk is the access that stays open. Revoking logins across several systems is easy to forget when the team is busy. This workflow starts the moment a last day is confirmed: it removes access, tracks laptop and equipment return, and sends the exit survey. If any step fails or stalls, the person you named is told straight away.

AI Offboarding runs your exit process in the background: revoking system access, tracking equipment return and triggering the exit survey, from the moment a departing employee's last day is confirmed. It follows the steps your team already uses, with one AI step to draft or decide where allowed, and flags any failed step to a person.
A forgotten login after someone leaves is a security gap, and a missing laptop is a cost that rarely gets recovered. Manual exit checklists slip most often when the team is stretched, which is exactly when departures pile up. This workflow follows your exact offboarding steps every time and raises an alert the moment something fails. You also get exit feedback more consistently. The Scope Card names the trigger, the systems, every step and the alert contact before you buy, so your security and HR teams can sign off together.
Once a last day is confirmed, the workflow starts revoking system access as one of its steps. Access removal follows the same steps for every leaver.
Equipment return is tracked as part of the exit workflow, against the items you list. Missing items are flagged to a person, rather than noticed months later.
The exit survey is triggered by the workflow at the point you choose in the process. You hear from leavers while their experience is still fresh.
Any failed step in the exit workflow is flagged to a named person. The gap can be closed while it matters, instead of turning up at an audit.
Your portal lists these the moment you order. Delivery starts the working day after everything is in and your access is checked.
| Option | Delivery time | Price |
|---|---|---|
| Standard | 20–30 working days | $2,400 |
| Express | 15–25 working days | $2,900 |
| Rush | 10–20 working days | $3,350 |
Before you start: Check recent leavers for accounts still active and equipment not returned. Note how many completed an exit survey.
These are things to track, not promised results. Outcomes depend on your data, your team and your market.
The build price is one-time. Running it afterwards is billed in your own accounts and typically runs about $20 to $100 a month for automation platform and AI model usage, depending on how many departures you process each month.
AI usage during the build and testing is also billed to your accounts, so you keep ownership of every provider relationship. Nothing runs through us.
Ask about running costsIf you need something outside the Scope Card, add a note at checkout. You get a written Change Quote, and that work only starts once you accept it. Your original order runs on its normal timeline either way. Larger or bespoke projects go through the Custom AI request form instead.
Request a custom versionOptional monthly maintenance covers monitoring, fixes, model and platform updates, a monthly health report and monthly change hours, enough for an updated checklist step or a new system connection swap. It starts after the 30 days of included support, bills monthly, and can be cancelled any month.
$249/mo (the minimum fee, includes 2 change hours)
Optional. Starts after the post-launch support period. Cancel any month.
How maintenance works| Do it yourself with a SaaS tool | Hire a custom agency | Upmark Labs | |
|---|---|---|---|
| Price | An IT offboarding tool charges a monthly seat fee regardless of departures | An HR consultancy bills hourly to document the exit process | Ours is one fixed price, shown before you buy |
| Scope | An offboarding tool gives you generic templates to configure yourself | A consultancy's scope depends on the engagement agreed | Ours is written on the Scope Card before purchase |
| Delivery | An offboarding tool is live immediately but untrained on your steps | A consultancy usually takes several weeks to map and build | Ours has a fixed delivery time shown before you buy, with faster options |
| Access left open | An offboarding tool still relies on someone configuring every rule correctly | An agency build depends on what was agreed and documented | Ours alerts your named contact automatically when a step fails |
The build is one fixed price, shown on this page before you buy, with express and rush delivery available at a set extra cost. Running the workflow afterwards costs roughly $20 to $100 a month in automation platform and AI usage, paid directly in your own accounts. There is no per-user fee from us.
Revocation requests go out across your connected systems as soon as the last working day is confirmed in your HRIS, not on a delayed batch schedule. Exactly which systems and how quickly each responds depends on your own admin settings, which is why the setup includes 20 test runs to verify timing on your data before launch.
No. It is built for the opposite moment: when someone leaves rather than joins. The two share a similar workflow structure, up to 12 steps and 3 connected systems, but the steps themselves are different, covering access removal, equipment return and exit surveys instead of account creation and welcome scheduling.
Expect to spend one to two hours describing their current exit process and gathering system access inside the 72-hour intake window. After that, expect around an hour reviewing the 20 test runs, plus the 45-minute recorded handoff session before launch.
Small adjustments to existing steps fit inside the monthly change hours included with maintenance. Adding a fourth connected system or going past 12 steps is a defined add-on, quoted and agreed before that work starts, so the cost is known upfront.
Yes. Access to each connected system is shared by adding our team as a user or creating a key you control, never by email, and the workflow only moves the fields your systems already store, such as name, role and last day. It does not create a separate copy of employee records outside your existing HRIS.
Yes, on the schedule you set during intake, typically on or shortly after the last working day. The survey questions come from what you provide; the workflow only handles the sending and reminder logic, not the analysis of what comes back, which is a separate build if you need it.
You can move to optional monthly maintenance, or stop there with a fully working workflow and no ongoing commitment. Either way, the workflow configuration and system connections remain yours and keep running exactly as built and tested. Maintenance covers monitoring, fixes, a monthly health report and change hours for an updated checklist step or a system swap.
Order AI Offboarding and it starts running your exit checklist on a fixed delivery date, closing access the same careful way for every leaver. The scope above is what you get, in writing, before you pay.

Runs new-hire onboarding checklists, documents and first-week guidance.

Answers employee HR questions from your policies and routes requests.
