Pay bands and increments for small companies

Pay in a young company starts as a series of individual negotiations. By the time there are thirty people, those negotiations have produced a structure nobody designed: two people in the same role paid 40 percent apart, a 2021 hire earning less than a 2025 hire with the same title, and an increment cycle that is really a series of retention panics. Pay bands are the way out, and they are less work than they sound.

What a pay band is

A pay band is a salary range attached to a role level, with a minimum, a midpoint and a maximum. A company with roles from associate to senior manager typically has five to seven levels. The band says: anyone at this level, in this function, earns somewhere between these two numbers, and here is where a fully competent person sits.

Bands exist for three reasons. They let you make an offer in an afternoon instead of a negotiation. They give managers a defensible answer to "why does she earn more than me". And they turn the increment cycle from a set of exceptions into a rule with exceptions.

Building the first version

1. List every role and assign a level. Levels are about scope and autonomy, not titles. Two people called "manager" may be at different levels; one may manage nobody.
2. Put current salaries on the table, by level. You will see the spread immediately. The spread is the problem the bands will fix over two or three cycles, not in one.
3. Set the midpoint. Use what you actually pay a solid performer at that level today, adjusted by whatever external reference you trust: offers you have lost candidates to, salary data from recruiters you work with, published surveys where available. Do not chase the top of the market unless you intend to pay it.
4. Set the range. A common width is 20 percent below midpoint to 20 percent above for junior levels, widening to 30 percent either side for senior levels where skill differences are larger. Adjacent bands should overlap; a strong senior engineer may legitimately earn more than a new engineering manager.
5. Write the cost to company (CTC) rules. Decide once what the band refers to: fixed CTC is the safest because variable pay and reimbursements vary by person. See our guide to salary structure for how the components fit together.

Expect the first version to be wrong in places. It is still better than the structure you have now, because it is written down.

Dealing with people outside the band

Some people will be below the minimum. Bring them to the minimum in the next cycle, or over two cycles if the gap is large, and treat it as a correction rather than a performance increment. Some will be above the maximum. Do not cut their pay; freeze or slow their increments, tell them why, and consider whether they are in fact operating at the next level and should be promoted. Hiding the problem does not make it go away; it surfaces the day someone compares payslips.

The increment budget

Decide the budget before anyone is reviewed. The budget is a percentage of the total fixed payroll, set by the founders with the finance view of the year ahead. Indian increment budgets in recent years have typically landed between 8 and 12 percent for most sectors, with IT services at the lower end and early-stage product companies higher; use your own affordability, not the headline number.

Split the budget into three pools before allocating anything: a merit pool distributed by rating, a correction pool for people below band minimum or badly placed within it, and a promotion pool for level changes. Promotions eat budget fast, which is why they should be decided before the merit allocation, not after.

Linking rating to increment

A simple matrix works: the row is the performance rating, the column is where the person sits in the band. A high performer below midpoint gets the largest increment; the same performer above midpoint gets a smaller percentage, because they are already paid for that performance. A low performer above midpoint gets nothing. Publish the matrix to managers, not the percentages, and let them see the logic. The rating itself should come from a calibrated review cycle, not from the increment meeting.

The April letter

In India the increment cycle almost always lands in April, aligned to the financial year. The letter should state the new CTC and the effective date, the revised component breakdown, and, if the band framework is shared with employees, the level and position in band. Keep the letter to one page; attach the new structure as a table. Generate letters from a template rather than editing last year's by hand; a letter with the wrong name on it is the most avoidable HR incident there is, and your HR system's letter templates should produce the whole batch from the approved spreadsheet.

Load the new salaries into payroll for the April run, with arrears if the letter goes out late, and check that the statutory contributions recalculate correctly against the new basic.

What to tell employees

Transparency is a choice with trade-offs. Publishing the bands themselves is rare in Indian small companies and tends to create more questions than it answers until the bands are mature. What you can and should share: that bands exist, that increments follow a matrix, that the rating is calibrated across managers, and what someone needs to do to move to the next level. That last point is what most employees actually want to know, and almost nobody tells them.