The Hiring Equation: Core Work

Why this matters

Most hiring in service businesses is reactive. Someone quits, a project overflows, a founder feels the pressure, and a job ad goes up the same week. The role is half-defined. The interview is a gut-feel conversation. Two months later the person is either gone or parked in a seat doing work that does not match what the business actually needs.

In the UAE, a bad hire carries a financial cost on top of the cultural one. Visa processing runs AED 7,000-15,000 (USD 1,910 to USD 4,090). You pay salary through a 6-month probation period where productivity is often close to zero. If the person leaves after 14 months, you owe end-of-service gratuity. Add recruitment agency fees, management time spent re-hiring, and the invisible cost of a team losing faith in your ability to pick the right people. A single failed hire at the mid-level can cost AED 80,000-120,000 (USD 21,800 to USD 32,700) when you add it all up.

The hiring equation is simple: hire only when you have proven a system cannot solve the problem, and hire into a role that is already designed before the offer letter goes out. This chapter maps directly to the Skills and Behaviour audits in the ARCAS diagnosis engine, and to people leakage in the Five Levels model.

A founder you might recognise

Last year, the founder of a 26 person commercial pest control firm in Dubai hired four people. Two of them did not survive probation. One is still employed but mostly idle because the role she created for him turned out to overlap with work her operations lead was already doing. The fourth is strong, but she admits she got lucky.

Her pattern was consistent each time: she felt overwhelmed, opened a WhatsApp group with two recruiters, and said "I need someone for operations." The job descriptions were vague. Interviews were unstructured. She hired the person who seemed the most confident in the meeting.

When she ran her ARCAS diagnosis, the Skills audit flagged a capability gap in the delivery team, but the Behaviour audit revealed something else: the real problem was process. The existing team did not have documented processes for the work she was trying to hire people into. She was hiring people to figure things out instead of hiring them to run things that already worked.

The stage-fit hiring model

Not every stage of growth needs the same kind of hire. The mistake founders make is hiring for the company they want to be instead of the company they are right now.

At 10 people, you need do-ers. People who can carry a full workload with light supervision. Generalists who are comfortable with ambiguity. Do not hire managers at this stage. You do not have enough people to manage, and you will end up paying a management salary for someone doing individual contributor work.

At 20 people, you need your first team leads. These are senior do-ers who take ownership of a workflow and the two or three people in it, without the full-time manager title. Give them a clear scope: the technician lead owns all preventive maintenance scheduling, including the two technicians who execute it. That is a team lead role with an operating remit.

At 30 people, you need a real operations layer. Someone who owns the gap between you and the delivery team. This is where most founders hire too early (at 15 people) or too late (at 45 people). The signal that you need this hire: you are spending more than 40% of your time on internal coordination instead of clients or growth.

At 50 people, you need specialised functions. HR, finance, business development as distinct roles. Before 50, these are responsibilities distributed across the team. After 50, each one generates enough volume to justify a dedicated person.

The competency framework for service businesses

Service businesses have four competency layers. Every role you hire for should be mapped to one or more of these before you write the job description.

Technical skill. Can the person do the core task? For a project coordinator, this means: can they build a schedule, track milestones, and flag delays before they become problems?

Client handling. Service businesses live and die on client relationships. Even back-office roles touch the client indirectly. Define what "client-aware" means for each role.

Process discipline. Will this person follow the system you have built, update the tracker in Zoho, fill in the handover sheet, close the loop? This is the competency most founders forget to test for.

Ownership instinct. When something falls between two roles, does this person pick it up or wait for instructions? In small teams, this is the difference between someone who adds capacity and someone who adds management load.

Write these four layers into every job description. Test for them in every interview. Weight them according to the role: a field technician needs 60% technical, 20% process discipline, 15% client handling, 5% ownership. An account manager flips those numbers.

When to hire vs. when to fix the system

Before you post a job ad, run this test. Open a blank page in Google Docs and answer three questions:

1. What work is not getting done?
2. Is it not getting done because no one has time, or because no one has a clear process?
3. If you gave your current team an extra five hours per week each, would this problem disappear?

If the answer to question 3 is yes, you do not have a hiring problem. You have a systems problem. Fix the process, automate the admin, or redistribute the workload. Hiring a new person into a broken system just means one more person doing things the wrong way.

Another founder ran a 34 person commercial security services firm in Sharjah. She was convinced she needed two more supervisors. When she mapped the actual time her existing supervisors spent each week, she found 11 hours per person going to manual scheduling in Excel that could be handled with a shared Google Calendar and a simple checklist. After fixing that, her current supervisors had capacity for the additional sites. The two hires she was about to make at AED 12,000 (USD 3,270) per month each became unnecessary.

The Emiratisation angle

If you operate in the UAE with 50 or more employees, Emiratisation quotas are not optional. But beyond compliance, there is a practical question: how do you design roles that work for Emirati hires?

Three things matter. First, structured onboarding. Do not throw a new Emirati hire into a role with no documentation and expect them to "figure it out." That approach fails for any new hire, but it fails faster when the person is new to the private sector. Build a 90-day onboarding plan with weekly milestones.

Second, clear KPIs from day one. Ambiguity kills retention. An Emirati hire who does not know what success looks like in their role will disengage within three months. Define two or three measurable outcomes for the first quarter and review them every two weeks.

Third, a visible progression path. If the role is a dead end, you will not retain the person. Map where this role leads in 12 and 24 months. This does not mean promising a promotion. It means showing them what skills they will build and what doors those skills open.

The businesses that struggle with Emiratisation are almost always the ones with unclear roles across the team. Fix the system, and the quota becomes easier to meet.

Common mistakes

1. Hiring for attitude and hoping skills will follow. Attitude matters, but service businesses need people who can do the work in the first month, well before month six. Test for the technical competency first. Cultural fit is the tiebreaker.
2. Skipping the probation review. UAE labour law gives you six months of probation. Use it. Set a 90-day checkpoint with clear criteria. If the person is not meeting them, have the conversation early instead of waiting until month five.
3. Duplicating roles under different titles. If you already have an operations coordinator, do not hire a "project administrator" who does the same work. Check your role cards from the previous chapter before creating a new position.
4. Hiring friends or referrals without the same process. Referrals are fine as a source. They do not justify skipping the competency test. The friend of your best employee might be your worst hire.

When to move on

Move to the next chapter when you have mapped your current team against the stage-fit model, written competency requirements for your next two hires, and answered the "hire vs. fix the system" test for at least one open need. If you discovered you do not need to hire yet, that is a valid outcome. The goal is to build the right team at the right time.

Working prompts

People. Who on your current team is in a role that fits their actual competency? Who is in a role that was designed around availability instead of skill? Where are you carrying someone who passed probation but never reached full productivity?

System. Do you have a written hiring process, or does each hire follow a different path depending on urgency? Is there a standard interview structure, or does each hiring manager run it differently? Do you have a probation review template?

AI. Once your hiring process is documented, where could you use tools to reduce admin? CV screening against your competency framework. Automated scheduling of interviews. Probation milestone reminders in Google Workspace. These are worth considering only after the human process is clear.

Founder exercise

Part A - Stage-fit audit (20 minutes). List every person on your team. Next to each name, write whether they were hired as a do-er, team lead, manager, or specialist. Now compare that to what they actually do today. Mark anyone whose current work does not match the role they were hired into. These mismatches are your biggest source of people leakage.

Part B - Next-hire competency card (30 minutes). Pick the most urgent open need in your business. Before writing a job description, fill in this card:

• Role title
• Stage-fit category (do-er / team lead / manager / specialist)
• Technical skill required (be specific)
• Client handling expectation
• Process discipline requirement
• Ownership level expected
• 90-day success criteria (two or three measurable outcomes)
• What system must exist before this person starts

If you cannot fill in the last line, you are not ready to hire.

Part C - Hire vs. fix decision (15 minutes). For each open need you identified, answer the three questions from the "When to hire vs. when to fix the system" section. Track your answers in a simple table in Excel or Google Sheets. Share it with your operations lead or co-founder before taking action.

ARCAS lens

The hiring equation connects your people system to your cost structure. Every misfit hire appears twice in the diagnosis: once in the Skills audit as a capability gap, and again in the revenue model as margin leakage. The Five Levels model treats people leakage as the most expensive and slowest to fix. Getting hiring right is about stopping the cycle of hiring to patch problems that better systems would prevent, not about building a perfect team.

Start now: Quick self-assessment

Rate your business 1-5 on each row (1 = not in place, 5 = working well).

25-30: Your hiring equation is solid. Focus on refining competency tests and onboarding. 16-24: The structure is forming but gaps remain. Prioritise the probation review process and the hire-vs-fix test. 6-15: Hiring is reactive and costly. Start with Part B of the founder exercise and build one competency card before your next hire.