Hiring Without Breaking Delivery: A Migration Path

Most B2B teams in India hit the same wall somewhere between 8 and 15 people: hiring stops being an event and becomes a background process, and nobody owns it. The founder still does the first interview, offers go out as PDFs on letterhead, and onboarding is whoever happens to be free on Monday morning. The risk isn't a bad hire — it's that the new joiner quietly pulls two senior people off client work for three weeks and delivery slips. Here is a migration path that changes how you hire without touching the thing that pays the bills.

What does "not breaking production" mean when you're hiring?

In a services business, production is the client delivery your current revenue depends on — so a hiring migration is safe only if it never takes more than a fixed, planned slice of senior time. Treat it like a deployment with a rollback: run the new process alongside the old one for one or two hires before you retire the old one. Set a hard budget — say 90 minutes per interviewer per candidate, and nobody sitting on panels for two open roles at once. If the new process can't fit inside that budget, it isn't ready to ship.

Which parts of hiring should you systemise first?

Systemise the handoff, not the sourcing — the expensive failures happen between offer and month three, not at the top of the funnel. Sourcing can stay scrappy for a long time; referrals and two good job boards will carry a 20-person company. What breaks is context transfer. Write down four things:

• A scorecard per role: five to seven must-have criteria, each paired with the question that tests it.
• A fixed interview loop — the same three conversations, in the same order, 45 minutes each.
• An onboarding checklist that starts before day one: laptop, email, tool access, payroll and PF documents.
• A 30/60/90 plan written by the hiring manager, not HR.

Write them once and reuse them for every hire into that role. On tooling, a spreadsheet is fine until three people edit it at once; past that, a light ATS or even a self-hosted CRM repurposed as a candidate pipeline carries you to 50 people comfortably — our products include one we use exactly this way.

How do you onboard a new joiner without a senior person losing a week?

By pre-building the first two weeks as a dated schedule with named owners, instead of letting onboarding stay an ambient activity. Done properly, the first fortnight costs a buddy about four hours and the manager about ninety minutes; the rest is reading, access setup and one small, real task. Give the new joiner something that ships in week one — a docs fix, an internal tool, a small change on a live account. Shipping real work early tells you more about fit than any amount of pairing, and all-day shadowing is expensive supervision, not onboarding.

What does a phased migration look like over a quarter?

Run it in three phases across roughly eight to twelve weeks, each adding one piece of structure and none of them requiring a freeze on delivery. Take a 14-person studio hiring three people in a quarter: weeks 1-3, write scorecards and the interview loop for its two most-hired roles, changing nothing else. Weeks 4-8, use the new loop for one hire only and log the hours interviewers actually spend — if the panel burns more than 12 hours in total, cut a round. Weeks 9-12, publish the onboarding checklist and the 30/60/90 template and run them for the next two joiners. One mid-size client project typically absorbs 60-70% of a senior developer's week; badly run onboarding eats 15-20 hours of that in month one, which is the number to watch.

What breaks if you migrate too fast?

Two things: client delivery, when the same seniors are sitting on interview panels and hand-holding at once, and the process itself, when it becomes heavier than the work it supports. The usual over-correction is a six-stage loop with a take-home, a panel and a culture round for a five-person team — candidates with options drop out fast, and in India strong ones usually have two other offers running. Keep it to three conversations plus a paid exercise of two to three hours. Decide early where candidate data lives as well: under the DPDP Act you need a lawful basis, a retention limit (12 months is a common choice) and a way to delete on request. Build software only after you have run the process twice by hand; a single onboarding checklist tool is a two-to-three week job, and that kind of small custom build is usually cheaper than bending an ATS you don't control.

Where to start

Pick the one role you hire most often and write its scorecard this week — that is the whole of step one, and it costs ninety minutes and no money. Everything else, the loop, the checklist, the 30/60/90, hangs off it. Maysan Labs builds internal tools, dashboards and portals for teams going through exactly this stage of growth, so if that checklist turns into something you want to run properly across every hire, the conversation is easy to have when you get there.