Building Compensation Bands for Professional Services Firms

Why Professional Services Compensation Is Harder Than It Looks

Picture this: an HR manager at a 90-person management consulting firm is asked, for the third time this quarter, why a Senior Consultant in the Chicago office earns $14,000 more than a counterpart in Atlanta doing the same client work. She opens the spreadsheet she inherited. There are six tabs, three naming conventions, and no documented rationale for any of the numbers. She knows what needs to happen — she just doesn't know where to start.

That scenario is common in professional services firms. The industry spans management consulting, accounting, legal services, engineering, architecture, IT consulting, and staffing (NAICS 54 — Professional, Scientific, and Technical Services), and it shares a structural challenge that makes compensation design genuinely tricky: almost every firm runs two distinct role populations — billable staff whose time is sold to clients, and support staff whose time keeps the firm running internally. Those two populations have different market benchmarks, different leverage points for retention, and different signals for leveling. Cramming them into a single undifferentiated band structure usually produces either compressed billable-role ranges (which drives attrition among your revenue generators) or inflated support-role ranges (which creates budget pressure with no revenue offset).

This guide walks through how to build compensation bands for professional services firms that account for that two-track reality — from selecting the right benchmark sources, to constructing the bands, to maintaining them as the firm grows.

Understand Your Two-Track Role Architecture Before You Set a Single Number

Before pulling any benchmark data, map the roles you actually have into two tracks.

Track 1 — Billable roles. These are the people whose hours appear on client invoices: Analysts, Associates, Consultants, Senior Consultants, Managers, Senior Managers, Directors, and Principals (the exact titles vary by firm type). The market for these roles is relatively transparent — firms compete for them openly, and candidates often know what peer firms pay. Underpricing billable roles is a direct attrition risk; losing a billing Senior Consultant mid-engagement is expensive in ways that extend well beyond the salary differential.

Track 2 — Support and functional roles. These include Finance, HR, IT, Marketing, Business Development, and Operations staff who do not bill to clients. Their market benchmarks come from a broader labor pool (any company with those functions, not just professional services firms), and their roles often align more cleanly to standard occupational categories.

The practical implication: you need two reference points when building ranges. A Senior Consultant's band should be anchored to professional services compensation data. A Payroll Specialist's band at the same firm should be anchored to the general administrative/financial occupations market — because that is who you are competing with when the Payroll Specialist considers leaving.

Once you have your two-track map, document each role's NAICS context (NAICS 54 for most professional services) and its SOC code. SOC codes are the occupational classification system that BLS uses for all wage data — which matters in the next step.

Anchor Bands to BLS OEWS Data for US Firms

The U.S. Bureau of Labor Statistics Occupational Employment and Wage Statistics (OEWS) program is the most defensible public benchmark source available to an SMB HR team. It produces annual employment and wage estimates for approximately 830 occupations across the nation, all 50 states, and roughly 530 metropolitan and nonmetropolitan areas, drawn from a sample of approximately 1.1 million establishments. You can access it at bls.gov/oes.

For a professional services firm, the relevant SOC families include:

• 13-1000s — Business and Financial Operations (Management Analysts, HR Specialists, Business Development roles)

• 13-2000s — Financial Specialists (Accountants, Financial Analysts — relevant for accounting and finance consulting firms)

• 15-1000s — Computer and Mathematical (IT consultants, software/data practitioners embedded in consulting practices)

• 17-0000s — Architecture and Engineering (for engineering consulting and A&E firms)

• 23-1000s — Legal (for legal services firms)

For each role, find the OEWS national or state-level median (the 50th percentile annual wage) for the closest SOC match. That median becomes your band midpoint anchor — the starting assumption for what you expect to pay a fully-performing employee in that role in a given market.

If you want to understand how to navigate OEWS data end-to-end — selecting the right release, applying geographic differentials, and interpreting the percentile columns — the BLS OEWS benchmarking guide covers the full workflow.

For Canadian offices (Ontario and British Columbia), Statistics Canada's Table 14-10-0417-01 provides NOC-based wage percentiles by province and census metropolitan area under an open government licence. The methodology differs from OEWS — consult the table documentation before treating Canadian and U.S. percentile figures as directly comparable.

Build the Band: Midpoint, Spread, and Min/Max

Once you have your benchmark midpoint, the band is constructed by choosing a range width (also called midpoint spread) — the percentage distance from the minimum to the maximum of the band, expressed as a percentage of the midpoint.

A common starting framework:

• Entry-level and support roles: 40–50% spread

• Mid-level professional and billable roles: 50–60% spread

• Senior and management roles: 60–80% spread

Wider spreads at senior levels reflect the greater performance variance at those levels and the longer time an employee might reasonably spend in the band before a promotion.

Worked example — Senior Consultant band. Suppose the OEWS national median for Management Analysts (SOC 13-1111) is your midpoint anchor. Say you decide on a 50% spread. The formula:

• Minimum = Midpoint ÷ (1 + spread/2) = Midpoint ÷ 1.25

• Maximum = Midpoint × (1 + spread/2) = Midpoint × 1.25

If your midpoint is $95,000 (a round example — verify your actual OEWS figure for the current release and your geography):

• Minimum = $95,000 ÷ 1.25 = $76,000

• Maximum = $95,000 × 1.25 = $118,750

That produces a band of $76,000–$118,750 with a midpoint of $95,000 and a 50% spread. This is a teaching illustration of the formula — anchor your real band on the current OEWS figure for your specific SOC code and metro area.

The deeper guide on band construction mechanics — including how to handle band overlap and midpoint progression ratios between levels — is in the complete job band structure guide.

Level the Billable Track With Criteria That Travel

One of the persistent problems in professional services is that job levels drift — "Senior Consultant" means something different in every office, and sometimes on every team. When that happens, the compensation bands technically exist but are not applied consistently, which recreates the exact pay inequity the structure was designed to prevent.

A leveling framework for the billable track should define each level on at least three criteria that do not depend on tenure or title inflation:

1. Scope of client ownership — does this person own a client relationship, a work stream, or an individual deliverable?

2. Supervision — does this person supervise junior staff on engagements, and at what degree of independence?

3. Complexity — are the problems they solve defined, structured, or ambiguous?

For example:

• Analyst: Works on defined sub-tasks; no client ownership; supervised throughout.

• Consultant: Owns a work stream; some client contact; supervised at major milestones.

• Senior Consultant: Owns deliverables; direct client relationship on assigned scope; manages Analysts day-to-day.

• Manager: Owns an engagement or a client; responsible for quality across the team; minimal direct supervision.

When your leveling criteria are documented and applied consistently, band placement becomes defensible — not just to employees but to auditors, regulators, and future leadership. The job leveling framework guide for small companies provides a full criteria-setting worksheet if you need to build this from scratch.

Handle Pay Transparency Requirements for Posted Roles

Professional services firms in pay-transparency jurisdictions — California, Colorado, New York, Illinois, Washington, and others — are required to include a pay range in posted job listings. As of 2026, depending on how localities are counted, 16–18 states have enacted statewide pay transparency laws. (Lift HCM, 2026 — covers 17 states + multiple municipalities, affecting an estimated 65% of U.S. employers.) For Canadian offices, Ontario's pay transparency rules took effect January 1, 2026, requiring employers with 25 or more employees to include expected compensation or a salary range in publicly advertised postings for roles up to $200,000, with the range not exceeding $50,000. British Columbia has required pay ranges in all job postings since November 1, 2023.

What this means practically: your bands are your posted ranges. A band you built on a defensible benchmark methodology and documented leveling criteria is far easier to post publicly than a number someone typed into a spreadsheet last quarter. If your bands are not documented, pay transparency requirements will force the conversation anyway — it is better to have built the structure intentionally.

The band you post in a job listing is the band you will be held to. Build it on documented methodology, not on what the last person in that seat happened to earn.

For roles where your firm operates across multiple states, note that California's SB 642 (effective January 1, 2026) redefined "pay scale" as a good-faith estimate the employer reasonably expects to pay upon hire — and extended the statute of limitations for civil actions to six years for willful violations. Verify your current obligations with employment counsel; this article describes compliance context, not legal advice.

Support-Role Bands: Don't Anchor to the Billable Market

A common mistake is to let billable-role market pressure bleed into support-role bands. If your Senior Consultants command strong market compensation and your firm runs high utilization, there is a temptation to bring support roles along proportionally — but the labor market for a Payroll Specialist or an HR Coordinator is set by the general market for those roles, not by consulting firm economics.

Anchoring support roles to the wrong benchmark causes two problems:

• Overpay relative to the market compresses your margins without improving retention (candidates and employees benchmark against the actual market for their role).

• Structural compression between support managers and billable staff creates internal equity complaints that are difficult to resolve.

Build support-role bands from the relevant OEWS SOC category for that function — not from a "what do other consulting firms pay their HR people" estimate. For example, an HR Generalist band should be anchored to SOC 13-1071 (Human Resources Specialists) or 11-3121 (Human Resources Managers), depending on scope — not to the consulting firm's general compensation scale.

The same two-track discipline applies when you review and update bands annually. Billable and support tracks may move at different rates in a given year. Keeping them separate in your documentation makes those adjustments defensible.

Putting It Together: A Practical Starting Sequence

If you are building compensation bands for a professional services firm for the first time, a workable sequence is:

1. List all active roles and sort them into billable vs. support tracks.

2. Assign SOC codes (and NOC codes for Canadian staff) to each role.

3. Pull OEWS medians for your primary geography for each SOC; note the publication date of the release.

4. Set midpoints — start at the OEWS median; adjust up or down by ±5–10% if your firm has a documented pay positioning philosophy (e.g., targeting the 60th percentile to compete aggressively for billable talent).

5. Choose spreads by level using the framework above; calculate min and max.

6. Document leveling criteria for the billable track so band placement is consistent across offices and teams.

7. Audit current salaries against the new bands — identify anyone below minimum (an immediate action item) and anyone above maximum (flag for future cycle planning).

8. Update job postings to reflect the ranges in jurisdictions that require disclosure.

If you want a structured template to work through that sequence — including the band math, leveling criteria fields, and a current-employee audit tab — the Job Band Structure Builder is built for exactly this workflow. It includes BLS OEWS and Statistics Canada benchmark data so you are not hunting down percentile tables manually, and it produces posting-ready pay ranges for the jurisdictions where you hire. You can also start with a free trial at app.jobbands.com/signup to see whether the structure fits before committing.

For context on how this kind of band-building plays out in other industries, the compensation bands guide for nonprofits covers a similarly bifurcated role structure — program staff vs. administrative staff — with analogous methodology.

A compensation band structure is not a one-time project. Professional services firms grow by adding practice areas, acquiring smaller firms, and promoting high performers into new roles. The bands you build this quarter need to be maintainable — documented clearly enough that the next person in your seat can update them without starting from scratch. ```