Both managers say they cannot wait. The delivery lead needs another person to serve customers already sold. The sales lead needs another person to build the next pipeline. The company can fund one additional role now.

Don't ask which department matters more. Ask which blocked outcome is the current constraint, when the cash commitment begins and what happens if that role waits.

Department hiring request prioritization requires a shared decision basis. Without it, the founder is comparing two persuasive conversations rather than two operating choices.

Ask hiring managers to identify the blocked outcome

Urgency is not a common unit of measurement. One manager may mean overtime this week; another may mean a growth target at risk next quarter.

Give both sponsors the same short request:

  • Name the outcome the business cannot currently deliver.

  • Identify the work and crucial skills the role adds.

  • Explain the consequence of waiting, with supporting evidence. For delivery, name who is dealing with the affected customer launch dates.

  • State the proposed start and the first payment date.

  • Describe a smaller or reversible alternative.

Before approving the recruitment process, ask hiring managers to attach the blocked outcome to a job description. Name the job responsibilities and skills that make the new hire necessary now. Avoid job titles that describe an ideal person without explaining which work is waiting.

State the hiring priorities alongside organizational goals. A request for future growth and a request protecting current employees need comparable evidence. The hiring strategy for open roles should identify what can proceed, rather than simply create job openings. HR needs to know whether job postings and the interview process are approved for one position or both, and who makes the job offer decision. A hiring request that describes general improvement without a blocked outcome needs more work before it can displace another request.

The note applies Arron's funded-growth and CFO partnership themes. This shared-constraint rule and salary comparison are original editorial applications, not his quoted policy or a client case.

Hypothetical: one $90,000 role and one $110,000 role

Assume a hypothetical delivery role has a $90,000 annual salary and a sales role has a $110,000 annual salary. Both hiring managers request an immediate start.

For a simple salary-only comparison, monthly amounts are $90,000 ÷ 12 = $7,500 and $110,000 ÷ 12 = approximately $9,166.67. A two-month delay defers $15,000 and approximately $18,333.33 respectively.

Those figures exclude benefits, employer costs, recruitment, equipment, training and actual payroll dates. They are not the complete cost of either employee or a universal hiring benchmark. Deferring a salary is also not necessarily a saving if the company loses an important outcome while waiting.

Suppose, in this same hypothetical, signed customer work cannot launch until delivery capacity is added. The proposed sales hire would build opportunities that are not yet contracted. The founder should examine whether another sales role would add demand the company still cannot serve.

That evidence may favor delivery first. It does not make sales unimportant. Change the facts—for example, spare delivery capacity and too few qualified opportunities—and the priority may change.

If department requests keep outpacing the funded operating plan, use the Profit & Tax Leak Check to examine which constraint the next hire actually removes.

Department hiring request prioritization: the cost of waiting

A useful tie-break conversation asks both sponsors to discuss the same delay period. Sixty days is an illustrative review window, not a rule that every business should adopt.

What would customers experience? Which existing commitments could fail? What revenue depends on the role, and how certain is that revenue? Which employees would absorb the work? Can the team manage that temporary arrangement without silently sacrificing another priority?

Separate a plausible future benefit from an already-promised obligation. Neither should win automatically, but leadership needs to know which kind of evidence it is evaluating.

Finance checks cash timing; the CEO owns the tie-break. Put the top hiring priorities beside the earliest viable start for each role. HR should check candidate availability against labor market evidence, rather than describe the job market as generally difficult. Employee referrals provide candidate leads; they don't confirm the right person can start. Record who verifies talent availability and the handover needed. If a preferred start is unrealistic, bring a dated interim arrangement back to the approver before changing the department sequence. Hiring decisions need both operating priority and recruitment feasibility.

Bennett's next-hire affordability guide owns the wider financial test. This note addresses the different question of which department receives the first approval.

Set hiring priorities before the hiring process begins

Translate the choice into hiring goals: the core job, required skills and expectations for new employees. Tell both sponsors why one request receives first approval. HR and the recruiter need a clear instruction about the open positions, not two requests with one unspoken budget limit. The hiring efforts should follow that instruction rather than reward whichever manager began recruiting first.

The deferred team needs next steps too. State the review date, what evidence could reopen the decision and who owns that evidence. If sales is deferred until delivery capacity is ready, say who confirms readiness. If delivery is deferred until a customer commitment is verified, name the person who verifies it.

Acknowledge both sponsors' concerns without making departmental loyalty the tie-break. Otherwise, the workplace culture rewards persistence over evidence, and the actual constraint remains unchanged.

Stakeholders can disagree with the priority while still understanding the condition that changes it. A hiring team cannot prepare responsibly for a decision that remains a private thought in the founder's head.

Focus on the root causes of the two requests. What resources does the organization need to fill the delivery gap, and what demand exists for sales capacity? Rank that evidence before comparing recruiting efforts or managers' success stories.

Confirm the top priority before advancing the candidate pipeline. Choose recruitment strategies after the department decision, rather than letting the easiest-to-fill job determine the operating sequence. Candidates should receive reviewed commitments, including a start date that actually has approval.

Reopen the decision when the constraint changes

A current priority shouldn't become a permanent departmental ranking. Define success at the review date in the request. If the assumed constraint was wrong, change the sequence rather than defend the original approval.

Review decisive customer, capacity and start-date evidence. If the role no longer removes the constraint, explain the change before making another commitment. Keep the original reasoning for later feedback.

Don't assign invented numerical weights to the tie-break; ask sponsors to explain the evidence.

Arron's first-constraint note sets the leadership context. His resource-map article helps connect growth plans with the people they require.

Before the next competing request, ask both managers to bring the blocked outcome and consequence of delay. Bring the hiring sequence to the Profit & Tax Leak Check if the financial plan still cannot support the chosen start.

Frequently asked questions

Should the higher-revenue department get the first hire?

Not automatically. Compare the constraint each role removes and the consequence of waiting. Existing revenue and departmental status do not establish the next operating priority.

What should both hiring managers submit?

Use the same blocked outcome, required skills, delay consequence, cash start date and alternative. Comparable evidence makes the tie-break decision easier to explain.

Why compare the same delay period?

Use the same decision window so one sponsor's immediate problem can be compared with another's later opportunity.

Does the cheaper role deserve priority?

A lower salary is one factor, not the decision. The wrong hire can leave the constraint untouched despite a lower salary.

What does the salary hypothetical leave out?

Benefits, employer costs, recruiting, equipment, training and payment timing. The example compares salary exposure only and must not be treated as a complete hiring budget.

Who makes the final tie-break decision?

The named CEO or delegated approver uses finance's cash analysis and each sponsor's operating evidence.

What should the deferred department receive?

Give it the reason, review date and evidence that can reopen the request. Assign ownership rather than leaving the manager to guess what changes the answer.

When should the approved hiring sequence change?

Revisit it when decisive evidence, capacity or cash timing changes. Record why the new facts alter the priority before issuing another commitment.