CFO Search in Mexico: The Cultural Variable That Decides It
May 11, 2026
Sales Comp Plan Design: Why Your Revenue Is Broken
May 15, 2026
First HR Hire: Why Startups Always Wait Too Long
The First HR Hire: Why Startups Build People Infrastructure Too Late
Fifty employees. No employee handbook. No onboarding. No performance system.
The founder said, "We haven't needed HR yet." Three employment issues later, they needed it retroactively. I've seen this sequence enough times that the headcount alone tells you where it's going to break.
The company grows from ten people to thirty to sixty through sheer momentum. The founder makes every hiring decision personally. Compensation is negotiated ad hoc. Onboarding is a laptop, a Slack invite, and a conversation with whoever has ten minutes. Then something breaks: an employee files a complaint, and there's no process to handle it; a termination goes sideways because nobody documented the performance issues; a manager creates legal exposure because there was no training on what managers can and can't do.
The founder's response is always some version of: "I guess we need an HR person."
The problem isn't that companies don't build people infrastructure. It's that they build it after the risk has already materialized.
Why Founders Delay This Hire
These aren't excuses. They're the belief system that creates the delay.
"HR is bureaucracy." The founder associates HR with the large-company experience they had before founding: slow approvals, mandatory training, and thick policy manuals. They're not entirely wrong about that experience. They're wrong about what HR should look like at their stage.
"We're small enough to handle it ourselves." At twenty people, the founder knows everyone. The relationships are personal. The processes are informal but functional. The belief is that this can continue indefinitely. It can't, but at twenty people, there's no evidence to the contrary.
"We'll deal with it when we have to." The founder is focused on product, revenue, and customers. People infrastructure feels like a nice-to-have. They'll build it when they have time. They never have time. Then the crisis arrives, and they build it retroactively, which costs three times as much and takes twice as long.
"I don't want to change the culture." The most revealing one. The founder equates HR with cultural compromise. There's a kernel of truth here. Bad HR implementation does kill good culture. Good HR implementation preserves it.
What Breaks Without People Infrastructure
Compensation Becomes a Mess
Without a compensation framework, every offer is a negotiation. Early employees negotiated when the company was desperate. Recent hires negotiated when the company had options. The result: people in similar roles at wildly different pay levels, with no logic connecting the numbers.
The problem isn't the numbers. It's that there's no logic behind them.
This is invisible until someone compares notes. Then it's a morale crisis. The senior engineer who joined at $130K discovers that a junior hire started at $145K because the market moved, and nobody adjusted the existing team.
Onboarding Creates Early Turnover
The founder sees the people who stayed. They don't see the ones the system quietly pushed out.
The senior hire who spent their first week without access to the tools they needed. The product manager who never met half of their cross-functional partners. The sales rep who started selling without understanding the product. Some stayed and figured it out. Some left in the first ninety days, and the founder attributed it to "bad fit" rather than bad infrastructure.
Performance Problems Fester
Without a performance management framework, underperformance is handled in one of three ways: avoidance (the manager ignores it), explosion (the manager fires the person without documentation), or the founder's personal intervention (which doesn't scale past 30 people).
None of these scales. All of them compound.
Legal Exposure Accumulates Silently
Most of this risk sits invisible until someone decides to make it visible.
Hiring processes that inadvertently ask legally problematic questions. Terminations lacking documentation. Wage and hour practices that don't comply with state-specific requirements. Managers making promises about advancement that the company can't honor. None feel dangerous at the time. Each one is a liability sitting in the background.
When the Hire Is Already Overdue
By the time these signals appear, the company is already late.
The founder is personally handling employee issues that consume hours each week. Compensation questions, interpersonal conflicts, and onboarding confusion, each is a fifteen-minute interruption that adds up to a part-time job that isn't the founder's actual job.
Managers are making people decisions inconsistently. One gives raises based on gut feeling. Another hasn't had a performance conversation in a year. Without a framework, managers default to their own instincts, and those instincts vary wildly.
The company has had a near-miss with employment law. A termination that could have gone sideways. A compliance question nobody could answer confidently. A conversation with a lawyer that revealed gaps the founder didn't know existed.
New hires are taking too long to become productive. If it consistently takes three to four months before new employees contribute, the onboarding process is the problem. The cost is invisible but real.
The culture the founder values is eroding under scale. Informal decision-making that worked for fifteen people creates confusion at fifty. The founder notices the culture feels different but can't identify why. The reason is that culture at scale requires infrastructure that hasn't been built.
What the First HR Hire Should Actually Do
This is where most companies get the second mistake wrong.
They hire too senior, too early, or too late, under pressure.
The first HR hire at a growth-stage company is not a CHRO. It's not a Chief People Officer. The title inflation here is predictable. The conditions don't support a CHRO. The company hires one anyway. What the role actually requires is an operationally strong people leader, typically at the Director or VP of HR level, who can build the infrastructure that should have been in place six months ago.
First sixty days: assess and triage. Map the existing people landscape: compensation data, compliance gaps, pending issues, onboarding failures, and manager capability. Identify the three to five highest-risk areas. Don't change anything yet.
This is the formation lap. If you start racing here, you crash.
Days sixty through one-twenty: build the foundation. Minimum viable people infrastructure: an employee handbook that reflects actual practices, a compensation framework that provides logic and consistency, an onboarding process that gets new hires productive faster, and a performance conversation framework that gives managers a starting point.
Days one-twenty through one-eighty: operationalize. Train managers on basic people management. Implement the performance framework. Establish the compliance baseline. Create the feedback channels that tell the founder what's actually happening in the organization.
Beyond one-eighty: evolve. With infrastructure in place, the HR leader begins the strategic work: organizational design for the next stage, leadership development, and workforce planning.
Start operational. Earn strategic credibility through operational excellence.
The Cross-Border Complication
In cross-border companies, this isn't just late. It's dangerous.
For U.S. companies with operations in Mexico, the first HR hire is even more urgent and more complex. Mexican employment law is structurally different: stronger employee protections, different termination requirements, and different benefits obligations. The U.S. founder who applies American HR assumptions to Mexican operations creates legal exposure that goes beyond what a retroactive fix can address.
If the company has employees in Mexico, the first HR hire needs cross-border experience or must be paired immediately with Mexican employment counsel.
This isn't an HR problem. It's a structural risk most founders don't know they're carrying.
The Pattern
Companies build finance infrastructure early because failure is immediate.
People infrastructure fails slowly, until it doesn't.
This is why the first HR hire almost always happens too late. The signal isn't visible until the cost is already real. By the time the search starts, the company isn't building infrastructure. It's repairing damage.
Hire before the system breaks.
Because once it does, you're not building infrastructure. You're unwinding decisions that should never have been made.
Charlie Solórzano is a Managing Partner at Alder Koten, a boutique executive search firm specializing in C-suite and board placements across the U.S. and Mexico markets. He advises founders, investors, and boards on leadership transitions using The Race Conditions Model™, a proprietary diagnostic framework built on the thesis that leadership success is determined by conditions, not credentials.
Ready to Make the First HR Hire?
Getting the timing and level right on the first HR hire is as consequential as the hire itself. Too senior too early, and you get a CHRO in conditions that need an operator. Too late, and you're repairing damage instead of building infrastructure. If you're approaching this search, let's talk about what the role actually requires at your stage.
Schedule a Confidential ConsultationFrequently Asked Questions
When should a startup make its first HR hire?
Before the system breaks — which is typically earlier than most founders expect. By the time the visible signals appear (founders personally handling employee issues for hours each week, managers making inconsistent people decisions, a near-miss with employment law, new hire productivity taking three to four months), the company is already late. The invisible signals arrive sooner: compensation decisions being made without a framework, onboarding running on informal processes, performance problems being avoided rather than addressed. The right time is when these patterns are forming, not when they've become crises.
Should a startup hire a CHRO or a VP of HR as their first people leader?
Almost always a Director or VP of HR, not a CHRO. The conditions at most growth-stage companies don't support a CHRO — the infrastructure doesn't exist yet, the strategic mandate hasn't been established, and the organizational complexity doesn't require C-suite people leadership. What the company needs is an operationally strong people leader who can build the minimum viable infrastructure first and earn strategic credibility through operational excellence. Hiring a CHRO too early into conditions that need an operator produces exactly the bureaucratic experience the founder feared.
What does the first HR hire actually need to do in the first 180 days?
Three stages. First sixty days: assess without changing — map compensation data, compliance gaps, pending issues, onboarding failures, manager capability. Identify the highest-risk areas before building anything. Days sixty through one-twenty: build minimum viable infrastructure — a handbook that reflects actual practices, a compensation framework with logic behind it, an onboarding process, and a performance conversation framework for managers. Days one-twenty through one-eighty: operationalize — train managers, implement the performance framework, establish the compliance baseline. Strategic work comes after the operational foundation is solid, not before.
Why do startups with good cultures delay building people infrastructure?
Because they equate formalization with cultural compromise. The founder built the company by moving fast and associating HR with the large-company experience they rejected. There's a kernel of truth: bad HR implementation does kill good culture. But the alternative — no people infrastructure at all — doesn't preserve culture. It allows culture to erode under scale in ways the founder notices but can't diagnose. Informal decision-making that worked at fifteen people creates confusion and authority gaps at fifty. The infrastructure doesn't change the culture. It holds it.
What legal risks accumulate when startups delay HR infrastructure?
Several, and none announce themselves until someone decides to act on them. Hiring processes that inadvertently ask legally problematic questions. Terminations that lack the documentation required to defend against wrongful termination claims. Wage and hour practices that don't comply with state-specific requirements. Managers making promises about advancement that the company can't honor. Compensation structures with unexplained inequities that create discrimination exposure. Each one sits invisible in the background. The cost of addressing them retroactively is consistently three to five times higher than building the infrastructure that prevents them.
How does having employees in Mexico change the first HR hire for a U.S. startup?
It makes the hire both more urgent and more complex. Mexican employment law is structurally different from American employment law: stronger employee protections, different termination requirements, profit-sharing obligations (PTU) that have no U.S. equivalent, IMSS contribution requirements, and STPS compliance standards. The U.S. founder who applies American HR assumptions to Mexican operations creates legal exposure that retroactive fixes often can't fully address. If the company has employees in Mexico, the first HR hire either needs genuine cross-border experience or must be paired immediately with Mexican employment counsel. This is foundational, not optional.
