A wiki is organized for the people who wrote it.
Your wiki has most of the answers, spread across hundreds of pages written for whoever needed them at the time. That's what a wiki is for, and it's good at it. A new hire can't tell which pages matter for their role, or which decisions still stand and which were reversed two reorgs ago.
Writing it up for each new hire is nobody's job.
Turning scattered pages into one story for one role is a research project. The People team can't do it for every function. Managers can. They don't.
Firstweek reads your wiki. It doesn't replace it.
Firstweek connects read-only to Confluence and Google Drive, plus Slack and your CRM, and writes from what's already there. Nothing to migrate. Your wiki stays the source of truth. Each new hire gets one onboarding artifact built from all of it: every claim cited, approved by the hiring manager before day one.
Your wiki answers questions people already know to ask. Firstweek writes up what a new hire doesn't know to ask yet, from the same wiki.
Questions
No. Firstweek connects read-only to Confluence and Google Drive and reads what's already there. Nothing moves, and nothing gets duplicated.
No. Confluence stays the source of truth. Firstweek turns what's in it into one onboarding artifact a new hire reads before day one.
Compare Firstweek with: an onboarding checklist · an AI chatbot · 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.