Buyer's question

How to Onboard a New Hire with AI Cut time-to-productivity in half.

New hire onboarding is uniquely well-suited to AI assistance — high volume of information transfer, repeatable across hires, lots of internal context to absorb. Done well, AI can cut time-to-productivity from 3 months to 6 weeks. Here's the workflow.

Short answer

Build a New Hire Onboarding Project per role, loaded with role-specific docs, past examples, and a structured 30-60-90 day plan. New hire interacts with it daily — gets context, asks questions, drafts work. Time-to-productivity drops 30-50%. Manager time on onboarding drops similarly.

The setup

Pick a role that gets hired regularly (AE, marketer, CSM). One-off roles aren't worth the setup.
Build a Claude Project for that role. Knowledge: role description, team structure, the 30-60-90 day plan, examples of past good work, internal acronyms and tools, key client/account context.
Train new hire to use it from day 1. First task: ask the Project to summarize what they should know in their first week.
Iterate based on what works. Each new hire surfaces gaps in the Project. Fix them. Next hire benefits.

Specific workflows that work

1. The "what should I know" daily prompt

New hire pastes today's calendar into the Project and asks: "what context should I have for each of these meetings?" Project pulls relevant background.

2. Account research before client meetings

New AE has Project produce a one-page brief on each account before meetings. Catches them up in 5 minutes vs reading 30 pages of CRM.

3. First-draft work

New hire drafts emails, briefs, proposals in the Project. Manager reviews. Loop iterates. Quality of first drafts is way better than zero-context first attempts.

4. Internal context lookup

"How do we handle X?" "Who owns Y?" "What's our policy on Z?" Project answers from loaded knowledge instead of new hire pinging 5 people.

5. Practice scenarios

Role-play discovery calls, objection handling, customer escalations with Claude playing the customer.

What to load in the Project

Role description and success criteria.
Org chart with names, roles, and what each person owns.
Standard 30-60-90 day plan for the role.
Internal glossary (acronyms, product names, methodology).
Past good examples of the role's work output.
Common questions new hires ask (build over time).
Tools the new hire will use, with quick-start references.

What NOT to put in the Project

Confidential personnel files of other employees.
Customer data without proper data handling.
Compensation information.
Anything covered by attorney-client privilege.
Files you cannot legitimately share with the new hire on day 1.

FAQ

Won't AI-assisted onboarding feel impersonal?

Done right, the opposite. The new hire gets faster context, which means more time for real human connection during the human onboarding moments.

How much manager time does this save?

Typically 30-50%. Manager still does the high-value coaching; AI absorbs the repetitive context-transfer.

Should I tell the new hire they're using AI?

Yes, openly. Frame it as a tool to accelerate their ramp, not as a substitute for the human team.

Will this work for engineering onboarding?

Yes — combined with Claude Code or Cursor for codebase navigation, engineering onboarding speeds up dramatically.

Does this work for senior hires?

Yes, often even better. Senior hires bring more skill but less context; AI is great at context transfer.