The Startup Founder's HR Guide: What to Build, When, and In What Order

Most founder HR guides ask you to download a checklist. Those lists aren't wrong—but they skip the part that actually determines whether any of it works: the decisions you need to make before you build anything.

I've spent nearly six years as a fractional HR leader working exclusively with early-stage startups. Before that, I spent 10 years as a full-time HR leader. In that time, I've seen the same pattern play out repeatedly: founders who skip the philosophy and go straight to the tactics end up with policies that don't reflect how they actually want to run the company, processes nobody follows, and a people function that feels bolted on rather than built in.

This guide is different. It's not a checklist—it's a sequence. And it starts where the work actually has to start which is with the decisions that govern everything else.

Stage 1: Start With Your People Philosophy

Before you write a policy, post a job, or set a salary, you need to answer a handful of foundational questions. These aren't tasks. They're decisions—and making them deliberately, before you need them, is what separates founders who have a people function from founders who have a pile of HR paperwork.

Your Values

Values aren't a wall decoration or a careers page bullet list. They're the operating system for every decision your people function makes. Your compensation philosophy should reflect your values. Your promotion criteria should reflect your values. Your performance expectations should reflect your values.

The difference between values that actually work and values that don't is behavioral specificity. "Integrity" sounds right but it doesn't tell anyone what to do when they face a real decision. "We do what we say we're going to do, and when we can't, we say so immediately" is the same value—but now it's actionable. When you're working through your values, push past the words to the behaviors. What does this value look like when someone is living it? What does it look like when they're not?

Values work best when it happens in conversation with your founding team, not in a vacuum. A facilitated session—even an informal one—where you surface what you actually believe about how work should happen tends to produce values that feel true rather than aspirational.

Your Compensation Philosophy

Most founders set salaries the same way. A candidate mentions what they made at their last job, the founder adds a little, and an offer goes out. This is how you end up with a compensation structure that wasn't designed—it accumulated. And accumulated comp structures almost always have problems like compression between early and later hires, unexplainable pay gaps between similar roles, or equity grants that don't reflect any coherent philosophy.

Before you make your first offer, decide how you want to pay people relative to the market. The framework most HR practitioners use has three positions: lead the market (pay above median to attract and retain top talent), meet the market (pay at median), or lag the market (pay below median, typically offset by equity or mission). None of these is the right answer for every company. The right answer depends on your stage, your cash position, and what you're competing for. If you're weighing what kind of HR support can help you think through these decisions, here's how to know when your startup actually needs fractional HR.

A few things founders consistently underestimate here:

Salary is only one part of total rewards. Equity, bonus, culture, benefits, flexibility, and growth opportunity all contribute to what a candidate actually experiences as their compensation. A below-market salary with meaningful equity and full benefits can be a genuinely competitive offer. A market-rate salary with no equity and poor benefits often isn't. Know what your total package looks like before you start recruiting.

Scan comp data, not job postings. The most common mistake founders make when trying to understand market rates is pulling numbers from other job postings. Job postings are unreliable—companies post aspirationally, and the actual offer is often different. When possible, use verified compensation data. Tools like Radford, Levels.fyi, and Carta provide real compensation data by role, level, and geography. This data can be expensive to access, but it's significantly more accurate than inferring rates from what competitors are advertising.

Make the decision by role category, not company-wide. You may want to lead the market for engineers, meet the market for sales, and lag slightly for operations roles where equity upside is less relevant. That's a coherent philosophy. What isn't coherent is making different decisions for different candidates within the same role based on whoever negotiated harder.

Your Hiring Philosophy

A few decisions here that founders often make implicitly—and then discover the consequences of later:

Which states will you hire in? This isn't just an operational question. Employment law is state-by-state, and some states carry significantly more compliance complexity than others. California, for example, requires employers to offer access to a 401(k) retirement plan and has some of the most employee-protective employment laws in the country. New York, Colorado, and Illinois have their own requirements around pay transparency—meaning you may be required to post salary ranges in job listings depending on where your candidates are located. Deciding your hiring geography up front, before you've made commitments you didn't know you were making, matters more than founders typically realize.

Employee or contractor? The classification question should be answered deliberately before any working relationship starts—not after. Misclassification is one of the most expensive HR mistakes an early-stage company can make, and it compounds the longer you wait to fix it. If you're not sure how to classify someone, ask an HR professional before you start the engagement.

What does your hiring process actually look like? Consistency matters here for both quality and legal defensibility. Decide in advance what stages candidates go through, who's involved, what you're evaluating, and how decisions get made. An ad hoc hiring process produces ad hoc hires.

Stage 2: The Foundation (Pre-Hire)

With your philosophy in place, the pre-hire infrastructure is relatively straightforward. These are the things that need to exist before your first employee starts.

An offer letter template. Not something you draft fresh for each hire. A template, reviewed once by an employment attorney, that you use consistently. It should confirm the role, compensation, start date, and employment relationship—including at-will status. Consistency here prevents you from accidentally creating different terms for different people.

Worker classification clarity. Before anyone starts working for you—employee or contractor—have a clear answer to the classification question and a record of how you made that decision.

A basic anti-harassment and anti-discrimination statement. Several states require this in writing. Even where it's not required, having it acknowledged by every employee before they start matters if you ever have to respond to a complaint.

A compensation framework. Not a full salary matrix—but a coherent answer to "how are we paying for this role and why?" grounded in your compensation philosophy and actual market data.

A hiring process. Defined stages, defined evaluation criteria, defined decision-making. Before you post your first job.

Payroll set up properly. Through a legitimate payroll system that handles withholding, tax filings, and reporting. Not Venmo. Not bank transfers. A real payroll platform, from the first payment.

For a more detailed look at what's non-negotiable before your first hire—and what can wait—this post covers the full breakdown.

Stage 3: The First 10 Hires

This is the phase where the gaps in your foundation show up—and where the things you skipped come back to cost you. A few areas that break quietly if you don't address them here.

Onboarding

The most common onboarding failure isn't a bad first week. It's no one thinking about onboarding until the person's first day.

A new hire's first 30, 60, and 90 days set the foundation for how they perform, how connected they feel to the company, and whether they stay. Getting this right doesn't require a complicated program. It requires one thing most founders skip: thinking about it in advance.

The exercise I run with every founding team is simple. We get on a call—founders, early leaders, anyone who has context on what a new hire needs—and do a brain dump. What does this person need to know? Who do they need to meet? What access do they need on day one? What should they be able to do independently by day 30? By day 60? What does success look like at 90 days?

From that conversation, we build a simple 30/60/90 day plan. Not a 40-page document. A clear roadmap that gives the new hire context, sets expectations, and tells them what they're working toward.

One thing that almost always comes out of that conversation and almost never gets covered otherwise: who teaches this person how the company makes money? Everyone on your team should understand your business model—how revenue is generated, what the unit economics look like, what success means at the company level. This gets missed constantly. A new hire who doesn't understand how the business works can't make optimal decisions, can't prioritize effectively, and can't connect their work to outcomes that actually matter.

A Basic Employee Handbook

You don’t need a 50-page document but you do need a clear, honest answer to the questions your employees are going to have: how time off works, what the expectations are around conduct, how concerns get raised, and where to go with questions. The goal is consistency—the same answers for everyone, in writing, acknowledged by every person who joins.

Performance Expectations

Before you can have a performance conversation, you need to have communicated what good performance looks like. This sounds obvious. It almost never happens proactively. Managers often wait until someone is struggling to define what they expected—at which point the employee is hearing the standard and the failure simultaneously.

Set expectations at the start of every role, not in response to a problem. If you do find yourself in a situation where you need to address underperformance, here's how to have that conversation without making it worse.

Manager Basics

If you're promoting anyone into a management role during this phase—or hiring your first people manager—invest in giving them a foundation before they start managing. A conversation about what you expect from managers at your company, how you want feedback to be given, and what support they'll have goes a long way. Even a basic manager coaching conversation before someone takes on direct reports is more than most early-stage companies provide.

Stage 4: 10–50 Employees

This is the phase where founder-led HR stops being feasible. The volume of people questions, the complexity of the situations, and the strategic decisions required all exceed what a founder can handle well alongside everything else they're managing. This is where fractional HR tends to deliver its highest ROI—you're big enough to have real people infrastructure needs, but not yet big enough to justify a full-time senior HR leader.

Performance Management

At 10 people, your performance process can be lightweight. A start/stop/continue conversation. A stoplight framework—what's green, what's yellow, what's red. Something that creates a regular rhythm of feedback and gives employees a sense of where they stand.

The goal at this stage isn't a sophisticated review system. It's a consistent practice. Managers giving feedback regularly, employees knowing where they stand, and the company having a shared vocabulary for what good performance looks like.

As you grow toward 50, that lightweight process will need to evolve—more structure, more documentation, clearer criteria for evaluation. But the habit of regular performance conversations is the foundation everything else builds on. You can't add structure to a process that doesn't exist.

Multi-State Compliance

If you're hiring remotely—and most startups are—you're likely adding employees in new states regularly. This is where founders consistently get caught off guard.

Employment law is not a single national framework. It is state-by-state, and in some cases city-by-city. California requires employers to provide access to a 401(k) plan and has mandatory paid sick leave, extensive protections around termination, and some of the strictest employment law in the country. Colorado, New York, Illinois, and Washington now require pay transparency—meaning job postings must include salary ranges. Several states have mandatory paid family and medical leave requirements that vary significantly from federal law.

Your compliance obligations are determined by where your employees work—not where your company is incorporated or where your headquarters is. Every time you hire in a new state, you're taking on that state's employment law framework. Before you make an offer to someone in a new state, spend time understanding what that means—or ask someone who knows.

For a deeper look at the compliance basics that apply from the earliest stages, this post covers what you need to know.

Compensation Benchmarking

By the time you have 20 or 30 employees, the compensation decisions you made in your first year are showing their age. Market rates shift. Your team's roles evolve. People you hired at one level have grown into something different. New hires are coming in at rates that may or may not be consistent with your existing team.

This is the phase to do your first formal compensation review—auditing what you're paying against current market data and looking for the compression, gaps, and inconsistencies that accumulated while you were moving fast. It's also when your total rewards picture—equity refresh strategy, benefits benchmarking, bonus structure if you have one—deserves real attention rather than the default decisions you made early on.

HR Technology

At some point between 10 and 50 employees, your spreadsheets stop working. You need an HRIS—a system that tracks employee data, manages time off, stores documents, and serves as the source of truth for your people information. You probably also need an ATS (applicant tracking system) if you're hiring consistently.

The right tools depend on your size and needs. What matters most at this stage is that someone owns the decision and the implementation—because HR tech that nobody set up properly and nobody maintains is often worse than no HR tech at all.

When to Bring In Fractional HR

The honest answer: after your first ten employees, as you're starting to scale and founder-led HR is no longer feasible or desirable.

By this point, you have real performance management needs, multi-state compliance exposure, compensation questions you're not equipped to answer alone, and a manager population that needs development. These are not tasks. They require judgment, experience, and dedicated time. A fractional HR leader at this stage can build the infrastructure, navigate the complexity, and give you the strategic thought partnership that founder-led HR never could—at a fraction of the cost of a full-time senior hire.

If you're trying to figure out whether this is where you are, this post walks through the signals.

Stage 5: 50–100 Employees

By 50 employees, the people function has real complexity. You have multiple layers of management, a culture that's been shaped by hundreds of decisions you may or may not have made intentionally, and an organization that's large enough to have real structural questions. This phase is about building the infrastructure that lets the company scale without losing what made it work.

Organizational Design

How your company is structured communicates everything about how decisions get made, where accountability lives, and how information flows. A structure that worked at 20 people often creates real bottlenecks at 50—too many direct reports, unclear ownership, leadership gaps in critical functions.

This is the phase to be intentional about structure rather than reactive to it. Not a reorg for its own sake, but an honest look at whether the way you're organized reflects how you actually want to operate—and whether it can hold up to the growth ahead.

Manager Development

By now, you have a meaningful population of people managers—and the variance in how they manage is one of the biggest variables in your culture and your retention. Some of your managers are exceptional, some are struggling, and most are somewhere in the middle, doing their best without much support.

Manager development at this stage isn't a training program. It's a sustained investment in the people who are most responsible for how your employees experience working at your company every day. That means regular coaching conversations, a shared framework for how managers are expected to operate, and honest feedback about what's working and what isn't.

The promotion question from Part 1 comes back here: did you ask if they wanted to manage? Did you train them? Did you get them coaching? The managers you invested in early are the ones who are thriving now. The ones you promoted and left to figure it out are the ones causing your retention problems.

Culture Infrastructure

Culture is the sum of every decision your managers make every day about what gets rewarded, what gets tolerated, and what gets called out. By 50 employees, your culture has been shaped by thousands of those decisions—some of them intentional, many of them not.

This is the phase to get explicit about what you're actually building. That means revisiting your values and asking honestly whether they're still living in the decisions your team makes, or whether they've become wall decorations. It means looking at where the stated culture and the lived culture have started to diverge—because they almost always do during fast growth—and deciding what you're going to do about it.

It also means thinking about the rituals and practices that reinforce culture at scale: how you run all-hands meetings, how you celebrate wins, how you handle failure, how you bring new people into the community. These things don't happen accidentally at 50 people. Someone has to design them.

Planning for a Full-Time People Hire

Somewhere between 75 and 100 employees, most companies cross the threshold where fractional HR is no longer sufficient as a primary model. The volume of HR work becomes constant rather than episodic. The complexity of the people function requires someone embedded and full-time. And the strategic needs of the organization require a dedicated senior leader—not someone splitting time across multiple clients.

Planning for that hire before you urgently need it is significantly better than making it reactively. A fractional HR leader can help you define what the role actually needs to look like, build the infrastructure that makes a new hire successful from day one, and support the transition so you're not starting from scratch.

For a detailed look at how to think through the fractional vs. full-time decision, this post covers it in depth. And if you're wondering whether what you need is CHRO-level leadership rather than an HR manager, here's how to think through that decision.

The Through Line

Every section of this guide connects back to the same thing: decisions made proactively are almost always better than decisions made reactively.

The founders who have the cleanest people operations at 100 employees aren't the ones who moved fastest or spent the most. They're the ones who thought before they built—who made the philosophy decisions before they needed policies, who built the foundation before they needed to scale, and who got the right support before the absence of it started costing them.

You don't have to build everything at once. You have to build the right things in the right order, before the moment when the absence of them becomes a problem.

That's what this guide is for.

Building a people function and not sure what to tackle first? I work with early-stage startups at every stage of this build—from pre-hire through the first full-time People hire. Book a free consultation here.