Apple cluster control means running many iPhones from one computer: screens viewed together, tasks dispatched by group, results collected in one place.
This one answers: Which Jobs Should You Hand Over Before Hiring in Apple Cluster Control.
Someone running a small studio did the arithmetic and then did not hire.
He was managing around twenty accounts on his own and had been tired for a month. The plan was to bring in one person. Before doing it he wrote the numbers down: a hire costs a salary, contributions, and a desk for a year. That same money buys a batch of devices, a screen, and, more importantly, a lot of hours of his own time freed up by not doing repetitive work.
What he did instead was spend two weeks handing over the repetitive half. He ended up not hiring that quarter.
This does not mean never hire. It means that “I am too busy” and “I need a person” are two different statements, and the first one needs three questions asked of it before it turns into the second.
Question one: is the load judgement work or moving work
Write down what a day actually consists of, and mark each item as judgement or moving.
- Judgement: deciding what content to make, how to phrase a reply, which account to push, whether to drop a product. Hard to hand over, and where your value sits.
- Moving: switching accounts, filling in the same fields, copying data into a sheet, checking each device in turn. Easy to hand over, and all of it repeats.
Most people who feel overloaded are carrying a large share of moving work and not realising it. They remember the judgement calls because those are tiring, and forget the moving because it feels trivial.
If moving work is over half the day, the first move is handing that over, not hiring. Hiring a person to do moving work is buying the problem at full price.
Question two: how much of it is moving
Roughly quantify it. Not to the minute，half-hour granularity is enough.
A useful pattern from people who have done this: a day’s work often splits into about three hours of moving and two hours of judgement, with the rest being interruptions. Handing over the three hours does not make you free，it means you now have five hours of room for judgement, which is more than one person’s worth of thinking.
The line that matters is this: if after handing over the moving work you still cannot cope, you genuinely need a person. If you can cope, you needed automation, and you would have hired someone to do a job that should not have existed.
Question three: what would the hire actually own
If you do hire, write down their remit in one sentence. If the answer is “help me with everything”, you have an automation problem, not a staffing problem.
A hire makes sense when what they own is judgement work you cannot do more of:
- Content direction，what to make and how to differentiate
- Client relationships，the conversations that need a person
- Accounts and platform rules，knowing what is safe and what is not
A hire does not make sense when their remit is “run the tasks and check the devices”. That is moving work, and putting a salary behind it costs you every month.
What to hand over first, if you decide to automate
Ordered by what to do first:
- Read-only jobs：data collection, status checks, scheduled reminders. Zero risk, and they build the confidence you need for the rest.
- Copy-and-fill jobs：content distribution, fixed-field entry, schedule execution. Keep one human confirmation step before anything goes out.
- Standard replies：price, stock, shipping, lead time. Answer-fixed, low-cost if wrong.
What not to hand over: price negotiation, anything involving a promise, and any conversation where the tone has already turned.
The arithmetic, honestly
Two things are easy to get wrong in this comparison.
First, a hire is not just a salary. Add contributions, equipment, a desk and the ramp-up time. A new person is not productive in week one, and may not be for a month.
Second, automation is not free either. It costs setup time, and it costs ongoing checking. What it does not cost is a monthly salary for work that repeats.
The right comparison is therefore not “automation versus a hire”. It is “automation plus maybe a hire later” versus “a hire now, doing everything, including the parts that should not exist”.
If the answer is genuinely to hire
Sometimes it is. Three signals say so:
- Judgement work is already more than one person can carry, and handing over the moving work would not change that.
- Revenue is limited by your hours, not by task volume. Some businesses grow only as fast as the founder’s decisions.
- There is client-facing work nobody is doing, and it is being lost rather than delayed.
In those cases, hire，and hand over the moving work anyway. A new person should spend their first month on judgement work, not on retyping things that a machine could do.
Finally
Back to that studio owner.
He handed over the repetitive half in two weeks, which gave him about fifteen hours a week back. He said the interesting part was that he did not immediately use those hours for growth. He used them for a fortnight to catch up on sleep first, and then started on content.
The right question is not “should I hire”. It is “what exactly would this person do”. Answer that precisely and hiring versus automating decides itself.