You just signed an offer letter. Your first ever employee is starting next Monday. Congratulations -- and also, you probably have no idea what to do now.
You've never onboarded anyone before. You don't have an HR department. You don't have an employee handbook, a training plan, or even a second desk. Everything you know about management comes from being managed by other people, and some of them weren't great at it either.
Here's what actually matters in the first 30 days, stripped of the corporate HR fluff that doesn't apply to a team of two.
Before Day 1: What to prep
The week before your new hire starts is when most of the important work happens. If you skip this part, day one will be awkward for both of you.
Get the basics ready:
- Set up their email account and any tools they'll need (Slack, project management, file storage)
- Create login credentials for everything -- don't make them spend day one waiting for access
- Prepare a simple document with all the accounts, links, and passwords they'll need
- If they'll work from your office, set up their workspace (desk, chair, monitor, power strip)
- Order any equipment that takes time to arrive (laptop, headset, whatever they need)
Prepare a welcome document:
Not a 40-page employee handbook. A one-page document that covers:
- What your company does, in plain language
- What their role is and what you expect from them in the first month
- How you prefer to communicate (Slack for quick stuff, email for formal things, calls for complex topics)
- Your working hours and expectations around availability
- Who to ask when they're stuck (which is you, but say it explicitly)
Write a first-week plan:
Not a detailed schedule for every hour. Just a rough outline: day one is orientation and setup, days two and three are shadowing and learning, days four and five are their first small task. Having a plan tells your new hire that you've thought about their experience, which matters more than you think.
Day 1: The first impression
Day one sets the tone for everything that follows. The goal is simple: make them feel welcome, give them context, and let them get oriented without pressure.
Morning:
- Send a welcome message before they arrive (or before their first remote login). Something genuine, not corporate: "Hey [name], excited to have you starting today. Here's what the day looks like..."
- Walk them through the welcome document. Don't just hand it to them -- talk through it
- Give them a tour of the tools and show them where things live
- Have coffee or lunch together. Yes, this matters. The relationship you build on day one carries forward for months
Afternoon:
- Let them explore. Give them time to read through existing documents, look at past projects, and get familiar with how things work
- Don't assign real work on day one. The temptation is strong because you've been doing everything alone and you're desperate for help. Resist it
- End the day with a 10-minute check-in: "How was it? Any questions? Anything confusing?"
The welcome email template:
If your new hire is remote or starts the next day, a welcome email the night before goes a long way. Here's what it should include:
- What time to "arrive" (login, show up)
- What the first day will look like
- Any prep they should do (install software, read something)
- How to reach you if something goes wrong
Keep it warm and short. This isn't a formal letter. It's a note from their new boss saying "I'm glad you're here."
Week 1: Survival mode
The goal of week one is not productivity. It's orientation. Your new hire needs to understand how your business works before they can contribute to it.
Days 2-3: Shadowing
Have them watch you work. Not literally standing behind you, but let them sit in on calls, see how you handle emails, watch how you make decisions. This teaches them more about your business than any document could.
After each session, debrief briefly: "That call was about X. Here's why I handled it that way." These 30-second explanations build context fast.
Days 4-5: First real task
Give them something small but real. Not busywork -- actual work that contributes to the business but has low stakes if it's not perfect.
Good first tasks:
- Draft a response to a straightforward customer email (you review before sending)
- Organize a document or process that's been messy
- Research something you've been meaning to look into
- Set up a tool or system you've been wanting to implement
Bad first tasks:
- Anything client-facing without your review
- Anything with a tight deadline
- Anything that requires context they don't have yet
Give feedback on the first task. This is the most important moment of week one. How you give feedback now teaches them what good looks like in your company. Be specific: "This part was great because..." and "Next time, try this approach because..."
Weeks 2-4: Building momentum
By week two, your new hire should be starting to contribute real work. This is when you shift from "teaching" to "coaching."
Week 2: Increasing autonomy
- Start assigning tasks without detailed instructions. Give them the goal and let them figure out the approach
- When they ask how to do something, resist the urge to just tell them. Instead: "How would you approach it?" Then guide them
- Have a brief daily check-in (15 minutes max). Ask: What did you work on? What's blocking you? What's next?
- Start delegating one thing you've been doing yourself. This is the whole point of hiring, and it needs to start now
Week 3: Training plan
By now you should have a sense of what they're good at and where they need development. Create a simple training plan:
- List 3-5 skills they need to develop in the next 60 days
- For each skill, identify how they'll learn it (practice, reading, shadowing, course)
- Set one measurable goal for each skill
This doesn't need to be a formal document. A shared note or a simple list works fine.
Week 4: Expectations setting
Before the 30-day review, make sure your expectations are crystal clear:
- What does "good performance" look like in their role?
- How will you measure their progress?
- What are the most important outcomes you need from them in month two?
- What should they do when they're stuck or unsure?
Write these down. Unclear expectations are the number one cause of early-hire problems, and they're entirely preventable.
Day 30: The review that matters
The 30-day review is not a formal HR process. It's a conversation. But it's an important one, so prepare for it.
What to cover:
- How are you feeling? -- Open with this. Their emotional state tells you more than any metric
- What's going well? -- Start with the positive. Be specific about what they've done well
- What's been challenging? -- Give them space to be honest. "Everything's fine" usually means they don't feel safe enough to share
- Here's what I've noticed -- Share your observations. Where they've exceeded expectations, where they need to improve
- Here's what the next 30 days look like -- Set goals for month two
- What do you need from me? -- This question matters. You're probably not a perfect manager. Give them a chance to tell you what would help
The right tone:
The 30-day review should feel like a conversation between two adults working toward the same goal, not a performance evaluation. If your new hire leaves the meeting feeling anxious, you did it wrong. If they leave feeling clear about where they stand and what's expected, you did it right.
The conversations nobody prepares you for
Here's what the onboarding checklists on Google don't tell you: the hardest part of your first hire isn't the logistics. It's the conversations.
"This isn't what I expected."
Sometimes, within the first two weeks, either you or your new hire realizes the role isn't what they expected. Maybe the job description wasn't clear enough. Maybe they oversold their experience. Maybe your company culture is just different from what they imagined.
Address it immediately. The longer you wait, the worse it gets. A direct but kind conversation in week two can save both of you months of frustration.
"I need to give you tough feedback."
When you've been a solo founder, you've never had to tell someone their work isn't good enough. It's uncomfortable. But avoiding the conversation does more damage than having it.
The formula: "I noticed [specific thing]. The impact is [specific impact]. What I need going forward is [specific expectation]." No sandwiching, no softening, just clarity with kindness.
"I made a hiring mistake."
It happens. If by day 30 you genuinely believe this isn't working and it's not fixable with coaching, you need to act. Every week you delay makes it harder and more expensive.
This doesn't make you a bad manager. It makes you a new one. The lesson is in what went wrong and how to screen better next time.
Your first hire changes everything
Hiring your first person is one of the biggest transitions a solo founder goes through. You go from doing everything yourself to being responsible for someone else's work, growth, and experience.
It's harder than it looks, but it gets easier. The key is having a structure -- even a simple one -- so you're not making it up as you go.
The First-Hire Onboarding Playbook gives you that structure: 30 scenario-specific frameworks covering everything from the welcome email to the 30-day review to the conversations nobody warns you about. Each one comes with a worked example and a management insight from people who've been through it. Built specifically for solo founders who don't have an HR department and don't want one.