Indian startup founders choosing their first employees around a product prototype in a Bengaluru workshop

Hiring Your First 10 Employees in India

17 min read

Most Indian founders hire their first 10 employees in the wrong order. They hire a senior “strategy” person before they have repeatable sales, a full-time HR manager before they have 15 people, and three engineers before they know which product customers will pay for. Then they blame the talent market for a cash problem they created themselves.

So who should your first 10 employees be? The answer is not a fixed org chart. Hire the people who remove your current bottleneck: usually a builder, a customer-facing operator, a second builder, and only then specialists. Keep founder ownership of hiring, pay mostly in cash you can afford, use ESOPs carefully, and budget for statutory compliance from day one.

What your first 10 employees should actually do

Your first 10 employees are not a miniature version of a large company. They are a force multiplier for the founders.

At this stage, every hire should do at least one of three things:

  • Build and ship the product.
  • Bring in customers or improve retention.
  • Remove recurring operational work that is blocking the founders.

If a proposed hire does none of these, do not hire them yet. “They will help with strategy” is not a job description. Neither is “we need someone senior in the team.”

The first 10 employees create the company’s operating habits. They decide whether meetings are short or endless, whether bad news travels quickly, whether customers get answered, and whether people take ownership without waiting for instructions. Later hiring will amplify these habits. It will not magically repair them.

Rule: Hire against a measurable bottleneck, not against a vague feeling that the company is becoming busy.

First 10 employees startup India: the practical sequence

There is no universal sequence, but there is a reliable default for an Indian product startup still searching for repeatability.

Hire Typical timing Primary job What must be true before hiring
1. Founding engineer or product builder After founders validate the problem Turn customer pain into a working product You know the first use case and can explain it clearly
2. Customer-facing operator Very early Talk to users, onboard them, collect objections Founders are already speaking to customers regularly
3. Second technical hire When shipping is the bottleneck Increase product velocity and reduce single-person dependency The first builder has enough work for another person
4. Sales or growth owner Once a channel shows signs of repeatability Turn founder-led selling into a process You have evidence that customers will pay
5. Operations or implementation hire When delivery consumes founder time Make fulfilment reliable Workflows are documented enough to hand over
6. Product or design generalist When customer feedback is piling up Improve usability and prioritisation There is a clear product backlog tied to customer problems
7. Finance and administration operator When transactions and compliance become recurring Control cash, invoices, payroll and filings Founders are losing time or making avoidable errors
8-10. Repeat the constraint After evidence, not ambition Increase output in the strongest function The existing team has a measurable workload and owner

This sequence changes by business. A logistics startup may need operations before a second engineer. A B2B SaaS company may need a solutions engineer before a marketer. A consumer app may need growth and customer support earlier. The principle stays fixed: the next hire must remove the constraint that is costing you the most growth or founder time.

The first hire: do not outsource product judgment

Your first employee should usually be a builder who can work close to customers. That may be a founding engineer, product engineer, or technical generalist. It should not be a manager.

You need someone who can:

  • Ship a usable version without a six-month architecture exercise.
  • Debug production problems without escalating every decision.
  • Speak to users and change the product based on evidence.
  • Work with incomplete specifications.
  • Explain trade-offs in plain language.

Do not hire a “CTO” because the title sounds fundable. If you have two founders and a prototype, you need someone who writes code and owns outcomes. A senior executive from a large Indian IT services company may have impressive experience but still struggle when there is no product manager, QA team, procurement department or brand name to hide behind.

Test the work. Give candidates a paid, time-boxed assignment based on a real problem. Ask them to walk through what they would not build. The refusal is often more revealing than the demo.

The second hire: get closer to customers, not farther away

Your second employee should often be a customer-facing operator. This person can be an implementation lead, sales generalist, customer success owner, or business operations generalist, depending on your model.

Founders commonly make the opposite choice. They hire another engineer because engineering feels productive. Meanwhile, nobody is onboarding users, following up on unpaid invoices, recording objections, or finding out why customers stop using the product.

In an Indian startup, this role may need to handle several jobs:

  • Run product demos.
  • Coordinate with a customer’s procurement or IT team.
  • Train users in English or a local language.
  • Chase documents, payments and implementation dependencies.
  • Write down recurring objections for the product team.

Do not call this “sales” if the product still needs explanation and hand-holding. Call it what it is: learning how the customer buys and uses the product.

When to hire your third to fifth employee

By employee three, your hiring decision should be driven by evidence from the first two people.

If product delivery is slow

Hire a second technical generalist. Avoid splitting into frontend, backend, DevOps and QA too early. At five or six people, a narrow specialist can create handoffs that did not exist before. You want people who can own a feature from customer problem to deployment.

If customers are interested but do not convert

Do not automatically hire more salespeople. First find the broken step. Is pricing unclear? Is implementation too painful? Does the product fail a security review? Is the buyer different from the user? More sales activity will only increase the number of confused prospects.

If customers are buying but delivery is chaotic

Hire operations or implementation. In businesses such as logistics, construction supply, manufacturing procurement and managed services, the operational layer is the product. A salesperson who signs contracts that your team cannot fulfil is not helping you grow.

If founders are spending half their week on admin

Hire a sharp operations and finance generalist before hiring a head of finance. This person can manage vendor payments, payroll coordination, collections, basic reporting, travel, contracts and documentation. Use a chartered accountant and employment lawyer for specialist work. Do not turn a junior hire into a pretend CFO.

Do not hire a head of sales before you have a sales motion

This is one of the most expensive early-stage mistakes in India.

A founder closes five deals through personal relationships and then hires a sales leader at ₹25-40 lakh per year to “scale the process”. But the founder was the process. The founder supplied credibility, product knowledge, pricing flexibility and relentless follow-up. The new hire receives a spreadsheet and a quota.

Hire sales leadership only after you can describe:

  • The target buyer and economic decision-maker.
  • The average sales cycle.
  • The source of qualified leads.
  • The conversion rate at each stage.
  • The average contract value and gross margin.
  • The reason deals are lost.
  • The time required to recover customer acquisition cost.

If you cannot answer these, hire a sales generalist who will sell alongside you and document the motion. You need learning, not hierarchy.

India-specific salary and runway math

There is no single “startup salary” in India. Bengaluru engineering salaries, Pune product salaries, Delhi-NCR sales salaries and tier-2 city operations salaries differ sharply. Remote hiring widens the range further.

For early planning, founders often see broad annual cash ranges such as:

  • Junior operations or support: ₹3-8 lakh.
  • Strong generalist or early sales hire: ₹6-15 lakh.
  • Product engineer: ₹8-20 lakh.
  • Senior founding engineer: ₹15-35 lakh or more.
  • Experienced functional leader: ₹25 lakh upward.

These are planning ranges, not market quotes. A candidate’s actual price depends on skill, location, competing offers, domain knowledge and how much risk they are taking by joining you.

Calculate the complete monthly cost, not just CTC:

Monthly people cost = salary + employer statutory costs + benefits + recruitment cost amortisation + equipment + office or coworking cost.

Suppose you hire four people at an average CTC of ₹12 lakh. That is ₹48 lakh of annual CTC, or ₹4 lakh per month before other costs. Add founders’ salaries, cloud, contractors, travel, rent, legal and sales expenses. Your actual monthly burn may be ₹7-10 lakh or more.

If you have ₹60 lakh in the bank and burn ₹8 lakh per month, you do not have 7.5 months of comfortable runway. You have less once hiring delays, receivables and fundraising time are included. Keep at least two months as a buffer for an early company. Do not hire to the cash balance. Hire to the milestone the cash must buy.

Cash versus ESOPs for the first 10 employees

Early employees accept risk. You should compensate them honestly for it.

Do not offer a low salary with a large verbal promise about “massive upside”. The employee cannot pay rent with your future valuation. Put the equity terms in writing and explain the tax and vesting mechanics.

For Indian startups, typical ESOP terms may include four-year vesting with a one-year cliff, but the right grant depends on seniority, cash discount, role criticality and dilution. A founding engineer taking a meaningful pay cut deserves more than a junior employee joining at market salary.

Explain:

  • The number of options, not just the percentage.
  • The fully diluted share count used for the percentage.
  • The exercise price and vesting schedule.
  • What happens if the employee resigns or is terminated.
  • The exercise window after leaving.
  • Tax treatment at exercise and sale.
  • Whether future funding will dilute the holding.

Read this practical guide on ESOPs for early employees in India before making promises. Also remember that sweat equity is not a casual substitute for salary; it has separate legal and tax considerations. See sweat equity agreements in India if you are considering that route.

Employment contracts and compliance in India

Do not copy an American offer letter and call the job done. Your Indian entity needs proper documentation and payroll processes.

Your employment agreement should cover:

  • Role, reporting line and place of work.
  • Salary structure and payment date.
  • Probation and notice period.
  • Confidentiality and intellectual property assignment.
  • Invention and code ownership.
  • Data protection and information security obligations.
  • Conflict of interest and outside work.
  • Termination terms.
  • Leave, benefits and applicable company policies.

Check applicability of provident fund, ESIC, professional tax, labour welfare fund, gratuity, state-specific shops and establishments rules, maternity benefits, POSH requirements and payroll tax deductions. The exact obligations depend on your state, headcount, salary levels and entity structure. Use a competent payroll provider and employment counsel. “Our CA handles it” is not a compliance strategy unless you know exactly what they handle.

Contractors can help for short assignments. They are not a magic way to avoid employment obligations. If you control their hours, methods, reporting and ongoing work like an employee, misclassification can create legal and tax exposure. Make sure contractor agreements assign intellectual property properly and protect confidential information.

How to interview the first 10 employees

Do not run a polished corporate interview. It produces polished corporate answers.

Use a structured process:

  1. Screen for the actual work. Ask for examples of something the candidate personally shipped, sold, fixed or improved.
  2. Test judgment. Give them a messy situation with missing information. Ask what they would do in the first 48 hours.
  3. Check speed and ownership. Ask about a failure where nobody assigned the problem to them.
  4. Use a paid work sample. Keep it small and relevant. Do not ask for free production work.
  5. Run reference checks yourself. Speak to former managers and peers. Ask what the candidate did when the plan failed.
  6. Sell the actual job. Explain the uncertainty, salary, location, working hours and founder involvement. Do not hide the mess.

Ask questions that expose behaviour:

  • Tell me about a time you shipped something that customers did not want.
  • What is a decision you made with incomplete data?
  • What would your previous manager say you needed to improve?
  • Show me how you would prioritise these five customer requests.
  • What work do you refuse to do, even in a small company?

Be cautious with candidates who speak only about team achievements. Early employees must know what they personally owned.

Culture is set by what you tolerate

Founders talk about culture as if it comes from a values poster. It comes from hiring decisions, promotions and tolerated behaviour.

If your first salesperson lies about pipeline and you keep them because revenue is weak, you have chosen dishonesty as a company value. If your first engineer repeatedly misses commitments and you keep rewriting the roadmap around them, you have chosen low accountability. Your next hires will notice.

Write down five operating rules. Keep them behavioural:

  • Bad news travels the same day.
  • Customer commitments are written down.
  • Every project has one owner.
  • Disagree in the room; commit after the decision.
  • Small releases beat impressive plans.

Then enforce them yourself. Founders who arrive late, change priorities daily and bypass managers cannot demand discipline from employee number eight.

Remote, office or hybrid for a 10-person Indian startup?

Choose the model based on the work, not fashion.

Product teams can work remotely if communication, documentation and release ownership are strong. Customer implementation, warehouse operations and field sales often need physical presence. Hybrid arrangements fail when they create two classes of employees: people in the room who receive context and remote employees who receive minutes.

Before hiring, define:

  • Which roles need regular physical presence.
  • Core hours for collaboration.
  • Expected response times.
  • Where decisions are recorded.
  • How performance is measured.

Do not rent a large office because investors expect one. Your first office should support the work and fit the runway. A ₹3 lakh monthly office bill is ₹36 lakh a year before furniture and deposits. That can fund several months of engineering or customer acquisition.

What investors look for in your first 10 hires

Investors do not expect a seed-stage company to have every function staffed. They do expect the team to make sense.

During a seed or pre-Series A discussion, be ready to explain:

  • Why each hire was made in that order.
  • What metric or bottleneck justified the hire.
  • Which roles are missing and why.
  • How much runway remains after the hiring plan.
  • Who owns product, sales, operations and finance.
  • Which employee is a single point of failure.
  • What happens if the next round takes six months longer.

A 10-person team with no clear ownership is worse than a six-person team with high output. Investors have seen founders use headcount as a proxy for progress. They will ask what the team produced, not how many offer letters you signed.

Do not hire a finance head to impress investors. Do not hire a VP of marketing because the pitch deck has a marketing slide. Hire when the work exists and the economics support it.

The 30-day hiring plan you can use this week

Build a one-page hiring plan before opening any role.

  1. Write the bottleneck. Example: “Founder spends 25 hours per week on customer onboarding, delaying product releases.”
  2. Define the output. Example: “New hire owns onboarding and reduces founder involvement to five hours per week within 60 days.”
  3. Set a cash ceiling. Include salary, statutory costs, equipment and recruitment fees.
  4. Write a scorecard. List three outcomes and five skills. Do not write a generic job description.
  5. Source through people who have seen the work. Ask founders, former colleagues, operators and domain communities for referrals.
  6. Interview with two founders or senior team members. Keep the final decision with the founders for the first 10 hires.
  7. Set a 30-, 60- and 90-day plan. If you cannot define early outputs, you are not ready to hire the role.

Run a weekly hiring review. Track candidates by source, stage, salary expectation, evidence of ability and references. Do not let one impressive interview override weak evidence.

When not to hire

Do not hire when:

  • You are still changing the customer and problem every week.
  • The founders have not done the work themselves at least once.
  • The role exists mainly because a competitor has one.
  • You cannot explain the first 90-day output.
  • The hire reduces runway below the time needed to reach your next fundable milestone.
  • You are using headcount to look credible in a fundraising process.

Use freelancers, agencies, part-time specialists or advisors for bounded work. But protect intellectual property and confidentiality. An advisor can help with a narrow problem; they should not become an unaccountable shadow executive. If you need outside judgment, read how to find a startup mentor in India and ask for specific help, not general encouragement.

Bottom line

Your first 10 employees should not make your startup look bigger. They should make it harder for the bottleneck to survive.

Hire builders before managers. Hire customer closeness before marketing theatre. Hire operations when delivery breaks. Pay fairly in cash, document equity, comply with Indian employment rules, and keep founders in every early hiring decision.

The best early team is not the one with the most impressive résumés. It is the smallest group that can repeatedly ship, sell and deliver without the founders carrying every task. If a hire cannot move one of those outcomes, keep your cash.

FAQs

Who should be the first employee in an Indian startup?

Usually a technical or product builder who can ship quickly and work directly with customers. If the product is already built and delivery is the bottleneck, the first hire may instead be an operations or implementation generalist.

How many employees should a startup have before raising a seed round in India?

There is no required headcount. A strong two- or four-person team with customer evidence is better than a 15-person team with weak usage and no clear ownership. Raise against a milestone, not an employee number.

What salary should I offer my first employee in India?

Start with the market cash range for the role and location, then adjust for risk, seniority and equity. Many early product engineers fall somewhere between ₹8 lakh and ₹20 lakh annual CTC, but exceptional candidates and senior founding engineers can cost much more.

Should my first 10 employees receive ESOPs?

Most meaningful early hires should receive some equity, but the grant must match the risk and pay cut. Document the number of options, vesting, exercise price, exit rules and tax implications. Never sell ESOPs as guaranteed wealth.

Should I hire a senior manager early?

Usually no. Hire a senior individual contributor who can produce the work and set standards. A manager becomes useful when there are enough people and recurring work to manage.

Can an Indian startup hire contractors instead of employees?

Yes, for defined work and limited periods. Use a proper agreement covering payment, confidentiality and intellectual property. Do not treat a full-time, supervised worker as a contractor merely to avoid payroll or employment obligations.

When should a startup hire its first HR employee?

Not at five or ten employees unless your business has unusual compliance or hiring volume. Founders should own early culture and hiring. Use payroll, legal and HR specialists part-time until people operations becomes a recurring workload.

How do I know whether I need another engineer or a salesperson?

Measure the constraint. If paid demand exists but product delivery is slow, hire engineering. If the product works but qualified prospects are not moving through a repeatable sales process, hire customer-facing sales capacity. Do not hire sales to compensate for a broken product.

What should investors see in a first-10-employee hiring plan?

They should see the bottleneck each hire removes, the expected output, the cash cost, the remaining runway and the milestone the team should reach. A headcount chart without this logic is not a plan.

If you want a hard second opinion on your early hiring plan, Malpani Ventures works with founders at precisely this stage.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top