When should a business hire its first admin person?

This decision arrives late in most businesses, and it arrives late for a specific reason: administrative work is visible, urgent and cheap-looking, while the work it displaces is neither urgent nor obviously priced. An owner doing the invoicing on a Sunday does not experience that as a cost, because no invoice arrives for it and nothing was formally given up.

The comparison that makes this decidable has two sides and both are commonly mis-stated. On the benefit side, what matters is not how many hours of admin exist but what the owner would do with those hours instead — and specifically what those hours would produce. For an owner whose time converts directly into revenue, that number is large and knowable. For one who would use recovered hours for rest or for work that does not generate revenue directly, the case is different and may still be right, but it is a different argument and should be made honestly rather than dressed up as an economic one.

On the cost side, the wage is not the cost. Statutory employer contributions apply before any benefit, equipment or software, and they behave differently across earnings — one component stops at a wage base, another has no ceiling, and the unemployment components sit on low bases at rates specific to the employer's own history. A comparison run against the wage will understate the commitment by a margin large enough to change the answer at the boundary, which is precisely where these decisions sit.

There is a sequencing question that usually goes unasked and frequently improves the outcome. Much of what the first admin hire would do can be removed rather than transferred: invoicing that issues automatically, enquiries that acknowledge themselves, scheduling that does not require a phone call, reminders that fire without anyone remembering. Doing that first shrinks the role and often changes what kind of person is needed — from someone processing paperwork to someone handling customers, which is a considerably more valuable hire.

The role definition is where these hires most often disappoint, and the failure is predictable. Hired to do everything nobody else wants, the person spends their time on a rotating set of tasks, none of which is owned, and the owner concludes that the hire did not help. Naming two or three things the person owns completely — the enquiry queue, the schedule, the invoicing — produces a measurable difference. Everything else being incidental is fine; everything being incidental is not.

One practical marker worth watching, because it precedes the financial case and is easier to see: when administrative load starts producing customer-facing failures. Enquiries answered late, appointments confirmed inconsistently, invoices sent weeks after work, follow-ups not happening. At that point the cost of not hiring has moved from the owner's evenings to the customer's experience, and it is compounding rather than merely tiring.