Salary Bands & Pay Benchmarking Guide for Indian SMBs

Most small and mid-sized businesses set salaries the same way: a candidate names a number, the hiring manager compares it with what similar people earn internally, a counter-offer is made, and the figure is approved. It works until it doesn't. Two people doing similar work find out they earn very different amounts. A strong performer receives a competing offer 30% higher and leaves. A new hire is paid more than the manager's longest-serving team member. This salary band and compensation benchmarking guide for India shows how to replace ad-hoc negotiation with a structured, defensible pay framework that you can build without a large HR team.

The goal is not to make pay rigid. It is to make pay explainable: to be able to tell any employee, candidate, or auditor why a given person earns what they earn, and how it relates to the market, the role, and their performance.

What salary bands and benchmarking mean

Compensation benchmarking is the process of comparing your pay for specific roles against the market, using reliable external data, so you know whether you are paying below, at, or above prevailing levels.

Salary bands (also called pay ranges) define a minimum, midpoint, and maximum pay for a group of similar roles. Each employee's pay sits somewhere within the band, depending on experience, skill, performance, and tenure.

Job levels or grades group roles of similar size and complexity, so that you do not have to build a separate range for every title.

Together, these three elements form the foundation of a pay structure: you decide which jobs are similar (levels), what the market pays (benchmarking), and how much flexibility you allow (bands).

Why SMBs should invest the effort

• Fairness and trust: Employees who understand how pay is determined are less likely to feel treated unfairly.
• Retention: Knowing where your pay stands against the market lets you act before people leave, rather than after.
• Hiring speed: Recruiters and hiring managers can make offers within approved ranges without waiting for ad-hoc approvals.
• Cost control: Bands prevent runaway offers and quiet pay creep.
• Pay equity: A structured framework makes it easier to spot and correct unexplained gaps between similar roles, and it complements any pay equity audit you run.
• Compliance readiness: Documented logic helps when pay practices are questioned.
• Budget planning: Increment and hiring budgets become easier to forecast when you know the ranges.

Step 1: Clarify your compensation philosophy

Before collecting any data, agree on what you want your pay to say about your company. This is your compensation philosophy, and it can be one page long.

Questions to settle:

• Market position: Do you want to pay at the market median, above it for critical roles, or below it with other benefits to compensate? Many SMBs choose the median for most roles and a higher position for scarce skills.
• Pay mix: What mix of fixed pay, variable pay, and benefits do you want? A sales role might have a high variable share, while an operations role may have mostly fixed pay.
• Internal equity versus external competitiveness: When these conflict, which wins? A clear principle prevents arguments later.
• Performance link: How much should pay differences reflect performance versus tenure and experience?
• Transparency: Will you share bands with employees? Many companies share the range for an employee's own level, while keeping individual salaries confidential.
• Geography: Do you pay the same across locations or adjust by city? Cost of living and talent supply differ across metros and smaller cities.

Write these down and have leadership sign off. This document guides every later decision.

Step 2: Define job levels

Without levels, bands become a mess of one-off ranges. Create a simple level structure that reflects increasing scope, autonomy, and impact.

A simple level framework for a 100 to 300 person company

Adapt this to your business. Some companies add parallel tracks for individual contributors (specialists) so that a senior technical expert can progress without managing people. If you are also designing a promotion policy and career ladder, build the levels once and use them for both purposes.

Mapping roles to levels

For each role, consider:

• Scope: How large an area does the role cover?
• Complexity: How difficult are the problems?
• Autonomy: How much independent judgement is required?
• Impact: What is the consequence of success or failure?
• Knowledge: How much specialised expertise is needed?

Use a simple scoring sheet or a panel discussion with managers. The aim is consistency, not mathematical precision.

Step 3: Collect market data responsibly

Benchmarking needs data from outside. Options include:

• Published salary surveys from reputable consulting firms and industry bodies. These often provide percentile data by role, level, industry, and location.
• Subscription-based compensation databases that aggregate anonymised data from many employers.
• Recruiter and search partner insights, which reflect current offers and acceptances.
• Industry networks and peer groups, where HR leaders may share ranges in a compliant way.
• Your own offer data, including accepted and declined offers, counter-offers, and resignation reasons.
• Job postings with disclosed ranges, where available, as a rough signal.

Treat any single source with caution. Combine at least two or three, and note the date and sample size. Avoid anything that involves sharing confidential pay data between competitors in a way that could raise competition law concerns; use anonymised, aggregated third-party sources.

What to check in a survey

• Job matching: Are the survey's job descriptions similar to yours, or only similar in title?
• Company size and industry: A 5000-person multinational pays differently from a 100-person startup.
• Location: Make sure the data reflects your city or region.
• Pay elements: Does the number include fixed pay only, or total cash including variable pay?
• Percentiles: The 25th, 50th (median), and 75th percentiles give a better picture than an average.
• Data date: Salaries move; adjust older data with a reasonable ageing factor.

Matching your jobs to the market

Job titles are unreliable. A "manager" in one company may be a senior executive elsewhere. Match jobs on content: responsibilities, required experience, team size, and impact. Where a role is a hybrid, match to two benchmark jobs and blend the data.

Step 4: Analyse and set the market reference point

For each benchmark job, record the market median (50th percentile) and, if you wish, the 25th and 75th percentiles. Then convert to a market reference point for each level by averaging or fitting a line across the jobs at that level.

Example

Suppose you benchmark three roles at level L3 and find these annual medians (in lakhs, illustrative): 9.0, 9.8, and 10.4. The level reference point could be around 9.7. If you want to lead the market for critical skills, you can apply a premium (for example, aim for the 60th or 75th percentile for those roles) and note it as a skill premium instead of changing the whole band.

Adjusting for your philosophy

If your philosophy is to pay at the median, the band midpoint equals the market median for the level. If you aim higher for scarce skills, set the midpoint at a higher percentile for those job families, but document the reason.

Step 5: Design the salary bands

Band structure basics

For each level, define:

• Minimum: The lowest pay for a fully qualified person new to the level.
• Midpoint: The market reference point. A fully proficient person should be paid around here.
• Maximum: The most you will pay for the level before the person should be promoted or moved to a different arrangement.

The range spread is the difference between the maximum and minimum, expressed as a percentage of the minimum. Typical spreads increase with level:

Use these as starting points and adjust to your market.

Overlap between levels

Adjacent bands usually overlap by a modest amount so that an experienced person at one level can earn more than a new joiner at the next. Too much overlap makes promotions feel meaningless. Too little makes bands rigid. A midpoint progression of roughly 10% to 20% between levels is a common design range for many organisations.

A worked example

For level L3 with a market median of ₹9.7 lakh per annum:

• Midpoint: ₹9.7 lakh
• Spread: 40%
• Minimum = Midpoint ÷ (1 + spread ÷ 2) = 9.7 ÷ 1.2 = about ₹8.08 lakh
• Maximum = Minimum × (1 + spread) = about ₹11.3 lakh

Round the numbers to clean values, such as ₹8.1 lakh, ₹9.7 lakh, and ₹11.3 lakh. Repeat for every level.

Pay components inside the band

Decide whether the band refers to total fixed pay, CTC, or total target cash. Be explicit. For Indian payroll, CTC includes employer contributions such as PF and gratuity accrual, while "gross" and "take-home" differ again. Be consistent in the definition and in how you present bands to managers. When you structure CTC under the labour code wages rule, check how the proportion of basic pay affects PF, gratuity, and bonus costs, as covered in your CTC structure design.

Variable pay and benefits

Bands typically refer to fixed pay. Overlay your variable pay structure, such as a target percentage of fixed pay at each level, and add benefits separately. For sales roles, define on-target earnings (fixed plus variable) as the benchmarking measure.

Geographic differentials

If you operate across locations, either create separate bands by location tier or apply a multiplier to a base band. Keep the number of tiers small, such as two or three, to avoid complexity.

Step 6: Place employees in bands: the compa-ratio

Once bands exist, place each employee within their band and calculate the compa-ratio:

Compa-ratio = Employee's pay ÷ Band midpoint

A compa-ratio of 1.00 means the employee is paid exactly at the midpoint. Below 1.00 means below midpoint; above 1.00 means above.

Interpreting the results

Analyse by team, gender, location, and tenure. Unexplained patterns, such as consistently lower compa-ratios for women or recent hires, signal issues to examine.

Another useful measure: range penetration

Range penetration is the position of pay within the range: (Pay – Minimum) ÷ (Maximum – Minimum). It helps with decisions about increments, as an employee at 90% penetration has limited room for further base increases.

Step 7: Deal with outliers

Employees paid below the minimum

Plan to bring them up to the minimum. If the cost is too high to do at once, phase the adjustment over two cycles, starting with high performers and those at highest flight risk. Communicate that a market adjustment is being made, and keep it distinct from the performance increment.

Employees paid above the maximum

Do not cut pay. Options include freezing base pay increases until the band catches up, offering one-time lump sum awards instead of base increases, expanding the role scope to justify a higher level, or promoting if the person is truly operating at the next level. Document the plan.

Compression and inversion

Salary compression occurs when new hires are paid close to or more than experienced employees. It often arises when market rates rise quickly. Address it through targeted adjustments, rather than waiting for people to find out and leave. Track the gap between new hire pay and incumbent pay as a regular metric.

Step 8: Link bands to increments, promotions, and hiring

Bands are tools for decisions, not just charts.

Increment decisions

Combine performance rating and compa-ratio in an increment matrix. A common approach gives higher increments to high performers with lower compa-ratios, and smaller or lump-sum rewards to high performers who are already high in the band. Example:

Make sure your performance ratings are fair by using a calibration process before pay decisions are made.

Promotions

A promotion moves someone into a higher band. Set a guideline, such as placing the promoted employee at or above the minimum of the new band and generally within a defined increase range, for example 8% to 15%, subject to budget and internal equity. Avoid promotions that give a title without pay movement; it erodes trust.

Hiring offers

Give recruiters and hiring managers a clear rule: offers within the first half of the band for people meeting the requirements, and exceptions requiring HR approval. Check the offer against current employees in similar roles, to avoid creating inversion. Document the reason for any above-band offer. This helps you maintain pay equity and speeds up decisions.

Step 9: Communicate transparently

Communication determines whether your framework builds trust or suspicion.

• Train managers first. They need to explain the bands, handle questions, and avoid promises they cannot keep.
• Share the philosophy and structure with employees. Explain levels and how pay is determined, even if you do not publish every band.
• Provide employees with their own band. Many companies show employees the range for their level. It reduces rumours.
• Explain what influences pay movement. Performance, skills, scope, and market changes.
• Be honest about constraints. If budgets are limited, say so.
• Create a channel for questions. Use your HR helpdesk or a designated contact to handle pay queries consistently.

Be aware of evolving rules and expectations about pay transparency in job postings and pay equality. Stay informed about local requirements and consult legal counsel if you plan to publish ranges externally.

Step 10: Maintain and review

Salary bands lose accuracy quickly if they are never updated.

• Annual review: Refresh market data and adjust bands, typically before the increment cycle.
• Mid-year check: Review critical and fast-moving roles, such as technology and sales, in case market movement is rapid.
• Governance: Assign a person or small committee to approve exceptions and maintain the framework.
• Documentation: Keep records of changes, data sources, and decisions.
• Audit: Periodically check for pay equity, compression, and adherence to the bands.
• Metrics: Track compa-ratio distribution, offer acceptance rate, attrition in critical roles, time to fill, and percentage of offers within band.

Practical template: the band design worksheet

Create a spreadsheet with these columns for each job family and level:

• Job family and level
• Benchmark sources used and date
• Market 25th, 50th, and 75th percentile
• Target percentile (from philosophy)
• Midpoint
• Range spread
• Minimum and maximum
• Number of employees in the level
• Average compa-ratio
• Number below minimum and above maximum
• Notes and approvals

Keep a separate tab with assumptions, definitions of pay elements, location differentials, and version history.

Using HR software to support bands

Spreadsheets can hold the first version of your bands, but as you scale, integrated data helps. Useful capabilities include:

• A single employee master with job, level, location, and pay history.
• Automatic compa-ratio and range penetration calculations.
• Dashboards showing pay distribution by level, gender, and location.
• Increment simulation tools that test budget scenarios against bands.
• Workflow approvals for offers that exceed the band.
• Audit logs for pay changes.

Linking payroll with your HR records ensures that bands reflect actual pay, not stale data, and gives you fast answers to questions from leadership.

Common mistakes to avoid

1. Benchmarking by title only. Match on job content and scope.
2. Using a single data source. Triangulate across sources.
3. Ignoring total rewards. Employees consider benefits, flexibility, and growth alongside salary. Reference your benefits design when comparing.
4. Making bands too rigid. Allow documented exceptions, but track them.
5. Neglecting internal equity. Market data alone can create inconsistencies within teams.
6. Failing to communicate. Silence breeds rumours.
7. Updating too rarely. Markets move; so should your data.
8. Using bands to cap growth unfairly. Provide a path through promotion or role expansion.
9. Overlooking location. One national band may overpay in small cities and underpay in metros.
10. Skipping manager training. Even the best framework fails if managers cannot explain it.

Case study: bringing structure to a 150-person company's pay

A 150-person software services company in Pune had grown quickly through referrals and quick offers. Pay differences between similar developers reached 40%, managers kept asking for exceptions, and two high performers resigned citing "no clarity on growth". The HR head decided to build a first version of bands within a quarter.

Month one: levels and job families. The team defined six levels and three job families: engineering, delivery and support, and business functions. They mapped all 150 employees to a level using a short panel review with department heads. About fifteen people were mapped differently from their titles, which sparked useful conversations about expectations.

Month two: data and bands. They obtained two salary surveys and combined them with recruiter feedback and their own recent offer data. They set a median-based midpoint for most roles and a higher target percentile for two scarce engineering skills. Spreads were set at 30% for junior levels and 45% for senior levels.

Month three: placement and plan. Compa-ratios showed that 18 employees were below minimum, mostly experienced people hired early at lower pay, while 6 were above maximum, mostly early joiners who had received frequent increments. The team created a two-cycle correction plan: raise the 18 to the minimum starting with high performers, and hold base pay for the 6 while using one-time awards and role expansion. Total cost of the correction was budgeted separately from the normal increment pool, which kept the performance conversation clean.

Result. Managers received a one-page guide for making offers, with approval needed only for offers above the midpoint. Employees received their level, their band, and a simple description of what it takes to move up. Within two cycles, unexplained pay differences narrowed, offer approvals became faster, and exit interviews stopped citing pay clarity as a reason for leaving. The company did not publish every band, but it did share each person's own range and the framework.

The lesson is that a first version does not need to be perfect. It needs to be consistent, documented, and open to improvement each year.

Manager talking points for pay conversations

Equip managers with simple language for the questions they will face:

• "Why am I paid this?" Your pay reflects the level of your role, your experience and skills, your performance, and what the market pays for similar roles. You are currently at a specific position in the range for your level.
• "Why did a new joiner get more than me?" Offers are made within the band for the role at the time of hiring. If there is a gap that does not reflect experience or performance, raise it with HR; we review such cases during our regular pay checks.
• "How can I earn more?" By growing your skills and performance within the level, taking on larger scope that leads to promotion, or developing a skill that is in high demand.
• "Will the band change?" We review bands every year with fresh market data. Adjustments are made as needed and communicated.

Practise these conversations in a short workshop with role plays. Managers who feel prepared avoid both over-promising and evasive answers.

Total rewards: remember the whole picture

Benchmarking base salary alone can mislead. Employees weigh health coverage, flexibility, learning support, recognition, and job security. If your cash pay sits slightly below the market median but you offer strong benefits, flexibility, and growth, say so explicitly in offers and reviews. Conversely, if you rely on benefits to compensate for low base pay, test whether it works by tracking offer acceptance and resignation reasons. Your recognition program and learning budget are part of the same package and should be considered when you present a total rewards statement to employees.

Frequently asked questions

1. How many salary bands does an SMB need?

Typically between five and eight levels are enough for a company with a few hundred employees. You can add job families, such as technology, sales, and operations, if their market pay differs significantly.

2. Where can a small company find reliable salary data?

Use a combination of published salary surveys, subscription databases, recruiter insights, and your own offer and exit data. Triangulate and note the date and sample size of each source.

3. What is a compa-ratio, and why does it matter?

It is an employee's pay divided by the band midpoint. It helps you spot underpaid or overpaid employees, plan increments, and monitor pay equity.

4. Should we share salary bands with employees?

Many organisations share each employee's own band and the framework. Whether to publish all bands is a policy choice. Consider your culture, legal advice, and readiness to answer questions.

5. How often should we update benchmarks?

At least annually, ahead of the increment cycle, with interim reviews for fast-moving roles.

6. What should we do if market data suggests we must raise many salaries at once?

Prioritise by criticality, performance, and distance from the minimum. Phase adjustments over one to two cycles and communicate the plan.

7. How do bands fit with the new labour codes?

The labour codes affect how wages are defined for PF, gratuity, and bonus. Define whether bands refer to CTC, fixed pay, or gross, and test the impact of different pay structures on statutory costs. Verify current rules with your advisers.

8. Can we pay above the band for a scarce skill?

Yes, with a documented exception process, such as approval by HR and the finance head, and a review of the impact on internal equity. Track exceptions to see if the band itself needs adjusting.

Conclusion: pay you can explain

A salary band framework turns pay from a series of individual negotiations into a system that is competitive, fair, and explainable. Start small: define a philosophy, create levels, gather market data from more than one source, build bands with sensible spreads, check where employees sit, and use the results in your next increment cycle. Refresh it every year, train your managers, and communicate clearly.

If you want your employee records, pay history, and reports in one place so that compa-ratio checks and increment planning take hours rather than weeks, CozyHR can help you bring your people and payroll data together. Explore CozyHR when you are ready to make pay decisions with confidence.