All Posts

A strong performer asks why a new hire makes more than they do. What you say next tells you everything. Either you have a compensation system, or a collection of decisions. Most HR leaders reach for the number. You explain the new hire's experience. The competitive market. The timing of the offer. All of it true. None of it holds up. Because the employee is not really asking about the number. They are asking whether the system is fair. And "the market was hot when we hired th

Pay transparency doesn't expose your pay. It exposes your structure. Everyone thinks the hard part is the number. It isn't. The number is easy to post. What transparency reveals is the architecture behind it. If your levels are inconsistent, transparency doesn't hide that. It publishes it. Two people, same work, different ranges. The gap was always there. Transparency didn't create it. It just made it visible. This was never a pay problem. It was a structure problem. Build th

Fractional is not a compromise. It is what happens when senior expertise finally meets the market that needs it most. For years the same conversation kept happening. A colleague would move to a smaller company, call me up, and say the same thing. Scott, I would love to work with you but I cannot afford you. I heard that so many times I stopped being surprised by it. These were good companies with real problems. They knew exactly what they needed. They just had no way to acces

You never made one bad pay decision. You made twenty reasonable ones. A counteroffer you had to match. A retention bump for someone you could not afford to lose. A new hire whose market number came in high. A title bump because the promotion budget was frozen and it was the only lever you had. Every one of them made sense in the moment. Every one of them, you could defend on its own. Then a strong performer asks, in a one on one, why a new hire started above where they sit to

A merger almost cost me my job. It became the best thing that ever happened to the companies I work to serve. When I was told my position was being eliminated, my first instinct was to find another full-time role. I started applying. I received offers. On paper the path forward was clear. But something had already shifted. And I think I knew it before the merger ever happened. A year earlier, a founder I knew asked if I would help a software company with their compensation pr

Every compensation complaint you received this year was a systems failure. Not yours. A Director of People Operations at a 200-person software company reached out to me through a mutual contact. She was relatively new to formal compensation work. The CEO had personally handled compensation decisions for years and explicitly wanted to be removed from the process. He handed her the function and she came to our first meeting with urgency and humility in equal measure. She knew w

Leaders always think they have a pay problem. What they actually have is a decay problem. Every company I walked into had something in place. A framework. A set of jobs. Some structure. Nobody called me in because they had nothing. They called me in because what they built had simply stopped working. What I kept finding was misalignment. Roles that had drifted from their definitions. Titles that had outpaced the work. People placed in the wrong level so long ago that nobody r

Your hiring managers are negotiating against themselves. Every single time. When every pay decision starts with "what are they expecting?" instead of "what is this role worth?" you don't have a compensation strategy. You have a guessing game. I pulled the data on a strong performer at a company that wanted to move them into a higher level role. They were 60% below the midpoint of their current role. Not the role they were being promoted into. Their current one. Every time thi

I am the person an HR leader frantically messages on a Friday afternoon. It didn't start that way. My first role was at a Harvard Medical School teaching hospital. I wasn't thinking about compensation ranges or job architecture. I was thinking about how organizations work, and why people inside them either feel valued or forgotten. That curiosity eventually found its language in Total Rewards, and I never looked back. Throughout my career, I've moved through companies of ever

The best compensation structure for an early-stage SaaS company is not the same one that works when you've scaled. That is not a design flaw. That is how maturity is supposed to work. Most scaling companies are in one of two places. Either they have no structure at all, every hire is a negotiation, pay is based on what the candidate asked for, and nobody can explain why two people in the same role are making different salaries. Or they built something early, a rough leveling

Most scaling companies think they need a grade structure. What they actually need is something simpler, and easier to explain. Here's what actually happens when you build one before you're ready. When you consolidate 80 unique roles into 12 salary grades, you're asking your managers to defend an approximation. Each role gets slotted into the grade with the closest midpoint, but closest isn't the same as right. And when a candidate pushes back on an offer, or a tenured employe

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