New hire onboarding
One entry starts payroll setup, accounts, equipment requests and the manager's checklist.
A new hire's details start in one place and need to land in five. Hours change, someone takes leave, a pay rate moves, and each update is another form to chase. n-frames connects your HR and payroll tools to IT, equipment and managers, so people data travels on its own.
Carrying data from one system to the next by hand is slow, error-prone and costly, and it isn’t what they’re here for. It’s not a people problem. It’s a plumbing problem.
This is the trip a new person's details make today, usually by email. Each step below runs off the HR record once it's connected.
Name, role, department, manager, start date and work location go into Gusto or whatever holds your people records. That entry is the only one anyone types.
If payroll runs in the same tool, this part is already done. If it's separate, we create the payroll profile from the HR record so nobody keys the same person twice. More on payroll automation.
Email, Slack and the apps that role needs are set up before the start date, from a list per department rather than whoever remembers.
Watch for: apps that need a paid seat. We route those to the person who approves spend instead of creating them silently.
The laptop or kit request opens with the start date and ship-to address, so it arrives before the person does.
First-week meetings, training and paperwork land with the manager as tasks with due dates, not as an email they might miss.
Anything that couldn't be done automatically shows up as an open item with an owner, so a missing login is spotted the day before, not the morning of.
Gusto for payroll, onboarding spread across email and chat.
The problem A new hire finishes onboarding in Gusto and then someone creates their email account, adds them to Slack, orders a laptop and notifies the manager, in that order, when they remember.
Completing onboarding in Gusto creates the accounts, opens the equipment request and tells the manager together. Day one starts with a working login.
One entry starts payroll setup, accounts, equipment requests and the manager's checklist.
Approved hours and leave reach payroll from the app where they were approved, with no one retyping a timesheet.
Pay runs post to your books split the way you report, instead of a journal entry someone builds by hand.
Leave, expense and equipment requests go to the right approver and wait in a queue, not buried in somebody's inbox.
A departure closes accounts, schedules the equipment return and updates payroll at the same time.
Headcount, hours and labor cost from your HR and payroll tools in one view, with no export to stitch together.
What lands on the HR manager's desk in a normal week.
Without us A new hire's details go into four systems.
With us One entry set up payroll, accounts and the checklist.
Without us Hours are retyped from a timesheet.
With us Approved time flowed to payroll.
Without us Time-off requests wait in an inbox.
With us Requests reached the right approver.
Without us An exit means a long checklist and missed steps.
With us Offboarding closed accounts and updated payroll together.
If one of these has happened in the last quarter, the gap is already costing you.
How you'll know: Weeks after someone's last day, their name still shows in Slack, a shared folder or a customer-facing app.
Fix: Tie offboarding to the termination date in your HR tool, so every connected app is closed on that day and anything that can't be closed automatically lands on a named owner's list.
How you'll know: An employee flags a short paycheck, and the new rate turns out to be sitting in an email or the HR record only.
Fix: Sync pay changes from the HR record to payroll with their effective date, and flag any change that arrives after the payroll cutoff.
How you'll know: A manager approved leave in a calendar or chat, and the balance in your HR tool never moved.
Fix: Make one system the place approvals happen, and send the result everywhere else, including the shared calendar.
You stop being the switchboard between systems. Employees get their accounts and answers sooner, and HR gets back the hours it spent forwarding forms.
n-frames works with the HR, payroll and finance tools you already run, including Gusto, Expensify and QuickBooks, and connects them to the email, chat and IT tools around them.
n-frames builds HR automation on the tools you already use: one entry for a hire, change or exit, carried to payroll, accounts, equipment and managers, with anything that needs a human sent to the right one. We keep it running once it's live.
Automate our hires and exits →Automating one HR process in isolation, onboarding for example, only moves the problem if payroll, accounts and equipment requests are still separate steps. We connect the whole chain, so one entry starts everything downstream, not only the first form.
No. Your HR tool stays the place people records live. We connect it to the systems it doesn't reach, and only suggest a change if the tool genuinely can't hold what you need.
Most of it. Closing accounts, pausing access, scheduling the equipment return and updating payroll can all start from the termination date. What stays human is the conversation, and any app with no way to remove a user automatically, which we list for a named owner.
We move only the fields each system needs, and agree up front where data goes and who can see it. Pay and personal details don't get copied into tools that have no use for them.
n-frames does. We connect HR, payroll, IT and finance tools for small and mid-size companies, so a new hire, a pay change or an exit is entered once and reaches every system it should.