The pattern is real and measurable
Most Indian founders hire 25-40 people in year one. Revenue in year one: Rs 20-50 lakhs for a SaaS startup, Rs 5-15 lakhs for a marketplace. Do the math. You have hired one person per Rs 2-5 lakhs of revenue. That employee costs Rs 6-12 lakhs annually in salary alone. You are bankrupt by month 9.
Why does this happen? Three reasons.
Reason one: Visibility bias
Hiring feels like progress. You announce a new hire. Your co-founder feels relief. The office gets louder. The cap table grows. None of this is progress. Revenue is progress. Your GTM is either working or it is not. A new account executive does not change that.
Founders confuse team size with momentum. Investors reward momentum. So you hire to show momentum to investors. But investors are also trained to read burn rates. You are fooling yourself, not them.
More people does not fix a broken sales process.
Reason two: Fear of attrition
You hire 8 engineers because you think you will lose 2-3 by month 6. Talent is poached. Startup life is hard. Your prediction has some truth. But your math is backwards.
If you hire 8 and lose 3, you still have 5. If you hire 5 and lose 2, you have 3. One is expensive and chaotic. The other is lean and focused. Instead of hiring buffer, hire slow and pay well.
A single strong engineer at Rs 20 lakhs annually builds more than three mediocre engineers at Rs 10 lakhs. You will attrition the weak ones anyway. Start there.
Reason three: No friction in the firing decision
This is the deepest reason. In India, you have no firing culture. You cannot fire someone in month 3 if they are not working out. The HR process is slow. The discomfort is high. So you never hire the right person in the first place. You hire the "safe" person. Then you hire two more to cover for the safe person. Now you have three people doing one job.
Most founders have never fired anyone. The thought paralyzes them. So they do not hire salespeople and expect engineers to sell. They do not hire a finance person and lose Rs 15 lakhs to a vendor billing error. The hiring becomes reactive and loose.
What should happen instead
Hire for a specific, measurable outcome, not for a role. Do not hire an "account executive." Hire someone who will close Rs 1 crore in ARR in 6 months. If they do not, the hire was wrong, not the execution.
Write the success metric before you write the job description. Share that metric with the candidate. Now the hire is a bet, not a hope.
Hiring timeline that works
| Timeline | Action | Red flag |
|---|---|---|
| Month 1-3 | Founder does the work | Hiring before you know what the work is |
| Month 4-6 | Hire one specialist | Hiring for "coverage" not for leverage |
| Month 7-9 | One person covers Rs 30-50 L revenue | Hire number 2 before hire 1 is productive |
| Month 10-12 | Hire second specialist | Hiring to replace founder work, not multiply it |
The cost of over-hiring
Over-hire by 10 people in year one. Each person costs Rs 8 lakhs annually. That is Rs 80 lakhs in wasted salary expense. Your seed was Rs 2-3 crore. You just burned 27-40% of your seed on people who had no job to do.
Now it is month 13. You have Rs 40-50 lakhs left. The cash runway is 2 months. You must lay off 5-7 people. The good ones are already interviewing elsewhere. You lose your best engineer because she saw the dysfunction coming. You are left with the ones who had no option to leave.
Lay off the weak ones early. It is a favor, not a punishment. They find a better fit. You find money instead of wasting it.
Hire only when the absence of that person costs you more than the salary.
What to do today
Count your open roles. For each role, write down the specific revenue or product outcome that hiring will unlock. If you cannot write it in one sentence, do not hire. If the outcome could happen without the hire, you are hiring to feel busy, not to scale.
Start there.