At 150 to 500 people, onboarding tools fall into five types: an HRIS for paperwork and access, checklist tools for tasks, training platforms for skills, wikis and search for reference, and buddy programs for questions. Each does its own job. None of them tells a new hire who owns what or why things are the way they are.
What does each kind of onboarding tool actually do?
Five categories. You probably have four of them already.
- HRIS and paperwork. Gets the forms signed, the payroll record created, the laptop ordered and the accounts provisioned. BambooHR handles e-signature paperwork, a role-based checklist and task reminders. Rippling automates records, paperwork, hardware and access. Workday orchestrates onboarding tasks at enterprise scale. This is the layer that keeps you compliant, and it should stay exactly where it is.
- Checklists and task tools. Make sure nothing gets missed: the access request, the policy sign-off, the day-three meeting. Often built into the HRIS. Some include a 30-60-90 template; Rippling, for example, produces a checklist and a generic 30-60-90 template.
- Training and enablement. Teach the product, the method and the certifications. Good for skills that are the same for everyone in a role.
- Wikis and search. Hold what someone wrote down, and help people find it. Useful once you know what you're looking for.
- Buddy programs. Give the new hire a person to ask. The oldest onboarding tool there is, and still the one doing most of the work.
Every one of these is worth having. Keep the HRIS. Keep the checklist. Only 12% of employees strongly agree their organization does a great job of onboarding new employees (Gallup), and it isn't because companies forgot to buy tools.
What breaks at 150 people?
Proximity.
At 40 people, a new hire learns the context by sitting near it. They overhear why the pricing changed. They were in the room, or one desk from it. Nobody wrote an onboarding doc because the company was the onboarding doc.
At 150, that stops working, for three reasons:
- Most of the team wasn't there. The decisions that shaped how things work were made before most current people joined.
- Functions have separated. Sales doesn't hear what engineering decided, and the reverse.
- The buddy is busy. They have a full job, a quarter to hit, and a week of PTO that starts on the new hire's second day.
The tools from the list above all still function. The paperwork gets signed faster than ever. What's gone is the informal layer that used to explain everything, and no category was bought to replace it.
What breaks at 500?
Scale, on top of proximity.
- Every function has its own stack. Engineering lives in GitHub and Jira. Sales lives in the CRM. Everyone lives in Slack, in different channels.
- The People team can't write for every function. They own onboarding for sales, engineering, product, support and finance. They can't know why each of those teams works the way it does.
- Managers hire several people at once. The role-specific part of the 30-60-90 template was always theirs to fill in. With three starts in a month, it stays blank.
- The wiki has layers. Pages from before the last reorg sit next to pages from after it, with equal confidence.
At this size, onboarding is usually well organized and thinly explained. A new hire can finish every task in the HRIS on schedule and still not know who owns the account they were just handed.
Where does the context live in each case?
Go back through the five categories and ask where the missing part is.
- HRIS and paperwork hold records, forms and access. They can't hold why anything is the way it is.
- Checklists hold tasks and due dates. They can't hold the reason behind each task.
- Training holds product and method. It can't hold this team's history and decisions.
- Wikis and search hold what someone wrote down. They can't tell a new hire which pages still apply, or what to look for.
- Buddy programs hold whatever the buddy remembers. They can't hold anything on the days the buddy is out.
The second half of each line is the same thing each time. It's context: who owns what, why decisions were made, what's in motion right now.
That context isn't missing. It's in Slack threads, Jira tickets, CRM notes and Confluence pages, written by the people doing the work. No tool in the five categories was built to read all of that and write it up for one person. So the job falls back on the buddy and the manager, one question at a time.
Those questions have a price. A new hire is on payroll from day one, and each question also costs whoever stops to answer it. The onboarding cost calculator works that out from your own salaries and assumptions.
What does Firstweek add alongside your HRIS?
One thing: the written context.
Firstweek reads the tools your teams already use through read-only connections: Slack, Confluence, Jira, Google Drive, GitHub, HubSpot or Salesforce. It writes each new hire one onboarding artifact covering the company, the team, the role, who owns what and what's happening now. Every claim links to the thread, page or record it came from. The hiring manager approves it before day one.
What it doesn't do matters as much:
- It doesn't run payroll, benefits, e-signatures or provisioning. That's your HRIS.
- It doesn't connect to your HRIS, and doesn't need to.
- It doesn't replace the checklist. Your checklist stays, and the context sits next to it.
- It isn't a training platform or a wiki.
It isn't an alternative to anything on the list. It sits beside them. The side-by-side versions are here: Firstweek vs. BambooHR, Firstweek vs. Rippling and Firstweek vs. Workday. Or read a sample artifact and judge the output directly.
FAQ
What onboarding tools does a company need between 150 and 500 people?
An HRIS for paperwork and access, a checklist for tasks, training for role skills, and a wiki for reference. Those cover logistics. The remaining gap is written context for each new hire: who owns what and why things work the way they do.
Which HR tools include a 30-60-90 template?
Many HR platforms include checklists and templates. Rippling, for example, produces a checklist and a generic 30-60-90 template. A template sets out what to do and when; the reasons behind it have to come from the team's own history.
Does Firstweek replace our HRIS?
No. Keep it. Firstweek doesn't handle payroll, benefits, paperwork or provisioning, and assumes you already have a system that does.
Why isn't a buddy program enough?
A buddy is one person's memory, available when they are. It works well for judgment and badly as the place where the team's history is stored.
Sources: Gallup, for the 12% figure.
Run it on your next hire. 30 days. Then we talk. Start a pilot or see a sample artifact. How it works for scaling teams.