CEO Executive AssistantThe startup CEO guide to people operations management addresses the function that most startup CEOs say is their top priority and simultaneously the function where operational rigor is most often absent. Hiring great people is table stakes. Building the operational systems that attract, develop, retain, and manage those people through the 10-to-100 headcount journey is where most startup people operations either scale or break.
This guide is not about HR philosophy. It is about the specific operational decisions that startup CEOs face as they build people operations from the first full-time hire through Series B scale: when to invest in HR leadership, how to build recruiting operations, what performance management looks like when it works, how to structure compensation and equity, and when HR technology helps versus when it creates overhead the company does not need.
The People Operations Challenge at 10 to 100 Headcount
The 10-to-100 headcount journey is where people operations failures have the highest organizational impact. At ten people, the CEO can manage every key relationship directly. At twenty-five people, the organization begins to develop informal hierarchy and culture that the CEO is not fully controlling. At fifty people, management layers form, recruiting becomes a full-time function, and compensation equity becomes a serious governance challenge. At one hundred people, people operations either work as a system or the organization develops the talent management dysfunctions, retention problems, and management inconsistencies that eventually impair business performance.
According to Harvard Business Review research on scaling organizations, the most common reason high-growth startups experience performance degradation at fifty to one hundred employees is not product market fit deterioration. It is organizational and people management breakdown that was predictable and preventable with better operational infrastructure.
The CEO’s role in people operations is not to be the head of HR. It is to set the talent philosophy, build the organizational systems, make or endorse the key structural decisions, and hold the people operations function accountable for outcomes that directly affect the company’s ability to execute.
Structuring HR for the 10-to-100 Journey
Startup HR structure should be built in phases that match organizational scale, not in anticipation of scale that has not yet arrived.
Phase 1 (10 to 25 employees): At this stage, a dedicated HR function is typically not justified. The CEO or a strong executive assistant/office manager handles basic HR administration: onboarding paperwork, benefits enrollment, PTO tracking, and basic compliance. Payroll is managed through a platform like Gusto or Rippling. Employment law compliance is managed through a relationship with an employment attorney who reviews offer letters, equity agreements, and any personnel decisions with legal risk.
Phase 2 (25 to 50 employees): This is the stage where most startup CEOs first need dedicated people operations capacity. The right hire is typically a Head of People or People Operations Manager, not a Chief People Officer (CPO). This person owns recruiting coordination, onboarding, benefits administration, performance review process management, and basic HR policy compliance. They are an operational leader, not a strategic executive, and they should report to the CEO.
Phase 3 (50 to 100+ employees): At fifty to one hundred employees, people operations should have a dedicated team with capacity across recruiting, HR business partnership, compensation and equity administration, and learning and development. A VP People or CPO is appropriate when the function has enough scope and strategic complexity to require executive leadership. The decision to hire at the VP or C-level should be based on actual organizational need, not on the desire to have a senior title in the function.
Build the people operations function around the operational systems it needs to run, not around the headcount the function will eventually need. Define what the people ops function is accountable for producing, build the systems that produce those outcomes, and staff the function to run those systems effectively.
Building Recruiting Operations
Recruiting is the most time-sensitive people operations function in a high-growth startup. Headcount gaps directly constrain execution, and an unstructured recruiting process produces slower hiring, worse candidate experience, higher offer rejection rates, and lower quality hires than a well-built recruiting operation.
Build recruiting operations around four core systems: a structured sourcing process, a standardized interview process, a decision-making framework, and a candidate experience workflow.
Sourcing is where most startup recruiting processes are most informal and most improvised. Build a sourcing strategy for each role type that defines: which channels are primary (employee referrals, LinkedIn, job boards, recruiting agencies), what the sourcing volume target is by channel, what the outreach messaging framework is, and who owns sourcing for each channel. Track sourcing funnel metrics by channel: applications reviewed, phone screens scheduled, on-site interviews conducted, offers made, and offers accepted. This data tells you which sourcing channels are producing hires and which are generating volume without quality.
Interview process standardization is one of the highest-leverage recruiting investments a startup can make. Build a structured interview process for each role family that defines: the number of interview stages, the competencies assessed at each stage, the specific questions asked to assess each competency, and the scoring rubric used to evaluate candidates. Structured interviews produce significantly more predictive hiring decisions than unstructured conversations. McKinsey research on hiring effectiveness consistently shows that structured, competency-based interviews outperform unstructured interviews on predicting job performance.
Decision-making frameworks prevent the most common startup hiring failure: the team loves a candidate who is charming but whose skills or work style is not right for the role, or a candidate who is technically strong but whose values are misaligned. Build a hiring decision process that requires a written evaluation from each interviewer before the debrief meeting, a structured debrief that discusses competencies systematically rather than allowing one enthusiastic advocate to carry the decision, and a final hiring decision that requires agreement on the candidate’s fit against the role’s defined requirements.
Candidate experience starts with the first point of contact and extends through onboarding. Build a candidate communication workflow that ensures every candidate receives acknowledgment of their application within forty-eight hours, timely communication at each stage of the process, and respectful notification if they are not moving forward. Candidates who have a poor experience rejecting your offer tell other candidates. In a market where talent is scarce, candidate experience is a competitive differentiator.
Creating Performance Review Cycles That Do Not Stall the Company
Performance reviews are among the most feared and most often bungled management processes in startups. Done poorly, performance review cycles consume weeks of manager and employee time, produce generic feedback that nobody acts on, and create anxiety without generating useful information. Done well, performance reviews give employees clear feedback on their performance, align individual goals with company priorities, support compensation decisions, and identify development needs before they become retention risks.
Build a performance review process that is calibrated to your company’s stage and rhythm. For companies below fifty employees, a semi-annual review cycle with lightweight mid-year check-ins is sufficient. For companies above fifty employees, a semi-annual or quarterly goal-setting and review cycle with a single annual performance rating is appropriate. Annual-only reviews with no mid-year cadence are insufficient at any scale.
The review process design should specify: the review frequency and calendar, who completes reviews (manager-only, peer review, self-assessment, skip-level input), the rating system and scale, the format for written feedback, the timeline from review completion to feedback conversation, and the connection between performance ratings and compensation decisions.
Keep the review format simple. A three-to-five question format that covers: what the employee accomplished against their goals, what their strengths are, where they have development opportunities, and what their goals are for the next period, is more useful than a twenty-question form that requires hours to complete and generates feedback that is too generic to act on.
Performance improvement plans (PIPs) are a late-stage intervention and should not be the first tool deployed when someone is underperforming. Build a performance management framework that gives managers the skills and processes to address performance issues earlier, through direct feedback conversations and goal clarification, before they require formal intervention. The most common reason PIPs fail to produce improvement is that they are not preceded by a pattern of direct, documented performance conversations. Train managers on performance conversations as a standard management development investment.
Managing Compensation and Equity Operations
Compensation operations become a significant management and compliance challenge as headcount grows and the organization takes on more diverse role types, levels, and geographies. Building compensation operations that are fair, competitive, and defensible is both a retention strategy and an equity (in the fairness sense) imperative.
Build a compensation framework that includes: a job leveling system that defines levels from individual contributor to executive; a salary band for each level based on market data; an equity grant range for each level; and a bonus or variable compensation structure for roles where variable pay is appropriate.
Market compensation data should come from reliable benchmarking sources such as Radford/Aon, Mercer, Carta Total Compensation, or Levels.fyi for engineering roles. Use market data at the 50th, 75th, and 90th percentiles for each role and level, and define where in that range the company targets offers based on competitive strategy and financial position. Companies at early stages with significant equity upside can compete at the 50th percentile of cash compensation. Companies at later stages with more liquid equity need to compete at higher cash percentiles.
Equity operations require a dedicated process for grant management. Every equity grant should be: authorized by the board or the board’s compensation committee; documented in the cap table management system; accompanied by a grant notice that specifies the number of shares or options, the exercise price (for options), the vesting schedule, and any acceleration provisions; and communicated to the grantee with a clear explanation of the grant’s current value and potential future value at various exit scenarios.
Pay equity analysis should be conducted annually or whenever the company reaches a new compensation framework milestone. Pay equity analysis examines whether employees in similar roles at similar levels and with similar performance are being compensated comparably, and flags disparities that may reflect unintended bias in compensation decisions. Build pay equity analysis into the annual compensation review process before merit increases are determined.
The finance operations infrastructure that supports compensation decisions is detailed in the startup finance ops guide.
Building Onboarding Programs
New employee onboarding is the first real experience a hire has of the company they just joined. Most startup onboarding programs are weak: they cover paperwork, IT setup, and a few introductory meetings, and then leave the new hire to figure out how to be effective largely on their own. Strong onboarding programs accelerate time-to-productivity, improve early retention, and establish cultural expectations more effectively than any policy document.
Build an onboarding program that covers the first ninety days, not just the first week. The first week should include: logistics setup (IT, tools, accounts), company mission and strategy orientation, product and business model overview, introduction to immediate team and key cross-functional partners, and initial goal setting with the manager. The first thirty days should include: deep functional orientation, beginning contribution to real work with clear scope, regular check-ins with the manager, and introduction to broader organizational context. Sixty to ninety days should include a formal thirty/sixty/ninety day review against initial goals.
Build role-specific onboarding supplements that address the technical, process, and relationship knowledge specific to each role family. An onboarding program that is the same for every employee is better than nothing, but it is not optimized for the very different contexts that an engineer, a salesperson, and a finance manager need to be effective quickly.
Onboarding buddy programs, which pair new employees with an experienced colleague outside their immediate team who is not their manager, consistently improve new employee experience and retention at thirty, sixty, and ninety days. The buddy provides informal context, answers questions that new employees feel awkward asking their manager, and gives the company an early signal about new hire experience through regular buddy check-ins.
Knowing When to Invest in HR Technology
HR technology is one of the areas where startup CEOs most often overbuy early. The promise of automated, integrated HR platforms is compelling, but the reality at early stages is that the organizational processes to use sophisticated HR technology effectively often do not exist yet.
For companies below fifty employees, the minimum viable HR technology stack is: a payroll and HRIS platform (Gusto, Rippling, or BambooHR), a cap table management platform, and an applicant tracking system (ATS) for recruiting (Greenhouse, Lever, or Ashby). This stack costs between $500 and $2,000 per month and handles the core HR operations without over-engineering.
Add HR technology deliberately as organizational needs justify it. Performance management software such as Lattice, Leapsome, or Betterworks becomes valuable when the company has implemented a structured performance review process that is running consistently and where the administrative burden of managing it in spreadsheets is material. Employee engagement survey platforms such as Culture Amp or Glint become valuable when the company has the management infrastructure to act on survey results, which typically means at fifty-plus employees with a management layer that can translate survey data into team-specific actions.
The most common HR technology mistake at startup scale is implementing sophisticated platforms before the processes they support are stable. A performance management platform that is implemented before the company has a consistent performance review process will not create a consistent review process. It will create an expensive technology layer on top of an inconsistent process.
The startup product ops guide addresses how product and engineering teams connect to people operations, particularly in recruiting and technical team development contexts.
Managing Culture as an Operational Discipline
Culture is frequently discussed in startup contexts as something that happens organically rather than as something that must be operationally managed. At ten employees, culture can be managed through the CEO’s direct influence. At fifty employees, it must be operationalized through hiring, onboarding, performance management, and management development, or it drifts.
Related Reading
For further context, explore Startup CEO Guide to Business Operations Management and Startup CEO Guide to Customer Success Operations.