What a great 30-day onboarding plan actually looks like

The first 30 days determine the next 3 years

You spent weeks finding the right person. You made the offer. They accepted. Then they show up on day one and sit at a desk with no laptop, no login credentials, and a manager who's "in meetings all morning but will catch up later."

This is how most startups onboard. It's also why 20% of turnover happens in the first 3 months. Bad onboarding doesn't just waste time — it tells your new hire that you don't have your act together. And they start looking for the exit before they've even found the bathroom.

Before day one: the pre-boarding week

Onboarding starts before the person walks in. The week before their start date:

Equipment and access. Laptop configured. Email set up. Slack/Teams account created. Access to all tools they'll need. If they're remote, ship the laptop so it arrives 2 days early. There is zero excuse for a new hire spending their first day waiting for IT.

A welcome message. From their direct manager, not HR. "Looking forward to working with you. Here's what your first week looks like." Include their schedule for the first 3 days so they know what to expect.

Tell the team. Announce the new hire. Name, role, background, what they'll be working on. Make sure the team knows they're coming and is prepared to be welcoming and helpful.

Week 1: orientation and context

Day 1: make them feel welcome, not overwhelmed.

Block 2 hours with their manager. Not "I'll try to find time." Block it. Explain the team structure, current priorities, and what success looks like in this role. Give them the context they need to understand why their work matters.

Assign an onboarding buddy — someone who's been there 6+ months and can answer the dumb questions nobody wants to ask their boss. "Where do people eat lunch?" "Is it okay to message the CEO directly?" These small questions matter more than you think.

Days 2-3: learn the product and the customer.

Have them use the product as a customer would. Watch customer demos. Read customer feedback. Sit in on a sales call or support conversation. Every new hire, regardless of role, needs to understand what you sell and who buys it.

Days 4-5: meet the team, understand the work.

Schedule 30-minute 1:1s with everyone they'll work closely with. Not just their team — the people in other functions they'll interact with. Each person should explain what they do, what they're working on, and how the new hire's role intersects with theirs.

By end of week 1, they should be able to explain what the company does, who the customers are, and how their role contributes. If they can't, the onboarding has failed.

Week 2: start contributing

Give them a real task, not busywork. Something small but meaningful that they can complete within a week. For an engineer: fix a well-defined bug. For a marketer: write one blog post or set up one campaign. For sales: research 10 target accounts and present your findings.

The task should be scoped so they can succeed without handholding, but challenging enough that they learn something. Early wins build confidence. Busywork builds resentment.

Daily check-ins. 15 minutes at the end of each day. "What did you work on? What are you stuck on? What do you need from me?" These check-ins catch problems early and make the new hire feel supported without micromanaging.

Week 3: increase ownership

Expand their scope. Move from single tasks to a small project. They should own something end-to-end — defining the approach, doing the work, presenting the result. This is where you see whether the hire is self-directed or needs more support.

Introduce them to the broader business. Invite them to a leadership meeting or a cross-functional planning session. Let them see how decisions are made. For startups, this exposure is one of the biggest perks of the job — don't save it for month 3.

Reduce check-in frequency. Move from daily to every other day. The goal is a gradual increase in autonomy, not a sudden drop-off of support.

Week 4: set expectations for the road ahead

The 30-day review. Sit down with them for an honest conversation. Not a formal performance review — a two-way check-in.

From you: "Here's what's going well. Here's where I'd like to see growth. Here's what I expect over the next 60 days."

From them: "Here's what I'm enjoying. Here's what's unclear. Here's what I need to be more effective."

This conversation sets the tone for the relationship. If something's off — wrong expectations, missing skills, culture mismatch — it's much cheaper to address at day 30 than day 90.

Define their 60-day goals. Clear, measurable objectives they own. By the end of month 2, they should be operating at 70-80% of full productivity with decreasing need for guidance.

The template

Week 0 (pre-boarding): Equipment ready. Welcome message sent. Team informed.

Week 1: Company context. Product immersion. Team introductions. Buddy assigned.

Week 2: First real task. Daily check-ins. Tools and process mastery.

Week 3: First project ownership. Cross-functional exposure. Check-ins every other day.

Week 4: 30-day review. 60-day goals set. Transition to normal workflow.

Adjust for the role, but the structure stays the same. The goal is simple: by day 30, your new hire should feel like a real member of the team who understands the business, has contributed something meaningful, and knows exactly what's expected of them next.

That's worth 10 hours of planning. Because the alternative — a confused new hire who quits in month 2 — costs you 30,000 or more to replace.