All Posts

It’s a classic sign that you’ve outgrown your initial approach. You look at your HRIS and see "Software Engineer III," "Senior Developer," and "Lead Coder" all doing the exact same work, but on three different pay bands. This is "technical debt" for People Ops. It’s the legacy of hiring for speed over structure. When you're stuck in the Guesswork Gap , you do whatever it takes to close a candidate in the moment. The result is a mess that’s impossible to manage at scale. Clean

At the Seed stage, you hire for the mission. You need people who are there for the "why." They are the ones who take the pay cut because they believe in the vision. But as you hit your stride, you start hiring for the "how." You hire the specialists. These are the ones who know exactly how to scale your engineering or sales org. Some call them Mercenaries. I call them high-level professionals who know their market value. The Guesswork Gap hits when you try to manage both g

We’ve all been there. You’re in a Board meeting or a high-stakes ELT session when the CFO asks a pointed question about attrition in Engineering or the cost of the new hiring plan. If the answer starts with "I think" or "the general sentiment is," the room starts to drift. It is not that your insight is wrong. It is that the answer requires more: data . When you are stuck in the Guesswork Gap , you are often forced to rely on anecdotes because your compensation data hasn't be

It happens every merit cycle. You’re sitting with your Head of Finance, trying to justify a 15% raise for a key employee because "they’re the heart of the team" or "they’ve been here since the beginning." Those things matter. But they aren’t the data points Finance needs to approve the spend. When you’re stuck in the Guesswork Gap , you’re often forced to advocate for your people based on vibes alone. That’s how budgets get stalled. It’s not that Finance doesn't care, they ju

"I wanted to give you the raise, but HR wouldn't let me." If you've heard a manager say this, you have a Guardrail  problem. When managers don't have a clear framework to explain pay decisions, they default to blaming "the system" or HR to avoid an uncomfortable conversation with their team. This creates a culture where HR is seen as the "Budget Police" and managers are seen as powerless advocates. It’s a dynamic that erodes trust on both sides. Bridging the gap means giving

When you're stuck in the Guesswork Gap , offer letters are usually 10% math and 90% "selling the dream." Founders often over-index on the mission because they aren't confident in their actual numbers. They're guessing at the market rate and just hoping the candidate doesn't push back too hard. But once you outgrow that scrappy phase and build Guardrails , the tone changes. A "Guardrail" offer is clear, clinical, and confident: Math over Pitching : You aren't "pitching" a sala

In the early days, you guess at perks based on what’s trendy. It feels like culture at the time. But as you scale, those guesses just start eating into your runway. I call this the Guesswork Gap . You’re paying for "premium" meditation apps or $1,500 learning credits that only 5% of the team actually touches. Meanwhile, your best people are looking at the exit because their base pay hasn't kept up with the market. If you have outgrown the "founder discretion" phase, you have

Founders and Heads of People in SaaS startups: Stop overthinking your first compensation ranges. One of the bigger misconceptions held by seed-to-Series B leaders is that you need "perfect" data to build your first salary structure. You don't. You need Guardrails. Without ranges, every offer is a negotiation against yourself. With ranges, every offer is a strategic decision. Here is the "MVP" (Minimum Viable Pay) Playbook to build your first set of ranges in 60 minutes: The

With the EU Directive deadlines looming and new laws popping up across US states, every leadership team is feeling the pressure. Founders and Heads of People are concerned. They imagine a line of angry employees outside their door demanding raises because they saw a job posting with a higher range or—soon—a mandated internal report. But in my experience, employees don't quit because of the number. They quit because of the silence. When there is silence on pay , human nature f

Earlier today I had an opportunity to chat with CNBC Make It about a growing trend in compensation: the "Peanut Butter" raise. The Strategic Risk My take is that market leverage is a temporary tactic, but retaining top-tier performance is a long-term strategy. Right now, some companies may see the cooler job market as an opportunity to simplify their merit process. They lean into "normalizing mediocrity" by spreading a thin 3% budget across the board, assuming that lower tu

And you hope they do not find out. Every Founder and VP of People dreads this moment during a growth spurt. You find the perfect candidate. They are a game-changer. But the market price for their role has jumped 20% since you hired your current team. To land them, you must break your own pay band. You sign the offer letter, but your instincts tell you it is a mistake.    Because you know the clock is ticking. Eventually, people talk. And when your loyal high-performer finds o

It is the silent struggle of every HR leader in a growth company. You took this role to lead the People Strategy : • Building a high-performance culture. • Developing your next layer of leaders. • Driving the talent acquisition roadmap. But then the "Comp & Benefits Reality" hits. Instead of developing people, you get pulled into a different type of strategic work. One that requires deeper technical and financial engineering. It starts innocently enough. • "I'll pull a quick

It is the moment every founder worries about. Your key player puts in their notice: "I’ve been offered a role at a competitor for 20% more." The instinct is to panic. You immediately think: "I have to match it. I can't afford to lose them right now." Here is the paradox: If you convince them to stay solely by matching the money, you haven't really kept them. You’ve just delayed them for another six months. Why? Because rarely does someone leave a job they love just for money.

There is a risk organizations face for retention and it isn’t when a project fails or a client churns.    It is the day after  bonuses hit bank accounts. As a founder, you view the bonus cycle as a "Lock-In." You think, "I just wrote a huge check. They know they’re valued. We’re good for another year." But your top performers view it differently. They view the bonus as a "Settlement." The salary paid for their time. The bonus paid for their results. The ledger is now balanced

We need to kill the "Annual Bonus." For decades, companies have relied on this tool to drive performance. The logic seems sound: "Work hard for 12 months, and we will give you a big check in December." But in a modern startup, this logic is broken. 𝗧𝗵𝗲 "𝗧𝗶𝗺𝗲-𝗚𝗮𝗽" 𝗣𝗿𝗼𝗯𝗹𝗲𝗺: For a reward to reinforce a behavior, it must happen immediately after the action. The Annual Bonus breaks this rule. You are asking an employee to hustle in February for a reward they 𝘮𝘪�

You have a 3% merit budget. Your managers are staring at a spreadsheet, trying to decide who gets what. The human instinct is to avoid conflict. So, managers do what is called "spreading the peanut butter." They give the low performer a 2.5% raise (to be nice). They give the top performer a 3.5% raise (to stay within budget). Everyone gets a thin layer. It feels fair. It feels safe. 𝗕𝘂𝘁 𝗺𝗮𝘁𝗵𝗲𝗺𝗮𝘁𝗶𝗰𝗮𝗹𝗹𝘆, 𝘆𝗼𝘂 𝗷𝘂𝘀𝘁 𝗵𝘂𝗿𝘁 𝘆𝗼𝘂𝗿 𝗿𝗲𝘁𝗲𝗻𝘁𝗶𝗼𝗻. Her

I see the same scenario play out in startups consistently. A Founder fights hard to get a "Yes" from their top candidate. They stretch the budget. They offer $15k over ask. They think they have won on the numbers. But the candidate still walks away. Why? Usually, it’s because the Offer Letter looked like a black box. The Equity section simply said: "Option to purchase 15,000 shares." To a Founder, that looks like generosity. To a smart candidate, that looks like a lottery tic

Most founders I meet are guessing at their compensation strategy. Here is a 5-Point "Comp Health Check" you can use to stop the guessing game. 1. Philosophy : Do you have a written statement defining how  you pay relative to the market? Warning Sign:  "We pay what it takes to get them." Healthy Sign:  "We target the 75th percentile for engineering and 50th for admin." (For example). 2. Data : When was the last time you benchmarked your roles against real market data? Warning

"Market Rate" is a misleading term. It implies there is a specific sticker price for talent. Like a gallon of milk. Leaders often think they can just look up "VP of Engineering" and find a single answer. But in the real world, compensation data isn't a price tag. It is a scatter plot. If you pull the raw data, you will see a massive range for the exact same job title. Why? Because the "market" is a messy mix of bootstrapped startups (paying in equity) and Big Tech giants (pay

I see a specific inefficiency in almost every Series B payroll. A founder looks at their budget and sees a $180k - $220k line item for a "VP of Operations" or "Head of Product." On paper, the compensation matches the market data for an executive. But in reality, the founder is still doing the job.  They are still designing the strategy, making the final call on vendors, and carrying the mental load. This happens because we confuse Reward  (Performance) with Role  (Scope). Whe