--- # === IDENTITY === id: business/startup-operations/employee-onboarding-playbook-for-startups/2026 canonical_question: "How do I onboard employees at a startup — first day/week/month/quarter, tool provisioning, buddy system?" aliases: - "Startup employee onboarding playbook 2026" - "First 90 days new hire onboarding template" - "Tool provisioning and buddy system setup guide" entity_type: execution_recipe domain: business > startup-operations > employee-onboarding-playbook-for-startups region: global jurisdiction: global temporal_scope: 2025-2026 # === VERIFICATION === last_verified: 2026-03-12 confidence: 0.88 version: 1.0 first_published: 2026-03-12 # === TEMPORAL VALIDITY === temporal_validity: status: evolving last_breaking_change: "Rippling and Gusto expanded SCIM-based auto-provisioning to 500+ apps (2025); SHRM updated structured onboarding guidelines emphasizing AI-personalized onboarding journeys" next_review: 2026-09-08 change_sensitivity: high # === CONSTRAINTS === constraints: - "Employment law varies by jurisdiction — verify local requirements for I-9/right-to-work forms, tax withholding (W-4/equivalent), and mandatory training before Day 1" - "Tool provisioning must follow least-privilege access — grant only role-appropriate permissions via RBAC templates" - "Buddy assignments require volunteers, not conscripts — forced buddy programs show lower engagement scores" - "Remote onboarding requires shipping hardware 3-5 business days before start date — factor into pre-boarding timeline" - "All onboarding documents (offer letter, NDA, IP assignment, benefits enrollment) must be signed before or on Day 1" # === SKIP CONDITIONS === skip_this_unit_if: - condition: "User needs a high-level people operations strategy, not execution steps" use_instead: "Search knowledgelib.io for people operations strategy — no dedicated unit yet" - condition: "User is onboarding contractors or freelancers, not full-time employees" use_instead: "Search knowledgelib.io for contractor onboarding — no dedicated unit yet" - condition: "Company has 200+ employees and needs enterprise onboarding workflows" use_instead: "business/erp-integration/employee-onboarding-automation/2026" # === AGENT HINTS === inputs_needed: - key: company_size question: "How many employees does the startup currently have?" type: choice options: ["1-10 (seed stage)", "11-50 (Series A)", "51-150 (Series B+)", "150+ (growth stage)"] - key: work_model question: "What is the work arrangement?" type: choice options: ["fully remote", "hybrid (some in-office days)", "fully in-office"] - key: hris_platform question: "Which HR/payroll platform is in use?" type: choice options: ["Rippling", "Gusto", "BambooHR", "Deel", "none yet — need recommendation"] - key: budget_for_tools question: "What is the monthly HR tooling budget per employee?" type: choice options: ["free tier only", "up to $15/employee/month", "up to $35/employee/month", "no limit"] # === EXECUTION METADATA === execution: required_inputs: - name: "Org chart or team structure" source: "founder or people ops lead" format: "document or spreadsheet" - name: "Role description and reporting line for new hire" source: "hiring manager" format: "document" - name: "Tool stack list (SaaS apps used by team)" source: "IT admin or founder" format: "spreadsheet or list" outputs: - name: "Onboarding checklist (pre-boarding through 90-day)" format: "document or project management board" description: "Complete timeline with task owners, due dates, and verification checkpoints for each onboarding phase" - name: "Tool provisioning runbook" format: "checklist or automation workflow" description: "Role-based access templates mapping each role to required SaaS tools, permission levels, and provisioning method" - name: "Buddy program guide" format: "document" description: "Buddy matching criteria, meeting cadence, conversation prompts, and feedback collection template" - name: "90-day scorecard" format: "spreadsheet" description: "Performance and integration milestones with manager and buddy ratings at 30/60/90 days" tools_required: - name: "Rippling" purpose: "HRIS, payroll, benefits, and automated IT provisioning via SCIM" tier: "paid" cost: "$8-35/employee/month depending on modules" alternatives: ["Gusto", "BambooHR", "Deel"] - name: "Notion or Confluence" purpose: "Onboarding wiki, checklists, and knowledge base" tier: "free or paid" cost: "$0-10/user/month" alternatives: ["Google Docs", "Slite", "Tettra"] - name: "Slack or Microsoft Teams" purpose: "Communication, buddy channels, and onboarding bot notifications" tier: "free or paid" cost: "$0-12.50/user/month" alternatives: ["Discord (startups only)"] - name: "Google Workspace or Microsoft 365" purpose: "Email, calendar, and document access provisioning" tier: "paid" cost: "$6-22/user/month" alternatives: [] credentials_needed: - service: "HRIS platform (Rippling/Gusto/BambooHR)" type: "admin account" where_to_get: "https://www.rippling.com or https://gusto.com" free_tier_limits: "Gusto Simple plan starts at $40/mo + $6/person" - service: "Identity provider (Google Workspace/Okta/Azure AD)" type: "admin account" where_to_get: "https://workspace.google.com or https://www.okta.com" free_tier_limits: "Google Workspace starts at $6/user/month" estimated_duration: "4-6 hours initial setup; 2-3 hours per new hire thereafter" estimated_cost: "$0 (manual checklists) to $35/employee/month (fully automated HRIS)" # === DISTRIBUTION === canonical_source: "https://knowledgelib.io/business/startup-operations/employee-onboarding-playbook-for-startups/2026" suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-12)" # === RELATED UNITS === related_kos: related_to: - id: "business/people-ops/hr-maturity-assessment/2026" label: "HR maturity assessment across recruiting, onboarding, performance management, compensation, L&D, and compliance" # === SOURCES === sources: - id: src1 title: "The New Hire Onboarding Checklist: Everything You Need to Know" author: BambooHR url: https://www.bamboohr.com/resources/ebooks/the-new-hire-onboarding-checklist-everything-you-need-to-know type: industry_guide published: 2025-01-15 reliability: authoritative - id: src2 title: "Employee Onboarding Process Best Practices for 2026" author: WorkMotion url: https://workmotion.com/employee-onboarding-process-best-practices/ type: industry_guide published: 2025-11-20 reliability: authoritative - id: src3 title: "27+ Employee Onboarding Statistics and Trends You Must Know in 2026" author: AIHR url: https://www.aihr.com/blog/employee-onboarding-statistics/ type: research published: 2025-12-10 reliability: authoritative - id: src4 title: "Onboarding: The Key to Elevating Your Company Culture" author: SHRM url: https://www.shrm.org/executive-network/insights/onboarding-key-to-elevating-company-culture type: industry_guide published: 2025-06-15 reliability: authoritative - id: src5 title: "Rippling vs Gusto: HR and Payroll Comparison" author: Rippling url: https://www.rippling.com/blog/rippling-vs-gusto-hr-payroll-comparison type: vendor_comparison published: 2025-08-01 reliability: commercial - id: src6 title: "Employee Onboarding Statistics 2026: The Data Every HR Leader Needs" author: Enboarder url: https://enboarder.com/blog/employee-engagement-onboarding-stats/ type: research published: 2025-10-15 reliability: authoritative --- # Employee Onboarding Playbook for Startups ## Purpose This recipe produces a complete, phased onboarding system for startups — from pre-boarding automation through 90-day performance assessment — including tool provisioning runbooks, buddy program setup, and milestone scorecards. The output is a repeatable onboarding process that reduces new-hire time-to-productivity by up to 50% and improves first-year retention by up to 82%, based on structured onboarding research. [src3] ## Prerequisites - [ ] **Role description and reporting line** available from hiring manager — defines onboarding content scope - [ ] **Tool stack inventory** — complete list of SaaS apps used by the team, with current admin credentials - [ ] **HRIS platform admin access** — Rippling, Gusto, BambooHR, or equivalent with ability to create employee records - [ ] **Identity provider admin access** — Google Workspace, Okta, or Azure AD for email and SSO provisioning - [ ] **Signed offer letter** — confirms start date, role, compensation, and work arrangement - [ ] **Knowledge base platform** — Notion, Confluence, or Google Docs for hosting onboarding documentation ## Constraints - Employment law compliance: I-9 (US), right-to-work verification, tax withholding forms must be completed by Day 1 or within legally mandated windows. Jurisdiction-specific requirements override this recipe's defaults. [src4] - Tool access follows least-privilege principle: new hires receive only role-appropriate permissions. Avoid granting admin access during onboarding. [src5] - Buddy assignments must be voluntary. Research shows forced buddy programs correlate with lower engagement and higher buddy burnout. [src3] - Pre-boarding communications must not include sensitive credentials via email. Use secure provisioning (SCIM, SSO invite links, or encrypted credential managers). [src5] - Hardware for remote employees must ship 3-5 business days before start date. Late hardware is the number one Day-1 failure mode. ## Tool Selection Decision ``` Which path? ├── Startup has 1-10 employees AND budget = free │ └── PATH A: Manual + Free Tools — Google Docs checklists + manual provisioning ├── Startup has 1-10 employees AND budget > $0 │ └── PATH B: Gusto + Notion — basic HRIS automation + structured wiki ├── Startup has 11-50 employees AND any budget │ └── PATH C: Rippling/Gusto Plus + Notion — SCIM provisioning + automated workflows └── Startup has 51+ employees └── PATH D: Rippling Unity + Okta — full HRIS + IdP + SCIM auto-provisioning ``` | Path | Tools | Cost | Setup Time | Scalability | |------|-------|------|------------|-------------| | A: Manual + Free | Google Docs, Sheets, manual app invites | $0 | 2-3 hours | Low (breaks at ~15 hires) | | B: Gusto + Notion | Gusto Simple + Notion free tier | $40/mo + $6/person | 4-5 hours | Medium (up to ~30 hires) | | C: Rippling/Gusto Plus | Rippling Core or Gusto Plus + Notion | $8-35/person/mo | 5-8 hours | High (up to ~200 hires) | | D: Full Automation | Rippling Unity + Okta + Notion | $35+/person/mo | 8-12 hours | Enterprise-grade | ## Execution Flow ### Step 1: Pre-Boarding Setup (Before Day 1) **Duration**: 2-4 hours setup; trigger 5-7 days before start date **Tool**: HRIS platform + identity provider + knowledge base Create the pre-boarding workflow that fires automatically when a new hire's start date approaches. This phase handles everything the employee and organization must complete before Day 1. **HR/Legal checklist** (assign to People Ops or founder): - Create employee record in HRIS (name, role, department, start date, compensation, reporting manager) - Send offer letter for e-signature (include NDA, IP assignment, at-will acknowledgment) - Trigger benefits enrollment packet (health, dental, vision, 401k if applicable) - Queue tax withholding forms (W-4, state forms, or international equivalents) - Send welcome email with: start date/time, first-day logistics, parking/remote setup info, dress code, contact for questions **IT provisioning checklist** (assign to IT admin or founder): - Create email account in Google Workspace/Microsoft 365 - Create accounts in role-required tools (derive from role-based access template) - For SCIM-enabled platforms: add to identity provider group; SCIM auto-provisions downstream apps - For non-SCIM tools: create accounts manually using role email - Order and configure hardware (laptop, monitor, peripherals) — ship to remote employees - Set up MFA enrollment invitation - Create Slack/Teams account, add to team channels and #new-hires channel **Role-based access template** (create once, reuse per role): ``` Role: [Software Engineer] ├── Communication: Slack (channels: #engineering, #general, #new-hires), Email ├── Code: GitHub (team: engineering, repos: [list]), CI/CD dashboard (read-only first 2 weeks) ├── Docs: Notion (workspace: Engineering), Google Drive (folder: Engineering Shared) ├── Project: Linear/Jira (project boards: [list]) ├── Infrastructure: AWS Console (read-only IAM role), Datadog (viewer) └── HR: HRIS self-service portal, benefits enrollment portal ``` **Verify**: All tool accounts created, hardware shipped/ready, welcome email sent, documents pending signature in HRIS. **If failed**: If SCIM provisioning fails for specific apps, fall back to manual account creation. Log which apps lack SCIM support for future automation. ### Step 2: Day 1 — Welcome and Orientation **Duration**: Full day (6-8 hours structured) **Tool**: Calendar (pre-scheduled), Notion/Confluence (onboarding hub), Slack Day 1 sets the emotional tone. Research shows 70% of new hires decide if a job is the right fit within the first month, and 29% know within the first week. [src6] **Morning block (first 3 hours)**: - Welcome meeting with hiring manager (30 min): role expectations, team intro, first-week goals - IT setup verification (30 min): confirm all tools accessible, MFA enrolled, VPN working - HRIS self-service walkthrough (15 min): payroll setup, benefits enrollment deadline, time-off requests - Company overview session (45 min): mission, values, org chart, product demo, key metrics dashboard - Buddy introduction meeting (30 min): informal meet, exchange working styles, set recurring meeting cadence **Afternoon block (3-4 hours)**: - Team lunch or virtual coffee (60 min): informal team bonding - Onboarding hub walkthrough (30 min): show where all documentation lives, how to find answers - First task assignment (60-90 min): small, completable task that produces visible output (e.g., commit a README fix, update a doc, configure their dev environment) - End-of-day check-in with manager (15 min): how did Day 1 feel, any blockers, preview of Week 1 **Verify**: New hire can access all required tools, has met their buddy and manager, completed at least one small task, and knows where to find help. **If failed**: If tool access issues persist, escalate to IT immediately. If buddy is unavailable, assign interim buddy from same team. ### Step 3: Week 1 — Orientation and Context Building **Duration**: 5 days (structured sessions + self-paced learning) **Tool**: Notion/Confluence (onboarding checklist), Calendar, Slack Week 1 transitions from logistics to context. The new hire should understand what the company does, how their team operates, and what success looks like in their role. **Daily structure for Week 1**: - Morning standup with team (15 min daily) - One 1:1 cross-functional intro per day (30 min): meet key stakeholders from product, engineering, sales, support - Self-paced learning blocks (2-3 hours): read team documentation, review recent project history, complete any compliance training - Buddy check-in (15-30 min, 3x during Week 1): answer questions, share unwritten norms, introduce to informal channels - End-of-week recap with manager (30 min Friday): review Week 1, set Week 2-4 goals, address concerns **Deliverables by end of Week 1**: - All compliance training complete (security awareness, harassment prevention, data handling) - Development environment fully configured (for technical roles) - Attended at least 3 cross-functional introductions - Documented 3 questions or observations about processes (signals engagement) **Verify**: Onboarding checklist shows all Week 1 items complete. Manager confirms new hire is engaged and unblocked. **If failed**: If new hire seems disengaged, schedule extra buddy time and a candid manager check-in. Disengagement in Week 1 is a leading indicator of early attrition. ### Step 4: 30-Day Integration — Learn Phase **Duration**: Days 8-30 **Tool**: Project management tool, 1:1 meeting templates, feedback forms The first 30 days focus on absorbing information — understanding the company, team workflows, and codebase/processes deeply enough to contribute independently. [src2] **Key activities**: - Ramp up to full participation in team ceremonies (standups, retrospectives, planning) - Complete 2-3 progressively complex tasks with decreasing supervision - Shadow a senior team member on a real project for 2-3 days - Buddy meetings shift to weekly cadence (minimum 4 meetings in first 30 days) - Manager 1:1 weekly (30 min): progress against goals, feedback in both directions **30-day checkpoint**: - Manager completes 30-day scorecard (role knowledge, cultural fit, collaboration, independence) - New hire completes onboarding satisfaction survey - Buddy provides informal feedback to manager - Review and adjust 60-day goals based on 30-day performance **Verify**: 30-day scorecard completed. New hire has delivered at least 2 independent contributions. No critical blockers or cultural misalignment flags. **If failed**: If scorecard shows gaps, create a targeted 2-week improvement plan. If cultural misalignment detected, escalate to People Ops for mediation. ### Step 5: 60-Day Integration — Contribute Phase **Duration**: Days 31-60 **Tool**: Project management tool, performance tracking Days 31-60 shift from learning to contributing. The new hire should be producing meaningful work with decreasing guidance. [src2] **Key activities**: - Own a complete feature, project component, or work stream end-to-end - Present work to team (demo, review, or knowledge share session) - Begin mentoring newer hires if applicable (reinforces learning) - Buddy meetings continue biweekly - Participate in hiring or process improvement discussions **60-day checkpoint**: - Manager completes 60-day scorecard (adds: output quality, velocity, initiative) - Compare against role-specific ramp benchmarks - Adjust 90-day goals to reflect actual pace - Identify any training gaps or resource needs **Verify**: New hire is independently productive on core responsibilities. Peer feedback is positive. No performance concerns. **If failed**: If contribution level is below expectations, assess root cause (training gap vs. role mismatch vs. support gap). Provide targeted support before 90-day assessment. ### Step 6: 90-Day Assessment — Full Autonomy **Duration**: Days 61-90 **Tool**: Performance review template, HRIS The 90-day mark is the critical evaluation point. Research indicates that new hires who report a great first 90 days are 10x more likely to stay long-term. [src6] **Key activities**: - Operate at full expected capacity for the role level - Take ownership of a significant initiative or improvement - Provide feedback on the onboarding process itself (continuous improvement loop) - Buddy program formally concludes (relationship continues informally) **90-day assessment**: - Formal performance review: manager + self-assessment + peer feedback (360-degree if team size allows) - Decision point: confirm in role, extend probation, or separate - Document assessment in HRIS for compliance and future reference - Celebrate successful completion (team acknowledgment, small gesture) **Scorecard dimensions**: ``` 90-Day Scorecard ├── Role Competency (1-5): Can they do the job independently? ├── Cultural Alignment (1-5): Do they embody company values? ├── Collaboration (1-5): Do peers enjoy working with them? ├── Initiative (1-5): Do they identify and solve problems proactively? ├── Growth Trajectory (1-5): Are they improving week-over-week? └── Overall Assessment: [Exceeds / Meets / Below Expectations] ``` **Verify**: 90-day assessment documented in HRIS. Clear decision made and communicated to new hire. Onboarding process feedback collected. **If failed**: If assessment reveals role mismatch, consult legal before separation. Document all feedback and support provided. ### Step 7: Buddy System Setup and Operations **Duration**: 1-2 hours initial setup; ongoing **Tool**: Slack, Notion, HRIS The buddy system is the single highest-ROI onboarding investment. 56% of new hires report a buddy helped them become productive faster, and buddy effectiveness reaches 97% when 8+ meetings occur in the first 90 days. [src3] **Buddy selection criteria**: - Same team or adjacent team (understands daily work context) - 6+ months tenure (enough institutional knowledge to share) - Volunteered for the role (never assign involuntarily) - Not the new hire's direct manager (buddies provide safe space for questions) - Ideally similar role level (peer relationship, not mentorship hierarchy) **Buddy responsibilities**: - Week 1: Meet 3x (Day 1 intro + 2 check-ins), introduce to team norms and unwritten rules - Weeks 2-4: Meet weekly, answer questions, provide context on decisions and history - Months 2-3: Meet biweekly, shift from onboarding support to collegial relationship - Provide informal feedback to manager at 30-day and 90-day checkpoints **Buddy conversation prompts** (provide as a Notion/doc template): - Week 1: "What confused you most today? What do you wish someone had told you?" - Week 2: "Who else should you meet? What process seems inefficient to you?" - Week 4: "What would you change about how we work? What's your biggest win so far?" - Day 60: "Do you feel like you belong here? What would make your experience better?" **Verify**: Every new hire has an assigned buddy before Day 1. Buddy meeting cadence is tracked (minimum 8 meetings in 90 days for maximum effectiveness). **If failed**: If buddy drops out or is unavailable, reassign within 24 hours. Track buddy volunteer pool size — if below 2:1 ratio to new hires, recruit more buddies. ## Output Schema ```json { "output_type": "onboarding_system", "format": "document_set", "components": [ {"name": "pre_boarding_checklist", "type": "checklist", "description": "Tasks due 5-7 days before start date, assigned to HR and IT", "required": true}, {"name": "day_1_schedule", "type": "calendar_template", "description": "Hour-by-hour Day 1 agenda with meeting links and facilitators", "required": true}, {"name": "week_1_plan", "type": "checklist", "description": "Daily activities and deliverables for orientation week", "required": true}, {"name": "role_access_template", "type": "spreadsheet", "description": "Role-to-tool mapping with permission levels and provisioning method", "required": true}, {"name": "buddy_program_guide", "type": "document", "description": "Selection criteria, meeting cadence, conversation prompts, feedback template", "required": true}, {"name": "30_60_90_scorecard", "type": "spreadsheet", "description": "Assessment dimensions with rating scales at each milestone", "required": true}, {"name": "onboarding_satisfaction_survey", "type": "form", "description": "New hire feedback form deployed at 30 and 90 days", "required": false} ], "expected_output_count": "6-7 documents", "reusability": "Template-based — create once, customize per role and department" } ``` ## Quality Benchmarks | Quality Metric | Minimum Acceptable | Good | Excellent | |---------------|-------------------|------|-----------| | Time-to-productivity (days to independent work) | < 90 days | < 60 days | < 45 days | | New hire 90-day retention rate | > 80% | > 90% | > 95% | | Onboarding satisfaction score (1-5) | > 3.5 | > 4.0 | > 4.5 | | Tool provisioning completion by Day 1 | > 85% | > 95% | 100% | | Buddy meeting completion rate (8+ in 90 days) | > 60% | > 80% | > 95% | | 30-day scorecard completion rate | > 90% | > 95% | 100% | **If below minimum**: Audit the specific failing phase. Most failures cluster in pre-boarding (IT provisioning delays) or buddy program (volunteer shortage). Fix the bottleneck phase before scaling headcount. ## Error Handling | Error | Likely Cause | Recovery Action | |-------|-------------|----------------| | New hire has no tool access on Day 1 | SCIM provisioning failed or IT checklist incomplete | Manually create accounts immediately; post-mortem on provisioning pipeline; add failed app to manual-provision list | | Buddy no-show for first meeting | Buddy overloaded or forgot | Reassign buddy within 24 hours from volunteer pool; send calendar hold for first 3 meetings | | New hire disengaged by Week 2 | Unclear expectations or cultural mismatch | Schedule candid 1:1 with manager; review role description alignment; increase buddy meeting frequency | | 30-day scorecard not completed | Manager too busy or lacks template | Send automated reminder at Day 25; provide pre-filled scorecard template; escalate to People Ops if still missing by Day 35 | | Hardware not delivered for remote hire | Shipping delay or wrong address | Ship replacement via overnight delivery; provide temporary BYOD policy with security requirements | | Benefits enrollment deadline missed | Welcome email buried or instructions unclear | Contact benefits provider for grace period (most allow 30-day extension); improve pre-boarding email sequence | ## Cost Breakdown | Component | Free Tier | Paid Tier | At Scale (50+ employees) | |-----------|-----------|-----------|--------------------------| | HRIS/Payroll (Gusto/Rippling) | N/A (no free tier) | $40/mo + $6-35/person | $8-20/person/mo (volume discount) | | Identity provider (Google Workspace) | N/A | $6/user/month | $6/user/month | | Knowledge base (Notion) | Free (up to 10 guests) | $8/user/month | $8/user/month | | Communication (Slack) | Free tier | $7.25/user/month | $12.50/user/month (Business+) | | Hardware (laptop + peripherals) | N/A | $1,200-2,500 one-time | $1,000-2,000 (bulk pricing) | | **Total per new hire (first month)** | **$0 (manual process)** | **$1,300-2,700** | **$1,100-2,200** | | **Recurring monthly per employee** | **$0** | **$27-60/person** | **$35-47/person** | ## Anti-Patterns ### Wrong: Information firehose on Day 1 Cramming all company history, product details, tool training, compliance modules, and team introductions into a single 8-hour Day 1 marathon. Result: new hire retains less than 20% and feels overwhelmed rather than welcomed. [src2] ### Correct: Phased information delivery Spread orientation across the first week. Day 1 covers logistics, team, and one small win. Deeper knowledge transfer happens in Week 1 through daily focused sessions. Compliance training completes by end of Week 1, not Hour 3. ### Wrong: Skipping pre-boarding entirely New hire shows up on Day 1 to find no laptop, no email account, no desk assignment, and paperwork that takes 2 hours to complete. Result: first impression is chaos, signaling the company does not value their time. [src1] ### Correct: Pre-boarding automation fires 5-7 days before start HRIS triggers IT provisioning, document signing, and welcome communications automatically. By Day 1, the new hire has a functioning email, access to Slack, signed paperwork, and a clear schedule. ### Wrong: Assigning a buddy and forgetting about it Pairing a new hire with a buddy but providing no structure, conversation prompts, or accountability. Result: buddy meets once, relationship fades, new hire loses a critical support channel. [src3] ### Correct: Structured buddy program with cadence and tracking Provide buddies with a conversation prompt guide, set minimum meeting frequency (8+ in 90 days), and track completion. Collect feedback from both buddy and new hire at 30 and 90 days. ## When This Matters Use this recipe when a startup needs to build or improve its employee onboarding process from scratch or replace an ad-hoc approach. Especially critical when headcount is growing faster than 2 hires per month, when new-hire attrition exceeds 15% in the first 90 days, or when time-to-productivity consistently exceeds 60 days. ## Related Units - [People Ops Foundation Playbook](/business/startup-operations/people-ops-foundation-playbook/2026) - [People Ops Maturity Assessment](/consulting/people-ops/people-ops-maturity-assessment/2026) - [Contractor Onboarding Checklist](/business/startup-operations/contractor-onboarding-checklist/2026) - [Employee Engagement First Year](/consulting/people-ops/employee-engagement-first-year/2026)