My first remote hire almost quit in week 2.
Not because the role was wrong. Not because the pay was wrong. Because I had no onboarding plan. I sent them a laptop, added them to Slack, and pointed them at a Notion doc that hadn’t been updated in 4 months.
By day 10 they were confused, underutilised, and quietly wondering if they’d made a mistake. I found out on a Friday afternoon check-in that almost didn’t happen.
We fixed it. They stayed. But I rebuilt the entire onboarding process that weekend and haven’t had that problem since.
Why Startup Onboarding Usually Fails
Founders think onboarding is about information transfer. Here’s the product, here’s the team, here’s the Notion wiki.
It’s not. Onboarding is about belonging and momentum.
A new hire needs to feel like they’re in the right place and doing something useful within the first 5 days. If they’re still waiting for access to tools, sitting in on calls they have no context for, and reading documentation from 2022 — they’re not onboarding. They’re enduring.
The 30-60-90 Framework
Every hire now gets a written 30-60-90 day plan before their first day. It covers three things:
Days 1-30: Context and first contribution
They learn the company, meet the key people, and ship one small thing. The goal: they feel useful by end of week 2.
Days 31-60: Ownership
They take ownership of their first real workstream. I’m still available but I’m not holding their hand.
Days 61-90: Accountability
They’re running their function. We do a formal 90-day review — what went well, what didn’t, what changes.
The Prompt That Builds This in 20 Minutes
“Write a 30-60-90 day onboarding plan for a new [role] at an early-stage B2B SaaS startup. Company context: [2 sentences about what we do and our stage]. Their responsibilities: [paste job description or key outcomes]. Week 1 should focus on context and relationships — who they need to meet and what they need to read. Month 1 should end with one specific deliverable that proves they can do the job. Month 2 should have them owning [specific workstream]. Month 3 should have them running it independently. Include a 90-day review framework.”
The First Week Checklist Prompt
“Create a first-week onboarding checklist for a new [role] joining remotely. Include: tools to set up with access instructions, people to meet with a 1-sentence context for each meeting, documents to read in priority order, and one small task to complete by end of week 1 that gives them a quick win. Format as a checklist they can tick off themselves.”
The Check-In Email Prompt
I send this at end of day 3, day 7, and day 30:
“Write a check-in email to a new [role] who is [X days] into their role. The tone should be: genuinely curious, not evaluative. Ask: what’s been clearer than expected, what’s been murkier than expected, what do they need that they don’t have yet, and one thing they’d change about their first [X days] if they could. Keep it under 100 words. It should feel like a conversation, not a form.”
What Changed After I Fixed Onboarding
My last two hires both told me at their 30-day mark that it was the best onboarding experience they’d had. One of them came from a 500-person company with a dedicated HR team.
It took me 20 minutes with an AI prompt to build something better than what a full HR function had produced.
That’s the whole point.
Get the Full Hiring Prompt Library
15 prompts covering job descriptions, screening, interviews, offers, onboarding, and more — free download.