Building a salary band structure for a 30-person company

Key Takeaways

• Around 30 people, ad-hoc offer-by-offer pay negotiation stops working: employees compare notes, and unexplained gaps between similar roles become a retention problem.
• A defensible band combines three inputs (role levels, market benchmarking, and a deliberate spread) not a manager's sense of what a candidate will accept.
• Rolling out bands without adjusting existing pay first triggers resentment; the fix is a compression audit before the announcement, not after.
• In the UAE, the basic-versus-allowances split inside a band changes the accruing gratuity liability, so the structure has a cost beyond the headline number.

A company hiring its 30th person has usually made 29 separate pay decisions, each negotiated in isolation against whatever the candidate asked for and whatever the hiring manager was willing to concede that week. That works fine at ten people. At thirty, it produces two employees in the same role, doing comparable work, three years apart in tenure, earning salaries that differ for no reason anyone could defend in a conversation, and eventually someone finds out. A salary band structure replaces that with a small number of defined ranges per role level, built from market data and a documented spread, so every pay decision has a reason attached to it before it's made rather than invented afterward.

Why ad-hoc pay breaks down at this size

Below roughly 15 people, informal pay works because everyone's history is common knowledge: the founders know exactly why each offer landed where it did, and there's little room for a gap to go unnoticed. Past 25 to 30, three things change at once.

First, headcount crosses the threshold where people no longer all report to the same person or sit in the same room. Pay decisions get delegated to team leads who don't have visibility into what other leads offered, so consistency degrades even when everyone is acting in good faith.

Second, tenure spreads out. The company now has employees hired in year one at whatever the founders could afford, and employees hired in year three when budgets were looser and a strong candidate could negotiate harder. Later hires routinely land above earlier ones doing equivalent work: a pattern compensation literature calls pay compression, and one the people affected notice quickly (SHRM: Address Pay Compression or Risk Employee Flight, retrieved 2026-09-11).

Third, and this is the one that actually costs a company its best people: employees talk. UAE hiring circles are small enough, and job-hopping common enough, that pay information travels through informal networks even without formal transparency norms. The employee who discovers a peer earns more for the same scope doesn't usually raise it directly. They update their resume.

A band structure doesn't eliminate variation in what people earn. It gives that variation a source: role, level, and where someone sits in the range for demonstrated performance, rather than which week they happened to negotiate.

The three inputs that make a band defensible

A band built by picking a number that "feels right" for each role is not meaningfully different from ad-hoc pay. It just has a chart around it. What makes a structure defensible is that each range can be traced back to three separate inputs.

Role levels. Group jobs by scope and impact, not by title. A "Senior Manager" with two direct reports and a "Senior Manager" running a ten-person department are not the same level even if HR software lists them identically. Most 30-person companies need only three to five levels total: collapsing everyone into fewer, broader bands is usually more useful at this size than a granular ladder built for a 500-person org.

Market benchmarking. Each level needs an external reference point: what the role costs to hire in the UAE market now, not what the company paid for it two years ago. Reliable inputs include paid salary surveys, recruiter data from live searches, and postings for comparable roles at comparable companies (GulfTalent: UAE and Gulf salary data, retrieved 2026-09-11). Treat any single source with some skepticism; benchmarking data is directional, and a range built on one outdated survey is barely better than a guess.

A deliberate spread. The gap between a band's minimum and maximum should be a stated policy, not an accident. A common default is roughly 30-50% between minimum and maximum, tighter for junior and highly standardized roles, wider for senior roles where variation in individual impact is larger and genuinely harder to price. The spread is what lets the structure absorb real people: a strong performer three years into a role should sit meaningfully above where a new hire starts, inside the same band, without needing a level promotion just to get a fair raise.

Skipping any one of the three produces a structure that looks rigorous but isn't. Levels without market data drift from reality within a year. Market data without levels turns into re-benchmarking every individual salary from scratch. A spread without either of the first two is just a range with nothing attached to it.

A practical example structure

A 30-person company organized across four functions (leadership, operations, revenue, and delivery) typically needs no more than four to five bands to cover the whole org. A simplified example, illustrative only. Run actual figures through current UAE market data rather than treating these as benchmarks:

The pattern that matters more than the exact numbers: new hires enter low-to-mid in their band, and room above them is reserved for tenure and demonstrated impact within the same role, not just for people who negotiate hardest at the offer stage. That reserved headroom is what makes the structure defensible when an existing employee asks why a new hire started close to their own salary after five years in the role.

Rolling it out without triggering resentment

The step companies skip is the one that determines whether the rollout goes well: run every current employee's actual salary against the new bands before anyone outside HR and leadership sees the structure. This produces three categories, and each needs a different response.

Employees who land inside their band need no action beyond communication: the point where they sit in the range should map to a reason (tenure, scope, performance) that a manager can explain in one sentence.

Employees who land below their band's minimum (common for early hires whose pay never caught up as the company matured) are the compression cases. These need a real remediation plan, phased over one or two review cycles if a single correction isn't affordable immediately, not a vague promise to "look at it next year." Announcing bands while quietly leaving underpaid long-tenured staff below the floor is the single fastest way to convert a fairness initiative into evidence that the company already knew about the problem and chose not to fix it.

Employees who land above their band's maximum (usually a handful of early, generously negotiated hires) are the sensitive case. The company should never cut a salary to fit a new band; the standard approach is to freeze that salary in place and let market bands catch up through normal annual increases over time, communicating the rationale privately rather than surfacing the gap publicly.

Sequence the announcement accordingly: fix or start fixing the below-band cases first, decide the above-band approach quietly, and only then communicate the structure to the wider team: framed around the levels and the logic, not a spreadsheet of who moved where.

What this means for a UAE payroll structure

Building bands forces a decision that's easy to defer in ad-hoc pay: the split between basic salary and allowances inside each offer. In the UAE that split is not a formality. It changes what the company owes.

End-of-service gratuity accrues on basic salary only, at 21 days of basic pay per year for the first five years and 30 days per year from year six, calculated on an employee's last basic salary and capped at two years' wages (The Official Portal of the UAE Government: Calculations for gratuity pay, retrieved 2026-09-11). Two employees on identical total packages can carry materially different accruing gratuity liabilities depending on how much of that package sits in basic pay versus housing and transport allowances: the fuller breakdown, including why the last-salary calculation retroactively re-prices every prior year of tenure, is in our UAE payroll and employment cost guide.

A band structure is the natural place to standardize this. Rather than each offer letter setting its own basic-to-allowance ratio, define the split once per level and apply it consistently. It removes an internal-equity problem (two people on the same band with wildly different basic salaries carry different notice-pay and leave-pay bases too, not just different gratuity exposure) and gives finance a predictable, bandwide gratuity accrual to plan against instead of one improvised per hire. Run the structure's actual basic-pay figures through the gratuity calculator before finalizing a band, rather than estimating the liability from the total package. Standardising that basic-to-allowance split is also far easier to hold once it's built into the payroll platform itself, rather than re-decided by whoever happens to draft the next offer letter.

Frequently asked questions

How many salary bands does a 30-person company actually need?

Most companies this size need four to five bands total across the whole organization, not per department. Fewer, broader bands are easier to administer and explain than a granular ladder designed for a much larger headcount; add levels later as roles genuinely diverge in scope, not preemptively.

What if we can't afford to fix everyone who falls below their band?

Phase it. Prioritize the largest gaps and longest-tenured underpaid employees first, commit to a stated timeline across one or two review cycles, and communicate the plan directly to affected employees rather than waiting for them to ask. A credible phased plan is far better received than silence.

Should salary bands be shared with employees?

At minimum, share the band and level for an employee's own role so they understand where their pay sits and what moves it. That's the fairness benefit bands are meant to deliver. Full company-wide range transparency is a further step some companies take later; it isn't required to get the internal-equity benefit.

The bottom line

Ad-hoc pay works only as long as a company is small enough that every salary decision is common knowledge. Past roughly 30 people, that stops being true, and the fix is a structure built from role levels, market data, and a stated spread: rolled out only after existing pay gaps are found and addressed, with the basic-versus-allowance split standardized to keep gratuity exposure predictable.

Figures were verified on 11 September 2026 against the UAE Government's official gratuity calculation guidance, SHRM, and GulfTalent's UAE salary data. Run actual figures through current sources rather than treating any example numbers here as benchmarks.