The First Hire 30/60/90 Onboarding Playbook (The Version That Does Not Waste Two Months)

The first-hire onboarding most solo founders run is some version of this. Day 1, they show the new hire around the tools and explain “we do X here.” Days 2 to 30, the new hire shadows or assists. Day 30, the founder thinks the hire is settling in. Day 60, the hire is still asking the same questions and producing work that needs heavy correction. Day 90, the founder realises the fit is wrong but has spent so much sunk cost that they extend by another month “to see.” Day 120, the relationship ends badly and the founder has lost four months of productivity, a salary’s worth of money, and the institutional knowledge transferred to someone who is now gone.

The playbook in this piece is built to test fit earlier, build independence faster, and force the retain-or-cut decision at day 90 with real data, not feelings. It is structured around three thirty-day blocks, each with a clear goal, a clear test, and a clear decision. The 30-day block tests whether the person can do the work AT ALL. The 60-day block tests whether they can do it WITHOUT YOU. The 90-day block tests whether the cost is worth the output. Each block has a written review at the end that you and the hire both sign.

This is the playbook for a first hire in a service business, consultancy, agency, or content business in India. The principles apply to any first hire; some specifics (probation rules, statutory tax handling) are India-specific.

Before day 1: the setup that saves you a week

The single most common time waster of a first hire is the founder discovering on day 1 that none of the access, tools, or documentation is ready. The hire then spends days 1 to 4 waiting for accounts to be provisioned, watching the founder set things up, and asking questions that should have been answered in a doc. This is preventable.

Have the following ready before the hire walks in:

• Login provisioning: Email account on your workspace domain, Notion or ClickUp invite already accepted, Slack or Teams invite already accepted, Bitwarden account with all shared vault items already assigned, accounting tool access if relevant
• Equipment ready: Laptop set up with OS, browser, password manager, the team chat tool, and any other essentials. If you are using a personal laptop, the BYOD policy is signed
• Paperwork done: Employment contract or contractor agreement signed both ways, NDA signed, IP assignment signed, statutory enrollments started (PF, ESI if applicable, professional tax)
• The starter document set: A single “Day 1 doc” with the company overview (one paragraph), the role definition (three sentences), the first week’s specific tasks, the communication norms (working hours, response time, channel preference), and the names and roles of the three to five most important external contacts (clients, vendors, the CA)
• A 30-day plan written down with five to seven specific deliverables and the support they will need

The pre-day-1 setup takes the founder about six hours total spread over the week before. Skipping it costs about three days of productivity on the other side.

Days 1 to 30: the fit test

The goal of the first 30 days is not training. The goal is to find out whether this person can do the work at the level you need, with the support you can realistically provide. Most onboarding goes wrong because it confuses these two things.

Concrete pattern that works:

Day 1: Spend the morning together going through the Day 1 doc, the tools, and the first week’s tasks. The afternoon, the hire starts on the smallest, lowest-stakes task on the list. End of day, a fifteen-minute check-in: what worked, what blocked, what is still unclear.

Days 2 to 7: The hire takes on three to five small, low-stakes, well-defined tasks (each one to three hours of actual work, generous deadlines). You review each one in detail. The point is not for the tasks to be useful to the business; the point is to calibrate the gap between their work output and the standard the business needs.

Days 8 to 21: The tasks scale up in stakes and length. Each task has a clear deliverable, a clear deadline, and a clear definition of done. You spend less time on each one. By the end of week 3, you are reviewing rather than co-producing.

Days 22 to 30: The hire takes one task that is real client-facing work, with the founder reviewing before it ships but not during execution. This is the first “for real” test.

Daily check-ins at this stage are short (10 to 15 minutes), end-of-day, focused on three questions: what got done, what is blocked, what is unclear. Avoid status meetings longer than this; they eat time and produce no calibration data.

The 30-day review at the end of this period is the most important conversation of the entire onboarding. It is not “are we happy with each other.” It is two specific questions, both backed by written observation:

1. Did the hire’s output match the brief, in your opinion? Not “did they try hard.” Specifically: were the deliverables what you asked for, at the quality you needed, within the time given? Pull out the actual tasks and the actual outputs. Be specific.

2. Did the time investment on your side match what you planned? If you planned to spend two hours a day in the first week and one hour a day in week three, did that happen, or are you still spending three hours a day in week four? If the trajectory is not bending toward independence, the fit is wrong.

The decision at day 30 is not “continue or not.” It is “continue with what changes.” If the answers to both questions are yes, continue as planned. If one is no, the next 30 days need different structure: more SOPs, tighter scoping, lower-stakes tasks, or a real conversation about whether the role match is wrong. If both are no, the honest conversation about extending probation needs to happen now, not in 60 days.

Days 31 to 60: independence ramp

If you passed the 30-day review, the next 30 days are about transferring real ownership of one repeatable workflow.

Pick a single category of work that the hire will OWN by day 60. Not “help with.” Own. They are responsible for the output, they manage the timeline, they handle the client communication for that category (with you copied), and they only escalate to you on things outside their scope.

Concrete examples of “own” by day 60:

• All monthly client reporting (they produce the reports, you spot-check before they ship)
• The end-to-end new-lead intake process (they qualify, they schedule discovery, they hand off to you for the pitch)
• The content production pipeline (they take the brief, produce the draft, hand to you for final review)
• The bookkeeping reconciliation cycle (they reconcile, they flag exceptions, you approve)

The shift from “assisting” to “owning” is the test that matters more than any other in this period. A hire who can take a defined category of work and run it without you is on track to be a net positive on hours. A hire who keeps needing your input on the same questions in week 8 that they needed in week 2 is not.

Communication shift in this period: Daily end-of-day check-ins become every-other-day. Friday end-of-week review (30 minutes, written agenda) replaces some of the daily friction. The hire owns enough that they are now telling you what is happening rather than asking what to do.

The 60-day review is also two questions:

1. Are you spending less than 5 hours a week managing this person and their work? If yes, the independence ramp is on. If no, either the role definition is too broad, the SOPs are insufficient, or the hire cannot work at this independence level. Diagnose which.

2. Has the hire produced at least one output you would have been happy to produce yourself? Not “they did okay for a junior.” Specifically: a piece of work that, blind, you would not have flagged as below your bar. If yes, the work-quality fit is there. If no, either the standard needs to come down (acknowledge the cost), the training time needs to extend (acknowledge the runway), or the fit is wrong (act on it).

If the 60-day review surfaces a serious gap, the conversation needs to be specific: “By day 90, the role needs to deliver X. Here is what needs to be true on your side, and here is what needs to be true on mine. If we are not there by day 90, we both need to acknowledge the fit is not working.” This is the conversation that lets a 90-day exit happen cleanly if it has to.

Days 61 to 90: scaling output

If the 60-day review went well, the third block is about scaling. The hire owns one category by now; the question is whether they can take on a second, or take more of the first, without the founder having to re-train.

Two specific moves:

Move 1: They train you on their workflow. Reverse the onboarding. They walk you through the SOP they have developed for the category they own. Not the SOP you gave them on day 1; the version they have evolved as they actually did the work. This both improves the SOP (real practitioners always find improvements) and tests whether they have genuinely internalised the work or are still operating from memory.

Move 2: Give them one stretch task. A task that is genuinely outside the role definition, that you would normally do, that requires judgment. Watch how they handle it. Do they ask the right questions, scope it well, deliver in the right format? Or do they treat it as the same kind of task they have been doing, miss the differences, and produce something that needs heavy rework?

The stretch task is the single best predictor of whether this hire scales beyond the first 90 days. A hire who handles a stretch task well at day 75 is someone who will compound over years. A hire who treats every task identically and gets surprised when the requirements differ is someone whose ceiling is what they are already doing.

The 90-day review is the retain-or-cut decision. Three questions, decided by written evidence:

1. Is the hire net positive on hours? Look at the actual numbers. How many hours per week are you spending on them and their work, versus how many hours per week of work would have come out of you if you were still doing it solo? If the math is not yet net positive (you spend 12 hours on them, they produce 15 hours of work that would have taken you 18), discuss runway. If the math is clearly negative (you spend 15 hours on them, they produce 10 hours of work that would have taken you 8), the fit is wrong.

2. Is the hire net positive on revenue or capability? Did the engagement open up work you could not have done alone? Did it free your time for higher-leverage work that produced revenue? Or are you doing the same work and spending more money?

3. Would you make this hire again, knowing what you know now? Honest answer. If yes, you have your first team. If no, you are extending out of sunk cost, which is the expensive way to make the eventual exit decision.

The mistakes that destroy onboarding

No written role definition. “We will figure it out” is the most expensive sentence in onboarding. The hire fills the time with whatever they want to do, which is rarely what the business needs. Every gap they fill incorrectly is rework you will pay for.

Sink-or-swim with no calibration. Founders who give the hire a task on day 2 and expect a finished product on day 5 with no in-between check-ins get bad output and learn nothing from it. The calibration data only emerges from frequent, structured check-ins.

Skipping the SOPs. “I will explain it as we go” means the founder repeats the same explanation four times, the SOP never gets written, and the hire’s ramp time stretches indefinitely. (See the three SOPs every solo founder needs before hiring for the specific ones to have ready before day 1.)

Daily standups longer than 15 minutes. A 30-minute daily standup eats 2.5 hours of weekly time on both sides. It produces less calibration than a 10-minute end-of-day with a written agenda.

Ignoring the 30-day review. “Let us give it another month” without a documented review is how the 90-day exit becomes a 120-day exit. The 30-day review is the cheapest exit point if the fit is wrong.

Extending out of guilt. If the 90-day review says the fit is wrong, extending because “they tried hard” punishes everyone. The hire keeps performing in a role that does not fit them; the founder keeps paying for output that is not breaking even; the eventual exit gets worse, not better. Make the call, communicate it clearly, give a fair notice and severance under the contract, and move on.

After day 90: the second test

If the hire passes the 90-day review, the next test is at the six-month mark. Six months is the standard probation period under most Indian state Shops and Establishments Acts, and the regulatory window for a clean parting if the fit is still uncertain. The bar at six months is higher: full ownership of multiple workflows, ability to handle one client end-to-end without founder involvement, contribution to process improvements that the founder did not initiate.

If a hire is still net positive but not yet truly independent at six months, that is a normal pattern for a junior. If they are clearly independent and producing, the next decision is what to give them ownership of for the second year (and whether to give the formal title change that often accompanies it).

If they are not yet net positive at six months, an honest conversation about whether the role is structured wrong or the fit is wrong needs to happen, with a clear plan to get there or part ways within the next 60 days.

---

The onboarding playbook only works if the pre-conditions are in place. The hiring decision itself is covered in when to make your first hire as a solo founder. The contractor-vs-employee decision is in contractor vs first employee in India. The SOPs you need written before day 1 are in the three SOPs every solo founder needs before hiring. The tooling stack that does not require migration when you add a second user is in the 1-to-3 person tech stack that scales without rebuild.