Building a Fair Salary Structure for Your First 10 Employees

Why Your First Hires Deserve More Than a Gut-Feel Number

Most early-stage founders approach their first few hires the same way: they think of a number, check if they can afford it, and offer it. Sometimes that works. More often, it creates a mess six months later when your second engineer finds out your third engineer earns 15% more for the same role, and suddenly your team culture has a crack running straight through it.

A salary structure doesn't have to be complicated. You don't need a dedicated HR team, a consultant on retainer, or enterprise software. What you need is a logical framework you can build in an afternoon and explain to any employee in under five minutes. This guide walks you through exactly that.

Start With Job Levels, Not Job Titles

Before you assign a single rupee or dollar figure to any role, define what different levels of contribution look like in your company. Titles are slippery — a "Senior Developer" at a 5-person startup means something completely different than at a 500-person company. Levels are more honest.

A simple three-tier model works well for most teams under 10:

  • Level 1 — Contributor: Someone who executes defined tasks with guidance. They're still learning your systems, your context, your standards.
  • Level 2 — Independent: Someone who owns outcomes, not just tasks. They solve problems without daily direction and occasionally help others.
  • Level 3 — Lead: Someone who multiplies the team's output — through mentoring, architecture decisions, client relationships, or operational ownership.

You can map these levels across every function: engineering, sales, operations, design. Now when you're filling a role, you hire to a level first, then assign a title. This makes pay bands dramatically easier to set — and defend.

Research Market Rates the Right Way

This is where founders often either over-rely on a single source or skip benchmarking entirely. Neither is great. You need at least two or three data points to triangulate a realistic range for each level in your geography and sector.

Here are reliable places to pull compensation data without paying for an enterprise subscription:

  • LinkedIn Salary Insights — available within job postings; gives a rough local range by title and experience.
  • Glassdoor / AmbitionBox — crowdsourced, so skews toward bigger companies, but useful for sanity-checking floor and ceiling.
  • Levels.fyi — excellent for tech roles specifically; includes equity and bonus breakdowns.
  • Your network — a five-minute call with another founder in your space will tell you more than three hours of spreadsheet research.

Once you have data, define a pay band for each level: a minimum, a midpoint, and a maximum. A common rule of thumb is to make the band about 50% wide — meaning the maximum is roughly 50% higher than the minimum. So if your Level 1 midpoint is ₹6,00,000 annually, your band might run from ₹5,00,000 to ₹7,50,000.

Place new hires in the lower half of their band. Reserve the upper half for people who've proven themselves in your specific context.

Break Down the Salary Components

In India especially (and in many other markets), your employees don't just receive a flat salary — their total compensation package has distinct components that affect tax liability, provident fund contributions, and take-home pay. Getting this structure wrong creates compliance headaches you really don't want.

A standard Indian CTC (Cost to Company) structure for a small business typically includes:

  1. Basic Salary: Usually 40–50% of CTC. This is the foundation everything else is calculated against. Higher basic means higher PF deduction but also higher HRA eligibility.
  2. House Rent Allowance (HRA): Typically 40–50% of Basic. Employees in metro cities can claim HRA exemption up to a certain limit — a meaningful tax benefit they'll appreciate.
  3. Special Allowance: The balancing figure that makes the total add up to your CTC target. Fully taxable but flexible.
  4. Employer PF Contribution: 12% of Basic Salary (up to ₹15,000 Basic). This comes on top of the employee's own 12% contribution. Both are part of CTC in how most Indian companies present it.
  5. Gratuity Provision: 4.81% of Basic, set aside for employees who complete 5 years. Often included in CTC calculations even if not paid out monthly.
  6. Performance Bonus (if applicable): If you're offering a variable component, be specific about how it's earned — vague bonus promises breed resentment.

Build a simple Excel template that takes a CTC figure and automatically calculates each component. Share it with candidates during offer discussions. Transparency at this stage builds trust before the person even joins.

The Equity Question: When and How Much

If you're a funded startup, equity is part of the conversation. If you're bootstrapped, it might still be worth considering for your first few critical hires. Either way, keep it simple and put everything in writing.

For very early hires (employees 1–5), a typical ESOP grant might range from 0.1% to 1% depending on the role's seniority and strategic importance. Employees 6–10 usually receive smaller grants, since the risk-reward ratio has shifted and the company is more established.

Standard vesting in India is a 1-year cliff followed by monthly or quarterly vesting over the next 3 years — a 4-year total schedule. Don't deviate from this without good reason; candidates understand it and it signals you're running a professional operation.

One thing founders consistently forget: explain what the equity is worth in practical terms. Don't just say "0.25% of the company." Tell them what the company's last valuation was, what a potential exit might look like, and what dilution might occur in future rounds. People can't evaluate what they can't understand.

Communicating Your Structure to Candidates and Employees

Having a pay structure is only half the job. The other half is using it actively in conversations rather than hiding it.

When making an offer, walk the candidate through: the level they're being hired at, the full CTC breakdown, where they sit within the pay band, and what milestones or timelines govern movement through the band. This takes about 10 minutes and sets an expectation of fairness that pays dividends over time.

For existing employees, conduct a salary review at least once a year — ideally twice, once mid-year for performance conversations and once at year-end for adjustments. During each review, show the employee where they sit in their band and what progression looks like. People are far more tolerant of not getting a raise when they understand the framework behind the decision.

Staying Compliant Without a Full-Time HR Person

Compliance sounds intimidating but for a team under 10, your actual obligations are manageable:

  • PF Registration: Mandatory once you hit 20 employees, but you can register voluntarily before that — and many employees will expect it.
  • ESI (Employee State Insurance): Applies if any employee earns less than ₹21,000/month. Covers medical benefits. Employer contributes 3.25%, employee contributes 0.75%.
  • Professional Tax: State-specific; ranges from ₹0 to ₹2,500 annually. Check your state's slab.
  • TDS on Salary: Deduct tax at source from employee salaries each month if their income is above the exemption threshold. File quarterly TDS returns (Form 24Q).
  • Payslips: Issue every month. They don't need to be fancy — a clear itemised breakdown is sufficient and legally advisable.

A basic payroll tool — Razorpay Payroll, Greythr, or even a well-built spreadsheet — can handle most of this once your structure is set. The structure is the hard part. Execution becomes routine.

One Last Thing: Write It Down and Share It

Create a one-page Compensation Philosophy document. It doesn't need legal language. It just needs to explain: what factors determine pay levels, how you benchmark against the market, what the review cadence is, and how equity fits in. Post it in your internal wiki or share it in your employee onboarding packet.

This single document will save you more awkward conversations than anything else you do. When a team member asks "why does X earn more than me?", you can point to a framework rather than scrambling for an answer that sounds fair in the moment. That's not just good HR — it's good management.

Building a salary structure before you feel like you need one is one of the highest-leverage things you can do as a founder. It costs you an afternoon. It pays back in trust, retention, and the quiet confidence of knowing your team understands where they stand.