Before You Hire, Find the Bottleneck

The sentence "we need to hire" often arrives before anyone has said what is actually stuck.

I know why. When a business gets busier, the work is visible and the constraint is not. People are tired. Deadlines slip. A founder is answering messages at midnight. Adding a person feels like the responsible response. Sometimes it is. Sometimes it gives a messy process one more person to confuse.

At Perfume Lounge, we expanded the team while the economics of an order were still unsettled. More hands helped us process more volume, but volume was not the question we most needed to answer. That lesson is why I now want to know what a hire will change before I want to know the job title.

Name the work that is waiting

For two weeks, write down where work stops. Not "marketing is overloaded." What is waiting, for how long, and for whom? Are customer replies delayed because no one is available, or because every exception needs the founder's approval? Are designs delayed because there are too few designers, or because briefs change three times before sign-off?

Those are different problems. A support hire helps the first one. A decision rule may fix the second. A new designer helps with actual production capacity. A better brief may do more than a second designer.

I would measure the queue in units the team recognises: tickets waiting after one business day, proposals not sent, orders held for manual review, projects that have missed an agreed milestone. "Everyone is stretched" is a feeling worth listening to. It is not yet a hiring plan.

The other useful question is where the founder appears in the queue. If one person approves every discount, every creative change, and every refund, a hire simply adds another route back to that person. The business has a decision bottleneck, not a headcount bottleneck.

Decide what the hire must buy

The case for a hire should fit in three sentences. This work is currently waiting. A person with these skills can take ownership of it. If the hire works, this measurable thing will change within a reasonable period.

For a client service business, that might be more projects delivered on time without the founder reviewing every draft. For a consumer business, it might be shorter response time on the cases that cause refunds or repeat complaints. Sometimes the benefit is judgment rather than volume: an experienced operator may prevent decisions that would cost far more than a salary.

None of this means every role needs a neat return-on-salary calculation. Some work protects quality, trust, or the team's ability to keep going. But you should still be able to say what the role is for. If the answer is "we are growing," the case is incomplete.

Try the cheaper test first

Before opening a permanent role, I would ask whether the constraint can be reduced by a better handoff, a written rule, a small piece of software, or a fixed term specialist. That is not an argument for replacing people with tools. It is a way to avoid putting a full-time person inside a broken workflow.

Take customer support. If most messages ask the same five questions, the first job is to fix the page or process that creates those questions. Then see what remains. The remaining work may be more complex and more valuable, which changes the kind of person you should hire.

Or take a design studio. If revisions keep expanding because no one agreed on who approves the work, adding another designer can increase output and increase rework at the same time. A signed brief, a decision owner, and a defined review point may free more capacity than a new desk.

The test has a time limit. You cannot ask a tired team to live indefinitely with a "process improvement" that never comes. Give the fix a couple of weeks, check the queue again, and hire if the work is still there.

Look at the full cost, then look at the cash

A salary is only the visible line. Recruiting takes time. Training uses the attention of your strongest people. Tools, management, and the cost of a poor fit all belong in the decision. The role also becomes a fixed commitment that does not disappear when a strong month turns out to be seasonal.

If the business is still learning whether a channel or product works, ask whether the hire depends on that channel continuing to perform. If it does, a permanent role may be ahead of the evidence. If demand has been steady, the queue is real, and quality is suffering, waiting can be more expensive than hiring.

I would make both cases on the same page. What does it cost to hire now? What does it cost to leave the bottleneck in place for another quarter? A founder who only calculates the first number will underhire. A founder who only feels the second will overhire.

Write the first ninety days before the offer

The final test is to draft the person's first ninety days before posting the role. What decisions will they own? What will they stop doing that the founder currently does? What evidence will show that the bottleneck has moved? Who will train them, and what will that person stop doing during training?

If you cannot write that, you may need a clearer business decision before you need a candidate. Hiring is not the reward for growth. It is a way to remove a constraint you understand well enough to name.