Small Business Salary Guide

How to Actually Build a Salary Guide That Doesn't Fall Apart in Six Months

A salary guide is just an internal document that maps out pay ranges for every role in your company. Most small business owners treat it like an afterthought — they slap together a spreadsheet after their first bad hire and call it done. The problem is that whatever you build in January will look ridiculous by December if you don't account for at least three things: local market shifts, role evolution, and the fact that your highest performers will quietly leave if they figure out your ranges are arbitrary.

I built my first Small Business Salary Guide in 2018 for a team of about twelve people. It was a single Excel file with columns for job title, base salary, low end, high end, and a few notes. Simple, right? Here's what actually happened. We hired a mid-level developer at the top of the range for that band, and within eight months, she had outgrown the role entirely. She asked for a raise. The guide said she was already at the ceiling. We lost her to a competitor offering twenty percent more. That was the moment I realized a static guide is just a retention time bomb. It's a compensation framework that defines minimum, midpoint, and maximum base pay for each role, usually tied to experience levels and geographic market data. The midpoint typically aligns with the 50th percentile of market data for that role and location. The range spreads roughly ten to fifteen percent below and above that midpoint. Some guides include bonus targets, equity bands, and benefits cost estimates on top of base salary. The structure itself isn't complicated, but getting it right requires actual market research rather than guessing based on what your neighbor's business pays. Start with the roles that exist today, not the ones you hope to hire for next year. I made the mistake of including three positions we hadn't filled yet, and by the time we actually hired for them, those ranges were completely disconnected from reality. It created confusion and credibility problems. Build for your current headcount first, then add projected roles as separate line items with a clear annotation that they're illustrative.

The Actual Process

Step one is gathering market data. Most small businesses don't have a budget for paid surveys from Radford or Willis Towers Watson, and that's fine. Free and low-cost sources work well if you triangulate. Glassdoor has salary reports filtered by location and company size. Payscale offers a free tier that covers basic role-level data. LinkedIn Salary provides another data point. Take the average across at least three sources for each role, then adjust for your specific geographic area using Bureau of Labor Statistics Occupational Employment Statistics, which gives you metro-level median wages by SOC code. If you're in a high-cost city like San Francisco or New York, apply a location factor of roughly 1.2 to 1.4x depending on the role. Remote positions complicate this — pick one methodology and stick with it across the entire guide, or you'll create pay equity issues that become legal problems. Step two is setting your own company philosophy. Do you want to lead the market at the 75th percentile, match it at the 50th, or trail slightly at the 25th? There's no wrong answer, but you need a stated position because every hiring manager and every employee will eventually ask why someone in a similar role makes more or less than them. A consistent philosophy prevents those conversations from turning into improvisations. Step three is mapping internal equity. Pull your current compensation data for every employee and plot it against the ranges you just created. You're looking for two things: outliers where someone is paid significantly above or below the band for their role level, and compression issues where two people doing substantially different work sit at the same salary point. I found three compression cases in my first real audit — a senior account manager making the same as a junior account executive — and fixing them required raises for the lower roles that ate about eight percent of our annual payroll. Budget for that adjustment upfront, or you'll discover the problem during a performance review when someone compares notes with a peer.

A Counter-Intuitive Thing Nobody Tells You

Wider salary ranges aren't always better. The instinct is to make the bands broad so you have room to grow people without promoting them. But in practice, very wide ranges create two problems. First, managers lose motivation to develop people because there's always room at the bottom of the band. Second, wide ranges correlate with higher pay inequity because discretion replaces structure, and human discretion introduces bias without anyone noticing until an audit reveals it. A tighter range of maybe twelve to fifteen percent total spread forces promotion-based growth and reduces wage drift. Promotion is the clearest signal of increased responsibility, and tying salary increases primarily to promotion events keeps your comp philosophy honest. Another thing that catches people off guard: tenure should generally not drive salary progression within a band. People who've been with you longer shouldn't automatically earn more than newer hires at the same level unless they're taking on measurably more responsibility. I saw a company where a marketing coordinator who'd been there four years made nearly twenty percent more than a coordinator who'd been there six months, and the four-year person was doing the same job. That's not retention strategy, that's compounding error. When the newer person found out, they left within three months. Fix your salary progression criteria to reward level changes, not calendar time.

Small Business Salary Guide: Tools and Templates

You don't need expensive software. A well-built spreadsheet works for most companies under fifty employees. The key columns are: job title, role level, pay grade, minimum salary, midpoint, maximum salary, market percentile target, geographic adjustment factor, current incumbents and their salaries, and date of last review. Keep the current incumbents column visible — it's your equity audit tool and you'll reference it constantly. If you want a starting template, I keep a clean version available. You can download a Small Business Salary Guide template here that has the core structure pre-built with example data and conditional formatting that highlights anything over or under the band in red. It's basic, but it forces you to fill in the columns that matter instead of skipping ahead to the stuff that feels more interesting. Most people skip market data and jump straight to writing down whatever numbers seem reasonable. Don't do that. The numbers only seem reasonable until you compare them against actual market data.

Where This Method Breaks Down

Salary guides fail in several predictable scenarios. They break down when you operate in a niche role where market data simply doesn't exist — things like specialized equipment technicians or role hybrids that don't appear in standard occupational taxonomies. In those cases, you're either benchmarking against the closest adjacent role and adjusting for skill differences, or you're setting the range based on what it would cost to replace your current incumbent if they walked out tomorrow. Both are imperfect. The second one tends to be more accurate for niche technical roles because supply and demand for that specific skill set is what actually determines your cost. They also fail when you don't update them regularly. I've seen small business owners set a guide in January and never touch it again. By the following recruiting season, their ranges were thirty percent below market for certain roles because tech wages moved faster than their static document. Commit to an annual review schedule, and treat it like a tax filing — it doesn't matter how good the last version was, the world has changed since then. Finally, salary guides don't solve compensation problems that are fundamentally about job design. If someone's range is too low because their role keeps growing without a title change, no amount of spreadsheet math fixes that. You either need to promote the role, split it, or acknowledge that the title-on-paper doesn't match the actual scope of work. The guide surfaces these problems. It doesn't resolve them on its own.

The whole process takes about twenty hours for a first build if you're doing it right — roughly six hours on market data collection, eight on internal equity analysis, and six on structuring and documenting the philosophy. After that, annual maintenance is maybe three hours. The return on that investment shows up in reduced turnover on mid-level roles, fewer negotiation surprises during hiring, and a defensible position when someone asks why their colleague makes more than they do. You don't need perfection. You need consistency, and you need it documented somewhere that survives the next time your office manager quits and takes the old shared drive with them.