Building HR Systems That Scale
By the time a company calls me about HR, the symptom is almost always the same: every people decision is being made from scratch. Each offer letter is a fresh negotiation, each performance conversation a new invention, each new state a surprise. The problem is rarely that anyone is doing the work badly. It is that there is no system, so nothing compounds and every quarter starts over.
HR systems get built in risk order, not alphabetical order. The sequence that holds is employment documentation first, then leveling and performance, then hiring infrastructure, then the programs that improve experience. Reversing that order is how companies end up with an engagement survey and no offer letter template. A fractional CHRO builds in this sequence because it front-loads the work that is cheap to do early and dangerous to fix late.
Why Build Order Matters More Than Build Quality
Build order matters more than build quality because a beautifully run program sitting on top of a broken foundation is still a liability, just a well-branded one. An engagement survey does not help you if your employment agreements are unenforceable across the states you hire in. A recognition program does not protect you in diligence. I have watched companies invest a full quarter in culture initiatives while a single misclassified contractor and a stack of inconsistent offer letters sat untouched underneath. Risk order means you build the layers that reduce legal and financial exposure first, then the layers that improve experience, in that direction and not the other.
The five stages below are that order. In many engagements, the sequence is compressed or overlapped based on what discovery reveals, but the direction holds: documentation, then structure, then hiring, then enablement, then experience.
Stage 1: Employment Documentation and Classification
Stage one is employment documentation and worker classification, because it carries the highest exposure and it is the cheapest to fix before anyone forces the question. The artifacts are concrete: an employee handbook, a code of conduct, offer letter templates, a leave and PTO policy, and a multi-state compliance, confidentiality, and non-compete agreement engineered to hold across differing state laws. Alongside the documents, a classification review of every employee and contractor.
This is not theoretical. A fractional CHRO in the 5FT View Collective, built exactly this layer from zero in under twelve months for a company that had reached 275 people across five or more US states and international contractor markets with no HR function at all. Employment terms ended up standardized across every jurisdiction. That is what a finished Stage 1 looks like.
Stage 2: Leveling and a Documented Performance Framework
Stage two is leveling and performance, because once the documentation is sound, the next risk is inconsistency: pay decisions and performance judgments made differently by different managers. The artifacts are a leveling structure that defines roles and bands, career tracks including an individual-contributor path, and a documented performance framework that makes reviews repeatable. Across a body of work spanning more than fifty venture-backed companies, one CHRO built an eight-level career framework covering engineering, sales and operations, and compensation-equity complaints fell by roughly forty percent after leveling and dual-track paths were introduced.
Stage 3: Hiring Infrastructure and Offer Process
Stage three is hiring infrastructure, because now that roles and levels are defined, you can hire against them consistently. The artifacts are a structured interview process, scorecards tied to the leveling framework so every interviewer evaluates against the same bar, an offer and approval workflow, and a hiring roadmap mapped to the business plan rather than to whichever role feels most urgent this month. In our CHRO’s 275-person engagement, this layer cut time-to-fill from ninety days to forty-five, reached an eighty percent offer acceptance rate and eighty-seven percent retention at ninety days, delivered fifteen senior technical sales hires, and produced a three-year roadmap with the CEO, CFO and board covering more than forty hires mapped to revenue targets and territory coverage.
Stage 4: Manager Enablement
Stage four is manager enablement, because the systems only hold if the people using them can run them without escalating everything upward. The artifacts are a manager playbook, a documented process for routine performance and personnel conversations, and clear escalation paths. In the same engagement, every employee relations matter was resolved without legal escalation, and managers moved from escalating routine performance conversations to handling them directly once the structure behind those conversations existed.
Stage 5: Experience, Engagement and Culture Programs
Stage five is experience, engagement and culture, and it comes last on purpose. These programs are valuable, and they are also the layer that fails first when the foundation underneath is weak. The artifacts here are a structured onboarding experience, a way to measure engagement that actually feeds decisions, and recognition and development programs that reinforce the leveling you built in Stage 2. Onboarding, engagement measurement, and recognition work when they sit on solid documentation and fair leveling; they are decoration when they do not. In one engagement, a Collective CHRO sustained employee trust and retention through a specialty therapeutics company’s post-acquisition restructuring, which is integration and retention work, not healthcare regulatory compliance, and it held because the structural layers were already in place.
Multi-State: What Changes When You Hire Across Jurisdictions
Multi-state hiring makes Stage 1 harder than any other factor, which is why it deserves its own note. Each new state adds its own wage-and-hour rules, leave requirements, pay transparency laws, and notice obligations, and international contractors widen the surface again. This is why the multi-state employment agreement in Stage 1 has to be engineered to hold across differing state law rather than copied from a single-state template. In another CHRO engagement, obligations were mapped and remediated state by state across all five-plus jurisdictions, which is the work that makes the rest of the system portable.
What a Function of One Can Realistically Run
A single senior person can run HR for a company well past two hundred people, but only if the role is designed to build systems rather than to process transactions. That is the distinction that makes a function of one viable: the fractional CHRO installs the documentation, leveling, hiring and enablement layers, and once those exist, the day-to-day volume drops to something a coordinator or a PEO can administer. The senior time goes to judgment calls and design; the routine execution, benefits questions, onboarding paperwork, record keeping, moves to a lower-cost layer underneath. In the referenced CHRO engagement, a one-person people function operated at 275-person scale, and the CEO and board finally received workforce data they had never had before.
None of these stages happens in isolation from the rest of the business, which is the argument for building inside a Collective of fractional experts rather than hiring a solo operator: leveling is a finance decision, the hiring roadmap is an operating decision, and those handoffs are cleaner when a fractional COO services partner is in the same room.
Frequently Asked Questions
What HR systems should a growing company build first?
Employment documentation and worker classification, because that is where exposure is highest and the fix is cheapest early: handbook, offer letter templates, leave policy, and enforceable multi-state agreements. Leveling, hiring and enablement follow. Experience programs come last.
What goes in an employee handbook?
At minimum: a code of conduct, leave and PTO policy, anti-harassment and complaint procedures, and state-specific addenda for every jurisdiction you employ in. In a multi-state company, the handbook is not one document; it is a core plus jurisdiction-specific sections.
What is a leveling framework?
A leveling framework defines roles by scope and seniority into consistent bands, so pay, promotion and hiring decisions are made against a standard rather than case by case. It usually includes both a management track and an individual-contributor track.
When do we need a documented performance process?
Before you need to act on a performance problem, not during. A documented process makes reviews consistent across managers and gives you defensible ground when a difficult decision arrives. Building it reactively, mid-case, is the expensive way.
Can one person run HR for a 200-person company?
Yes, if the role is senior and systems-first. A fractional CHRO can install the full infrastructure and run a function of one at that scale; one Collective engagement did exactly that at 275 people. Once the systems are in place, routine administration can sit with a coordinator or a PEO.
Not sure which stage your company is actually on, or what to build next?
A discovery call is free and carries no obligation, and there is no paid diagnostic step. It is a low-pressure way to map where your people systems stand and what the highest-risk gap is. You can book a free discovery call whenever it is useful.
If you are still deciding whether you need senior HR at all, start with when to hire fractional HR leadership, or see the role in full at fractional CHRO.
Learn more about our Fractional CHRO Services.


