A chatbot requires the new hire to know what to ask.
Question-answering has a hidden requirement: you have to know the shape of what you don't know. A new hire in their first week doesn't. They don't know the objection-handling doc exists, or that the team dropped the old playbook for a reason. So they never ask.
The artifact is finished before the first question.
A chat window is empty until someone types into it. A Firstweek onboarding artifact arrives finished: the company, the team, the role and what's happening now. Every claim is cited, and the hiring manager approves it before the new hire has to think of a question.
The artifact comes first. Questions come after.
Once a new hire has read the artifact, they can ask follow-up questions grounded in it. By then they know what exists, which is most of knowing what to ask.
A chatbot answers the questions you think to ask. Firstweek writes up what a new hire didn't know to ask about, in a finished document they read before day one.
Questions
Yes, once the artifact exists, and the questions are grounded in it. What changes is the starting point: the new hire has already read a finished document.
It uses AI to read your sources and synthesize them. The product is the finished artifact, not a conversation. There's nothing to type before there's something to read.
Compare Firstweek with: an onboarding checklist · your company wiki · BambooHR · Pyn · Highspot and Seismic · Guru · Tettra · Workday · Rippling · Confluence AI and Google Drive AI · Glean · Trainual
Wondering what a new hire costs while they hunt for context? Try the onboarding cost calculator →
Run Firstweek on your next real hire. 30 days. Then we talk about whether it's worth keeping.