Live cohort · AI Leadership CourseCourse participants — enter your workspace
Vinay Pasricha Explorer of Emergence
Now Publishing across languages Building GoodSpace AI Running a live cohort

What a Bad Hire Really Costs in India

Two glowing waves, one gold and one blue, drift in and out of step across a dark field

Short answer: A bad hire costs far more than the salary you paid. Add up six things: the salary paid, the cost to recruit, onboarding and manager time, the output you didn't get, the cost to hire again, and the damage to your team and customers. In the illustrative example below, a ₹9 lakh-a-year hire who leaves after five months costs about ₹20 lakh. Your numbers will differ. Work them out anyway: most founders never do, which is why the same mistake keeps happening.

I'm Vinay Pasricha. I run GoodSpace AI, a hiring company in Noida, and I wrote Organizational Frequency, a book about why good people fail in the wrong places. This is what I'd tell a founder who has just made a bad hire, or is about to.

Why founders underestimate the cost

When a hire goes wrong, most founders count one number: the salary. "We paid him ₹75,000 a month for five months. Lesson learnt."

That's the smallest part of it. Salary is the only cost that shows up neatly in your books. Everything else hides in places nobody adds up: your calendar, your best manager's evenings, the customer who quietly moved half their orders to someone else, and the two good people who started looking because they were tired of covering.

In a large company, one bad hire is a line item. In an MSME with 30 or 80 people, one wrong person in a key seat can set a whole function back by a quarter.

A simple formula

Here's the formula I use. It's meant to be filled in on the back of an envelope, honestly.

Cost of a bad hire = A + B + C + D + E + F

  • A. Salary paid: everything you paid them, including benefits, from joining day to exit.
  • B. Recruitment cost: agency fees or job-board spend, plus the time your people spent screening and interviewing.
  • C. Onboarding and manager time: training, equipment, and the hours their manager spent explaining, checking and redoing work.
  • D. Lost output: the gap between what the seat should have produced and what it actually produced.
  • E. Re-hire cost: running the search again, plus the weeks the seat sits empty.
  • F. Team and customer impact: lost or reduced business, extra load on colleagues, and anyone good who left because of it.

A is certain. B and C you can estimate in an afternoon. D, E and F are judgement calls, and they're usually the biggest. Don't leave them out just because they're uncertain.

Illustrative example — plug in your own numbers

This is an illustration, not data. Every figure below is an assumption I've chosen to show how the formula works. It is not an average, a benchmark or a survey result. Replace each one with your own.

Say you run a ₹40 crore manufacturing business in Pune. You hire a regional sales manager at ₹9 lakh a year, or ₹75,000 a month. He interviews well and has a good track record at a bigger company. Five months later, he's gone.

LineWhat you count (assumptions)Illustrative figure
A. Salary paid5 months × ₹75,000₹3,75,000
B. RecruitmentAgency fee, assumed at one month's salary (₹75,000), plus interviewing time (₹25,000)₹1,00,000
C. Onboarding and manager timeYour sales head, costing ₹2 lakh a month, spends about 6 hours a week on him for 5 months: about 120 hours at ₹1,250 an hour (₹1,50,000), plus ₹20,000 for training and a laptop₹1,70,000
D. Lost outputThe seat should contribute ₹3 lakh a month from month three; it contributed ₹1 lakh a month in months three to five₹6,00,000
E. Re-hire costA second search (₹1,00,000) plus about six weeks of an empty seat (₹4,50,000)₹5,50,000
F. Team and customer impactOne dealer cuts orders and a senior executive covers the territory: a deliberately rough estimate₹2,00,000
Total₹19,95,000

So a ₹9 lakh hire cost about ₹20 lakh, a little over twice his annual salary. The salary itself was less than a fifth of the damage.

Don't quote "twice the salary" as a rule. It's only what these assumptions produce. A junior role with a short ramp-up may cost well below a year's salary; a senior hire who takes key accounts or good people with them may cost far more. The point is that A is usually the smallest line in an honest calculation, and the only one most founders count.

Two things make the number grow fast:

  1. Time. Every extra month you keep a mismatched person adds to A, C and D. Most founders sense within the first few weeks that something is off. Many wait months to act, hoping it will fix itself.
  2. Seniority. The more a role touches customers, money or other people, the bigger D and F get. A wrong manager doesn't just underperform. The people under them start underperforming too.

Bad hires are usually mismatches, not bad people

Here's what running a hiring company has taught me: most bad hires are not bad people. They're good people in the wrong place.

The sales manager who struggled in your 40-person company might have been excellent at the structured, process-heavy firm he came from. There, he had a CRM, a marketing team generating leads and a clear escalation path. With you, he had a phone, a price list and you. Nothing was wrong with his ability. The environment was different, and nobody tested for it.

In Organizational Frequency I call this a frequency mismatch. Every company has a characteristic frequency: its pace, its decision style, its tolerance for ambiguity, the register in which people think and talk. Every person has one too. When the two resonate, ordinary people do remarkable work. When they don't, talented people look mediocre, often within months. As I put it in the book, most hiring failures are resonance failures disguised as performance failures.

That changes what you do next. If you think the problem was the person, you'll hire the next person the same way and get the same result. If you see it as a mismatch, you fix how you hire.

Signs of a frequency mismatch

These are the signals to watch for in the first 30 to 90 days. One on its own means little. Three or more together usually point to a mismatch, not a skill gap.

  • Pace friction. They wait for approvals you never meant them to need, or they move so fast they skip the checks your business depends on.
  • Decision-style clash. You want them to decide and tell you later; they want everything signed off. Or the other way round.
  • Discomfort with ambiguity. They keep asking for a clear process in a company that doesn't have one yet, or they ignore the one process you really need.
  • Great interview, lost by week three. They performed well in conversation but can't find their feet in the actual work.
  • Your instructions keep getting longer. You find yourself writing detailed notes for things you'd expect someone at that level to simply handle.
  • The team routes around them. Colleagues stop copying them, go straight to you, or quietly redo their work.
  • "Attitude" is the word you reach for. When a founder says someone has an attitude problem, it's often a frequency problem that hasn't been named.
  • They were a star somewhere else. A strong record in a very different environment is a reason to check fit more carefully, not less.

How do you tell a skill gap from a mismatch? A skill gap closes with training and time, and you can see the curve bending. A mismatch doesn't close. More training just produces a better-trained person who still doesn't fit.

The four stages: understand, discover, validate, grow

Organizational Frequency sets out four stages. They're not a funnel. Each is a posture your company takes before any individual hire is made. Here's how I'd apply them in an MSME that doesn't have an HR department.

1. Understand your own frequency

Before you judge anyone else's fit, name your own. Most companies can't. They have a values poster and a job description, but no honest map of how they actually work.

Sit down with two or three people who have done well in your company and answer four questions. How fast do decisions get made here? Who makes them, and how much gets written down? How much ambiguity does a new person have to live with? How do people disagree? Write the answers in plain words. That page is worth more than any job description you've ever written.

2. Discover where the person actually belongs

Stop asking only what candidates have done. Ask how they naturally operate. Have them walk you through a normal week in their last job: who they worked with, what they decided on their own, what frustrated them. Frustration is a strong signal. Someone who was frustrated by slow approvals may thrive with you. Someone who was frustrated by a lack of structure may not.

Use more than conversation: look at real work and real interactions.

3. Validate against the environment, not the role

The role is a snapshot. The environment is a living system. So test in the environment. Give candidates a real problem from your business, not a textbook case. Have them meet the actual manager and two future colleagues, not just you. If you can, run a short paid assignment. Then ask: would this person do well here, with this manager, at this stage of our company? That's a different question from "can they do the job?"

4. Grow both the person and the company together

Hiring doesn't end on joining day. A person's frequency shifts as they mature. Yours shifts as you scale. The sales manager who fits your company at ₹40 crore may not fit it at ₹150 crore, and that's nobody's fault.

Hold short, honest check-ins at 30, 60 and 90 days. Ask both sides the same question: is this working the way we expected? If it isn't, act early. Moving someone to a seat where they fit, or parting well in month two, costs far less than waiting until month eight.

If you've already made a bad hire

Act on what you know. Look at the formula again: every month you wait adds to A, C, D and F.

  1. Name it early. If three or more of the signs above are showing by day 60, have the conversation.
  2. Check whether it's the seat or the person. Sometimes there's a better seat for them inside your company.
  3. If it isn't working, part with dignity. Be honest, be fair on notice and pay, and help them land somewhere that fits. Your industry is smaller than you think, and people remember how you behaved.
  4. Run a post-mortem on the hiring, not the person. Which of the four stages did you skip? Most of the time it's the first. You never named your own frequency, so you had nothing to match against.

Where GoodSpace AI fits

(Disclosure: I founded GoodSpace AI, which sells hiring services.)

GoodSpace AI is the hiring platform we built on these ideas. On our own numbers, we send the first shortlist in about a week, and interviews usually take another week. After that it depends on the candidate's notice period, anywhere from one to six weeks. On average, that's about four weeks from brief to joining. Our offer-to-join rate is nearly 90%, which I put down to how carefully we match for frequency before anyone gets an offer.

You don't need us to use the four stages. They work with a notebook and an honest hour. But if you're hiring below the CXO level and want it done for you, hire with GoodSpace AI. The hiring path on this site explains the doctrine in more depth, and my guide to AI in recruitment in India covers where AI helps in hiring and where it doesn't.

FAQ

How much does a bad hire cost in India?

There's no single honest number, because it depends on the role, the salary, how long the person stayed and what the seat should have produced. Add six costs: salary paid, recruitment, onboarding and manager time, lost output, re-hire cost, and team and customer impact. In this article's illustrative example, which uses assumed figures, a ₹9 lakh-a-year hire who leaves after five months costs about ₹20 lakh.

How do I calculate the cost of a bad hire?

Use the formula: salary paid + recruitment cost + onboarding and manager time + lost output + re-hire cost + team and customer impact. Take the first three from your records, estimate the last three honestly, and don't leave them out because they're uncertain. They're usually the largest.

What are the early signs of a bad hire?

Watch for pace friction, clashing decision styles, discomfort with ambiguity, someone who interviewed well but is lost by week three, instructions that keep getting longer, and a team that starts working around the person. Three or more of these in the first 90 days usually point to a frequency mismatch rather than a skill gap.

Is a bad hire always a bad person?

No. Most bad hires are mismatches: capable people placed in an environment whose pace, decision style or tolerance for ambiguity doesn't suit them. The same person may do very well somewhere else. That's why fixing how you hire matters more than blaming the individual.

How can a small business avoid bad hires?

Follow four stages. Understand your own company's frequency first, discover how candidates naturally operate, validate them against your real environment rather than the job description, and keep both sides aligned after joining with check-ins at 30, 60 and 90 days.

Where to go next

The full argument is in my book Organizational Frequency: why resumes and interviews measure the performance of fit rather than fit itself, and how the four stages work in practice. It's on Kindle: get Organizational Frequency on Amazon.

Before you read, try the free Find your organizational frequency self-reflection. For the longer essay on hiring by frequency, and to share a hiring mandate, see the hiring path.

Watch: The Hiring Mistake Every Company Makes.

Vinay Pasricha is the founder of GoodSpace AI and the author of six books, including Organizational Frequency. Watch his videos on YouTube.

Published 30 September 2026

What to read or do next