Onboarding docs are written twice a year and stale by the third hire. The knowledge exists: it is spread across your SOPs, your tools, and the head of whoever onboarded last.
Your Squad teammate assembles a first week per hire, per role. It pulls from your actual SOPs in Notion and Docs, cites what it uses, and says where a gap exists instead of inventing. The account checklist goes to IT as one tidy ticket, and the intro messages come drafted from the teammate's inbox.
The plan improves itself. What the last three hires in this role actually asked in week one goes to memory, and the next plan answers those questions up front.
Role, team, start date. The build starts the moment the hire is confirmed; no template to dust off.
Every section links the SOP it came from. A gap becomes a named question for the manager, not a made-up answer.
Every tool the role needs, who grants it, and the request drafted. IT approves the batch in one tap instead of eleven pings.
The welcome note, the team announcement, the buddy intro, each from the teammate's inbox, held for your approval.
The plan and checklist sit in Docs, shared with the new hire before their first morning. Week-one questions get folded into the next hire's plan.
WELCOME, SAM — YOUR FIRST WEEK Today: accounts are ready (list below). Read the two pages that explain how we work: 'How we ship' and 'Who owns what' (linked, from our real SOPs). 30-min walk-through with Ria at 2:00. This week: shadow the Tuesday release, own one small ticket by Thursday, meet the five people on your account list. Open question for your manager (not invented): the deploy-access SOP predates the new pipeline. Confirm which half still applies.
Your teammate connects through the integrations you approve, works on its own computer with its own browser, and asks you before anything irreversible.
A hire is confirmed. The build starts from your real SOPs.
The plan cites eleven docs and asks two questions where the SOPs contradict. The IT ticket lists every account in one place.
The new hire's actual week-one questions get folded into the plan for next time.
The third hire's plan is noticeably better than the first — and nobody rewrote anything by hand.
An AI teammate joins your calls, writes them up, and files each action against the person who owns it.
An AI teammate deduplicates records, fills the gaps, and closes stale deals every Sunday night.
An AI teammate digs an old decision out of years of messages and writes up what was agreed, who agreed, and where it was said, with links..