How to onboard a new hire on Starch
Onboarding a new hire is the first real test of whether your company runs on systems or on your memory. Done well, a new employee is productive inside their first two weeks — they know what's expected, where information lives, who to ask, and what they're supposed to accomplish in their first 30, 60, and 90 days. Done poorly, they spend their first month interrupting you for answers you've already answered, and you spend your first month resenting the hire you fought to make. What this workflow looks like in practice varies — a first operations hire at a services firm needs something different than a sales rep at a software company or a warehouse manager at a product business — but the core problem is the same everywhere: getting someone from zero context to contributing without the process living entirely in the founder's head. On Starch, the result looks like this: a new hire opens their first week to a structured onboarding path in your company wiki, receives an automated welcome sequence with the right context at the right time, has a 30-60-90 plan in their task view with clear priorities, and you have a calendar of check-ins already booked — without you manually coordinating any of it after the first setup.
Why it matters
A bad onboarding doesn't just slow one person down — it creates debt. The hire who never got proper context makes decisions you have to undo, asks questions that interrupt your team for months, and often churns inside six months. That's a recruiting cycle you pay twice. A structured onboarding compresses time-to-contribution, reduces founder dependency on any single hire's institutional knowledge, and signals to the new employee that this is a company that has its act together.
Common pitfalls
The most common mistakes: sending a wall of documents on day one with no sequencing, so the hire reads none of it. Skipping the 30-60-90 plan because it feels premature, leaving the hire to guess what success looks like. Scheduling onboarding check-ins ad hoc instead of booking them upfront, so they get dropped when things get busy. And treating onboarding as a one-time event rather than a 90-day ramp — most founders stop paying attention after week two, right when the hire's real questions start.
Starch apps used
See this running on Starch
Connect your tools, describe what you want, and the agent builds it. Closed beta is free.
Choose your operator
A version of this guide tailored to your role — same recipe, different starting context.
The AI stack built for small HR teams.
The AI stack built for the founder's office.
The AI stack built for small IT and ITOps teams.
The AI stack built for boutique professional services firms.
The AI stack built for small law and accounting practices.
The AI stack built for independent clinic owner-operators.
The AI stack built for restaurant and hospitality operators.
The AI stack built for fitness studio operators.
The AI stack built for small contractors and builders.
The AI stack built for small property management firms.
The AI stack built for educators, coaches, and course creators.
The AI stack built for CPG brands.
The AI stack built for DTC founders.
The AI stack built for local service businesses.
The AI stack built for event planners and agencies.
The AI stack built for foundation and nonprofit ops teams.
Related workflows in People & HR
Benefits enrollment is one of those operator workflows that looks manageable until it isn't.
Read guide →Employee offboarding is the set of steps you run every time someone leaves — voluntary or not.
Read guide →Headcount planning is the process of deciding who you need to hire, when, and what you can actually afford to pay them — and then holding that plan up against your cash position often enough that you don't get surprised.
Read guide →An employee engagement survey is how you find out what's actually going on with your team — before it shows up in turnover, missed targets, or a candid exit interview.
Read guide →