How to Onboard Your First Hire in 30 Days

Week 1 has three jobs: explain the company, define the role, and give the new hire a completed task to point at by Friday.

Day 1 should be 60 percent conversation. Walk through what the company sells, who the customers are, and how money comes in. Stripe's guide notes that early hires shape company culture through their behavior, work ethic, and interactions, which is why the first days are worth a founder's attention (Stripe on early hires). Then hand over accounts and the calendar.

Day 2 belongs to the role. Write the role down, not in the job description's language but in the form of five outcomes for the first 90 days. Onboarding templates consistently treat documented expectations as the first 30-day deliverable, alongside a mentor introduction and access confirmation (Qooper 30-60-90 template). AIHR, which provides a 30-60-90 template and guide, notes that 30 percent of new employees quit within the first 90 days, citing a Jobvite job seeker report (AIHR on 30-60-90 plans). That single statistic is the argument for treating week 1 as a retention event, not an administrative one.

Days 3 and 4 are for introductions. Keep them short and specific: one 15-minute call with each person the hire will depend on, each with a stated reason ("she owns the customer database you will query"). Ask each person to end the call with one piece of advice about how work actually gets done here.

Day 5 is the small win. A small win is a task the new hire can finish inside two hours that produces something the business keeps: a fixed data error, a cleaned spreadsheet, a documented process, a drafted customer reply. The point is not value, it is evidence. By Friday, the new hire should be able to say "I shipped this."

The day 5 checkpoint is a 30-minute review using three questions:

1. What did you expect that turned out to be different?
2. What was missing that would have helped on day 1?
3. What do you want to be able to do by day 30?

Write the answers down. They become the input for week 2 and the first honest signal about whether the role matches the person. Daily check-ins in week 1 should be short, 10 to 15 minutes, at the same time each day, so nobody has to ask for help.

Weeks 2 and 3 are where most plans plateau, because the founder gets busy and the new hire is left with reading material. The decision rule that keeps the ramp moving: alternate each day between one shadowing block and one task with written acceptance criteria.

Shadowing means the new hire sits in on real work: a sales call, a support ticket triage, a code review, a vendor negotiation. Have them write a half-page of notes after each session and send it to you. The notes are a free diagnostic; you learn what they noticed without putting them on the spot.

Small tasks should increase in scope on a schedule. A simple weekly ladder:

Keep every task reversible and reviewed. Stripe's hiring guide closes its hiring sequence with an onboarding step, which reflects that the transition from candidate to contributor is part of the same process, not an afterthought (Stripe hiring guide).

The Founder Institute's collection of startup hiring advice stresses that an inability to define roles and delegate tasks can sink a startup, and recommends a plan that gradually transfers responsibilities as the team expands (Founder Institute on delegating roles). Weeks 2 and 3 are exactly that gradual transfer, done in public.

Founders often hire for resilience, a bias toward action, adaptability, emotional intelligence, and mission obsession, according to a roundup of advice from founders and investors compiled by Intro (Intro on first 50 hires). Those traits show up in week 2 and 3 behavior: does the new hire ask for the missing login, or wait? Do they fix a typo they were not asked to fix? The tasks in these two weeks are really tests of those traits, and you should note what you see.

The day 10 and day 20 checkpoints are 30-minute structured reviews. Score three things on a simple scale from 1 to 3: task quality, task speed, and how much help was needed. If any score is a 1, do not add scope in the next week; shrink the task and add a review step. If all three are 3s, move faster than the ladder above. A panel of founders and experts speaking at an RBCx event, co-hosted with Highline Beta, recommended being specific in what you want while avoiding bias in how you judge candidates and, by extension, new hires (RBCx on first hires). The scoring keeps your judgment tied to evidence.

One more tool for these weeks: an onboarding checklist. Indeed's employer guide describes checklists that span pre-boarding through 30-, 60-, and 90-day milestones, and credits structured onboarding with shorter time to productivity and better retention (Indeed onboarding checklist). Use a checklist for the repeatable items and reserve your energy for the conversations.

In week 4 the new hire should own a small project with a start, a finish, and a deliverable someone else uses. Not a task from the ladder; a project. The difference is ownership: they decide how to do it, they communicate status, and they present the result.

A good week 4 project looks like this:

• Size: 3 to 5 working days of effort, with a buffer to day 10.
• Scope: one deliverable, one consumer, one definition of done you agree on in writing before they start.
• Reversibility: low blast radius. A broken internal report is recoverable; a broken customer-facing checkout is not.
• Visibility: a five-minute demo to the team on day 30 or the nearest day.

Worked example. Suppose the new hire is a support generalist at a software company. A week 4 project: reduce the median first-response time on billing questions by writing eight new saved replies, testing them on the last 30 billing tickets, and reporting the before and after. The definition of done is a one-page write-up with the eight replies attached and the two numbers. You review the replies before they go live, but the new hire owns the analysis and the recommendation. That project teaches the tooling, forces customer reading, and produces an artifact the team keeps, all in a week.

The AIHR guide frames the 30-60-90 structure around exactly this transition, moving from learning to performing to demonstrable impact, with documented feedback at each phase (AIHR template guide). The Management Center publishes a goal-setting template for the same 30/60/90 rhythm, which is useful if you want a shared document the new hire fills in (Management Center template). HR Consulting Group's write-up on building a 30-60-90 plan makes the same point from the service side: the plan is a tool for tracking progress and spotting problems early (HRCG on 30-60-90 plans).

The day 30 checkpoint is the important one. Run it in 45 minutes and structure it in three parts:

1. Delivered: review the project against the definition of done you wrote on day 23.
2. Learned: ask what they would do differently, and listen for judgment, not politeness.
3. Next 60: agree on two outcomes for days 31 to 90, in writing.

If you generated the plan as a document, the new hire can fill it in themselves. If you would rather have a working tool than a static template, describe the site, app, document or plan you need and a specialist picks it up and builds it with you at Quanta; an onboarding tracker with checkpoints and a feedback log is a realistic first request for a founder with no HR team.

The hardest part of a 30-day plan is the measurement. Too little and you learn nothing; too much and the new hire spends the week filling in forms. A practical rule: measure three things, weekly, each on a 1 to 3 scale, and never measure more than that in month one.

Three rules keep this from becoming surveillance:

• Score the work, not the person. "The report needed two rounds of edits" is a score. "You seem slow" is not.
• Never add scope in the same week you lower a score. Fix the task size first.
• Share your own scores. Tell the new hire what you think you did badly in week 1, for example a calendar you built wrong. It sets the norm that feedback is two-way.

Feedback loops should follow the cadence from the short answer: daily check-ins in week 1, then weekly one-on-ones from week 2, plus the four checkpoints at days 5, 10, 20, and 30. Paychex's cost-of-hiring breakdown includes onboarding, training, and lost productivity among the expenses employers must account for, which is why the measurement is worth the time: you are tracking the return on a cost you have already paid (Paychex on hiring costs).

A quick note on where to spend founder hours. If your new hire needs an AI-enabled workflow to do their job, texting them a dozen API keys is not onboarding. A single OpenAI-compatible key for text, image, video, audio and embedding models is the kind of setup task that belongs in the pre-start checklist, and Quanta Inference is one option for that.

The plan is a default, not a contract. Three situations call for a change, and each has a specific response.

The hire is ahead of schedule. Compress week 3. Move the week 4 project start to day 15 and give a second project in week 4. Keep the checkpoints where they are; you want the day 30 review to still happen, with more evidence in it.

The hire is behind on task quality. Do not extend the ladder. Cut it. Pick one task type, do it twice more with a review after each, and delay the project to days 25 to 30. If quality is still below the bar at day 20, that is the honest signal to discuss fit, and the earlier it happens the better for everyone.

The role definition was wrong. This is common with a first hire, where the founder guesses at the job. If week 2 reveals the work is different from what was described, say so explicitly and rewrite the five outcomes together. Founders who are specific about what they want while staying open to what the business needs get better results than founders who treat the job description as fixed (RBCx on being specific and avoiding bias).

One legal caveat that surfaces in month one: if the role starts looking like an employee role in practice (set hours, your tools, your supervision) while the paperwork says contractor, revisit the classification rather than hope. The IRS guidance on behavioral, financial, and relationship factors is the reference to read before you change anything (IRS worker classification).

Whatever you adjust, keep the four checkpoints. They are the spine of the plan: day 5 for expectations, day 10 for quality, day 20 for independence, day 30 for ownership.